Comments for monkinetic weblog

Comment on Distributed Social Networkers by Why I’m going to Vidoop

Why I’m going to Vidoop — Thu, 15 May 2008 07:52:55 +0000

[...] it’s not exactly news at this point, but it is indeed true that as of today I am now employed by Vidoop. This has been a few [...]

Comment on Distributed Social Networkers by Steve Ivy

Steve Ivy — Wed, 14 May 2008 21:32:14 +0000

Thanks Sean!

Comment on Distributed Social Networkers by SeanMcTex

SeanMcTex — Wed, 14 May 2008 20:25:16 +0000

Congrats, DiSo folks! Gratifying to see folks investing resources here!

Comment on Distributed Social Networkers by Chris and Will join Vidoop : DiSo Project

Chris and Will join Vidoop : DiSo Project — Wed, 14 May 2008 17:05:11 +0000

[...] Steve Ivy’s Blog [...]

Comment on Twitter down, and I didn’t know about it by kael

kael — Tue, 29 Apr 2008 23:03:24 +0000

Yet another addendum : a web-based PEP aggregator has been released.

This really looks like a personal Twitter page, though. It looks similar to the DiSo actionstream aggregator.

Comment on Twitter down, and I didn’t know about it by kael

kael — Sun, 27 Apr 2008 21:28:06 +0000

Addendum : here are some informations regarding the Twitter Jabber PubSub feeds.

A bot subscribed to xmpp:twitter@twitter.com and receiving the ATOM feeds could re-published them on the personal PEP node of a user for example.

Comment on OpenID login broken? by kael

kael — Fri, 25 Apr 2008 19:25:15 +0000

Done.

Btw, I've changed my JID hence my OpenID, and I forgot to mention it.

Comment on Twitter down, and I didn’t know about it by kael

kael — Fri, 25 Apr 2008 19:20:54 +0000

A WordPress PubSub plugin was recently released and it actually allows to turn every blog into a decentralized Twitter system, but we still need PubSub clients (although there's a Gajim SVN version with a very light support and Synapse-IM, a fork of Psi with a more advanced PubSub support).

Regarding Twitter PubSub nodes, instead of using PubSub nodes stored on their server, it would be possible to allow the Twitter bot to publish on our own PubSub node thanks to the affiliation mode by configuring a PubSub node with those two paramters ('<' and '>' changed into '*' for formating) :

field var='pubsub#publish_model' value publishers /value /field field var='pubsub#publisher' value twitter@twitter.com /value /field

But this would require that Twitter allows this kind of publication and I'm not sure they would want to. It would simply require to enter the name of the node in a Twitter interface.

Comment on OpenID login broken? by Steve Ivy

Steve Ivy — Fri, 25 Apr 2008 14:23:51 +0000

Hi Kael,

Good news. Can you re-post your last comment (the one in the email)? I thought it was good material to have on the site here.

Comment on OpenID login broken? by kael

kael — Fri, 25 Apr 2008 14:14:36 +0000

It’s fixed.

Comment on Twitter down, and I didn’t know about it by Steve Ivy

Steve Ivy — Wed, 23 Apr 2008 15:34:14 +0000

Yes, but to do this right means supporting PubSub - so that a federated xmpp account can subscribe to a published node on Twitter. In this case, I think that Twitter would have to be publishing a node for each user’s update stream in addition to the full stream now available.

Comment on Twitter down, and I didn’t know about it by Stephen Paul Weber

Stephen Paul Weber — Tue, 22 Apr 2008 18:06:59 +0000

There’s nothing holding this back from Twitter’s side. They’re making their full stream available over XMPP to pretty much anyone who asks (it’s OOB pubsub, but w/e) - they make no guarantees about the service, but it works as of now. Just need other services who want to consume.

Someone from DiSo is working on a XMPP-to-WP posting bot too, that simulates Twitter but posts to a Wordpress blog.

Comment on Google Contacts API debuts - how useful for distributed sites? by Stephen Paul Weber

Stephen Paul Weber — Sat, 08 Mar 2008 17:09:09 +0000

You read it like I do. Still, with the only useful data in most people’s GMail address books being email addresses, we’d need some kind of mapping service to get truly useful information (ie, URLs) out. Still, better than the antipattern

Comment on Google Contacts API debuts - how useful for distributed sites? by Steve Ivy

Steve Ivy — Thu, 06 Mar 2008 19:02:38 +0000

Here's a rough outline from Google's instructions:

Add your domain.
Verify your domain.
- Uploading a file:
- Adding a meta tag:
Provide domain information.
- Target URL path prefix
- Domain description:

Comment on Google Contacts API debuts - how useful for distributed sites? by James D Kirk

James D Kirk — Thu, 06 Mar 2008 18:51:00 +0000

Wouldn’t that potential roadblock depend upon the level of effort of registering ones site with Google?
Let’s do a “Pros and Cons” listing here, on what that might be like.