explaining trackback to journalists

Grok Headline matches for explaining trackback to journalists

‘Sending TrackBack pings
indiscriminately makes you a TrackBack
spammer’

‘Sending TrackBack pings
indiscriminately makes you a TrackBack
spammer’ 12/29/2003 08:30 AM

blog.codefront.net/archives/2003/12/29/sending_trackback_pings_indi scriminately_makes_you_a_trackback_spammer.php
track this site | 4 links

A Lot Of Explaining To Do...

A Lot Of Explaining To Do... 12/22/2004 01:13 AM

Dave Winer: At some point Microsoft is going to re-staff the IE team in response to Firefox. When they do it, how will they explain the seven years during which they invested nothing in the user experience of the browser?

Explaining my absence

Explaining my absence 12/30/2003 01:23 AM
Welcome loyal readers, as many of you have noticed and emailed about, I have been out of the normal routine for the past week and a half. I have been taking time off, due to an illness that currently has...

explaining margin of error

explaining margin of error 08/19/2004 07:18 PM
and debunking the myth of a "statistical tie"

Analysis: Microsoft, SCO have a lot more
explaining to do

Analysis: Microsoft, SCO have a lot more
explaining to do 03/08/2004 11:28 PM
Whether or not Microsoft is secretly bankrolling the SCO Group for more than $100 million to attack Linux and the general open source community through questionable intellectual property lawsuits, NewsForge has learned that U.S. federal regulators may have begun investigating the relationship between the two companies -- and may also be looking closely at a number of other people and companies connected to them through stock or other business transactions.

Explaining the 24-bit Base Registers

Explaining the 24-bit Base Registers 04/12/2004 11:13 PM
[Herewith an appearance by a guest author, name of John Fowler; explanation in the coda at the end].

I attended the IBM 360 40yr Anniversary at the Computer History Museum in Mountainview, California. I'm on their mailing list and went there for the sole purpose of finding out: what the heck were they thinking with the use of 24 bit addressing in base registers that were 32 bits wide?...

Explaining DDR Memory Bandwidth

Explaining DDR Memory Bandwidth 07/20/2004 07:57 AM

I think Sandy Berger has some explaining
to do

I think Sandy Berger has some explaining
to do 07/20/2004 03:14 AM
Ooops again. Sandy Berger

apnews.myway.com/article/20040720/D83U6TIO0.html
track this site | 4 links

Announcing (and explaining) our new 2.0
licenses

Announcing (and explaining) our new 2.0
licenses 05/25/2004 06:04 PM

Last night, after many months of gathering and processing great feedback from all of you, we turned on version 2.0 of the main Creative Commons licenses. The 2.0 licenses are very similar to the 1.0 licenses -- in aim, in structure, and, by and large, in the text itself. We've included, however, a few key improvements, thanks to your input. A quick list of new features follows. All section numbers refer to the Attr ibution-Noncommercial-ShareAlike 2.0 license. (Corresponding section numbers may vary across licenses.)

Attribution comes standard

Our web stats indicate that 97-98% of you choose Attribution, so we decided to drop Attribution as a choice from our license menu -- it's now standard. This reduces the number of licenses from eleven possible to six and makes the license selection user interface that much simpler. Important to remember: Attribution can always be disavowed upon licensor request, and pseudonymous and anonymous authorship are always options for a licensor, as before. If we see a huge uprising against the attribution-as-stock-feature, we'll certainly consider bringing it back as an option.

Link-back attribution clarified

Version 1.0 licenses did not carry any requirements to add hyperlinks as attribution. Under the 2.0 licenses, a licensor may require that licensees, to fulfill their attribution requirement, provide a link back to the licensor's work. Three conditions must be satisfied, though, before a licensee faces the linkback requirement: (1) linking back must be "reasonably practicable" -- you can't string me up for failing to link to a dead page, for example; (2) the licensor must specify a URL -- if you don't provide one specifically, i have no linkback obligation; (3) the link licensor provides must point to the copyright and licensing notice of the CC'd work -- in other words, licensors who abuse the linkback as an engine for traffic to unrelated sites don't enjoy linkback rights.

Synch rights clarified

The new licenses clarify when licensees may or may not synchronize musical CC'd works in timed-relation with a moving image. Basically, if a license allows derivatives, it allows the synching of music to video. If no derivs, no synching allowed. (See Sect ion 1b.)

Other music-specific rights clarified

The default rules for music-related copyrights can be particularly complicated, and the 2.0 licenses go to greater length to clarify how various CC license options affect music rights. In a nutshell: If you pick the "noncommercial" provision, you retain the right to collect royalties from BMI, ASCAP, or the equivalent for performance royalties; from Harry Fox or the equivalent for mechanicals; and from SoundExchange or the equivalent from webcasting compulsories. If you allow commercial re-use, you waive the exclusive rights to collect these various revenue streams. This is not a departure from the policy embodied in the 1.0 licenses -- these same results would be extrapolated by any reasonable interpretation. But 2.0 just makes it all clearer, and using the language of the profession. (See Sect ions 4e and 4f.) Note: This music-specific language marks the first time we've referred to any specific statutes in the generic CC licenses. This means that future iCommons licenses will have to do the same somewhat complicated mapping exercise for each respective jurisdiction.

