ricmac1:If you don’t want people searching your content, you can shut that off in your settingsAnd I do! But in the actually-existing fedi the search engine that was demo’ed at the Fediverse House developers meetup ignores consent settings so my posts will show up there . So this is a potentially-great thing about fedi that in practice leads to repeated firestorms when developers ignore consent. (And since trans and non-binary people are some of the most passionate about opposing non-consensual search, this relates to my point about cis-dominance) ricmac1:If you don’t want Meta, then choose an instance that blocks them out (or self-host)And I do! But Meta’s on the W3C group that controls the AcitivityPub standard, they give demos at Fediforum, a Meta-funded nonprofit was hosting the developer meetup at Fediverse House (and is also on the W3C group, where one of their representatives has twice shut down discussions he’s saw as critical of Meta on the W3C mailing list), and it’s rare to see press coverage of fedi that doesn’t include Meta — or that does acknowledge how many strong the opposition is to them being here. In practice, while having the ability to block Threads is certainly a good thing, the fedi influencers who have decided that Threads is a good thing here have only made that the default, they’ve made it so I can’t even really opt out. So yes I agree it’s annoying!Anyhow this all ties into why I see it as complex. The techie-elitism of “we don’t want normies here” is real, and it’s harmful. But it’s far from the only thing going on here.
