Has anybody considered the idea that boosts from non-Meta properties to Threads could legally be used to build ad profiles? We already know they do that sort of account association with non-fedi accounts.
EDIT: Looks like that's absolutely the plan. From the privacy policy
"Information From Third Party Services and Users: We collect information about the Third Party Services and Third Party Users who interact with Threads. If you interact with Threads through a Third Party Service (such as by following Threads users, interacting with Threads content, or by allowing Threads users to follow you or interact with your content), we collect information about your third-party account and profile (such as your username, profile picture, IP address, and the name of the Third Party Service on which you are registered), your content (such as when you allow Threads users to follow, like, reshare, or have mentions in your posts), and your interactions (such as when you follow, like, reshare, or have mentions in Threads posts).
We use the information we collect for Threads for the purposes described in the Meta Privacy Policy, including to provide, personalize, and improve Threads and other Meta Products (including seamless personalization of your experience across Threads and Instagram), to provide measurement, analytics and other business services (including ads), to promote safety, integrity and security, to communicate with you, and to research and innovate for social good."
https://help.instagram.com/515230437301944?helpref=faq_content
EDIT 2: After doing a little more thinking, I've come to the conclusion that the general narrative about Threads plan to steal users from similar federated services ignore the fact that it's certainly cheaper to let the volunteers of the fediverse take on the moderation costs while they monetize the data. Though the two certainly are not mutually exclusive.
I posted a version of this in another thread:
I really think Lemmy, Kbin, and Mastodon need to figure out a way to have a default terms of service that ships with their product which forbids using the API to collect data for anything outside of user-facing social network interfaces, including account association heuristics and similar processes.
A way for users to set licenses on individual posts would be huge as well, with a default license instance admins can set.
That way for-profit instances could be forced to filter out posts with licenses that do not allow for-profit use. Honestly, even just a simple check mark "[ ] allow for-profit republication", and have two licenses that can be attached: one that allows for-profit use and one that does not.
The fediverse should start baking in data control into it's legal framework. Want to federate with Mastodon? You need to follow the ToS for what you can do with its posts. If we wanted to get really extreme we could even say the license should be copy-left. Any instance that wants to federate with a non-profit instances needs to also be non-profit.
That could block for-profit companies from becoming part of the network in the first place, even by use of stealth relay instances.
#threads
Thoughts on this friends? @[email protected] @[email protected] @[email protected] @[email protected]
It'll be natural that a lot of instances will block these ad-ridden for-profit ones. A legal solution isn't necessary IMO, nor is trying to add a bunch of complication and process around "accepting terms" of instances you don't want to federate with. Allowlists and blocklists already work fine for that.
After reading a bit more I realize that's probably the best that can be done, thank you for replying and for Lemmy! ❤️
This is a great take. I think folks definitely need to start thinking about establishing legal bedrock for this sort of thing.