On Blog Pinging (again)
Published January 30th, 2006
When a major ping service has problems, I will remind you that Blog Pings are stupid. Some companies rely upon blog pings for their crawling system. What happens when a ping service is down? Your posts don’t get indexed. Oh Snap.
People have noticed that if you want to get higher rankings in some search engines, you should find everyone who has linked to you, and send Pings for them. Ping-spoofing. It really feels like email-spoofing to me. Maybe SPF could be extended to prevent this…
Anyways, At $work we do not currently accept pings from anyone. Instead we crawl every site in our system, every 30 minutes. Its not that hard, honestly, thanks to memcached and conditional http requests. (Oh, and lots of bandwidth).
Blog Pings have fundamental problems. Until they are both reliable and secure, I hope they will die. (By secure I mean knowing that the person who sent the ping is the person who owns the feed…). FeedTree tries to go down this path. It has many problems, the foremost is using Java. If you want everyone in the world to support your protocol, you need support for everyone still using c, perl, python, php, and ruby. The other problem with FeedTree, is that it makes crypto signing of pings optional. Rule number one of making a spec: Nothing is optional, because anything that is, won’t be implemented by half the software out there.
Have a happy Monday.
Written by Paul Querna, CTO @ ScaleFT. @pquerna