None of the wires cover it — not Reuters, not AFP, not AP, not Bloomberg.
One in three women is (roughly) one on six members of the human race. No news agency thinks long-term health issues affecting one in six people matter.
@kkarhan Yes, long covid hasn't been an issue for the same length of time but it's the same problem, the same mechanisms at play. At each level there are people making decisions about what audiences might want to read, and therefore what audiences get to read. There's nowhere near enough scrutiny on how those decisions are made and the structural issues that prevent improvements.
Request for admins: You might've seen this mentioned, but I wrote a tool to help people move their posts when they change instances.
It's still in development, but I'd like to hear from instance admins if there's anything about it they're worried might affect their instances, or anything that could be made clearer in the documentation to help.
If you need to move between #Mastodon instances and would like to keep your posts (including attached images and video), you can do that with #MastodonContentMover
It's a command-line tool that saves your posts from your current instance to your computer, and then reposts them to your new instance. It's in development, but an early test version is available.
(I need to update it to use the most recent version of the #BigBone library, but I don't want to try to rush that and mess something up, especially not right now, and the version that's there should still work fine. If you run into any problems with it please do let me know 🙏)
A whole set of biggest instances all run by one person, together with another of the biggest instances, are indexing people's posts and retaining copies of them (separately from Mastodon itself)
The records are not removed when the posts are deleted. If you try to post the same content on another of the linked instances, you are prevented from doing so
And I haven't seen a single person on here say a word about it. I bet even people on those instances don't know
People should know these instances are being linked in this way. Because in terms of data, in terms of resilience in a defederated network, they are no longer separate instances. They look like separate instances, but they are not. They are logically one. If you put your data in one of them, it is shared with all the others — invisibly to you.
Can you imagine what the #Fediverse would look like now if the response to Gab had been "Admins don't need to block these instances, individual users can just choose whether or not to apply a user-level block (mute) themselves"?
And #Meta is even more corrosive than Gab. Gab users just posted a barrage of hate and unpleasantness. Meta is commercially incentivised to destroy what some people are inviting it to into.
So annihilation.social, which seems to be an instance with known issues, is running a bot to identify and post about instances that are blocking #threads.
Other users are then using those posts to send messages to the instance admins asking them to justify their decision (to harass admins of instances that block #Meta, basically).
@tokyo_0 Hi, just trying to understand, is annihilation dot social "running" the bot or is it simply allowing the bot to be hosted on its instance? (Not that it would be easy to tell which is happening, I guess.)
@tokyo_0 yeah. I'm actually not sure if it's even possible to get the information the insurance has in an automated way without somewhere running an instance.
Incidentally— the bot doesn't seem to be specifically designed to post Threads blocks, it appears to post just literally all instance blocks. However, looking at the bot it does seem to be intentionally designed to drive harassment of instances which add blocks :(
#Japan: #Tsunami alert issued for east coast from Kyushu to Chiba and islands off the eastern coast, following a magnitude 7.7 #earthquake off the coast of the #Philippines
All in vulnerable locations along the coast are advised to evacuate to higher ground immediately.
Tsunami is forecast to reach up to 1 metre, and will arrive in Miyakojima and Yaeyama around 1:30 am, before arriving in other locations along the coast from around 2:30am onwards.
A lot of people have insisted #Meta isn't getting involved with the #Fediverse to embrace, extend and extinguish it...
... but even before fully implementing Fediverse interoperability in #Threads they're already talking openly about changing its protocols to add features like monetization. 🤔
Text in a screenshot reads as follows: McCue riffed on the idea that fediverse users could become creators where some of their content became available to subscribers only, similar to how Patreon works. For instance, fediverse advocate and co-editor of ActivityPub Evan Prodromou created a paid Mastodon account (@evanplus) that users could subscribe to for $5 per month to gain access. If he’s on board with paid content, surely others would follow. Cottle agreed that the model could work with the fediverse, too. He additionally suggested there are ways the fediverse could monetize beyond donations, which is what often powers various efforts today, like Mastodon. Cottle said someone might even make a fediverse experience that consumers would pay for, the way some fediverse client apps are paid today.
And aware, no doubt, that quote posts are a divisive, hot-button issue, they're already building into #Threads not only quote post functionality but more refined controls for it than I know of anywhere in the #Fediverse — a feature bound to attract attention and make people consider choosing Threads in preference to other Fediverse software that doesn't offer the same functionality.
@youronlyone I don't think they can force the rest of fedi to implement controls on quotes. I do think it's a bad idea to control who can quote post no matter if it's Mastodon or Threads doing it (or even Misskey). But it's just going to be circumvented/ignored easily, like how Masto's "opt-in search" has no effect on Misskey's note search per user.
What fedi really should focus on is controlling replies. And while I have reservations on federating that control, I do believe it's important to give users the power to control how their posts look like in their own instances without having admin privileges. Because it's a (micro)blog.