Warranties? Up to licensors

Unlike the 1.0 licenses, the 2.0 licenses include language that makes clear that licensors' disclaim warranties of title, merchantibility, fitness, etc. As readers of this blog know by now, the decision to drop warranties as a standard feature of the licenses was a source of much organizational soul-searching and analytical thinking for us. Ultimately we were swayed by a two key factors: (1) Our peers, most notably, Karl Lenz, Dan Bricklin, and MIT. (2) The realization that licensors could sell warranties to risk-averse, high-exposure licensees interested in the due diligence paper trial, thereby creating nice CC business model. (See the Prelinger Archive for a great example of this free/fee, as-is/warranty approach.) You can find extensive discussion of this issue in previous posts on this blog. (See Sect ion 5.)

Share Alike Across Borders

Version 2.0 licenses that feature the Share Alike requirement now clarify that derivatives may be re-published under one of three types of licenses: (1) the exact same license as the original work; (2) a later version of the same license as the original work; (3) an iCommons license that contains the same license elements as the original work (e.g. BY-SA-NC, as defined in Sect ion 1 of each license). The version 1.0 licenses required that derivative be published under the exact same license only. Our tweak means much better compatibility across future jurisdiction-specific licenses and going forward across versions. Less forking, more fun. (See Sect ion 4b.)

Otherwise, Share Alike Means Share Alike

After much very strong and eloquent argument from our readers and supporters, and notwithstanding the increased flexibility of Share Alike in the iCommons context, we decided not to make the BY-NC-SA and plain BY-SA licenses compatible. If you take a work under BY-NC-SA 2.0 and make something new from it, for example, you can re-publish under BY-NC-SA Japan, or BY-NC-SA 7.4 (when that comes), but you cannot republish it under any other license or combine it with BY-SA content. Similarly, a derivative made from a work under BY-SA 2.0 may be published only under BY-SA 2.0, BY-SA (iCommons license), or BY-SA 9.1, but it can't be mixed with BY-NC-SA or other noncommercial content and republished.

Nifty new Some Rights Reserved button

Check out the button at the bottom of this page. Wouldn't that look good on your site? Time for an upgrade, cosmetic as well as legal?

Explaining the URL-Based Mac OS X
Vulnerability (24-May-2004; 7.5K)

Explaining the URL-Based Mac OS X
Vulnerability (24-May-2004; 7.5K) 05/24/2004 09:58 PM

Explaining Open Source Software

Explaining Open Source Software 01/04/2004 02:20 PM
scubacuda writes "Mark Webbink, Red Hat's general counsel, has written an informative article explaining free and open source software. Geared towards ...

Explaining the Mars Photo Colorization

Explaining the Mars Photo Colorization 01/19/2004 09:34 AM

Announcing (and Explaining) Creative
Commons 2.0

Announcing (and Explaining) Creative
Commons 2.0 05/26/2004 07:38 PM
?Last night, after many months of gathering and processing great feedback from all of you, we turned on version 2.0 of the main Creative Commons licenses. The 2.0 licenses are very similar to the 1.0 licenses ? in aim, in structure, and, by and large, in the text itself. We?ve included, however, a few key improvements, thanks to your input. A quick list of new features follows.?

Explaining the importance of context in
ID mgmt.

Explaining the importance of context in
ID mgmt. 06/17/2005 04:49 PM
Last week, I asked if an identity needed to be unique, and answered that yes, it does, within a given context. That seems like an excellent segue to a discussion of context and how it relates to identity.

explaining the selection of The Brent
Woodall Foundation

explaining the selection of The Brent
Woodall Foundation 09/14/2004 07:17 AM
Go here to learn about Tracy and strengthen the good .. This month's charity

strengthenthegood.com/archives/2004/09/strengthen_the.htmltrack this site | 5 links

Announcing (and explaining) our new 2.0
licenses | Creative Commons

Announcing (and explaining) our new 2.0
licenses | Creative Commons 05/26/2004 07:25 AM
Creative Commons 2.0 licenses released .. the new versions

creativecommons.org/weblog/entry/4216
track this site | 5 links

Explaining The Windows/UNIX Cultural
Divide

Explaining The Windows/UNIX Cultural
Divide 12/16/2003 07:47 AM

TCS: Tech Central Station - Explaining
Liberal Anger

TCS: Tech Central Station - Explaining
Liberal Anger 04/28/2004 04:36 AM
Keith Burgess-Jackson: A Former Liberal Explains Liberal Anger

techcentralstation.com/042704I.html
track this site | 5 links

"Trackback [30]"

"Trackback [30]" 06/18/2004 04:59 AM

"Trackback [0]"

"Trackback [0]" 06/18/2004 04:59 AM

