I've started putting together a list of apps, focused on implementations of , documenting their status and what tech stack they're (being) built with: ethercalc.org/fediverse-stacks

This is a publicly editable doc, so would appreciate corrections/additions, and feedback especially from fediverse devs, but also from instance admins and users:

- What app/implementation/stack did you try?
- Pros/cons you encountered
- What stack & libraries would you choose if starting today?

PS. We've been talking with @bhaugen and others about the need for a generic agent-centric server, so that instead of signing up to a bunch of different servers, a user could have their indentity and data all in one place, and all the apps they use (clients, but if necessary server-side "plugins" as well) would interact with the activity/objects types that they support.

What do you think?

cc @cwebber @aaronpk @deadsuperhero @aral

@mayel @aral @deadsuperhero @aaronpk @cwebber @bhaugen totally. We need an ID that we can migrate from service to service. OpenID plus more.

Right now my data is spread. My identity is spread. And frankly I don't own my ID. If I wanted to migrate instances I'm at the mercy of the instance admins.

Gert V
Follow

@thinkMoult @bhaugen @cwebber @aaronpk @deadsuperhero @aral @mayel

Paradoxically, it seems to me that if we'd like to have *safe* SSO, we'd need a decentralized solution.
social.coop/@gert/100457720829

Sign in to participate in the conversation
social.coop

social.coop is a a coop-run corner of the fediverse, a cooperative and transparent approach to operating a social platform. We are currently closed to new memberships while we improve our internal processes and policies, and plan to re-open to new folks when that work is complete. [9/2/2018]