What this means:
Yeah, I get it.
Mastodon and its users rule supreme over the Fediverse. After all, the Fediverse was invented by Gargron. It started when Mastodon started, and everything that isn't Mastodon just latched onto Mastodon and its Fediverse.
Mastodon users are the only civilised users in the Fediverse, the only ones with something like a culture. The Fediverse culture is Mastodon's culture as defined in the spring of 2022. All those who don't live by Mastodon's culture are uncivilised, uneducated, savage barbarians. And it isn't just the Mastodon users' right and privilege to educate them and shape them into good Mastodon users, it's their duty.
Even when it turns out that these barbarians aren't even on Mastodon, that they're on something that's very much not Mastodon, they can't possibly have a culture of their own. After all, they don't live by Mastodon's culture, and if it isn't Mastodon's culture, it isn't culture at all. Not even if it predates Mastodon's current culture by over a decade like Friendica's culture does.
Of course, this also means that when non-Mastodon users come and give Mastodon users unsolicited "advice" or recommend them to use Mastodon in a certain way that goes against Mastodon's culture, the Mastodon users are fully justified to silence them by any means available.
When a Mastodon user uses "Fediverse" and "Mastodon" mutually synonymously, it's the right thing to do because that's part of Mastodon's culture. And it makes things easier to understand.
When a non-Mastodon user explains that the Fediverse is not only Mastodon, and that "Fediverse" and "Mastodon" do not mean the same, it's evil and intrusive and deeply disturbing.
When a Mastodon user refers to any message in the Fediverse as a "toot", it's the right thing to do because that's part of Mastodon's culture.
When a Misskey or Forkey user talks about "notes", it's irritating. When a Friendica or Hubzilla or (streams) or Forte user distinguishes between "posts" and "comments", it has even less of a place in the Mastodon Fediverse.
Features that only Mastodon has are actually mandatory for the whole Fediverse. Any Fediverse server software that hasn't got these features implemented in exactly the same way as Mastodon is broken.
Features in non-Mastodon Fediverse server software that Mastodon doesn't have are wrong and evil and not allowed to be used.
Mastodon users are allowed, justified and expected to tell non-Mastodon users to limit their posts to no more than 500 characters. It especially disturbs those who refuse to move away from the official Mastodon phone app.
Non-Mastodon users are not allowed to tell Mastodon users to not cut their long posts into threads.
Mastodon users are allowed, justified and expected to tell non-Mastodon users to put content warnings into their summary/abstract field.
Mastodon users are allowed, justified and expected to tell non-Mastodon users to only use their summary/abstract field for content warnings. After all, that's what Gargron invented that field for.
Non-Mastodon users are not allowed to tell non-Mastodon users that it was Evan Prodromou who invented that field as early as 2008. That he invented it as a summary field. That it was actually a Mastodon user who repurposed that field for CWs in 2017, the year after Mastodon was launched. Gargron only let it pass.
Non-Mastodon users are not allowed to use that field for anything else than CWs.
Non-Mastodon users are not allowed to add hashtags instead of CWs so that reader-side CWs can automatically be generated by filters. Even though Mastodon itself has literally introduced this very feature with version 4.0 in October, 2022.
Mastodon users are allowed, justified and expected to tell non-Mastodon users to not only write alt-texts for all the images they post, but to write them nicely long and detailed. After all, they've got 1,500 characters for alt-texts.
Misskey and Forkey users are not allowed to tell Mastodon users to limit their alt-texts to no more than 512 characters because that's the maximum that Misskey and the Forkeys accept, and on top of that, due to a bug, they delete all alt-texts longer than that. From a Misskey/Forkey point of view, writing long alt-texts is like not writing any alt-texts at all. But the Misskey/Forkey point of view is invalid in Mastodon's culture.
Mastodon users are allowed, justified and expected to toot to Lemmy any way they want, and that's the Mastodon way. If it doesn't work properly on Lemmy, then Lemmy is broken.
Lemmy users, even Lemmy moderators, and other users of Fediverse software that supports groups are not allowed to tell Mastodon users how to post to Lemmy in a way that Lemmy understands.
Mastodon users are allowed, justified and expected to even tell Lemmy users to limit their "toots" to no more than 500 characters and use hashtags, but not too many of them.
Lemmy users and even Lemmy moderators are not allowed to tell Mastodon users to stop spamming Lemmy with mentions and with hashtags that don't work on Lemmy anyway, also because both highly irritate the Lemmy users. Almost all of them came straight from Reddit after their third-party apps were killed, and almost none of them have ever been on Twitter or Mastodon.
Mastodon users and Mastodon admins are allowed and justified to block any and all non-Mastodon servers because they misbehave by Mastodon's standards.
(streams) and Forte admins are not allowed to block the entirety of Mastodon, all present and future servers, by user agent (which, by the way, they're totally capable of) because it misbehaves by their standards. Mastodon doesn't misbehave, and the Hubzilla/(streams)/Forte standards are all wrong if they differ from Mastodon's standards.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #Yeah, I get it.
Mastodon and its users rule supreme over the Fediverse. After all, the Fediverse was invented by Gargron. It started when Mastodon started, and everything that isn't Mastodon just latched onto Mastodon and its Fediverse.
Mastodon users are the only civilised users in the Fediverse, the only ones with something like a culture. The Fediverse culture is Mastodon's culture as defined in the spring of 2022. All those who don't live by Mastodon's culture are uncivilised, uneducated, savage barbarians. And it isn't just the Mastodon users' right and privilege to educate them and shape them into good Mastodon users, it's their duty.
Even when it turns out that these barbarians aren't even on Mastodon, that they're on something that's very much not Mastodon, they can't possibly have a culture of their own. After all, they don't live by Mastodon's culture, and if it isn't Mastodon's culture, it isn't culture at all. Not even if it predates Mastodon's current culture by over a decade like Friendica's culture does.
Of course, this also means that when non-Mastodon users come and give Mastodon users unsolicited "advice" or recommend them to use Mastodon in a certain way that goes against Mastodon's culture, the Mastodon users are fully justified to silence them by any means available.
When a Mastodon user uses "Fediverse" and "Mastodon" mutually synonymously, it's the right thing to do because that's part of Mastodon's culture. And it makes things easier to understand.
When a non-Mastodon user explains that the Fediverse is not only Mastodon, and that "Fediverse" and "Mastodon" do not mean the same, it's evil and intrusive and deeply disturbing.
When a Mastodon user refers to any message in the Fediverse as a "toot", it's the right thing to do because that's part of Mastodon's culture.
When a Misskey or Forkey user talks about "notes", it's irritating. When a Friendica or Hubzilla or (streams) or Forte user distinguishes between "posts" and "comments", it has even less of a place in the Mastodon Fediverse.
Features that only Mastodon has are actually mandatory for the whole Fediverse. Any Fediverse server software that hasn't got these features implemented in exactly the same way as Mastodon is broken.
Features in non-Mastodon Fediverse server software that Mastodon doesn't have are wrong and evil and not allowed to be used.
Mastodon users are allowed, justified and expected to tell non-Mastodon users to limit their posts to no more than 500 characters. It especially disturbs those who refuse to move away from the official Mastodon phone app.
Non-Mastodon users are not allowed to tell Mastodon users to not cut their long posts into threads.
Mastodon users are allowed, justified and expected to tell non-Mastodon users to put content warnings into their summary/abstract field.
Mastodon users are allowed, justified and expected to tell non-Mastodon users to only use their summary/abstract field for content warnings. After all, that's what Gargron invented that field for.
Non-Mastodon users are not allowed to tell non-Mastodon users that it was Evan Prodromou who invented that field as early as 2008. That he invented it as a summary field. That it was actually a Mastodon user who repurposed that field for CWs in 2017, the year after Mastodon was launched. Gargron only let it pass.
Non-Mastodon users are not allowed to use that field for anything else than CWs.
Non-Mastodon users are not allowed to add hashtags instead of CWs so that reader-side CWs can automatically be generated by filters. Even though Mastodon itself has literally introduced this very feature with version 4.0 in October, 2022.
Mastodon users are allowed, justified and expected to tell non-Mastodon users to not only write alt-texts for all the images they post, but to write them nicely long and detailed. After all, they've got 1,500 characters for alt-texts.
Misskey and Forkey users are not allowed to tell Mastodon users to limit their alt-texts to no more than 512 characters because that's the maximum that Misskey and the Forkeys accept, and on top of that, due to a bug, they delete all alt-texts longer than that. From a Misskey/Forkey point of view, writing long alt-texts is like not writing any alt-texts at all. But the Misskey/Forkey point of view is invalid in Mastodon's culture.
Mastodon users are allowed, justified and expected to toot to Lemmy any way they want, and that's the Mastodon way. If it doesn't work properly on Lemmy, then Lemmy is broken.
Lemmy users, even Lemmy moderators, and other users of Fediverse software that supports groups are not allowed to tell Mastodon users how to post to Lemmy in a way that Lemmy understands.
Mastodon users are allowed, justified and expected to even tell Lemmy users to limit their "toots" to no more than 500 characters and use hashtags, but not too many of them.
Lemmy users and even Lemmy moderators are not allowed to tell Mastodon users to stop spamming Lemmy with mentions and with hashtags that don't work on Lemmy anyway, also because both highly irritate the Lemmy users. Almost all of them came straight from Reddit after their third-party apps were killed, and almost none of them have ever been on Twitter or Mastodon.
Mastodon users and Mastodon admins are allowed and justified to block any and all non-Mastodon servers because they misbehave by Mastodon's standards.
(streams) and Forte admins are not allowed to block the entirety of Mastodon, all present and future servers, by user agent (which, by the way, they're totally capable of) because it misbehaves by their standards. Mastodon doesn't misbehave, and the Hubzilla/(streams)/Forte standards are all wrong if they differ from Mastodon's standards.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # Well, then you must live with long posts being long in your timeline. Users of non-Mastodon Fediverse server software will not stop using it as intended and start using it like Mastodon just because long posts disturb the users of the official Mastodon app.
Someone who has been on Friendica since 2011, and who is absolutely using Friendica like Friendica is intended to be used, will not use Friendica like Mastodon suddenly just because Mastodon users prefer that.
I mean, what if non-Mastodon users came and told Mastodon users to stop cutting their long posts into threads What if non-Mastodon users came and told Mastodon users to use the CW field for summaries instead of CWs because that's what that field is actually for What if Friendica and Hubzilla users came and told Mastodon users to replace their CWs with hashtags so that they can have their own individual CWs automatically generated reader-side, as has been their tradition since before Mastodon was even made
I keep seeing this again and again. At first, Mastodon users perceive non-Mastodon users as users on "hacked" Mastodon servers with increased character limits who simply don't know about Mastodon's culture which includes limiting all your "toots" to no more than 500 characters. And they try to educate them how to use Mastodon properly.
Once they learn that these people are, in fact, on something else, something entirely different from Mastodon, they perceive them as barbarian, culture-less intruders into their precious Mastodon Fediverse who need to be educated about proper Mastodon behaviour nonetheless.
They think Mastodon is the one supreme ruler over the Fediverse. They think they are the ones who have the exclusive saying over how anything in the Fediverse must be used. They think they have the Gargron-given right to tell e.g. Friendica users whose culture is over a decade older than Mastodon's current culture to completely abandon their own culture and 80% of Friendica's features along with it and only live by Mastodon's culture.
At the same time, they consider requests from outside of Mastodon to change their own behaviour aggressive and intrusive and against "the Fediverse culture", read, Mastodon's culture. And then they completely fail to understand why there's so much Mastodon hatred especially on Friendica, Hubzilla, (streams) and Forte. They're the good guys, the cultured and well-behaving ones, aren't they
To cut a long story short: If you don't like how people on Pleroma, Akkoma, Misskey, Iceshrimp-JS, Iceshrimp.NET, Sharkey, CherryPick, micro.blog, GoToSocial, snac, Hollo, Mitra, Socialhome, Friendica, Hubzilla, (streams), Forte, Lemmy, /kbin, Mbin, PieFed etc. behave, how they refuse to use their software like Mastodon and only like Mastodon, then go block their servers. I hope that option is built into the official Mastodon app.
# # # # # # # # # # # # # # # # # # # # # # Also, it seems like you're using Mastodon on a phone with the official Mastodon app.
However, unlike on commercial services, Mastodon's official app is not the one fully featured reference app. It's actually just about the worst Mastodon app. It only exists so that Mastodon newbies can start by loading an app named "Mastodon" from the Apple App Store or the Google Play Store.
It's also the only Mastodon app that can only show long posts at their full length. All third-party apps roll long posts in.
If you're on an iPhone, check , or .
If you're on Android, check or .
You'll probably discover all-new features of which you didn't know that Mastodon has them.
# # # # # # # # # # # # # # # # # # # # # # # # # # # If you really want to go for quality, what's needed is some automated system that checks each image post for
Any image post that breaks any of these mustn't count into the statistics as properly described.
# # # # # # # # # # # # # # # # # # # # #
Ein anderer ist, weil das, worber ich mit Bildern poste, so obskur ist, da keine KI darber genug wei, um die Bilder akkurat beschreiben, geschweige denn erklren zu knnen.
Genau zweimal habe ich mir Bildbeschreibungen von einer KI generieren lassen. Und das war, um aufzuzeigen, wie hoffnungslos untauglich KI ist, um meine Bilder adquat zu beschreiben, fr diejenigen, die der felsenfesten Ansicht sind, KI kann ausnahmslos jedes Bild perfekt beschreiben.
# # # # # # # # # # # # #
Good Too long Still not sufficiently detailed If the latter, then rest assured: When the alt-text announces an additional, much longer image description in the message text, then there actually is one.
That is, nowadays, my goal is to limit my alt-texts to a maximum of 512 characters. That's because if a post with a longer alt-text arrives on Misskey or Iceshrimp-JS or Sharkey or another Misskey fork, then the alt-text is deleted without any trace. It will look like there has never been any alt-text to begin with.
When I post memes, it's usually easier to keep alt-texts shorter. The tricky part is to still have all the text transcripts in the alt-text because I only write one visual description for each of my meme images unless it's based on a virtual world rendering. I do give some explanations in my meme posts, though.
These two are very recent:
# # # # # # # # # # # # # # # # # #
Here on Hubzilla, they aren't even a thought, also because Hubzilla doesn't know the concept of images having their own dedicated alt-text database field. (Before you ask: Hubzilla handles images and therefore alt-texts in messages vastly differently from Mastodon to begin with.)
At the same time, more and more Mastodon users are acting like image descriptions for the images in the link previews that are generated automatically in Mastodon timelines are becoming mandatory Fediverse-wide. Never mind that Mastodon itself has barely got enough character capacity to describe these preview images at the high level of detail that so many Mastodon users love, what with its meagre default character limit of 500.
Also, never mind that you'll have to edit your post to describe the preview image because it only appears after you've tooted your toot, so you can't see it before you toot your toot.
Also, never mind that everyone outside Hubzilla will get an image description for an image that's entirely absent because they don't have Mastodon-style link previews, because these link previews are a Mastodon-only thing.
Again, this is even worse here on Hubzilla. Unlike Mastodon, Hubzilla has a preview button that lets you look at your message before you actually send it. But Hubzilla doesn't generate link previews. And Hubzilla's preview button doesn't offer you the option to show you what your message will look like on Mastodon.
So I'd have to
All just to describe an image that isn't even there for my fellow Hubzilla users. Nor is it there for my contacts on Friendica, (streams), Forte, Misskey, Iceshrimp-JS, Iceshrimp.NET, Sharkey, Pleroma, Akkoma, snac2, GoToSocial, Hollo, Socialhome, Mitra, PieFed, Wafrn etc.
By the way, if a message comes from something else than Mastodon, and there's no actual link in it, Mastodon often creates a link preview for the profile or channel page of whoever has sent the message and picks their profile photo as the image for the link preview. Essentially, I'd have to reliably know when Mastodon does that, write two image descriptions for my profile photo (it's a rendering from OpenSim, and I always describe these twice besides, people should have a shorter description next to my usual detailed description) and copy-paste both into each post for which Mastodon will generate a link preview for my channel page.
Fortunately, Mastodon doesn't show Hubzilla profiles or channels like Hubzilla itself shows them, and neither do Mastodon apps. Otherwise, if Mastodon users figure out that the background image of my channel is part of my channel customisation and not a default Hubzilla Web UI element, they may demand I add an alt-text for the background image, lest I be mass-blocked as an ableist.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # #More and more Mastodon users are acting like alt-texts for profile images are becoming mandatory Fediverse-wide. Never mind that they're currently being rolled out by and by and only on Mastodon even.
Here on Hubzilla, they aren't even a thought, also because Hubzilla doesn't know the concept of images having their own dedicated alt-text database field. (Before you ask: Hubzilla handles images and therefore alt-texts in messages vastly differently from Mastodon to begin with.)
At the same time, more and more Mastodon users are acting like image descriptions for the images in the link previews that are generated automatically in Mastodon timelines are becoming mandatory Fediverse-wide. Never mind that Mastodon itself has barely got enough character capacity to describe these preview images at the high level of detail that so many Mastodon users love, what with its meagre default character limit of 500.
Also, never mind that you'll have to edit your post to describe the preview image because it only appears after you've tooted your toot, so you can't see it before you toot your toot.
Also, never mind that everyone outside Hubzilla will get an image description for an image that's entirely absent because they don't have Mastodon-style link previews, because these link previews are a Mastodon-only thing.
Again, this is even worse here on Hubzilla. Unlike Mastodon, Hubzilla has a preview button that lets you look at your message before you actually send it. But Hubzilla doesn't generate link previews. And Hubzilla's preview button doesn't offer you the option to show you what your message will look like on Mastodon.
So I'd have to
All just to describe an image that isn't even there for my fellow Hubzilla users. Nor is it there for my contacts on Friendica, (streams), Forte, Misskey, Iceshrimp-JS, Iceshrimp.NET, Sharkey, Pleroma, Akkoma, snac2, GoToSocial, Hollo, Socialhome, Mitra, PieFed, Wafrn etc.
By the way, if a message comes from something else than Mastodon, and there's no actual link in it, Mastodon often creates a link preview for the profile or channel page of whoever has sent the message and picks their profile photo as the image for the link preview. Essentially, I'd have to reliably know when Mastodon does that, write two image descriptions for my profile photo (it's a rendering from OpenSim, and I always describe these twice besides, people should have a shorter description next to my usual detailed description) and copy-paste both into each post for which Mastodon will generate a link preview for my channel page.
Fortunately, Mastodon doesn't show Hubzilla profiles or channels like Hubzilla itself shows them, and neither do Mastodon apps. Otherwise, if Mastodon users figure out that the background image of my channel is part of my channel customisation and not a default Hubzilla Web UI element, they may demand I add an alt-text for the background image, lest I be mass-blocked as an ableist.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
I mean, yes, some of them are on Mastodon. But not all Fediverse actors that at least sometimes appear in several instances are on Mastodon.
See, certain non-Mastodon Fediverse server software has a feature called "nomadic identity" (). This makes it possible to create clones (live backups sync'd bidirectionally against each other in real time) of one's identity with everything attached to it on other servers. First and foremost, it's Hubzilla ( ) that offers this feature, and it has since 2012.
What you see in this case is not two separate Fediverse identities, one of which is an automated reposter bot. It's one cloned nomadic identity, only that Mastodon can't understand it as such because it lacks the technical means to do so.
The idea behind this is resilience by redundancy: One server with your identity goes down, and you lose nothing because you still have the exact self-same identity with everything on at least one other server. Even if that server goes back online, the instance of your identity on it catches up with the others. The whole concept was born from Friendica servers disappearing and their users losing everything.
Fediverse server applications that know nomadic identity see all instances of a cloned identity as one and the same identity.
But Fediverse server applications like Mastodon that don't know nomadic identity see them as separate Fediverse accounts with separate identities.
For example, the Hubzilla channel that I'm replying from right now has one clone, so it has two instances. Mastodon understands them as two individual accounts. So do all Mastodon users, also because the huge majority of them has never heard of nomadic identity.
Thus, there are Mastodon users who follow both my main instance and my clone because they think these are two separate accounts. And now they end up receiving each one of my posts twice. Also, the federated timeline of the Mastodon server that they're on lists each one of my posts twice.
The latter also happens when one user on any given Mastodon server follows my main instance, and another user follows my clone.
Most Mastodon users, upon seeing my posts twice, will assume that I'm running some automated reposting bot (technically speaking, I could, but I don't) that serves to a) increase my reach and b) circumvent mutes and blocks. At least some may be tempted to block both my original instance and my clone.
# # # # # # # # # # # # #
For example, I have this Hubzilla channel here cloned across two Hubzilla hubs: hub.netzgemeinde.eu and hub.hubzilla.de.
A Hubzilla account requires an e-mail address and a password. It can be different on different hubs, and in fact, it should. I may or may not use different passwords on these two hubs.
But the account only serves as a login, as an access to the channel(s) hosted on them. It has nothing to do with my identity. Thus, it also does not know or use my short name.
Nonetheless, on these two independent accounts which may or may not have completely different login credentials, I have two instances of this Hubzilla channel here which are (or should be) constantly kept perfectly identical to one another. (In fact, I have another channel with a separate identity that's cloned across the same two hubs. Nomadic identity at Hubzilla/(streams)/Forte level comes with the side-effect that you can have what amounts to multiple separate Mastodon accounts, but all under the same login.)
So you can use the same e-mail address and the same password. But you don't have to. And, truth be told, you really shouldn't.
# # # # # # # # # # You don't even have to build it. It already exists in the Fediverse. No need to reinvent the wheel.
Hubzilla, (streams) and forte offer you not only full nomadic identity, but also groups. Optionally private groups. That can optionally hide from Fediverse account/channel directories. Optionally with any number of moderators from anywhere on Friendica, Hubzilla, (streams) and Forte.
They have the most advanced permissions systems in the whole Fediverse.
They support enclosed threaded one-post-many-comments conversations with thread titles like on Facebook, like on Tumblr, like on any blog out there, like in any forum out there.
The character limit on Hubzilla is over 16 million on (streams) and Forte, it's over 24 million. The number of options in polls is practically unlimited, as is the number of images that can be embedded in messages. And with "embedded," I mean like in a blog post or on a website with text above and below the images.
At the same time, they're part of the Fediverse. Hubzilla is based on Zot6/an older version of Nomad ActivityPub can be activated. (streams) is based on Nomad ActivityPub is optional, but activated by default. Forte is based on ActivityPub. Any Fediverse software that recognises groups recognises their groups as such.
Here is an article with a number of tables in which I've compared the features of Mastodon, Friendica, Hubzilla, (streams) and Forte:
.
CC:
# # # # # # # # # # # # # # # # A whole lot. Sorry, but this will be very very very long again.
I don't know if you've read my previous (very long) commentary. But just implementing one or two FEPs won't get you the same full-blown nomadic identity () that Hubzilla (what I'm writing from right now ) has had since 2012. And having this level of nomadic identity has to be the goal.
What has to be done is:
Take something like Mastodon.
Non-nomadic.
Where your account, your login, equals your identity.
Now, before you can make identities nomadic, you have to uncouple them from the login, from the account.
Mastodon has to introduce a sort of container for your identity, like the channels that Hubzilla, (streams) and Forte have always had (). This is necessary so that a future nomadic Mastodon will know what to clone and what not to clone. For example, cloning your password is dangerous nonsense.
So, everything that makes up your account except for your login credentials will have to be moved into this container.
Also, your login will have to change from short name + passphrase to e-mail + passphrase. Your short name is part of your identity, it's in the container, it will be cloned, so it can't be used to log you in anymore.
In order for this to work, half of Mastodon's server backend will have to be rewritten.
Next, Mastodon must switch from the Webfinger IDs that it uses now to decentralised IDs as per FEP-ef61. For a while, I guess, it will have to use both next to one another. Then it will have to phase out its Webfinger IDs.
The decentralised IDs must be tested against other Fediverse software that already understands them or that's nomadic itself: (streams), Forte, Mitra, Tootik. For example, of Mitra and of (streams) and Forte must test whether their software correctly understands Mastodon's DIDs. And the Mastodon developers must test whether Mastodon correctly understands the DIDs from Fediverse server applications that already use them.
Once it has gotten rid of its Webfinger IDs, the next phase can start.
The central element of nomadic identity is not the ability to move your identity. That's only a byproduct of cloning your identity.
A clone, in nomadic identity, is a full backup of the container with your identity in it. A real-time, live, bidirectional backup that you can log into and use just like the "original". The clone always has the same idea as the original, regardless of which server it's on.
The key elements of clones and cloning must be implemented and tested:
Only when cloning works reliably, we can talk about moving, even though that's what everyone on Mastodon is giddy about.
Why Because moving involves cloning. It's an automated process. At least it is on Hubzilla, (streams) and Forte, and it really should be one on nomadic Mastodon.
Basically, first you make a clone.
Then you declare the clone the new original, and your old original is demoted to a clone.
Then you have to wait until your change of ID from changing the original has federated to all your followers and followed and everywhere and whatnot.
Then, one last sync so that both the former-clone-now-new-original and the old-original-now-clone are really identical, and you won't lose any data.
Then your old-original-now-clone is deleted. We don't want to leave any dead stuff behind, now, do we
Lastly, if your old account where your old original used to reside has no other identity on it, the whole account is deleted. In nomadic containerised identity, accounts cannot/should not exist with no identity container on them.
The last possible step is still utter science-fiction: Cloning or moving from Mastodon to something else that's nomadic and understands FEP-ef61.
Cloning or moving from Mastodon to Mitra. From Mastodon to Tootik. From Mastodon to (streams). From Mastodon to Forte. Oh, and maybe also back to Mastodon.
The difficult part is not only to make Mastodon capable of cloning identity containers to other nomadic software. And to make Mastodon accept identity containers from other nomadic software being cloned to Mastodon. I mean, this would be difficult already. (streams) and Forte are vastly, vastly different from Mastodon.
No, the difficult part is to make these four capable of cloning from or to someplace else. As it stands now, you can only clone from Mitra to Mitra, from Tootik to Tootik, from (streams) to (streams), from Forte to Forte. Even cloning between (streams) and Forte has never been possible, even though they're very similar. Oh, and cloning from and to Hubzilla is another story because Hubzilla doesn't have FEP-ef61 implemented.
# # # # # # # # # # # # # # # # #
One, the "normie" way. Follow everyone you come across, and hope that something interesting washes up.
Trouble is, this gives you .1% interesting content and 99.9% cruft. The interesting content is spread among the cruft pretty homogenously.
At the same time, you get tons of content. You'll only be able to scroll down your timeline, let's say, an hour's worth of content a day, and you'll miss the content from the other 23 hours. This also means that you only catch one out of 24 interesting messages on average.
Two, the "pro" way. Use the hashtag search to find people who post certain content and follow them.
Trouble is, they, too, aren't always specialised in that content. From your point of view, they, too, post cruft. Your signal-to-noise ratio is higher, but you still get more noise than signal, more cruft than interesting content.
Now, there's a trick that many Mastodon users don't know because doesn't have that feature: You can follow hashtags.
If you're interested in certain topics, find the corresponding hashtags (it's often more than one) and follow them. This way, you receive content with these hashtags from whoever posts content with these hashtags, but without the uninteresting cruft from the same users.
# # # # # # # # # # # # # #
Have you read about nomadic identity yet ()
There is only one Fediverse server application that offers full-blown server-side nomadic identity via ActivityPub, and that's Forte (). This won't change anytime soon. For there is one critically important thing that has never happened yet, and that's the conversion of non-nomadic, account-equals-identity, ActivityPub-based Fediverse software to fully nomadic, identity-uncoupled-from-accounts, ActivityPub-based Fediverse software.
Forte itself came to exist in 2024 as a fork of something colloquially called (streams) which is already nomadic, but based on its own protocol named Nomad with ActivityPub as an optional secondary protocol. And (streams) is a fork of a fork of three forks of a fork (of a fork) of Hubzilla, the first nomadic Fediverse software, created in 2012 under the name Red and based on a precursor of Nomad.
A very long-term dream is a fully nomadic Fediverse. Not only would all Fediverse server software be every bit as nomadic as Hubzilla, but it'd be possible to move and even clone identities between different server applications. As it stands now, moving and cloning is only possible within Hubzilla, within (streams) and within Forte.
This would only be possible in an entirely nomadic Fediverse where you can clone your identity from anywhere to anywhere. And even then you'd have to first register a local account on whichever server you want to use and then clone your existing identity onto this account on this server.
Otherwise, this is not possible. And it isn't possible at all without registering a local account on whichever server you want to create.
I mean, I've read this request countless times.
There are lots of reasons why this is technologically impossible.
First of all: Where would peertube.tv know your mastodon.social login credentials from Your name and at least the salted hash of your passphrase
Besides: Where would peertube.tv store your data
On mastodon.social where your account is
And, pray tell, where would mastodon.social store a video the same way as PeerTube stores it, all the way to PeerTube's trademark peer-to-peer load balancing Also, how and why do you think should mastodon.social authorise peertube.tv to directly, remotely write to mastodon.social's local database and data storage
On peertube.tv
Well, that'd require peertube.tv to have a record of your identity in its local database. It can't store a video locally. and reference it locally through mastodon.social's local database. So peertube.tv's server backend would have to know you. It would have to have your identity.
Where would it get that
Again, no, it can't just simply reference mastodon.social's database for that. It'd need that record in its own local database.
Do you really believe that peertube.tv could go and leech all your account credentials from mastodon.social and automagically store them locally Do you really believe mastodon.social will let it do that
And do you seriously believe that if free, open-source, amateur-developed server software can easily do that, proprietary, closed-source, professional, military-intelligence-grade (as in FBI, DHS, CIA, NSA, STRATFOR, MI5, MI6, Mossad, Shin Bet), ultra-high-end espionage and surveillance software like Palantir or NSO Pegasus has no way at all of doing that
No, there's literally only one possible way for peertube.tv to get to know you and know whom this video belongs to if you upload one. And that's by you registering a local account on peertube.tv. Manually.
Okay, now you (or someone else) may come and say, "But Pixelfed can literally do that! I can log onto Pixelfed with my Mastodon account!"
No. No, you can't. Sorry to say, but you can't.
Pixelfed pretends you can. For the sake of convenience and ease-of-use. But it's bogus. All show. A smoke screen.
What Pixelfed actually does when you "log into it with your Mastodon account": It takes your Mastodon login name, it takes your Mastodon passphrase, and it registers a local account on that Pixelfed server with your Mastodon login credentials.
# # # # # # # # # # # # # # # # #
If you click an image without an alt-text that came from e.g. Misskey or Sharkey or Akkoma or GoToSocial or snac2 or Friendica or Hubzilla or Pixelfed or Vernissage or PieFed (anywhere that isn't Mastodon) and suggest an alt-text, the original poster won't see your suggestion. All those who think that if they see it on Mastodon, it came from Mastodon, will believe the original poster is an ableist swine who intentionally ignores them and their suggestion.
So Mastodon must acknowledge where a message came from, it must know whether or not that software has this feature built in, and if the software doesn't have this feature built in, Mastodon must fully deactivate the alt-text suggestion feature.
# # # # # # # # # # # # # #
Mastodon and its users rule supreme over the Fediverse. After all, the Fediverse was invented by Gargron. It started when Mastodon started, and everything that isn't Mastodon just latched onto Mastodon and its Fediverse.
Mastodon users are the only civilised users in the Fediverse, the only ones with something like a culture. The Fediverse culture is Mastodon's culture as defined in the spring of 2022. All those who don't live by Mastodon's culture are uncivilised, uneducated, savage barbarians. And it isn't just the Mastodon users' right and privilege to educate them and shape them into good Mastodon users, it's their duty.
Even when it turns out that these barbarians aren't even on Mastodon, that they're on something that's very much not Mastodon, they can't possibly have a culture of their own. After all, they don't live by Mastodon's culture, and if it isn't Mastodon's culture, it isn't culture at all. Not even if it predates Mastodon's current culture by over a decade like Friendica's culture does.
Of course, this also means that when non-Mastodon users come and give Mastodon users unsolicited "advice" or recommend them to use Mastodon in a certain way that goes against Mastodon's culture, the Mastodon users are fully justified to silence them by any means available.
What this means:
When a Mastodon user uses "Fediverse" and "Mastodon" mutually synonymously, it's the right thing to do because that's part of Mastodon's culture. And it makes things easier to understand.
When a non-Mastodon user explains that the Fediverse is not only Mastodon, and that "Fediverse" and "Mastodon" do not mean the same, it's evil and intrusive and deeply disturbing.
When a Mastodon user refers to any message in the Fediverse as a "toot", it's the right thing to do because that's part of Mastodon's culture.
When a Misskey or Forkey user talks about "notes", it's irritating. When a Friendica or Hubzilla or (streams) or Forte user distinguishes between "posts" and "comments", it has even less of a place in the Mastodon Fediverse.
Features that only Mastodon has are actually mandatory for the whole Fediverse. Any Fediverse server software that hasn't got these features implemented in exactly the same way as Mastodon is broken.
Features in non-Mastodon Fediverse server software that Mastodon doesn't have are wrong and evil and not allowed to be used.
Mastodon users are allowed, justified and expected to tell non-Mastodon users to limit their posts to no more than 500 characters. It especially disturbs those who refuse to move away from the official Mastodon phone app.
Non-Mastodon users are not allowed to tell Mastodon users to not cut their long posts into threads.
Mastodon users are allowed, justified and expected to tell non-Mastodon users to put content warnings into their summary/abstract field.
Mastodon users are allowed, justified and expected to tell non-Mastodon users to only use their summary/abstract field for content warnings. After all, that's what Gargron invented that field for.
Non-Mastodon users are not allowed to tell non-Mastodon users that it was Evan Prodromou who invented that field as early as 2008. That he invented it as a summary field. That it was actually a Mastodon user who repurposed that field for CWs in 2017, the year after Mastodon was launched. Gargron only let it pass.
Non-Mastodon users are not allowed to use that field for anything else than CWs.
Non-Mastodon users are not allowed to add hashtags instead of CWs so that reader-side CWs can automatically be generated by filters. Even though Mastodon itself has literally introduced this very feature with version 4.0 in October, 2022.
Mastodon users are allowed, justified and expected to tell non-Mastodon users to not only write alt-texts for all the images they post, but to write them nicely long and detailed. After all, they've got 1,500 characters for alt-texts.
Misskey and Forkey users are not allowed to tell Mastodon users to limit their alt-texts to no more than 512 characters because that's the maximum that Misskey and the Forkeys accept, and on top of that, due to a bug, they delete all alt-texts longer than that. From a Misskey/Forkey point of view, writing long alt-texts is like not writing any alt-texts at all. But the Misskey/Forkey point of view is invalid in Mastodon's culture.
Mastodon users are allowed, justified and expected to toot to Lemmy any way they want, and that's the Mastodon way. If it doesn't work properly on Lemmy, then Lemmy is broken.
Lemmy users, even Lemmy moderators, and other users of Fediverse software that supports groups are not allowed to tell Mastodon users how to post to Lemmy in a way that Lemmy understands.
Mastodon users are allowed, justified and expected to even tell Lemmy users to limit their "toots" to no more than 500 characters and use hashtags, but not too many of them.
Lemmy users and even Lemmy moderators are not allowed to tell Mastodon users to stop spamming Lemmy with mentions and with hashtags that don't work on Lemmy anyway, also because both highly irritate the Lemmy users. Almost all of them came straight from Reddit after their third-party apps were killed, and almost none of them have ever been on Twitter or Mastodon.
Mastodon users and Mastodon admins are allowed and justified to block any and all non-Mastodon servers because they misbehave by Mastodon's standards.
(streams) and Forte admins are not allowed to block the entirety of Mastodon, all present and future servers, by user agent (which, by the way, they're totally capable of) because it misbehaves by their standards. Mastodon doesn't misbehave, and the Hubzilla/(streams)/Forte standards are all wrong if they differ from Mastodon's standards.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #Yeah, I get it.
Mastodon and its users rule supreme over the Fediverse. After all, the Fediverse was invented by Gargron. It started when Mastodon started, and everything that isn't Mastodon just latched onto Mastodon and its Fediverse.
Mastodon users are the only civilised users in the Fediverse, the only ones with something like a culture. The Fediverse culture is Mastodon's culture as defined in the spring of 2022. All those who don't live by Mastodon's culture are uncivilised, uneducated, savage barbarians. And it isn't just the Mastodon users' right and privilege to educate them and shape them into good Mastodon users, it's their duty.
Even when it turns out that these barbarians aren't even on Mastodon, that they're on something that's very much not Mastodon, they can't possibly have a culture of their own. After all, they don't live by Mastodon's culture, and if it isn't Mastodon's culture, it isn't culture at all. Not even if it predates Mastodon's current culture by over a decade like Friendica's culture does.
Of course, this also means that when non-Mastodon users come and give Mastodon users unsolicited "advice" or recommend them to use Mastodon in a certain way that goes against Mastodon's culture, the Mastodon users are fully justified to silence them by any means available.
What this means:
When a Mastodon user uses "Fediverse" and "Mastodon" mutually synonymously, it's the right thing to do because that's part of Mastodon's culture. And it makes things easier to understand.
When a non-Mastodon user explains that the Fediverse is not only Mastodon, and that "Fediverse" and "Mastodon" do not mean the same, it's evil and intrusive and deeply disturbing.
When a Mastodon user refers to any message in the Fediverse as a "toot", it's the right thing to do because that's part of Mastodon's culture.
When a Misskey or Forkey user talks about "notes", it's irritating. When a Friendica or Hubzilla or (streams) or Forte user distinguishes between "posts" and "comments", it has even less of a place in the Mastodon Fediverse.
Features that only Mastodon has are actually mandatory for the whole Fediverse. Any Fediverse server software that hasn't got these features implemented in exactly the same way as Mastodon is broken.
Features in non-Mastodon Fediverse server software that Mastodon doesn't have are wrong and evil and not allowed to be used.
Mastodon users are allowed, justified and expected to tell non-Mastodon users to limit their posts to no more than 500 characters. It especially disturbs those who refuse to move away from the official Mastodon phone app.
Non-Mastodon users are not allowed to tell Mastodon users to not cut their long posts into threads.
Mastodon users are allowed, justified and expected to tell non-Mastodon users to put content warnings into their summary/abstract field.
Mastodon users are allowed, justified and expected to tell non-Mastodon users to only use their summary/abstract field for content warnings. After all, that's what Gargron invented that field for.
Non-Mastodon users are not allowed to tell non-Mastodon users that it was Evan Prodromou who invented that field as early as 2008. That he invented it as a summary field. That it was actually a Mastodon user who repurposed that field for CWs in 2017, the year after Mastodon was launched. Gargron only let it pass.
Non-Mastodon users are not allowed to use that field for anything else than CWs.
Non-Mastodon users are not allowed to add hashtags instead of CWs so that reader-side CWs can automatically be generated by filters. Even though Mastodon itself has literally introduced this very feature with version 4.0 in October, 2022.
Mastodon users are allowed, justified and expected to tell non-Mastodon users to not only write alt-texts for all the images they post, but to write them nicely long and detailed. After all, they've got 1,500 characters for alt-texts.
Misskey and Forkey users are not allowed to tell Mastodon users to limit their alt-texts to no more than 512 characters because that's the maximum that Misskey and the Forkeys accept, and on top of that, due to a bug, they delete all alt-texts longer than that. From a Misskey/Forkey point of view, writing long alt-texts is like not writing any alt-texts at all. But the Misskey/Forkey point of view is invalid in Mastodon's culture.
Mastodon users are allowed, justified and expected to toot to Lemmy any way they want, and that's the Mastodon way. If it doesn't work properly on Lemmy, then Lemmy is broken.
Lemmy users, even Lemmy moderators, and other users of Fediverse software that supports groups are not allowed to tell Mastodon users how to post to Lemmy in a way that Lemmy understands.
Mastodon users are allowed, justified and expected to even tell Lemmy users to limit their "toots" to no more than 500 characters and use hashtags, but not too many of them.
Lemmy users and even Lemmy moderators are not allowed to tell Mastodon users to stop spamming Lemmy with mentions and with hashtags that don't work on Lemmy anyway, also because both highly irritate the Lemmy users. Almost all of them came straight from Reddit after their third-party apps were killed, and almost none of them have ever been on Twitter or Mastodon.
Mastodon users and Mastodon admins are allowed and justified to block any and all non-Mastodon servers because they misbehave by Mastodon's standards.
(streams) and Forte admins are not allowed to block the entirety of Mastodon, all present and future servers, by user agent (which, by the way, they're totally capable of) because it misbehaves by their standards. Mastodon doesn't misbehave, and the Hubzilla/(streams)/Forte standards are all wrong if they differ from Mastodon's standards.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # Well, then you must live with long posts being long in your timeline. Users of non-Mastodon Fediverse server software will not stop using it as intended and start using it like Mastodon just because long posts disturb the users of the official Mastodon app.
Someone who has been on Friendica since 2011, and who is absolutely using Friendica like Friendica is intended to be used, will not use Friendica like Mastodon suddenly just because Mastodon users prefer that.
I mean, what if non-Mastodon users came and told Mastodon users to stop cutting their long posts into threads What if non-Mastodon users came and told Mastodon users to use the CW field for summaries instead of CWs because that's what that field is actually for What if Friendica and Hubzilla users came and told Mastodon users to replace their CWs with hashtags so that they can have their own individual CWs automatically generated reader-side, as has been their tradition since before Mastodon was even made
I keep seeing this again and again. At first, Mastodon users perceive non-Mastodon users as users on "hacked" Mastodon servers with increased character limits who simply don't know about Mastodon's culture which includes limiting all your "toots" to no more than 500 characters. And they try to educate them how to use Mastodon properly.
Once they learn that these people are, in fact, on something else, something entirely different from Mastodon, they perceive them as barbarian, culture-less intruders into their precious Mastodon Fediverse who need to be educated about proper Mastodon behaviour nonetheless.
They think Mastodon is the one supreme ruler over the Fediverse. They think they are the ones who have the exclusive saying over how anything in the Fediverse must be used. They think they have the Gargron-given right to tell e.g. Friendica users whose culture is over a decade older than Mastodon's current culture to completely abandon their own culture and 80% of Friendica's features along with it and only live by Mastodon's culture.
At the same time, they consider requests from outside of Mastodon to change their own behaviour aggressive and intrusive and against "the Fediverse culture", read, Mastodon's culture. And then they completely fail to understand why there's so much Mastodon hatred especially on Friendica, Hubzilla, (streams) and Forte. They're the good guys, the cultured and well-behaving ones, aren't they
To cut a long story short: If you don't like how people on Pleroma, Akkoma, Misskey, Iceshrimp-JS, Iceshrimp.NET, Sharkey, CherryPick, micro.blog, GoToSocial, snac, Hollo, Mitra, Socialhome, Friendica, Hubzilla, (streams), Forte, Lemmy, /kbin, Mbin, PieFed etc. behave, how they refuse to use their software like Mastodon and only like Mastodon, then go block their servers. I hope that option is built into the official Mastodon app.
# # # # # # # # # # # # # # # # # # # # # # Also, it seems like you're using Mastodon on a phone with the official Mastodon app.
However, unlike on commercial services, Mastodon's official app is not the one fully featured reference app. It's actually just about the worst Mastodon app. It only exists so that Mastodon newbies can start by loading an app named "Mastodon" from the Apple App Store or the Google Play Store.
It's also the only Mastodon app that can only show long posts at their full length. All third-party apps roll long posts in.
If you're on an iPhone, check , or .
If you're on Android, check or .
You'll probably discover all-new features of which you didn't know that Mastodon has them.
# # # # # # # # # # # # # # # # # # # # # # # # # # # If you really want to go for quality, what's needed is some automated system that checks each image post for
- the image description's absolute accuracy, no matter how obscure whatever the image shows is
- whether all details which matter according to quite a number of criteria are described appropriately and with enough details
- whether the alt-text, after having been transcoded to a CJK character set, has 512 characters or fewer
- whether the image has an additional, more detailed and more informative description in the message text when necessary
- whether any image description, especially in the alt-text, does not start with "Image", "Graphic", "Picture" or "Photo"
- whether each image description does mention any medium that is not a digital photograph
- whether each image description is written in plain, everyday language without (unexplained) technical language and/or jargon
- whether each image description avoids things like "shows" or "can be seen" or "is visible"
- whether the alt-text does not contain any explanations (except maybe for when the alt-text itself needs explanations)
- whether the alt-text does not contain copyright or license information
- whether the alt-text does not contain author credits
- whether the alt-text generally does not contain any information that is neither present in the message text nor available to sighted users in the image
- whether the alt-text is not used to write around Mastodon's 500-character limit
- whether the text bits in the image are transcribed verbatim
- whether text in foreign languages is transcribed appropriately, considering that screen readers cannot switch to different languages mid-sentence or in the middle of reading out an alt-text (I have to find out myself what the officially appropriate way is as every last image description guideline out there assumes that there are no other languages than English)
- whether the image descriptions in general and text transcripts in particular avoid all caps
- whether all acronyms are transcribed in a way that's the most appropriate for screen readers
- whether the alt-text does not contain any hashtags except if they're part of a text transcript
- whether the alt-text does not contain any emoji except if they're part of a text transcript
- whether the alt-text does not contain links (URLs are allowed if they're part of a text transcript)
- whether the alt-text does not contain line breaks
- whether the alt-text does not contain the double quotation marks found on keyboards
- whether the location shown in the image is mentioned if appropriate and not mentioned if mentioning it wouldn't be appropriate
- whether positions are described the right way
- whether shapes are described the right way
- whether sizes and dimensions are described the right way
- whether colours are described the right way
- whether people that mustn't or shouldn't be publicly identified are not identified
- whether people and their outfits are described appropriately, taking into consideration what the target audience knows or doesn't know
- whether the body shape of a person is only described when it matters within the context, or the level of detail required by the context makes it necessary
- whether people's race is not mentioned, and they're described with one of the five skin tones available as emoji (light, medium light, medium, medium dark, dark) instead
- whether people's gender is only mentioned either if they themselves have declared it openly, and this declaration can be sourced, or if they act out a certain gender in the image in other words, whether people's gender is not assumed in the image description
Any image post that breaks any of these mustn't count into the statistics as properly described.
# # # # # # # # # # # # # # # # # # # # #
New post: The Account Nobody Can Deposit To
-Accounts -Term-Care
<>
Long
<>
Einer der Grnde, warum alle meine Bildbeschreibungen und -erklrungen 100% handgeschrieben sind, egal, wie lang und detailliert sie sind.Ein anderer ist, weil das, worber ich mit Bildern poste, so obskur ist, da keine KI darber genug wei, um die Bilder akkurat beschreiben, geschweige denn erklren zu knnen.
Genau zweimal habe ich mir Bildbeschreibungen von einer KI generieren lassen. Und das war, um aufzuzeigen, wie hoffnungslos untauglich KI ist, um meine Bilder adquat zu beschreiben, fr diejenigen, die der felsenfesten Ansicht sind, KI kann ausnahmslos jedes Bild perfekt beschreiben.
# # # # # # # # # # # # #
Staartmees met felgekleurde oogring...
Long tailed tit with colorfull eyestripe...
, -tailedtit
,
<>
New post: Becoming
-Illness -Term-Care -Growth
Here are a few older alt-texts that I've written for original images of my own.Digital shaded rendering of the main building of the Universal Campus, a downloadable island location for 3-D virtual worlds based on OpenSimulator. The camera position is about three metres or ten feet above the ground. The camera is tilted slightly upward and rotated slightly to the left from the building's longitudinal axis. The futuristic building is over 200 metres long, stretching far into the distance, and its front is about 50 metres wide. Its structure is mostly textured to resemble brushed stainless steel, and almost everything in-between is grey tinted glass. The main entrance of the building in the middle of the front has two pairs of glass doors. They are surrounded by a massive complex geometrical structure, very roughly reminiscent of a vintage video game spacecraft with the front facing upward. Four huge cylindrical pillars carry the roof end, the outer two of which extend beyond it. All are tilted away from the landing area in front of the building and at the same time outward to the sides. The sides of the building are slightly tilted themselves. In the distance, a large geodesic dome rises from the building. There is a large circular area in front of the main entrance as well as several wide paths. They have light concrete textures, and they are lined with low walls with almost white concrete textures. Furthermore, various shrubs and trees decorate the scenery. A more detailed description including explanations and text transcripts can be found in the post.
Digital rendering from OSgrid, one of the biggest out of thousands of 3-D virtual worlds based on OpenSimulator. It shows Juno Rowland, a female avatar, standing at the end of a wooden pier with the ocean in the background. The avatar is designed to resemble a woman who is no older than in her 30s. She is slim underneath loose-fitting clothes. She has light to medium-light skin, brown eyes and black hair which is styled as a neck-long bob. She is wearing a black tank top with the logo of the 17th birthday of OSgrid on it, a straight, lower-thigh-length, light-to-medium-light-brown denim miniskirt, a pair of black flat ballet shoes and a golden necklace with the OSgrid logo. The OSgrid logo is made up from five identical parallelograms arranged in a circular, star-like pattern. It is also part of the birthday logo which is mostly two tones of yellowish orange. The writing on the birthday logo reads, from top to bottom, OSgrid, The Open Source Metaverse and 17th Birthday. A more detailed description of the image, including explanations, can be found in the post itself. If you are on Mastodon, Misskey or one of their forks, you can find it by opening the summary and content warning which includes, CW: long (22,270 characters, including 20,377 characters of image descriptions), eye contact, and then following the actual post text. If you are on Pleroma, Akkoma, another Pleroma fork, Friendica, Hubzilla or (streams), the full description will follow right after the images.
Digital rendering from OSgrid, one of the biggest out of thousands of 3-D virtual worlds based on OpenSimulator. It shows Juno Rowland, a female avatar, standing at the end of a wooden pier with the ocean in the background. The avatar is designed to resemble a woman who is no older than in her 30s. She is slim underneath loose-fitting clothes. She has light to medium-light skin and black hair which is styled as a neck-long bob. She is wearing a black tank top, a straight, lower-thigh-length, light-to-medium-light-brown denim miniskirt, a pair of black flat ballet shoes and a golden necklace. She is looking at the cover of the Leonard Cohen album Recent Songs on a white easel. The cover is a painting of the musician's face. He is shown to be a middle-aged man with light skin, green eyes and black hair in a black shirt. A hummingbird is drawn hovering above his shoulder to the left. The background is medium blue. Cohen's name and the album title are written in the top corners. A more detailed description of the image, including explanations, can be found in the post itself. If you are on Mastodon, Misskey or one of their forks, you can find it by opening the summary and content warning which includes, CW: long (22,270 characters, including 20,377 characters of image descriptions), eye contact, and then following the actual post text. If you are on Pleroma, Akkoma, another Pleroma fork, Friendica, Hubzilla or (streams), the full description will follow right after the images.
Good Too long Still not sufficiently detailed If the latter, then rest assured: When the alt-text announces an additional, much longer image description in the message text, then there actually is one.
That is, nowadays, my goal is to limit my alt-texts to a maximum of 512 characters. That's because if a post with a longer alt-text arrives on Misskey or Iceshrimp-JS or Sharkey or another Misskey fork, then the alt-text is deleted without any trace. It will look like there has never been any alt-text to begin with.
When I post memes, it's usually easier to keep alt-texts shorter. The tricky part is to still have all the text transcripts in the alt-text because I only write one visual description for each of my meme images unless it's based on a virtual world rendering. I do give some explanations in my meme posts, though.
These two are very recent:
Image macro, based on a screen capture from the Disney and Pixar animated film Finding Nemo. At the top, there is a white space with a two-line caption: OSgrid: offline for weeks to come, and Owners of other grids, looking at OSgrid residents:. In the screen capture below, ten seagulls are perched on two mooring lines in the background. An eleventh seagull pokes its head into the image from the bottom right. They all look at the camera. Each one is labelled with the question, Mine
Image macro, based on a screen capture from the animated film Finding Nemo. At the top, there is a white space with a two-line caption: Fediverse admin: announces the end of their instance and asks their users to migrate to other instances, and Admins of other instances:. In the screen capture below, ten seagulls are perched on two mooring lines. An eleventh seagull pokes its head into the image from the bottom right. They all look at the camera. Each one is labelled with the question, Mine
# # # # # # # # # # # # # # # # # #
Switching from Benzodiazepine Sleep Medications to Newer Drugs: Timing Is Everything, Study Finds
Stay curious follow .
More and more Mastodon users are acting like alt-texts for profile images are becoming mandatory Fediverse-wide. Never mind that they're currently being rolled out by and by and only on Mastodon even.Here on Hubzilla, they aren't even a thought, also because Hubzilla doesn't know the concept of images having their own dedicated alt-text database field. (Before you ask: Hubzilla handles images and therefore alt-texts in messages vastly differently from Mastodon to begin with.)
At the same time, more and more Mastodon users are acting like image descriptions for the images in the link previews that are generated automatically in Mastodon timelines are becoming mandatory Fediverse-wide. Never mind that Mastodon itself has barely got enough character capacity to describe these preview images at the high level of detail that so many Mastodon users love, what with its meagre default character limit of 500.
Also, never mind that you'll have to edit your post to describe the preview image because it only appears after you've tooted your toot, so you can't see it before you toot your toot.
Also, never mind that everyone outside Hubzilla will get an image description for an image that's entirely absent because they don't have Mastodon-style link previews, because these link previews are a Mastodon-only thing.
Again, this is even worse here on Hubzilla. Unlike Mastodon, Hubzilla has a preview button that lets you look at your message before you actually send it. But Hubzilla doesn't generate link previews. And Hubzilla's preview button doesn't offer you the option to show you what your message will look like on Mastodon.
So I'd have to
- write and send my message as usual
- switch to a tab with mastodon.social
- look for my message by using the hashtag search
- check whether Mastodon has generated a link preview, and if so, which image it has chosen
- find a copy of the image with the highest resolution possible
alternatively, if it's an in-world image from OpenSim, log into OpenSim, travel to that place and take a close look at the place to write a highly detailed image description (takes from five hours to two days) - switch back to my Hubzilla tab
- edit my message
- add the image description
- re-count the characters in the message
- edit the message
- add a long post content warning with the current character count if there is none, and it isn't a comment edit the character count of the existing long post content warning if there already is one
- save the edit
- discover that Mastodon hasn't recognised my edit as such, and now there are two copies of the same message on Mastodon, the old one without the image description and the new, longer one with the image description
All just to describe an image that isn't even there for my fellow Hubzilla users. Nor is it there for my contacts on Friendica, (streams), Forte, Misskey, Iceshrimp-JS, Iceshrimp.NET, Sharkey, Pleroma, Akkoma, snac2, GoToSocial, Hollo, Socialhome, Mitra, PieFed, Wafrn etc.
By the way, if a message comes from something else than Mastodon, and there's no actual link in it, Mastodon often creates a link preview for the profile or channel page of whoever has sent the message and picks their profile photo as the image for the link preview. Essentially, I'd have to reliably know when Mastodon does that, write two image descriptions for my profile photo (it's a rendering from OpenSim, and I always describe these twice besides, people should have a shorter description next to my usual detailed description) and copy-paste both into each post for which Mastodon will generate a link preview for my channel page.
Fortunately, Mastodon doesn't show Hubzilla profiles or channels like Hubzilla itself shows them, and neither do Mastodon apps. Otherwise, if Mastodon users figure out that the background image of my channel is part of my channel customisation and not a default Hubzilla Web UI element, they may demand I add an alt-text for the background image, lest I be mass-blocked as an ableist.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # #More and more Mastodon users are acting like alt-texts for profile images are becoming mandatory Fediverse-wide. Never mind that they're currently being rolled out by and by and only on Mastodon even.
Here on Hubzilla, they aren't even a thought, also because Hubzilla doesn't know the concept of images having their own dedicated alt-text database field. (Before you ask: Hubzilla handles images and therefore alt-texts in messages vastly differently from Mastodon to begin with.)
At the same time, more and more Mastodon users are acting like image descriptions for the images in the link previews that are generated automatically in Mastodon timelines are becoming mandatory Fediverse-wide. Never mind that Mastodon itself has barely got enough character capacity to describe these preview images at the high level of detail that so many Mastodon users love, what with its meagre default character limit of 500.
Also, never mind that you'll have to edit your post to describe the preview image because it only appears after you've tooted your toot, so you can't see it before you toot your toot.
Also, never mind that everyone outside Hubzilla will get an image description for an image that's entirely absent because they don't have Mastodon-style link previews, because these link previews are a Mastodon-only thing.
Again, this is even worse here on Hubzilla. Unlike Mastodon, Hubzilla has a preview button that lets you look at your message before you actually send it. But Hubzilla doesn't generate link previews. And Hubzilla's preview button doesn't offer you the option to show you what your message will look like on Mastodon.
So I'd have to
- write and send my message as usual
- switch to a tab with mastodon.social
- look for my message by using the hashtag search
- check whether Mastodon has generated a link preview, and if so, which image it has chosen
- find a copy of the image with the highest resolution possible
alternatively, if it's an in-world image from OpenSim, log into OpenSim, travel to that place and take a close look at the place to write a highly detailed image description (takes from five hours to two days) - switch back to my Hubzilla tab
- edit my message
- add the image description
- re-count the characters in the message
- edit the message
- add a long post content warning with the current character count if there is none, and it isn't a comment edit the character count of the existing long post content warning if there already is one
- save the edit
- discover that Mastodon hasn't recognised my edit as such, and now there are two copies of the same message on Mastodon, the old one without the image description and the new, longer one with the image description
All just to describe an image that isn't even there for my fellow Hubzilla users. Nor is it there for my contacts on Friendica, (streams), Forte, Misskey, Iceshrimp-JS, Iceshrimp.NET, Sharkey, Pleroma, Akkoma, snac2, GoToSocial, Hollo, Socialhome, Mitra, PieFed, Wafrn etc.
By the way, if a message comes from something else than Mastodon, and there's no actual link in it, Mastodon often creates a link preview for the profile or channel page of whoever has sent the message and picks their profile photo as the image for the link preview. Essentially, I'd have to reliably know when Mastodon does that, write two image descriptions for my profile photo (it's a rendering from OpenSim, and I always describe these twice besides, people should have a shorter description next to my usual detailed description) and copy-paste both into each post for which Mastodon will generate a link preview for my channel page.
Fortunately, Mastodon doesn't show Hubzilla profiles or channels like Hubzilla itself shows them, and neither do Mastodon apps. Otherwise, if Mastodon users figure out that the background image of my channel is part of my channel customisation and not a default Hubzilla Web UI element, they may demand I add an alt-text for the background image, lest I be mass-blocked as an ableist.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
et dun en garde vue depuis le dbut de la guerre, selon un rapport de relay par .
, .
<>
Are you absolutely certain that they are all Mastodon accounts Have you checked their profiles at the sources (in a Web browser, in case you're on a phone with a dedicated Mastodon app) and seen a Mastodon profile pageI mean, yes, some of them are on Mastodon. But not all Fediverse actors that at least sometimes appear in several instances are on Mastodon.
See, certain non-Mastodon Fediverse server software has a feature called "nomadic identity" (). This makes it possible to create clones (live backups sync'd bidirectionally against each other in real time) of one's identity with everything attached to it on other servers. First and foremost, it's Hubzilla ( ) that offers this feature, and it has since 2012.
What you see in this case is not two separate Fediverse identities, one of which is an automated reposter bot. It's one cloned nomadic identity, only that Mastodon can't understand it as such because it lacks the technical means to do so.
The idea behind this is resilience by redundancy: One server with your identity goes down, and you lose nothing because you still have the exact self-same identity with everything on at least one other server. Even if that server goes back online, the instance of your identity on it catches up with the others. The whole concept was born from Friendica servers disappearing and their users losing everything.
Fediverse server applications that know nomadic identity see all instances of a cloned identity as one and the same identity.
But Fediverse server applications like Mastodon that don't know nomadic identity see them as separate Fediverse accounts with separate identities.
For example, the Hubzilla channel that I'm replying from right now has one clone, so it has two instances. Mastodon understands them as two individual accounts. So do all Mastodon users, also because the huge majority of them has never heard of nomadic identity.
Thus, there are Mastodon users who follow both my main instance and my clone because they think these are two separate accounts. And now they end up receiving each one of my posts twice. Also, the federated timeline of the Mastodon server that they're on lists each one of my posts twice.
The latter also happens when one user on any given Mastodon server follows my main instance, and another user follows my clone.
Most Mastodon users, upon seeing my posts twice, will assume that I'm running some automated reposting bot (technically speaking, I could, but I don't) that serves to a) increase my reach and b) circumvent mutes and blocks. At least some may be tempted to block both my original instance and my clone.
# # # # # # # # # # # # #
<>
Well, nomadic identity, as it is, does not use the same login credentials on all servers. That'd be a security risk.For example, I have this Hubzilla channel here cloned across two Hubzilla hubs: hub.netzgemeinde.eu and hub.hubzilla.de.
A Hubzilla account requires an e-mail address and a password. It can be different on different hubs, and in fact, it should. I may or may not use different passwords on these two hubs.
But the account only serves as a login, as an access to the channel(s) hosted on them. It has nothing to do with my identity. Thus, it also does not know or use my short name.
Nonetheless, on these two independent accounts which may or may not have completely different login credentials, I have two instances of this Hubzilla channel here which are (or should be) constantly kept perfectly identical to one another. (In fact, I have another channel with a separate identity that's cloned across the same two hubs. Nomadic identity at Hubzilla/(streams)/Forte level comes with the side-effect that you can have what amounts to multiple separate Mastodon accounts, but all under the same login.)
So you can use the same e-mail address and the same password. But you don't have to. And, truth be told, you really shouldn't.
# # # # # # # # # # You don't even have to build it. It already exists in the Fediverse. No need to reinvent the wheel.
Hubzilla, (streams) and forte offer you not only full nomadic identity, but also groups. Optionally private groups. That can optionally hide from Fediverse account/channel directories. Optionally with any number of moderators from anywhere on Friendica, Hubzilla, (streams) and Forte.
They have the most advanced permissions systems in the whole Fediverse.
They support enclosed threaded one-post-many-comments conversations with thread titles like on Facebook, like on Tumblr, like on any blog out there, like in any forum out there.
The character limit on Hubzilla is over 16 million on (streams) and Forte, it's over 24 million. The number of options in polls is practically unlimited, as is the number of images that can be embedded in messages. And with "embedded," I mean like in a blog post or on a website with text above and below the images.
At the same time, they're part of the Fediverse. Hubzilla is based on Zot6/an older version of Nomad ActivityPub can be activated. (streams) is based on Nomad ActivityPub is optional, but activated by default. Forte is based on ActivityPub. Any Fediverse software that recognises groups recognises their groups as such.
Here is an article with a number of tables in which I've compared the features of Mastodon, Friendica, Hubzilla, (streams) and Forte:
.
CC:
# # # # # # # # # # # # # # # # A whole lot. Sorry, but this will be very very very long again.
I don't know if you've read my previous (very long) commentary. But just implementing one or two FEPs won't get you the same full-blown nomadic identity () that Hubzilla (what I'm writing from right now ) has had since 2012. And having this level of nomadic identity has to be the goal.
What has to be done is:
Take something like Mastodon.
Non-nomadic.
Where your account, your login, equals your identity.
Make your identity cloneable
Now, before you can make identities nomadic, you have to uncouple them from the login, from the account.
Mastodon has to introduce a sort of container for your identity, like the channels that Hubzilla, (streams) and Forte have always had (). This is necessary so that a future nomadic Mastodon will know what to clone and what not to clone. For example, cloning your password is dangerous nonsense.
So, everything that makes up your account except for your login credentials will have to be moved into this container.
- your short name
- your long name
- your profile images, including alt-texts
- your profile
- your followers
- your followed
- your toots, including stats like faves, boosts etc.
- copies of the conversation trees of all your toots, including stats like faves, boosts etc. as well as attached files for each message
- all files you've ever attached to toots
- your settings
- your filters
- your mutes
- your blocks
- your server blocks
- etc.
Change your login
Also, your login will have to change from short name + passphrase to e-mail + passphrase. Your short name is part of your identity, it's in the container, it will be cloned, so it can't be used to log you in anymore.
In order for this to work, half of Mastodon's server backend will have to be rewritten.
Decentralised IDs
Next, Mastodon must switch from the Webfinger IDs that it uses now to decentralised IDs as per FEP-ef61. For a while, I guess, it will have to use both next to one another. Then it will have to phase out its Webfinger IDs.
The decentralised IDs must be tested against other Fediverse software that already understands them or that's nomadic itself: (streams), Forte, Mitra, Tootik. For example, of Mitra and of (streams) and Forte must test whether their software correctly understands Mastodon's DIDs. And the Mastodon developers must test whether Mastodon correctly understands the DIDs from Fediverse server applications that already use them.
Once it has gotten rid of its Webfinger IDs, the next phase can start.
Implement cloning within Mastodon
The central element of nomadic identity is not the ability to move your identity. That's only a byproduct of cloning your identity.
A clone, in nomadic identity, is a full backup of the container with your identity in it. A real-time, live, bidirectional backup that you can log into and use just like the "original". The clone always has the same idea as the original, regardless of which server it's on.
The key elements of clones and cloning must be implemented and tested:
- cloning an identity container to a different server after registering a new, blank account there
- cloning an identity container to a different server where you already have an account with a different containerised identity
- anything that happens on the original being sync'd to the clone
- anything that happens on the clone being sync'd to the original
- clone going offline, things happening on the original, clone coming back online, things that happened on the original being reliably sync'd to the clone
- original going offline, clone still working with the ID based on the original's domain
- original going offline, things happening on the clone, original coming back online, things that happened on the clone being reliably sync'd to the original
- making additional clones of an identity container that has already been cloned at least once
- the whole syncing shebang from the original to any number of clones
- the whole syncing shebang from one of the clones to the original and also directly to the other clones
- declaring one of the clones the new original, thus changing the ID of both the former original and all clones
Implement moving within Mastodon
Only when cloning works reliably, we can talk about moving, even though that's what everyone on Mastodon is giddy about.
Why Because moving involves cloning. It's an automated process. At least it is on Hubzilla, (streams) and Forte, and it really should be one on nomadic Mastodon.
Basically, first you make a clone.
Then you declare the clone the new original, and your old original is demoted to a clone.
Then you have to wait until your change of ID from changing the original has federated to all your followers and followed and everywhere and whatnot.
Then, one last sync so that both the former-clone-now-new-original and the old-original-now-clone are really identical, and you won't lose any data.
Then your old-original-now-clone is deleted. We don't want to leave any dead stuff behind, now, do we
Lastly, if your old account where your old original used to reside has no other identity on it, the whole account is deleted. In nomadic containerised identity, accounts cannot/should not exist with no identity container on them.
Cloning and moving beyond Mastodon
The last possible step is still utter science-fiction: Cloning or moving from Mastodon to something else that's nomadic and understands FEP-ef61.
Cloning or moving from Mastodon to Mitra. From Mastodon to Tootik. From Mastodon to (streams). From Mastodon to Forte. Oh, and maybe also back to Mastodon.
The difficult part is not only to make Mastodon capable of cloning identity containers to other nomadic software. And to make Mastodon accept identity containers from other nomadic software being cloned to Mastodon. I mean, this would be difficult already. (streams) and Forte are vastly, vastly different from Mastodon.
No, the difficult part is to make these four capable of cloning from or to someplace else. As it stands now, you can only clone from Mitra to Mitra, from Tootik to Tootik, from (streams) to (streams), from Forte to Forte. Even cloning between (streams) and Forte has never been possible, even though they're very similar. Oh, and cloning from and to Hubzilla is another story because Hubzilla doesn't have FEP-ef61 implemented.
# # # # # # # # # # # # # # # # #
Tales of producer apologized for the long wait for a new entry and vowed not to let the series fall off
Yusuke Tomizawa admitted the dev bar has been raised and fans have been waiting WAY TOO LONG. For now, the focus is on remasters via Tales Remastered (including the recently announced Tales of Eternia Remastered), which exceeded expectations. But he knows a brand-new mainline game that meets fan hopes is "absolutely necessary" f...
ENDING FAT INSTABILITY
For the first time in a long, long life, I feel stable.
It is boring sometimes.
There is less drama, less urgency, less emotional weather pretending to be meaning.
But in a million years, I would not go back.
I would not go back to the fat instability of mind and body.
Six years of fasting have made the body lighter.
A year and a half of breathwork has made the mind quiet.
Routine has made the days trustworthy.
There is coffee in hand, a warm fire, Pete nearby, the dogs moving through the morning, and a body that no longer feels like an emergency waiting to happen.
None of this is glamorous.
It is simply a life that no longer needs to keep exploding into illness, falls, and confusion to prove that I am alive.
Sometimes peace is boring.
Good.
Boring is underrated.
.
<>
There are two typical ways of getting content onto your timeline.One, the "normie" way. Follow everyone you come across, and hope that something interesting washes up.
Trouble is, this gives you .1% interesting content and 99.9% cruft. The interesting content is spread among the cruft pretty homogenously.
At the same time, you get tons of content. You'll only be able to scroll down your timeline, let's say, an hour's worth of content a day, and you'll miss the content from the other 23 hours. This also means that you only catch one out of 24 interesting messages on average.
Two, the "pro" way. Use the hashtag search to find people who post certain content and follow them.
Trouble is, they, too, aren't always specialised in that content. From your point of view, they, too, post cruft. Your signal-to-noise ratio is higher, but you still get more noise than signal, more cruft than interesting content.
Now, there's a trick that many Mastodon users don't know because doesn't have that feature: You can follow hashtags.
If you're interested in certain topics, find the corresponding hashtags (it's often more than one) and follow them. This way, you receive content with these hashtags from whoever posts content with these hashtags, but without the uninteresting cruft from the same users.
# # # # # # # # # # # # # #
Is the # protocol any closer to having data portability
Have you read about nomadic identity yet ()
There is only one Fediverse server application that offers full-blown server-side nomadic identity via ActivityPub, and that's Forte (). This won't change anytime soon. For there is one critically important thing that has never happened yet, and that's the conversion of non-nomadic, account-equals-identity, ActivityPub-based Fediverse software to fully nomadic, identity-uncoupled-from-accounts, ActivityPub-based Fediverse software.
Forte itself came to exist in 2024 as a fork of something colloquially called (streams) which is already nomadic, but based on its own protocol named Nomad with ActivityPub as an optional secondary protocol. And (streams) is a fork of a fork of three forks of a fork (of a fork) of Hubzilla, the first nomadic Fediverse software, created in 2012 under the name Red and based on a precursor of Nomad.
A very long-term dream is a fully nomadic Fediverse. Not only would all Fediverse server software be every bit as nomadic as Hubzilla, but it'd be possible to move and even clone identities between different server applications. As it stands now, moving and cloning is only possible within Hubzilla, within (streams) and within Forte.
And how about single ID usable in different apps
This would only be possible in an entirely nomadic Fediverse where you can clone your identity from anywhere to anywhere. And even then you'd have to first register a local account on whichever server you want to use and then clone your existing identity onto this account on this server.
Otherwise, this is not possible. And it isn't possible at all without registering a local account on whichever server you want to create.
I mean, I've read this request countless times.
- Create an account on mastodon.social.
- Go to peertube.tv.
- Log onto peertube.tv with your mastodon.social credentials. Right away. Without first creating an account on peertube.tv.
- Upload a video credited to patrickleavymastodon.social.
There are lots of reasons why this is technologically impossible.
First of all: Where would peertube.tv know your mastodon.social login credentials from Your name and at least the salted hash of your passphrase
Besides: Where would peertube.tv store your data
On mastodon.social where your account is
And, pray tell, where would mastodon.social store a video the same way as PeerTube stores it, all the way to PeerTube's trademark peer-to-peer load balancing Also, how and why do you think should mastodon.social authorise peertube.tv to directly, remotely write to mastodon.social's local database and data storage
On peertube.tv
Well, that'd require peertube.tv to have a record of your identity in its local database. It can't store a video locally. and reference it locally through mastodon.social's local database. So peertube.tv's server backend would have to know you. It would have to have your identity.
Where would it get that
Again, no, it can't just simply reference mastodon.social's database for that. It'd need that record in its own local database.
Do you really believe that peertube.tv could go and leech all your account credentials from mastodon.social and automagically store them locally Do you really believe mastodon.social will let it do that
And do you seriously believe that if free, open-source, amateur-developed server software can easily do that, proprietary, closed-source, professional, military-intelligence-grade (as in FBI, DHS, CIA, NSA, STRATFOR, MI5, MI6, Mossad, Shin Bet), ultra-high-end espionage and surveillance software like Palantir or NSO Pegasus has no way at all of doing that
No, there's literally only one possible way for peertube.tv to get to know you and know whom this video belongs to if you upload one. And that's by you registering a local account on peertube.tv. Manually.
Okay, now you (or someone else) may come and say, "But Pixelfed can literally do that! I can log onto Pixelfed with my Mastodon account!"
No. No, you can't. Sorry to say, but you can't.
Pixelfed pretends you can. For the sake of convenience and ease-of-use. But it's bogus. All show. A smoke screen.
What Pixelfed actually does when you "log into it with your Mastodon account": It takes your Mastodon login name, it takes your Mastodon passphrase, and it registers a local account on that Pixelfed server with your Mastodon login credentials.
# # # # # # # # # # # # # # # # #
.
<>
<>
VnExpress
Nt giao An Ph chm tin , nguy c gin on kt ni sn bay Long Thnh
c ng t ng bi Global Feed Bot
This whole feature should only be available for posts that originated on Mastodon then.If you click an image without an alt-text that came from e.g. Misskey or Sharkey or Akkoma or GoToSocial or snac2 or Friendica or Hubzilla or Pixelfed or Vernissage or PieFed (anywhere that isn't Mastodon) and suggest an alt-text, the original poster won't see your suggestion. All those who think that if they see it on Mastodon, it came from Mastodon, will believe the original poster is an ableist swine who intentionally ignores them and their suggestion.
So Mastodon must acknowledge where a message came from, it must know whether or not that software has this feature built in, and if the software doesn't have this feature built in, Mastodon must fully deactivate the alt-text suggestion feature.
# # # # # # # # # # # # # #
Le vieux frigo blanc cass (Jean-Pascal Dubost)
Le vieux frigo blanc cass coinc contre table et murpoussait de longues, de si longues quintes catarr-heuses que sacr bon dieu secou, il avanait sans sefaire remarquer vers le milieu de la pice, l odonnait le soleil. (la pice frache)(Jean-Pascal Dubost)Recueil: Des lieux srsEditions: TarabusteFor stays under 30 days, Airbnb usually wins. For stays of 60+ days, direct negotiation with landlords often saves 20-40% over Airbnb pricing sometimes more in cities with strict short-term rental.
New post: The Cost of Appearing Functional
-Illness -Term-Care
China Positions Methalox Long March 10C as Its Commercial Rocket Workhorse After First Booster Recovery
New post: The Cost of Appearing Functional
-Illness -Term-Care
China recuper su primer cohete reutilizable y mostr una nueva forma de hacerlo EnG
China recuper su primer cohete reutilizable y mostr una... #china #cohete #recuperable #cx-26 #wenchang #exploracion #espacial #long #march #10b #TecnologiaNew post: What the System Doesn't Count
-Term-Care -Illness
New post: The Words That Don't Translate
-Illness -Term-Care
Last updated: 2026-07-25
All text and images © eLoc8.is-fabulous.com