• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle






  • My use case: I like to have all my emails stored locally just in case some disaster happens with the copies in the cloud; I also get to have both personal and work email addresses, from different providers, in one organized and unified interface, and the same goes for tasks, calendars and contacts; and some features from big web clients are sometimes too nosy for my taste (suggested replies, pushing their calendar, messaging, tasks and contacts products, etc)



  • Yeah, for now I’m skeptical because they’re Meta and they have to find ways to monetize this service, but on one day they’ve already overshadowed the rest of the fediverse easily. Even if they can’t profit as effectively off other instances, their instance is already ridiculously big and profitable regardless; the scraping thing really sounds like fear mongering. So if the only downside of federating with Threads is that my federated timeline would get cluttered with business accounts posting ads, I’d be alright with it, as long as I can get more content on my Home timeline from LOTS of people I want to follow who are not willing to interface with Mastodon, Pleroma, etc. Unless they force regular user accounts to publish advertisements to people outside the Threads instance, I’ll take it


  • On their app that should be harder to skip because the timeline is based on their algorithm and ads should be unavoidable, but how the hell would they force a user on another platform to see it? And how would they even directly target this person with a specific ad? If what people on instances federated with Threads see on their federated timeline are regular posts from business accounts placed in chronological order, I’m guessing there’d be no problem just blocking those “profiles” and moving on







  • Even worse:

    The identity and location of the activist was already known to the French authorities (they had already been evicted once before for squatting, and the nature of squatting means that their location is known).

    So they were probably not using a VPN to connect to Proton Mail, which was the specific target, since e-mail and VPN providers were treated differently under Swiss law until Proton and Threema fought the government on this issue. Tutanota had a similar issue. If you’re gonna rely on these services to break their jurisdiction’s laws, you should be covering your own ass with bulletproof opsec, because businesses with millions of accounts are not gonna shut down and burn evidence in order to protect one user. In the Proton case, the activist apparently connected to a known Proton Mail account with no VPN or Tor; in the Tutanota case, only e-mails that were not end-to-end encrypted would pose at risk