Folk have asked if topspicy.social will federate with meta or not.

This is what meta want to track if you use their threads app. They have a history of building profiles on folk who aren't signed up to their products through all their embedded tracking in all the websites their shit touches.

They can shove it up their metahole.

I should not be allowed near a video editor
@nikki is it me, or does it sound like dad says at the end there "what the shit"
@nikki No, no, I'm pretty surre this is why you should.
Pierre Bourdon (@[email protected])

Attached: 2 images I've seen 2 or 3 posts in my TL re: App Store privacy info for Threads vs. Mastodon. https://mastodon.social/@jsq/110653072170221591 for example. I feel like people greatly misunderstand the App Store privacy labels. They're not at all a ground truth you should read without careful interpretation. - Entirely self reported - No consistent auditing or data quality enforcement by Apple - Very vague, both on the scope of categories and what's "collection" - "May be collected" is a "worst case" statement. (cont)

Mastodon
@nikki Ok, fuck that. I was kind of on the fence with the idea of baselessly de-federating it initially, but I'm absolutely onboard on this basis now...
@nikki and of course since Apple and Google have a vested interest in this nonsense there’s no way to be selective about what is collected.

@nikki this is all data that may be collected by a mastodon instance too. For example, threads isn’t forcibly going to collect your health data but if you choose to share your health data then it’s stored by meta. That’s the same with mastodon instances where I see people post about their health all of the time.

The difference will come down to what they do with that data, how it’s processed and if it’s sold. Not whether or not they collect it.