Why the Ping Loop Did Not Crash WordPress

SIERRA MADRE, CA - MAY 29:  Seventieth anniver...Some days ago I did the Ping Loop Test and I luckily had only 4 duplicate posts to clean up. Now the question is, why did the loop stop. To answer this i didn´t have to go into analyzing logfiles and plugin behavior.

Ping.FM has rate limits of 3 messages per rolling minute to prevent spam. This absolutly makes sense for a message distribution service like them. And it does not just prevent spam but it also prevents fast loops that could crash a service.

Read the rest of this entry »

Finished Setting up Ping.FM Accounts

Here is a little status update:

I finished setting up accounts with all services that are supported by Ping.FM. I also played around a little bit with all those services what they have to offer API-wise. I noticed, that many web interfaces on those services are quite a pain to use. Some of them are outright confusing and its hard to find what you are looking for.  I did not see much of that highly praised User Experience Design out there in the Web 2.0.1 world.

I like to mention Tumblr here, as it stands out with his refreshingly clean userinterface. Its a joy to use and a strong recommendation, if you are looking for an easy, simple and elegant blogging service with a twitter-like follow function.

Read the rest of this entry »

Crash Your WordPress with a Ping Loop

Image representing WordPress as depicted in Cr...Ok this is a first bigger API Loop or Chain Reaction Experiment and I hope this blog will recover from it. Actually I am not sure what will happen. What I am doing is sending out this post with the help of the WordPress plugin PingPressFM and getting it back with another PingFM Plugin. I am a little bit exited and afraid to push the Publish button. I hope to recover soon from this experiment. Lets see what happens…

Update: Nothing big happened. I had to clean-up only 4 duplicate posts…

Read the rest of this entry »

Setting Up API Service Interactions

API-Madness has nearly finished setting up accounts with the major web 2.0 services. It is a nice exercise to set-up all those accounts. It teaches a lot about best practices.

The next step will be to check out each service in detail and see what API based interconnections it offers to other services. This will be quite some work. I hope it will not take more than a month to go through all the services and check out their API Features.

The current account list is:

Bebo, Blogger, Delicious, Digg, Facebook, FriendFeed, Gravatar, Hi5, identi.ca, kwippy, LinkedIn, LiveJournal, ma.gnolia.com, Mashable, MyBlogLog, MySpace, OpenCalais, MyVidoop, ping.fm, Plurk, Pownce, Rejaw, Technorati, Tumblr, Twitter, WordPress.com, Xanga

Reblog this post [with Zemanta]