There's a lot of energy on the #Fediverse right now to discuss/find a #Federated alternative to #Discord using #ActivityPub.
@strypey suggested that I put this out there to anyone who's thinking about it. We could probably rebuild most of Discord's features as an #Emissary inbox without doing a lot of back end code.
I'm too swamped to start on this right now. But if you're a great HTML+CSS designer, I'm able to give some time to a team who wants to take this on.
@benpate @strypey@mastodon.nzoss.nz I'm building Shoot, a discord-like federated instant messenger with activitypub! I would always appreciate any help with development, my pins has any more info as well
@maddyunderstars Looks cool! I'm starring and following your work.
It looks like you're using Typescript. All of my E2EE work is in Typescript, so there's a good chance you could use the library I'm making when you want to do encrypted groups.
Let me know when I can help :)
#Roomy currently based on AT Proto but looking to add #ActivityPub soon
https://itsfoss.com/roomy-discord-alternative/
Hey, this is pretty interesting. Thanks for sharing!
That would be really cool if they can support Bluesky and ActivityPub at the same time.
The article on the website makes it seem like you’re only signing in with your ActivityPub identity though?
Otherwise, “Fediverse” client support is limited to the Mastodon API, or oft-unimplememted C2S API.
I’ll definitely keep my eyes on this one!
@benpate @klu9 @strypey ATProto is used only for authentication, optional integrations, and optional backups.
We have our own somewhat generic event streaming server that we use for chat spaces, where each chat space could be migrated to another server without the permission of the current host.
It's "federated" in that each chat space will be able to be hosted on a different server and the client will still be able to join them all from the same app.
(1/2)
@benpate
> you’re only signing in with your ActivityPub identity though?
The article is light on specifics, but it seems like Roomy is a client app, not a server+client app like Mastodon. So in ATProto jargon;
https://dustycloud.org/blog/how-decentralized-is-bluesky/
... Roomy is an AppView, using the PDS for a logged in ATProto account as a data store (not sure if or how it uses Relays).
(2/2)
If Roomy enabled signing in with a fediverse account as an identity, there's no PDS to use for data. So I'm guessing the plan is to implement the Mastodon API, enabling Roomy to act as a fediverse client, and use a logged in account's home service as the data store?
What would be really intriguing is if Roomy borrowed from the @activitypods approach, allowing a fediverse account to be used as identity, with a Solid pod as the data store.
@strypey @activitypods Roomy implements its own storage. #ATProto is only really used as an identity / sign-in layer.