"0 Trackback(s)"

"0 Trackback(s)" 01/03/2004 07:07 PM

"TrackBack (0)"

"TrackBack (0)" 01/03/2004 07:07 PM

Net-Trackback-1.01

Net-Trackback-1.01 12/24/2004 12:10 PM

TrackBack (0)

TrackBack (0) 08/15/2004 02:34 AM

demsformars.com/blog1/mt-tb.cgi?__mode=view&entry_id=351
track this site | 2 links

Trackback [0]

Trackback [0] 06/18/2004 03:18 AM

old.weblogs.com/newsItems/trackback/?u=old&p=210&link=http%3A%2F%2F old.weblogs.com%2F2004%2F06%2F17%23a210
track this site | 38 links

"TrackBack (2)"

"TrackBack (2)" 06/11/2004 12:52 PM

Net-Trackback-0.992

Net-Trackback-0.992 04/22/2004 05:37 PM

"TrackBack (0)"

"TrackBack (0)" 12/30/2003 02:48 AM

Trackback

Trackback 12/03/2002 11:46 AM

Will someone test my trackback for me? I don't believe that it works. Or perhaps no one has ever used it. Please :-) Can you leave me a comment that you did as well? Thanks!

Net-TrackBack-0.21

Net-TrackBack-0.21 03/19/2003 10:24 PM

Trackback authentication

Trackback authentication 03/06/2004 02:09 AM

Jacques Distler: The anonymous nature of the internet makes the problem of “identity” a hard one. In physics, when we encounter an intractably-hard problem, our most frequent dodge is to redefine the problem to one which admits a solution, and hope that the result is a “good-enough” stand-in for the original problem. In that spirit, I (re)defined the problem as reliably associating comments posted with the websites of the commenters.

Just a suggestion: a lesser, but very much related and much more tractable, problem is trackbacks.  The reason why it is more tractable is that the trackbacks are issued by software which could reasonably be expected to have direct access to your weblog's private keys.  This could make signing totally automatic - simply check a box once, and your template could be updated and all future trackbacks would be automatically signed.

The signatures could be passed as a new CGI parameter or as a HTTP header.  Neither would likely affect any existing software that wasn't expecting this information.

Once trackback signing is widely enough adopted, people may feel comfortable turning off the ability to accept unsigned trackbacks.  And then much of the infrastructure will be in place to tackle the harder, and more important problem, of comment signing.

The key nut to crack there is to make it easy and painless to sign a comment.

Trackback Server in PHP?

Trackback Server in PHP? 03/08/2004 11:22 PM
Does anyone know of a trackback server (not client!) written in PHP? I want to add trackbacks to the IT Conversations site and would rather not spend a week writing it myself.

Trackback Wha'?

Trackback Wha'? 03/19/2003 10:24 PM
It's good to be joined in befuddlement by none other than the Docster. He, too, can't figure out Trackback. I've got the general idea. I just can't figure out how to get it working in Movable Type. Maybe someone should write a "Trackback for Dummies" and post it. And, please, only use small words. Thank you....

Trackback from iTunes

Trackback from iTunes 03/13/2003 06:17 PM

Today I looked at my list of contacts in AIM and knew Jerry Kindall was the l33t applescript developer of the bunch. I showed him my previous post, went off to grab a burrito for lunch only to find a working script in my inbox upon return. I just tried it out and it's working as I speak, with output identical to the winamp pings. The full instructions and applescript are included:

Trackback in, valid out (mostly)

Trackback in, valid out (mostly) 06/28/2004 09:41 PM
Jacques Distler: You gonna turn off Trackbacks (which don't declare a charset, and could be sent in any charset imaginable, but very frequently are Windows-1252)? Unless you have a way to guess the charset and re-encode the result to UTF-8, they will invalidate your pages as quick as you can sneeze. It turns out that by design it is rather hard for a string of bytes to accidentally be valid utf-8, unless that string is pure US-ASCII, in which case it doesn't much matter which encoding you presume. ...

Kwiki-Trackback-0.01

Kwiki-Trackback-0.01 04/05/2005 04:06 AM

TrackBack Category

TrackBack Category 03/13/2003 10:15 AM
Depending on how granular your MT categories are and how often you may find yourself talking about TrackBack, you may...

Six Apart getting hit by Trackback Spam
Also

Six Apart getting hit by Trackback Spam
Also 07/05/2004 09:10 AM

Ohhh feel the love. now they get to feel the same pain a bunch of us have felt all weekend. Maybe someone now will figure out how to fix this. You know Yahoo, Google, Hotmail solved a lot of problems by making users verify they where a human by entering text that is in a obscured box. This will not fix the trackback issue but could be a option. [Six Apart]

Example of TrackBack threading

Example of TrackBack threading 03/13/2003 10:15 AM
Here's the static output representing the TrackBack threading of this initial post as of 3:00 am PST. This was generated...
Grok Description matches for explaining trackback to journalists
GrokA matches for explaining trackback to journalists

explaining trackback to journalists