tothedaring

joined 2 years ago

@Markaos ah, thanks for the heads up. wasn't aware. still new to the fedi.

[–] tothedaring@kolektiva.social 7 points 1 year ago* (last edited 1 year ago) (2 children)

@clb92 @Albinjose7345 @privacyguides if we want more people to start their privacy journey and be capable of navigating these waters that change before people can get a chance to get their sealegs, we have to show up with grace & patience. we’re gonna have to show people how to look for accurate, vetted info in a sea of misinfo. it helps no one to approach the situ the way you and @moreeni did

[–] tothedaring@kolektiva.social 4 points 1 year ago (4 children)

@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)

[–] tothedaring@kolektiva.social 1 points 1 year ago (3 children)

@commie ya same. i didn't mention it bc it seems like there was an exodus from XMPP to Matrix for some reason

[–] tothedaring@kolektiva.social 7 points 1 year ago (5 children)

@sp6 oh i'm not suggesting Signal, though i trust it and use a FOSS client version of it. i agree with you there and would never pitch Discord either, but Element seems much more open to data leakage (bc of the bridges feature) than any other platform and lacks true decentralization (since everyone just uses the main homeserver) and ephemeral messaging, which makes it a non-starter for me.

i think Briar, Cwtch, Session, Simplex, and Tox are where we should be looking, no? or even @syphon over Element if Matrix is what we're set on using (based on privacy policy).

 

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.