Update regarding Meta/Threads:
We hear that the Threads app is coming July 6th.
It will at first not support ActivityPub, so it can't talk to Mastodon yet. That will be added later.
We're very much in agreement with @tchambers , see https://www.timothychambers.net/2023/07/03/instagram-threads-and.html
As he said: ““Watching Like A hawk, with our fingers on the block button.” We will NOT be pre-emptively taking a “Fediblock as a Frist Strike” position.”
1/2
@mwadmin @tchambers Different Mastodon instances, different target demographics and different priorities, no wukkas! (That's Australian for bee~ no, Australian for "no worries". That ad just sticks…)
Other instances, more specifically requiring proactive defensive action, other outcomes. An alternative perspective: https://topspicy.social/@nikki/110655139668141091 (this showing the receipts as to announced data collection on Meta's side, and their history of using that data in bad faith)
@mwadmin @tchambers I might be late to the party here, and I'd be happy to support this strategy... can someone point to any time this response to EEE has worked?
Podcasting versus closed non-RSS formats, Linux vs Windows NT, PHP versus Active Server pages, SVF versus Silverlight, Java withstood Microsoft versions of JVM, etc. Way more success stories than cases where EEE worked.
@tchambers @mwadmin thank you very much for the examples!
@mwadmin @tchambers I have already heard of this and I'm trying to see if there is anything stating what the Mastodon.social admins think in regards to Meta/Threads.