Discussing the threat posed by Meta #P92/#Barcelona joining the #Fediverse with some tech enthusiasts feels more and more like debating #ClimateChange with a denier.
«Look at all the data indicating that this will be a disaster. It has even happened twice already!»
Responses: «It won't happen this time» «It won't be that bad» «It's actually good if that happens» and «we can't do anything about it anyway»
Well at least now they are starting to say the quiet part loud, and unsurprisingly it's the fact that they don't actually care about open protocols and federation, and are perfectly fine with the genocidal corporate silos:
There's now a #FediPact tag, and a website collecting signatories thanks to @vantablack https://fedipact.online/
You can also follow the progress via the dedicated FediDB tracker https://fedidb.org/current-events/anti-meta-fedi-pact
set up by @dansup
(a thankless work, apparently, given how many of you are harassing him. JFC, people, if you are unable to debate and criticize without resorting to harassment and insults, maybe consider that Twitter is better suited for you than the Fediverse?)
One thing I've noticed with people in the “wait and see” camp is that none of them seems to be able to answer this very simple question:
Meta is a known bad actor. It has a track record of abysmal privacy policies, catastrophic moderation (Myanmar genocide docet) and successful open protocol busting (XMPP). What information do you have that would even suggest this isn't what they're bringing to the Fediverse, to justify a “wait and see” attitude?
So let me see if I get it right: people use the lack of QTs as an excuse to not come to #Mastodon, but stick with #BlueSky despite it lacking support for GIFs, videos, DMs, polls, and basic filtering capabilities?
@pomCountyIrregs@ChrisBoese the point is not what do people want. The point is refusing to use a platform that misses a feature they want but using another platform that missed several features they want, showing that the missing feature wasn't really the reason they didn't stick with Mastodon in the first place, but just an excuse.
OK maybe I can try this in English too. I'm looking for a #horror#comic or short #graphicNovel that was published in the #eighties or earlier and was a graphical representation of the well know “boyfriend's death” story (Sheriff finds the girl variant) https://www.snopes.com/fact-check/the-boyfriends-death/
It was published on an Italian comics magazine in the 70s or 80s, but I'm sure it was American. I can't find the issue anymore. Anybody knows it? Boosts welcome for reach.
The obvious recommendation here is to defederate with extreme prejudice any and all #Facebook-associated instance. We know how it will play out, we've seen it happen again and again. It doesn't matter how nice and cooperative they will be in the beginning, this is a power move against the #Fediverse, a move against which it has no chance of resisting if even an inch is given.
I have an #eWaste problem that I would like to solve: two #dell laptops that refuse to boot. One lights up for a couple of seconds, before shutting down again. The other seems completely dead, even after replacing the battery. The laptops are otherwise in decent conditions and I would like to revitalize them for my kids as they come of age.
Actually, joking aside, I'm now wondering if I could hire @foone to fix my #eWaste problem: send them the laptop, pay for expenses and labor, get back the two laptops restored in working order and a nice Fediverse thread where they complain about the state in which I left them. Counterpoints: stuff is probably too recent for @foone taste, and shipping there and back is probably going to cost me an arm and a leg.
Remember: if you boosted something in the far past and you see it making the rounds again and you think it's still worth seeing, you can unboost and reboost it to share it with your followers again. You may have new ones that are interested in it, or old ones that missed it the first time.
Since #Facebook/#Meta is apparently going to start testing #Fediverse/#Mastodon integration for their #P92/#Barcelona/#Threads “platform” soon, let's do another round of reminders of what this entails and why their instance and IPs should be blocked now with extreme prejudice.
The way #Mastodon “massages” images, often lowering quality while increasing storage size is one of the most flabbergasting misfeatures of this platform.
This particular issue doesn't affect end-users only, but has a catastrophic impact on the servers, both in terms of storage and bandwidth requirements.
The catastrophic ballooning effect is allegedly partially solved in 4.2.x per this changeset https://github.com/mastodon/mastodon/pull/23726
by removing the client size mangling, but from what I can see the fundamental issue remains: why are there limits on media dimensions at all, rather than just on file size? And why is the media getting transcoded in the first place?
There is actually a scenario where I think transcoding would make sense (at least for images and GIFs): convert everything to #JpegXL to minimize file size and support open standards. Of course with the dire situation of #JXL support in browsers at this time, this would also require deploying JS decoder for meda, which is suboptimal.
@kwheaton the whole of the point was to subtoot a poll that asked about vowels, but for some reason on reading it quickly I read wolves, so I decided to do the one on actual wolves so … depends on how wolfey your vowels are? 8-D