Okay so I finally got around to reading the Fluxer dev's (long!) blog post and... his take on federation is literally the exact same thing I independently suggested.
10/10 this guy knows what he's doing. This is going to work.
(Also fully agree with his "why not E2EE for messaging" section)
I'll still be mainly on Discord while this and other things cook but... watch what this guy's doing. He gets it!
@lina wow, this is exactly what i wanted (and was planning to build after my 15 year old discord account got banned for "being 12")
@lina if this can replace Matrix for FOSS project discussions it would be huge.
@lina is this the link?
https://blog.fluxer.app/how-i-built-fluxer-a-discord-like-chat-app/
@lina i wonder if fluxer will consider becoming part of the fediverse :D
i believe they can then piggyback on the e2ee work thats already being done here
https://soatok.blog/category/technology/open-source/fediverse-e2ee-project/
also https://github.com/shazow/ssh-chat is a nice proof of concept of using ssh to chat with others. e2ee encrypted because of ssh :)
@Logical_Error I don't think that makes a lot of sense. Fluxer is a realtime chat platform, and the Fediverse is more async. It doesn't really map well.
I'm sure people will build bridges so you can do things like export a specific Fluxer chat into the Fediverse though! I bet that already exists for Discord even (via APl).
@lina thanks!
I do have Strong Opinions on the need for e2ee here, and on adding e2ee on top of cleartext protocols, but eh. I will admit the project looks very interesting.
@lina pretty much client side federation, i guess, IRC style? relays being used just to hide your IP (and in theory optional)
that's a fun concept that i've not seen before, yeah
@5225225 Yup (main reason for relays is actually mobile apps I suspect, since you don't want an explosion of connections for those).
The OAuth thing on top (alongside, presumably, scoped usernames@domains) is what makes it automatic/transparent (no manually configuring networks or registering yourself).
@lina ah, makes sense
tbh i'm not entirely sure how much more work it is steady-state to keep 10 connections open as opposed to 1, but i suppose opening said connections isn't free. and a single relay would allow you to send data in batches if the device isn't being used, which does help battery
and ig for instances of censorship (a given relay just refusing to talk to a given server), you could either pick a different relay / connect directly just for that one server, since the relays aren't trusted infrastructure
neat. doing "federation" work client-side is one of the design goals for something i'm working on, since it does simplify stuff a lot
@lina Definitely something to consider, I like what they are trying to do :)