http://snarfed.org/2012-02-22_portablecontacts_for_facebook_and_twitter
http://snarfed.org/2012-01-16_webfinger_for_facebook_and_twitter
does anyone have any advice, existing code, or anything else i should
look at before i begin? i've seen discussions about schema mapping for
both of those services, and i'll follow them, but right now i'm more
interested in higher level thoughts. twitter's user streaming api is
alive, but never shipped activitystreams, and facebook's open streams
api and cliqset's feedproxy are dead. anyone know where cliqset's code
landed? anything else alive?
similarly, there's lots of consumer code out there, but less for
providers. apache has abdera, but this is just a side project, for
fun, so i'm going to pass on java. :P any others worth looking at?
I think generally speaking producing Activity Streams is assumed to be
"easier" than consuming, so it's the latter that library implementers
have focused on.
I started a Python consumer library here:
https://github.com/apparentlymart/activity-streams-python
All of the publisher implementations I've done have just hand-rolled a
compliant data structure and serialized it as JSON. That has worked well
enough for me.