3 ms·

We are putting together a wiki-style solution for community-curated post types. Common types are expected to be standardized so that apps are interoperable. For

We are putting together a wiki-style solution for community-curated post types. Common types are expected to be standardized so that apps are interoperable. For example status/microblog would be a standardized post type. We will launch with common types specified, so that everyone doesn't reinvent the wheel. After that, community managers will help keep the devs in line.

jsilence 14y ago
Maybe you should get in touch with the OpenSocial movement: http://www.opensocial.org/ http://www.opensocial.org/ Combine forces.
joe_the_user 14y ago
It sounds like a very nice idea. I'm putting together a "multi-protocol social client". I'd love to be able to use Tent. I am correct in assuming there isn't currently a reference implementation?
- Titanous 14y ago
  There is currently no reference implementation, but it will be on Github within a week or so.
benwerd 14y ago
Isn't this something Activity Streams could be very useful for? Activity Streams is also JSON-friendly.
e12e 14y ago
You might want to have a look at federated wiki for this: http://wardcunningham.github.com/ http://wardcunningham.github.com/
coopdog 14y ago
One issue I can see is that you only need to have one friend who uses a third party tentd with questionable privacy policies and now everyone they're connected to has their data exposed. Would it be possible to implement it such that you can say 'yes, you can have this data, but only if your server is not being run by 'blacklist' (would have to assume the requesting sever doesn't lie about it's identity). On the positive I can see this catching on because it's easy for existing social networks to integrate, it would almost become do or die forever more if a network that does integrate them catches on
- axx 14y ago
  Maybe this could be done by a IP/DNS blacklist on your API side. So you maintain a list on your "exit node" so that everyone who requests your data needs to be "a good guy". If this part would be done by the requester it could be spoofed easily, so it had to happen on the exit point.

jsilence 14y ago

Maybe you should get in touch with the OpenSocial movement: http://www.opensocial.org/ http://www.opensocial.org/ Combine forces.

joe_the_user 14y ago

It sounds like a very nice idea. I'm putting together a "multi-protocol social client". I'd love to be able to use Tent. I am correct in assuming there isn't currently a reference implementation?

Titanous 14y ago
There is currently no reference implementation, but it will be on Github within a week or so.

benwerd 14y ago

Isn't this something Activity Streams could be very useful for? Activity Streams is also JSON-friendly.

e12e 14y ago

You might want to have a look at federated wiki for this: http://wardcunningham.github.com/ http://wardcunningham.github.com/

coopdog 14y ago

One issue I can see is that you only need to have one friend who uses a third party tentd with questionable privacy policies and now everyone they're connected to has their data exposed. Would it be possible to implement it such that you can say 'yes, you can have this data, but only if your server is not being run by 'blacklist' (would have to assume the requesting sever doesn't lie about it's identity). On the positive I can see this catching on because it's easy for existing social networks to integrate, it would almost become do or die forever more if a network that does integrate them catches on

axx 14y ago
Maybe this could be done by a IP/DNS blacklist on your API side. So you maintain a list on your "exit node" so that everyone who requests your data needs to be "a good guy". If this part would be done by the requester it could be spoofed easily, so it had to happen on the exit point.