still hella confused as to why self-proclaimed privacy advocates—even teams like @privacyguides—are pushing @element so hard despite the data collection & sharing practices, the loosey-goosey metadata usage, and the fact that they host on AWS.
still hella confused as to why self-proclaimed privacy advocates—even teams like @privacyguides—are pushing @element so hard despite the data collection & sharing practices, the loosey-goosey metadata usage, and the fact that they host on AWS.
@mrmojo
>You’re supposed to host on whatever you want.
sure, but if the messages are stored on servers you don’t fully trust or control?
>Fork it if you want, remove what troubles you.
can’t argue with this, except that becomes it’s own point of vuln if you’re not adept in development or have sec experts vetting your setup, which make this easy to say and impractical to implement
(lol sorry for the spamming there… can’t figure out blockquotes)
Encrypted messages.
Also, you can limit which servers can participate in your room’s federation (in simple terms: which one has access to room data). There’s an option on the Element UI to disallow federating the room, and I think it’s also possible to have fine grained control over it (with so called server ACLs)
Isn’t it opt-in on all the released Element clients?
deleted by creator
whitelists: exist
deleted by creator