It’s just data

Pingback server

Simon Fell: OK, the archive pages are now pingback enabled

I knew you could do it. ;-)

On the question of PB vs TB, I see the primary advantage of PB over referrer logs is that PB provides access to the fragment id. I see the primary advantage of TB over PB is that TB adds access to the excerpt. In terms of implementation, PB requires more logic on the server (how'd you get those titles?), and TB requires more logic on the client (scanning for trackback:ping).

I agree about the client side - TB definitely requires more logic. However, on the server, it's pretty much the same, at least in my implementation. I retrieve the pinging/tracking document and verify it, in both cases, which is most of the work.

Posted by Greg Reinacker at

Pingback from as days pass by: Pingbacks and trackbacks and implementation

at

Pingback from as days pass by: Pingbacks and trackbacks and implementation

at

Pingback from Jon Schull's Weblog

at

Looking at the trackback spec, what's the point of the retreiving trackback pings section ? is it a requirement to implement that part of the spec ?

Posted by Simon Fell at

Looks the comment preview option has a buglet in that the remember info checkbox setting gets lost.

Posted by Simon Fell at

I haven't implemented the API to retrieve a trackback ping, and haven't heard a complaint yet. ;-)

I've tried preview from the comments page, and preview from the preview page, both with remember info turned on and with it turned off, and with both Mozilla and IE and each time it appears to do the right thing for me. Can you give me a more detailed scenario?

Posted by Sam Ruby at

I enter a comment, remember info is checked, hit preview, the preview appears, the name, email, url and comment fields are all re-populated, but the remember info check box is now unchecked.

This is with Safari though, jsut tested with IE5.2, and that was fine, so looks like its a Safari bug.

Posted by Simon Fell at

Somewhere I read that Safari's picky about the path in cookies.

What retrieving pings buys you is the threading that TrackBack was supposed to be about: both mt-thread and Ben's More Like This From Others use the RSS feed of pings. And Sam? Though it wasn't quite clear at the time, I'm pretty sure you actually did get a complaint about not implementing the API to retrieve.

Posted by Phil Ringnalda at

I guess it wasn't clear enough to me. ;-)

Posted by Sam Ruby at

I don't implement the retrieve API either...and thus far haven't had any problems or complaints...

Posted by Greg Reinacker at

I'll be sure to complain as soon as I'm part of a thread that passes though you, then. Meantime, I'll complain about Sam:

Luckily, Ask pinged me as well as you, so he shows up in the first and only level of this thread, since you're a dead end. Not that the original is a very good example of the benefits of threading, since for some reason either people don't thread much or they don't around me, but this one, which involves some intentional threading, is a bit better.

Posted by Phil Ringnalda at

Pingback from Sam Ruby: Another dead end?

at

Pingback test test Pingback test?   Pingback server....?11:19:24 AM      [Jon Schull's Weblog]...

Excerpt from Jon Schull's Weblog at

Pingback from Tim Knip's Groovey Weblog

at

Pingback test?   Pingback server....?11:19:24 AM      ...

Excerpt from Jon Schull's Weblog at

Trackback, pingback, linkback, etc.

As I've been working on Roller's further-reading feature for the 0.9.7 release, which is essentially the same as Mark Pilgim's automatic backlinks and further reading imp...

Excerpt from Blogging Roller at

Add your comment