@silverpill my biggest challenge now is multi-client support, trying to figure out how data can be synchronized across devices. My current codebase is assuming data on the server too much, so I probably need to rethink the architecture anyway.
@silverpill@mcc@julian@MrCheeze Sorry if this is not a right place to ask. I'm interested in FEP-ed61 but I'm stuck at Webfinger and gateways. What if a user only knows a webfinger handle alice@example.com but a gateway example.com is dead? The Webfinger section of FEP-ef61 reads like you somehow know the actor's gateway before you look up the actor.
@tengkuizdihar I'm leaning towards it, but still thinking. Right now chats in spaces are ephemeral and encrypted in transit, not e2e. Voice chat could be e2ee like recent Discord. Group chats are much trickier in terms of e2ee, but I'll look into it once Hamabe gets group chats.
I like listening to people chatting in streaming and podcasts, so I'm making a federated chat platform called Hamabē. Yes, it's FOSS.
Hamabē is a successor of Audon, but a new platform speaking ActivityPub and independent of Mastodon API. (Thank you @namekuji for letting me take the project over and kindly hosting my infra!)
You can follow Hamabē accounts from AP platforms and can receive notifications when a space starts (if your platform supports Event activity)
Right now Hamabē only has voice chat (along with simple text chat) to cover Audon's use cases, but there's a plan to add text-based group chat later.
Some basic features have been implemented, but it's still in very early stage and documentations are not ready yet. Issues and PRs are also closed for now, but I'll open them once it reaches first alpha release. :abunhdhappyhop: