@dimillian @Mathijs I found this blog post helpful for understanding the server side controls available for restricting access: https://hub.sunny.garden/2023/06/28/what-does-authorized_fetch-actually-do/
Knowing what you can enable to prevent anonymous access makes it clear just how public the defaults really are.
@joannekelly As long as you don't use the app you should have no issue. Let grandmas and whoever else doesn't care about this and let's take advantage to bring everyone over!
@joannekelly @dimillian not really keen to defend Meta or anything, but two very reasonable things could be going on:
1) Meta need time to build the infra and tooling for GDPR compliance. Having the tools and process for forget-me requests, and having the infrastructure in place and tested to support data sovereignty is not an intractable problem but it takes time.
2) per the article there’s new legislation that restricts the sharing of data between platforms, and Meta need clarification on how that affects Threads which shares a lot of services with Instagram (identity being the key one here). Having been in debates around what counts as data in scope for GDPR before, I know stuff like this isn’t cut and dry and it takes time to sort out.
I do think Meta wants to grab all your data, I just don’t think delaying the EU launch is because the EU has legislation that will prevent that. It does have some pro-consumer legislation that means Meta has to work a bit harder to do it though.
Isn’t this just a version of the No true Scotsman fallacy wrapped in the mister gotcha meme?
https://thenib.com/mister-gotcha/
People are allowed to be inconsistent and pick their battles while they weigh their principles against practicality
To pretend otherwise, is to accept that only people that live entirely off the grid are entitled to voice privacy concerns
People feel that we’re at a crossroads and that voicing their opinion might sway things
@dimillian
For some there is no difference and if they’d learn that Meta is already doing this they’d be equally outraged, making an accommodation by instances even more outrageous
I’ve seen hardcore privacy fanatics defend #Meta because they’d rather a company processes their data than a Mastodon instance because the former can be sued, how’s that for inconsistency
To say nothing about the false equivalency between access to public posts and a $700B+ corporation being able to correlate data
Personally I’ve got my principles, but by the looks of it, I might have to relent and become an unwilling participant of Threads given how many in my social graph already made the move, similar to how I was an unwilling participant of Twitter
Others will be willing participants because it might be the 1:1 Twitter replacement they’ve been looking for
@dimillian I think that 99% of the time, the password protection on Word files is used solely to allow a user to feel like they have secrets worth stealing
surely it’s just a coincidence that I’m posting this as a response here
@dimillian I’m likely to pass on Threads; I’m not seeing a benefit to me.
But, as to your question, I think the concern on privacy is about the app and what it’s gathering when it isn’t busy with its nominal function. A secondary concern is that after an initial phase, the algorithm that controls viewability will be tweaked to favor Meta’s commercial purposes. A tertiary concern is, yes, public is public, but Meta’s info selling business is in overdrive.