home.social

#500characters — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #500characters, aggregated by home.social.

fetched live
  1. @Truth & Answers Let me be honest: Mastodon isn't the right thing to rely on for this.

    There are two common misconceptions on Mastodon about Mastodon. The first one is that Mastodon is the only free, non-commercial, non-corporate, decentralised social anything. Once Mastodon users are over this, they still think Mastodon is the best free, non-commercial, non-corporate, decentralised social anything.

    I've seen Mastodon being advertised by users as a Fediverse alternative to literally everything, including Reddit (because, like, you can communicate, right?) and even YouTube (because, like, you can upload videos, right?).

    But again, let me be honest: The only thing that Mastodon can hope to be an alternative to is 𝕏. Because it's a Twitter clone. A purist Twitter clone whose developers intentionally reject feature requests because the requested features don't fit into their image of purist, minimalist, old-school, original-gangsta microblogging. They want to keep Mastodon a slightly more glorified SMS than 𝕏.

    Mastodon isn't even the only microblogging server application in the Fediverse. It isn't even the best at that. 80-90% of Mastodon's users don't and probably will never realise that Mastodon is an intentionally crippled resource hog. Many believe that Mastodon is the fully-featured be-all, end-all of social networking.

    By the way, even the Mastodon developers claim that Mastodon is fully featured. I've had a Mastodon dev try hard to convince me that Mastodon is fully featured although I've told him that I'm on Hubzilla. He essentially tried to tell me that Mastodon has every last feature that Hubzilla has plus even more on top.

    In reality, Mastodon isn't the fully-featured be-all, end-all of social networking. It isn't even a social network. It's social media, just like 𝕏 is social media. It's designed for pumping out content and being followed because it's designed as a Twitter-like microblogging application. And it isn't even the best at microblogging.

    Almost everyone on Mastodon is fully convinced that Mastodon has to be the best. After all, it's the biggest. It's what everyone chose.

    No.

    Mastodon is the biggest because everyone who wants to leave 𝕏 or Threads or Bluesky is railroaded to Mastodon. It's the biggest because all the newbies are only told about Mastodon. It's the biggest because none of the newbies even learn upon on-boarding that other 𝕏 alternatives exist in the Fediverse, that anything else exists in the Fediverse other than Mastodon. It's the biggest because mainstream media, tech media and even Fediverse activists only ever talk about Mastodon, Mastodon, Mastodon. (Granted, it's also the biggest because it's the only one with an official phone app in the Apple App Store and the Google Play Store. Even though that app sucks.)

    All these Mastodon users who claim that Mastodon is the best choice don't realise that they themselves did, in fact, not choose Mastodon. They didn't know they had a choice. All they were told about was Mastodon. Seriously, if they'd had a choice, they'd probably be on Sharkey now and not on Mastodon.

    I've read what people had to say who moved from Friendica to Misskey. Or to now defunct Calckey/Firefish. Or to Sharkey. Or to Akkoma. All these are microblogging server applications in the Fediverse. But none of them are intentionally crippled to stay close to Twitter, at least not to such a degree as Mastodon.

    It was nothing short of eye-opening to them. Only by daily-driving something else than Mastodon did they realise what the non-Mastodon Fediverse can be like. And how crippled Mastodon actually is. That Mastodon is far from being the absolute pinnacle in decentralised social media.

    They no longer had only 500 characters. They had thousands of characters. They would have had thousands of characters on every server running that software without having to ask around which one has more than 500 characters. It felt like a restraint being removed which they had never considered a restraint, at least not that much of it.

    They saw text formatting which they considered technologically absolutely impossible in the Fediverse when they were on Mastodon. In fact, they had considered text formatting entirely impossible while on Mastodon until they had come across the first message from outside with text formatting. Actual text formatting, not Unicode trickery. Now they suddenly saw a lot of the stuff that Mastodon's HTML sanitiser removes. And they themselves could use it!

    If they were on one of the *keys, they no longer had a timeline of single-message piecemeal. For the first time ever, they experienced what it's like to have something else than single-message piecemeal. Namely entire conversations right in front of them, right away. Without having to dig for them first.

    They had features which they had always wished the Fediverse may introduce. They never knew that the Fediverse does have these features, only Mastodon doesn't. They had features that were completely unimagiable to them in the Fediverse.

    There are users who have moved from Mastodon to something "minimalist" and lightweight like snac or GoToSocial, often on self-hosted, single-user, private servers. Even they suddenly had features they didn't have on Mastodon. Mind you, while not missing a single Mastodon feature (except maybe for a built-in Web UI).

    And that's just the microblogging side of the Fediverse. None of this is actual social networking. You know, what Facebook does.

    First of all, if it's about following and being followed, it's social media. A social network doesn't have followers. In case you don't know, Facebook doesn't have followers. It has "friends". Bidirectional connections. Not 𝕏/Mastodon-like mutuals which are two connections, one in each direction, but one connection that goes both ways.

    Besides, there are even more important social networking features missing from the microblogging side of the Fediverse.

    Where are the contact suggestions? Where does Mastodon suggest new contacts based on how many contacts you have in common with them? Where does Mastodon suggest new contacts based on what profile information you have in common with them?

    Oh, right, the latter is impossible because Mastodon doesn't have profile fields with defined purposes. In fact, where are these? Every good social network has them! But Mastodon only gives you four all-purpose profile fields (just like Mastodon only gives you four of everything, four file attachments, four options in polls...).

    Where is the list of unread posts, unread comments and other unnoticed actions? How are you to make sure you really catch everything your friends do? Because you can't do that if all you have is a timeline to scroll through until you no longer see new stuff. If you manage to scroll down that far. And only absolute newbies can do that on Mastodon because they hardly follow anyone.

    Where are groups? Seriously, I've lost count of how many times Mastodon users said "the Fediverse" must introduce something like Facebook Groups. The huge majority of Mastodon users is fully convinced that the Fediverse does not have groups in any shape or form because Mastodon doesn't have them.

    Where are all these things? In the Fediverse, no less? Where are they?

    I'll tell you where they are.

    Friendica. Hubzilla. (streams). Forte.

    The actual social networking side of the Fediverse (although Hubzilla is more like a social CMS or a "social Swiss army knife" that you can also use as a Facebook-like social networking application). I mean, I've already explained that Friendica was created in 2010 as a Facebook alternative. Not a faithful Facebook clone, though, but better than Facebook.

    Mike Macgirvin took over from Facebook what social networks really need. And Farmville isn't that, and spying on your users and passing that data on to the NSA and selling it to the highest bidder isn't that, so he didn't take over that. He didn't want to build a clone that also adopts the bad sides just to be as close to the original as possible.

    He took over the detailed profiles with profile fields with dedicated purposes. He took over profile privacy settings. In general, he took over a lot of privacy features. He took over advanced user discovery and connection suggestions. He took over bidirectional connections, only without that silly name "friends". He took over groups with moderation, only that a group on Friendica is just another account with a special automated reposter. He took over enclosed threaded conversations with one post at the top and otherwise only comments. He took over a "timeline" of full conversations as the default. He took over the event calendar. And so forth.

    Instead, he added useful stuff on top. He gave Friendica all the posting features to make it fully capable of long-form blogging with all bells and whistles. No character limit (except for in the database, but I think that was over 65,000 back in the day already). All HTML text formatting features (only that Friendica only used BBcode back then; now it can optionally also use Markdown). A post/thread title. Summaries. Embedded images and other media with no limit in number. He even added a spoiler tag like in forums that can hide parts of a message.

    He took care of privacy beyond what Facebook had to offer. He introduced a permissions system. Friendica got multiple profile per account, only one of which is public, so that you can show different sides of yourself to different connections.

    Now, if you want to embed images or other media in your messages, you have to store them somewhere. And not everyone could be expected to set up a little file space somewhere. So he built a file space into Friendica, one that can even be used as a Dropbox alternative, all the way to restricted access to certain directories.

    Mike also added a content warning system that automatically generates content warnings on the reader's side, based on a keyword list. If you need something behind content warnings, add the keywords to the list, and you'll have the respective content warnings, but the next user receiving the self-same post or comment does not have these content warnings if they don't need them.

    One important part of what makes Friendica Friendica is being able to connect to a whole lot of stuff. For example, Friendica could federate with StatusNet via the OStatus protocol from the get-go; this is also how it immediately federated with Mastodon when the latter was launched. Mastodon generates an RSS feed, something that many users don't know. Friendica not only generates an Atom feed, but it can subscribe to feeds. Friendica can "federate" with e-mail. Over time, more and more connection features were added, including Tumblr, Twitter (!), Facebook (only for a few years before Facebook crippled it) and a WordPress cross-poster.

    Lastly, he made it possible for third parties to add extra features by implementing an add-on system.

    I dare those who are fully convinced that Mastodon is the best Facebook alternative possible to use Friendica for a year. Not only dip one toe in to the water, but use it as their one and only daily driver for everything they've used Mastodon for. Not scratching the surface and using it like Twitter while ignoring any and all features the Twitter they remember didn't have, but going all in. In fact, I dare those who are fully convinced that Mastodon is perfect and fully-featured to do the same.

    And then there's Hubzilla. It came to exist by Mike forking Friendica in 2011, then forking that fork the same year, then rewriting that fork of a fork in 2012, then repurposing, rebranding, repositioning and greatly expanding it in 2015. Long story.

    Hubzilla adds even more stuff on top. Most importantly, it introduced nomadic identity (https://joinfediverse.wiki/Nomadic_identity) in 2012.

    Hubzilla, or its 2012 prototype form named Red, became the first decentralised social software that uncoupled the identity from the login. This was necessary for nomadic identity, but it also introduced the option to have multiple independent identities, basically what's an account elsewhere, on the same account, the same login. This makes sense, given the many different roles and purposes a Hubzilla channel can have. The big advantage over having multiple separate accounts is that you can switch between the channels on your account without logging out and back in.

    Hubzilla, or its 2012 prototype form named Red, got an even more advanced and fine-grained permissions system. Hubzilla has 17 individual permissions on three levels, channel level, contact level, content level. At channel level, each one has seven or eight permission options to choose from, depending on whether or not it makes sense to give a permission to everyone on the Internet.

    Mike added optional features to Hubzilla that were previously unseen on social anything, features that you'd rather expect from a CMS and maybe not even from that. Non-federating long-form articles. Planning cards that are based on these articles. Wikis that can be formatted with BBcode or Markdown. Webpages that can be formatted with BBcode, Markdown or HTML, that can include dynamic content from elsewhere on the channel, and that can add extra content to the channel pages.

    Hubzilla can even act as groupware. It has a CalDAV calendar server; the event calendar can double as a crude UI for the CalDAV calendars. It has an optional CardDAV addressbook server. Its built-in file storage can be accessed via WebDAV, so you theoretically even have some cloud file space you can mount as a network drive. Rather recently, there was even a way found to tie Collabora Office into Hubzilla.

    If you should ever read about Bonfire: Bonfire is Hubzilla ordered from Wish.com. Whatever Bonfire promises to have or to introduce has been available as a rock-solid stable feature on Hubzilla for over a decade. Bonfire only gets away with what it's trying to do because nobody knows Hubzilla.

    I think it's safe to say that those who "chose" Mastodon didn't choose it over the rest of the Fediverse because it's better. They "chose" it because they didn't even know they have a choice.

    As for your post, the technology for redeveloping socialising is there. And it certainly isn't Mastodon, and it never will be Mastodon. Mastodon can't be that due to its design philosophy, due to it being a Twitter clone, due to its own developers intentionally crippling it.

    If you want to move on from 1-way interaction, you have to move on from 1-way connections. Move on from Twitter followers to Facebook friends.

    You have to offer better options for the users than shouting into the void, attaching a bunch of hashtags and hoping that some of their followers or someone who is following one of the hashtags happens to be bothered to scroll down their timeline far enough.

    You have to make sure that people don't miss content due to basic design and philosophy decisions. You have to make sure that people don't miss content because they simply never know that this content is there in the first place, because they can't scroll down far enough their timelines until they reach that content. You need something else than a timeline of single messages to scroll down with the user not having an idea just how far down that timeline goes. You have to tell the user how much unread content there is, what it is, where it is, and take the user directly to that unread content.

    You have to stop presenting content to users as a long list of single posts and more single posts with only tiny details telling them that these posts are, in fact, part of a longer conversation which they don't see. Where they have to click or tap themselves through various UI pages to see that post in its context. Users must see the whole conversation Right. Off. The bat.

    You need groups. Not kluged onto something that had no group support whatsoever two seconds earlier, not intentionally crippled, not crippled by the technology they're built upon, not intentionally re-invented to be incompatible with whatever already exists (and this is how Mastodon would do them). But fully functional, on an appropriate base, interoperable, user-moderated, optionally private, optionally hiding from directories.

    If you want to go "social", you really have to go social. You have to go Facebook, not Twitter.

    Users must find other users based on common interests. Or users living close to them. Or users with lots of contacts in common with them. Not by being on the same local/regional server of the same server about a certain topic. Not by searching for hashtags in the main profile text. But by examining specialised profile fields and the contacts.

    Users must have such users suggested to them as new connections. Users must have such users at the top of their directory. This is how Facebook does it. And this is one thing that Facebook has always done right.

    Again, Mastodon will never offer any of this. But that doesn't mean that you'll have to compromise and lower your expectations. Because you don't have to. There are server applications in the Fediverse, fully federated with Mastodon, that offer literally all of that. They exist right now. And some of them have existed for longer than Mastodon.

    If you need something better than today's Mastodon, stop wishing for a better Mastodon. Instead, use something that's better and more appropriate for the job than Mastodon right now. For it exists right now.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Fediverse #Mastodon #MastodonFediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Privacy #Permission #Permissions #Groups #FediverseGroups #FediGroups #NomadicIdentity #MastodonCentricity #MastodonNormativity
  2. @Truth & Answers I've just come across a toot from a Mastodon user who demanded that everyone who posts, quote, "on Mastodon," end quote, limit their posts to 500 characters.

    This was far from being the first time I've read this very demand or similar demands. It just was the most recent time.

    Where this comes from? Well, it has two sides.

    The Mastodon side


    One side are Mastodon users. Not all of them, but most of them. Literally all of them were on-boarded onto Mastodon with the notion that Mastodon is its own enclosed network with nothing else in it. Those who pull them on board either think it's easier for them to understand if they aren't told about the non-Mastodon Fediverse, or they don't know about the non-Mastodon Fediverse themselves.

    Some of these newbies think Mastodon is the network because they've never heard of the Fediverse. Others think the Fediverse is Mastodon and nothing else.

    My estimation, and not only mine, is that more than 50% of all Mastodon users think the Fediverse consists of nothing else than Mastodon. A great deal of the rest thinks the Fediverse doesn't extend beyond Mastodon, Pixelfed and PeerTube. Not much anyway.

    It doesn't help that Mastodon, unlike other Fediverse server applications such as Misskey, the Forkeys, Friendica, (streams) or Forte, does not tell its users which server app a message came from. It doesn't help either that Mastodon "sanitises" away quite a few things that'd make non-Mastodon messages a dead giveaway. So the huge majority of Mastodon users believe that if they see it on Mastodon, it came from Mastodon.

    So these people are dropped into a network which they think is nothing but a purist, minimalist microblogging service with no more than 500 characters, and whose only differences from Twitter are the name, that it isn't just one website, that it isn't owned by Elon Musk, and that it isn't overrun by fascists.

    They get used to it. They get used to only having a maximum of 500 characters. They get used to the CW field being the CW field. They get used to Mastodon's entire culture which they see as the be-all, end-all of online culture.

    And then they come across a message with a whole lot over 500 characters for the first time. Something which, to their best knowledge, shouldn't exist in the Mastodon Fediverse. Something which mustn't exist in the Mastodon Fediverse.

    Some don't have any idea how it could be possible to "toot" more than 500 characters "on Mastodon", and they ask how one can do that. Others believe that all these "long toots" come from hacked Mastodon servers. Either way, they often demand that these Mastodon users adhere to Mastodon's culture and Mastodon's unwritten rules and act like all good Mastodon users shall act. Including not "tooting" more than 500 characters "on Mastodon".

    Both are being told that these "toots" aren't "toots" because they don't come from Mastodon. That the Fediverse is, in fact, not only Mastodon. That there's other server software in the Fediverse that has always been able to post way more than 500 characters.

    That changes nothing for them. They still demand everyone in the Fediverse adhere to Mastodon's culture and Mastodon's unwritten rules and only to these, and that everyone in the Fediverse use whatever they use exactly like vanilla, unmodified Mastodon.

    And they feel absolutely justified. According to their gospel, Gargron invented the Fediverse when he created Mastodon. And everything in the Fediverse that isn't Mastodon (once they discover that there is such stuff) has either been designed as an add-on glued onto Mastodon (Pixelfed, PeerTube), or it's an evil, savage intruder (everything that's capable of largely doing the same thing as Mastodon without being Mastodon).

    The Fediverse is to Mastodon users what the ancient world was to the Romans. Mastodon is the Roman Empire. Literally the only place that has got something like culture. A few places have voluntarily joined the Roman Mastodon Empire. All the rest consists of primitive, savage, culture-less barbarians whose lands need to be conquered by force to bring them culture.

    The non-Mastodon side


    The other side are the non-Mastodon users. This sounds harsh, but while Mastodon users act by faith and belief, non-Mastodon users act by knowledge. It's them who know what the Fediverse really is. That there has never been a point in history at which the Fediverse has only been Mastodon. And that culture does exist outside of Mastodon. Only that these cultures are different from Mastodon's culture, largely because they're geared towards the technical capabilities of the underlying software.

    To non-Mastodon users, the Fediverse feels like the New World when the European conquerors and settlers arrived. They demanded the natives adopt European culture and convert to Catholic Christianty or face death. The natives actually already had cultures. Cultures that suited them and their surroundings much more than the culture lived in European cities. But the Europeans didn't acknowledge the natives' cultures as such, nor did they care.

    From non-Mastodon users' point of view, Mastodon users act to them like the Europeans acted to the natives in their colonies-to-be.

    A very good example, also because it's such an extreme example, has to be Friendica. In case you don't know, Friendica (https://friendi.ca; https://en.wikipedia.org/wiki/Friendica; https://joinfediverse.wiki/Friendica) is a free, open-source, decentralised, federated Facebook alternative that first came out as early as May, 2010. Friendica developed a wholly different culture from Mastodon's because it's vastly different from Mastodon.

    Mastodon's culture was mostly coined in mid-2022 by those who escaped from Elon Musk's announcement to buy out Twitter in February/March, 2022.
    Friendica's culture was coined by its early users in 2010 already.

    Mastodon users are mostly used to living in a Mastodon-only network with no connection to anything that isn't Mastodon. They believe that Mastodon and the Fediverse were designed as such, and that Friendica is an illegitimate intruder.
    Friendica users are used to being able to connect to everything that moves, including Mastodon, including the whole Fediverse, no matter which iteration of the Fediverse, including diaspora*, and the some. That's because Friendica was designed from the ground up to be able to connect to a whole lot of stuff. It's part of its concept.

    Mastodon users believe that Mastodon was there before anything.
    Friendica users know that Friendica was there long before Mastodon, even before diaspora*, and that Friendica still wasn't the first.

    Mastodon users are used to only having 500 characters. They still consider that a lot in comparison with Twitter's 280 characters.
    Friendica users are used to not having any character limit whatsoever. Friendica's actual technical character limit is imposed by the maximum size of the message text database field, and that's over 16.7 million characters.

    Mastodon users are used to chopping long posts into threads. It's what they expect. Actual long posts irritate them.
    Friendica users are used to posting long post in one piece. It's what they expect. One and the same post being chopped up into itty-bitty bits irritate them.

    Mastodon users are used to putting CWs in a dedicated CW field.
    Friendica users are used to the self-same text field actually being a summary field (Friendica calls it "abstract"). While Mastodon got that field in 2017 as a pull request from a user, Friendica had it from the get-go, i.e. since 2010. And Friendica actually adopted it from Evan Prodromou's decentralised Twitter alternative StatusNet from 2008 with which Friendica was able to federate with from the get-go as well.

    Mastodon users "know" that Gargron invented the CW field.
    Friendica users actually do know for a fact that they've had the same field as a summary field since long before Mastodon was even made. There are still enough Friendica veterans around from before 2016.

    This also means that Mastodon users are used to poster-side CWs which all readers get just the same.
    Friendica users are used to CWs being automatically generated on the reader's side, individually for each reader, by an optional text filter.
    In fact, Mastodon can do the same. But nobody knows, it came way too late to become part of Mastodon's culture (Mastodon 4.0 in October, 2022), it's too tedious to use, it probably isn't supported by that many phone apps, and next to nobody uses Mastodon's Web interface. In the meantime, Friendica has had this feature for some twelve years longer, and it's only an on-off switch and one editable keyword list.

    Mastodon users are used to only having up to four images and to images always only being file attachments dangling below a post.
    Friendica users are used to being able to embed a virtually unlimited number of images to a post. And to actually embed them, as in, with text above the image and text below the image and another image below that text and more text below that image. Theoretically, they could insert tiny images into lines of text. By the way, Mastodon refuses to display embedded images. It also rejects any file attachments beyond the first four. And up to version 4.0 from October, 2022, it didn't support any kind of text formatting and "sanitised" all message texts down to plain text.

    This also means that Mastodon users are used to only having plain text or mucking around with Unicode characters for bold type and italics.
    Friendica users are used to being able to not only see, but also post all sorts of text formatting that HTML is capable of.

    Mastodon users are often deadly afraid of quote-posts because they only know quote-posts as a means of harassment and dogpiling on Twitter.
    Friendica users, their entire culture being entirely unfazed by whatever has ever happened on Twitter, are absolutely used to always having had quote-posts at hand and to using quote-posts as a means of forwarding content. They had what Mastodon calls "quotes" years before they had what Mastodon calls "boosts" (and what many Mastodon users refer to as "retoots").

    Mastodon users are used to conversations being loosely tied together from toots and to having to visibly mention all those whom they want to receive a reply.
    Friendica users are used to having enclosed threaded conversations with only one post and otherwise only comments. They're also used to everyone in the conversation, i.e. everyone who has received the original post, automatically receiving every single last comment. They're used to always seeing the entire thread immediately as opposed to single-message piecemeal.

    Mastodon users are used to shouting into the void with hashtags attached if they want to talk about a certain topic. It's the only way for them to do so.
    Friendica users are used to having groups. Oh, and full-text search.

    The conflict


    It should be obvious that these two types have a very high chance of not getting along, especially if the Mastodon user is fairly new and not used to there being stuff in the Fediverse that's nothing like Mastodon.

    Mastodon users keep demanding that everyone else in the Fediverse live by Mastodon's culture and Mastodon's rules and only by these.

    Mastodon users who have joined in 2026 keep ordering Friendica veterans who have joined in the early 2010s (before there was any Mastodon) to act like they're on Mastodon.

    They demand these Friendica veterans fully adopt Mastodon's culture (which isn't even geared towards Friendica's set of features).

    They indirectly demand these Friendica veterans give up their own culture (because they cannot comprehend that there can be any other culture in the Fediverse than Mastodon's, as in, that what Friendica has is a culture, even though it's different from Mastodon's).

    They directly demand these Friendica veterans give up some 40% of the features they've been using for a decade and a half and indirectly demand they give up another 40% of these features.

    They demand these Friendica veterans stop posting more than 500 characters at once.

    They demand these Friendica veterans put CWs into their abstract field. (Again, they think that Gargron has invented this field from scratch as a CW field,)

    They demand these Friendica veterans use their abstract field only for CWs.

    They demand these Friendica veterans stop "spamming" hashtags that clearly aren't there for content discovery. (They cannot comprehend that these hashtags are there to trigger automatic reader-side CWs because the entire concept is completely alien to them.)

    And so forth.

    These Friendica veterans have been in the Fediverse for about a decade and a half. And suddently, these Mastodon newbies appear and tell them how to use Friendica.

    Of course, these Mastodon newbies don't know a thing about Friendica. They think the Friendica veterans are Mastodon users, and they're telling them how to use Mastodon.

    So the Friendica users tell them, no, they aren't on Mastodon. They're on Friendica which has got absolutely nothing to do with Mastodon.

    Then the Mastodon newbies will believe that someone has created this weird Friendica thing after Mastodon was made (it can't possibly be any other way, right?9 and illegally hacked this Friendica thing into the Mastodon Fediverse. And whoever made Friendica omitted to make Friendica just like Mastodon.

    Okay, now the Friendica users tell them that Friendica was launched in 2010, how long before Mastodon that was, and that they themselves have been around for much longer than Mastodon, too.

    Now, either the Mastodon newbies will fail to comprehend that there can be anything in the Fediverse made before Mastodon if Gargron has invented the very technology. Or they think that the Fediverse was still created with Mastodon, and that Friendica still illegally intruded into the Mastodon Fediverse.

    Either way, the Friendica veterans will have to adapt and act entirely by Mastodon's standards. This is the Mastodon Fediverse, Mastodon is the biggest software (if only by monthly active users, by the way), Mastodon has defined "the Fediverse culture", and thus it's the Mastodon users and only the Mastodon users who get to say how people have to act and behave in the Fediverse.

    And then the Mastodon users wonder how there's so much Mastodon hatred on Friendica (and there actually is). How Friendica users complain about Mastodon users trying to force them to use Friendica like Mastodon. How Friendica users complain about Mastodon users chopping long posts into small bits. As if they had a choice. How Friendica users complain about CWs in whatever that abstract field is supposed to be. And so forth.

    How dare the Friendica users complain? The Mastodon users are the good guys! It's them and only them who have a culture, who have rules, who know how to use the Fediverse!

    By the way: It gets even worse between Mastodon and Lemmy.

    Mastodon's culture is an idealised version of pre-Musk Twitter's culture with bits of Tumblr's SFW culture mixed in. That's because just about everyone on Mastodon originally came from Twitter, and most of them escaped from Elon Musk. They want Mastodon (and the Fediverse) be a better Twitter. It helps that Mastodon is still trying hard to be a Twitter clone.

    Lemmy's culture, on the other hand, is a carbon copy of Reddit's culture. Lemmy is a Reddit clone that shares next to no features at all with Mastodon except for ActivityPub support. Next to all Lemmy users are former Redditors who left Reddit when Reddit started charging $20,000,000 for its client API, effectively killing off all third-party Reddit apps. They saw no reason in changing their culture because it wasn't the culture that drove them away. Hardly any of them were on Twitter, and almost none of them have ever been on Mastodon. Many think the Fediverse is Lemmy. Of the rest, many think the Fediverse is Lemmy with a side of PieFed.

    Mastodon lives on hashtags even more than Twitter. Lemmy has zero support for hashtags because Reddit doesn't have any either, and neither does Hacker News.

    Mastodon requires mentions to get replies to their recipients. One visible mention per recipient. Lemmy doesn't need mentions for this at all. Mentions on Lemmy only serve to, well, mention someone. Just like on Reddit.

    And so forth.

    It's actually easy to spot threads on Lemmy that were started by Mastodon users: The title is in the post text, or there's no title at all because the Mastodon users did as they always do: mention in the first line, then a new line because that looks prettier. Of course, there's a mention in the post text. And there's a bunch of hashtags strewn across the post text even though they don't even work. If you're very lucky, the hashtags are at the bottom, but most Mastodon users don't waste any of their 500 characters on that.

    I hope you get a rough idea how much headbutting there is between Mastodon users who think that the Mastodon users rule supreme over the whole Fediverse and Lemmy community owners who do rule over the Lemmy communities which these Mastodon users have just posted into.

    Countermeasures


    Both sides are actually taking countermeasures. The non-Mastodon side is more effective at it, though.

    On Mastodon's side, there are very few single users who block every single non-Mastodon server they come across.

    Countermeasures on the non-Mastodon side vary. They start with single users who block each Mastodon user who doesn't behave like they want them to behave, e.g. they block everyone who chops a long post into a thread at first trike.

    Then there's Hubzilla, reworked from a fork of a fork of Friendica by Friendica's own creator. Hubzilla has always been based on its own protocol, Zot6 (Friendica's creator calls it an older version of Nomad). ActivityPub support is optional, on by default on new servers and off by default on new channels. The current devs won't change anything about that. Not only doesn't Hubzilla's technology allow for moving it to ActivityPub as its base protocol, but ActivityPub being optional is seen as a last-resort "drawbridge" for those to whom Mastodon has become unbearable.

    Nowadays, Friendica's creator is working on two other applications in the same family. (streams) is a fork of a fork of three forks of a fork (of a fork?) of Hubzilla, and Forte is a fork of (streams). Both have an admin-side user agent filter. It can block entire Fediverse applications without having to hassle around with a URL list. It was mainly created and advertised as a means to permanently lock Threads out, even if Threads should change URLs. But it's also being advertised as being capable of blocking all of Mastodon, all present and future servers. Mastodon being intentially made barely compatible with the rest of the Fediverse is only one reason for this.

    (streams) and Forte also have another admin-side filter which, when turned on, locks everything out that doesn't support enclosed threaded conversations. That's because server applications like Mastodon mess with the way that (streams), Forte and their ancestors handle conversations. Granted, when this is activated only to get rid of Mastodon, it causes quite a bit of collateral damage.

    Generally, (streams) and Forte are very similar. The main difference is that Forte is entirely based on ActivityPub whereas (streams) is based on the current version of Nomad with ActivityPub still being optional. The reason why (streams) is kept around is for there to still be one of these applications with the same protocol-level "drawbridge" as Hubzilla. And in fact, the most important (streams) group used to have ActivityPub off with the intention to keep Mastodon out.

    I guess there are still Mastodon users who absolutely defend and support Mastodon's way being forced upon the non-Mastodon Fediverse, and who are irritated or upset about non-Mastodon users being very defensive of their own non-Mastodon ways and refusing to adopt Mastodon's (allegedly much superior) culture instead of embracing it.

    And I guess there are Mastodon users who feel absolutely entitled to get to every last Hubzilla and (streams) and Forte user unhindered and force them to use Hubzilla/(streams)/Forte exactly like Mastodon in every way possible.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Fediverse #Mastodon #MastodonFediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Lemmy #MastodonCulture #FediverseCulture #MastodonCentricity #MastodonNormativity
  3. @TeflonTrout :bc: he/him @Sharp Leaves Still, forcing Mastodon's culture and Mastodon's unwritten rules upon literally everyone in the Fediverse is bad.

    Maybe you haven't heard about this yet, but: The Fediverse is not only Mastodon. It has never been only Mastodon. It didn't even start with Mastodon. And it doesn't entirely work like Mastodon either.

    For starters, this means that just because you see it on Mastodon, it didn't necessarily originate on Mastodon.

    There are places in the Fediverse that are vastly older than Mastodon, and that are very different from Mastodon. Thus, they have their own culture, based on their own technology and their own features and where their users came from, and largely without any influences from Mastodon.

    The oldest still existing server software in the Fediverse is not Mastodon from 2016. It's Friendica (https://friendi.ca, https://en.wikipedia.org/wiki/Friendica, https://joinfediverse.wiki/Friendica). Friendica is essentially a mixture of a Facebook alternative and fully-featured long-form blogging. No Twitter or Mastodon influence anywhere. And Friendica first came out in May, 2010, five years and eight months before Mastodon.

    Friendica did not intrude into the Mastodon Fediverse that was created by Eugen Rochko as a Mastodon-only network. Mastodon was born into an already existing Fediverse that consisted of at least Friendica, Hubzilla (https://hubzilla.org, https://en.wikipedia.org/wiki/Hubzilla, https://joinfediverse.wiki/Hubzilla) and GNU social (https://en.wikipedia.org/wiki/GNU_social; now defunct).

    Here's how Friendica differs from Mastodon in ways that may disturb Mastodon hardliners:
    • Mastodon is hard-coded to 500 characters. This character limit is deeply engrained into Mastodon's culture.
      Friendica doesn't have an arbitrary character limit; it's limited by the maximum size of the database field for the post text. Currently, this is 16,777,215 characters. Thus, Friendica doesn't have keeping messages short in its culture, it never has, and it never will.
    • Mastodon users tend to be eager to block anyone who doesn't cut long posts into pieces of no more than 500 characters each.
      I know at least one Friendica veteran who blocks everyone upon first strike who does cut long posts into annoying strings of tiny chunks.
    • Mastodon introduced a CW field in 2017.
      Friendica has had the exact same field as a summary/abstract field since its own beginning in 2010. That, and Friendica has always had a much more efficient way of handling CWs, one that Mastodon itself adopted with version 4.0 in October, 2022. Thus, by its technology and culture, Friendica users despise misusing their abstract field to force the same CW upon everyone out there with a hot, flaming passion.
      So if you see someone "misusing" the CW field for "a subject or a summary or whatever that is," that might not be a clueless Mastodon user. Instead, it might be a Friendica user who has been around for a dozen years longer than you, who is used to living by Friendica's culture, and who knows tons more about the Fediverse than you do.
    • Friendica users are much less likely to add alt-texts to their images. That's for two reasons.
      One, Friendica's culture is not an idealised version of pre-Musk, very-left-wing Twitter's culture. It does not include attacking and punishing everyone who doesn't add 100% hand-written, 100% accurate, sufficiently detailed alt-texts to their images.
      Two, Friendica handles images drastically differently from Mastodon. Mastodon always has a nifty little entry field for alt-texts whenever you attach an image. On Friendica, images are embedded into posts rather than attached to them, like in a blog post. And oftentimes, you literally have to program the alt-text into the raw image embedding markup code.
    • On Mastodon, it's considered intrusive and reply-guying to reply to someone who hasn't mentioned you, and to whom you aren't mutually connected. You couldn't possibly have received the toot that you're replying to otherwise.
      On Friendica, that's perfectly normal. Friendica doesn't show you single messages by default. It always shows you the entire conversation thread, all the way up to the start post, with all branches. Thus, neither Friendica's technology nor Friendica's culture rules out replying to any comment in the thread.
    • Mastodon has only just introduced Twitter-style quote-posts a few months ago. With a safety feature that only works on Mastodon and GoToSocial for fear of that feature being used for harassment and dogpiling just like on Twitter. And because literally everyone on Mastodon comes from Twitter, it's actually being used for harassment and dogpiling.
      Friendica has had that very same feature since its inception in 2010, over a decade and a half longer. It has never not had this feature. It has always been able to quote-post any public message in the Fediverse. But since Friendica is not entirely populated by former Twitter users, it hasn't been used for harassment or dogpiling even once. It's only used to forward content. For most of the time, it literally was the only available way to forward a message.
    • Mastodon users tend to be very protective and defensive about their allegedly Mastodon-only Fediverse.
      Friendica users are used to being able to connect with everything that moves and then some. It's one of Friendica's key features that it speaks a whole lot of protocols, not just ActivityPub.
      Whereas Mastodon users see Mastodon as a "decentralised walled garden", Friendica users see Friendica as the gateway to the whole federated social Web plus some places that aren't, strictly speaking, federated.
    • Mastodon users will staunchly insist that "Fediverse" and "Mastodon" essentially mean the same because they believe they do. They will attack anyone who claims otherwise.
      Friendica users will staunchly insist that there's a huge difference between "Fediverse" and "Mastodon" because they actually know there is one. They will lecture anyone who claims otherwise.

    Of course, from a Mastodon point of view, it's both tempting and fully justified to tell the Friendica users that this is the Mastodon Fediverse, and that they will have to adapt the Mastodon culture and abolish their own culture or be thrown out. But for one, Mastodon's culture doesn't fit Friendica's technology.

    Besides, that'd literally be like European settlers holding Native Americans at gunpoint and forcing them to give up their own culture, adopt European culture and convert to Catholic Christianity or else. The only difference is that European settlers, unlike the Mastodon users, did not think that they were there first, and that everyone else is an intruder.

    I mean, sure, go ahead and attack anyone who doesn't strictly live by Mastodon's culture and Mastodon's rules if you think you have to. But prepare for a whole lot of defence and even counter-attacks from Pleroma, Akkoma, Misskey, Iceshrimp-JS, Iceshrimp.NET, Sharkey, GoToSocial, Hollo, snac2, Mitra, Socialhome, Friendica, Hubzilla, (streams), Forte and the rest of the non-Mastodon Fediverse.

    CC: @Jan Wildeboer

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #Fediverse #Mastodon #Friendica #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
  4. @🌱🏴‍🅰️🏳️‍⚧️🐧🔧📎 Ambiyelp I'm not talking about the visual description in the alt-text.

    I'm talking about a wholly separate explanation in the post text body. Like, where you'd write the actual toot. Where you probably only have 500 characters. Where you wrote the above comment. It's there where I want to put the explanation.

    The story behind this is as follows:

    I keep reading from Mastodon users that alt-texts (yes, actual alt-texts in this case) are useful for sighted people, too, because alt-texts can give them explanations and help them understand what they're looking at. This means that images must not only be described, but also explained if necessary.

    On the one hand, I keep telling Mastodon users again and again that explanations do not belong into the alt-text because there are people who can't access and read alt-texts; Mastodon users tend to be very defensive of using alt-texts to extend their 500-character limit by another 1,500 characters per image.

    Still, on the other hand, this means that especially Mastodon users want images that they don't understand to come with explanations right away. In particular, neurodivergent people often need explanations, in-depth explanations even. It appears to have gotten to a point where posting an image that needs explanations without explanations is considered just as careless and almost as ableist as posting an image without accurate and sufficiently detailed alt-text.

    At the same time, whenever I post an image of any kind, memes included, they're about such obscure topics that they need an explanation. Also, not everyone is always familiar with every meme template, so I have to give an explanation for the meme templates I've used as well. So I always explain whatever might need to be explained.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Ableist #Ableism #AbleismMeta #CWAbleismMeta
  5. @🌱🏴‍🅰️🏳️‍⚧️🐧🔧📎 Ambiyelp Question about describing memes, just to be on the safe side.

    Let's assume my character limit is not 500, but practically unlimited. Like, tens of thousands of times higher than on Mastodon.

    Let's also assume I don't have a problem with writing a whole lot of text, for while most of the Fediverse is fumbling around on a phone screen, I'm blind-typing on a hardware keyboard.

    How would you recommend me to explain meme templates in the post text (in addition to the visual description + text transcripts in the alt-text)?
    • not at all (leaves people clueless)
    • with one link to KnowYourMeme per used template (links are inconvenient, and the linked websites aren't necessarily sufficiently accessible)
    • no links, but a full, in-depth set of KnowYourMeme-level explanations down to the basics (that's 10,000+ extra characters in that one post)
    • same, but chopped into bits of no more than 500 characters (that's a thread of 30, 40, 50, 60 or more short posts)

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
  6. @DopeGhoti @Andrew How many characters would be sufficient for Mastodon to not count as ableist anymore?

    If you say, 1,500, who or what says that 1,500 characters are sufficient to describe any and all images, but a lower limit is not?

    For comparison, look at my cover photo. The one with the weird building. I have a post with just about the same image in it; here's the link.

    In this post, the image has two separate image descriptions. One is in the alt-text. The alt-text is exactly 1,500 characters long, a bit over 1,400 of which are image description. And that's the short description. It doesn't even have room for any text transcripts. It actually isn't much more than an "alibi description". It's only there because many people on Mastodon demand there be a 100% accurate and sufficiently detailed image description in the alt-text of each image in the Fediverse.

    Only that "sufficiently detailed" isn't always possible even in 1,500 characters.

    That's why there is an additional long description in the post text. It's sufficiently detailed, as in, fully detailed. An image like this requires a fully detailed description. It comes with transcripts of all bits of text within the borders of the image, and it comes with all explanations necessary to understand the image and the description. It's over 60,000 characters long.

    Yes, over 60,000 characters in one post. Your character limit is 500. Mine is over 16 million.

    Oh, and yes, it's guaranteed to be 100% hand-written. It took me two full days, morning to evening, to research for and write the long description with literally absolutely no help from any AI whatsoever. In fact, I've described details that no AI on the planet will ever be able to see in the image.

    So ideally, all Fediverse server platforms should have two image description fields for each profile image, one being the alt-text behind the image, one being a long description next to the image. The latter should not have an arbitrarily-chosen character limit.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Ableist #Ableism #AbleismMeta #CWAbleismMeta
  7. CW: Good image descriptions require a much bigger effort than you may think; CW: long (over 5,300 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, character limit meta, content warning meta, hashtag meta, alt-text meta, image description meta, AI mentioned (AI-)
    Image descriptions are important in the Fediverse, at least if your posts have a chance to reach Mastodon. But is it only about having image descriptions in general? Is it only about having image descriptions at all? Or is it about image description quality as well?

    Blind or visually-impaired users say that anything is better than nothing. But seriously, the image file name as the alt-text is useless. So is a copy of the post text as the alt-text; at least one mobile app for Mastodon seems to do that automatically. So is some gibberish written into the alt-text, just so that there's some alt-text.

    So you write a short image description for your alt-text. That should be much better than nothing.

    But then you're criticised and sanctioned because your image description lacks detail.

    Since you can't or don't want to write a longer description, you leave that to an AI.

    But then you're criticised and sanctioned because your image description is obvious AI slop. The AI is inaccurate, it hallucinates, it misidentifies things and it still leaves out details.

    Okay, so you sit down and put quite some time and effort into a hand-written image description that's both accurate and detailed. At least you think so.

    And still, someone may come and criticise and/or sanction you for having left out certain details.

    If you don't fix your image description to their satisfaction, you're insulted as ableist and blocked very publicly so that as many other users as possible block you, too.

    Now, minimum quality standards for image descriptions are evolving over time. What matters now didn't necessarily matter two years ago. Things that don't matter now may matter in two years or in five years. Even today, alt-text activists criticise image posts that are several years old for image descriptions that they consider less than optimal. This means the image descriptions that you write today must be good enough for as long as your image posts stay available. If they aren't, have fun going through all your old image posts, editing them and upgrading the image descriptions to the latest minimum requirements.

    There's only way to be safe from Mastodon's alt-text police in the long run: First of all, you must educate yourself about all the rules and guidelines of alt-texts and image descriptions, and there are dozens of websites about these. You can't know beforehand which ones of these rules will be declared mandatory by someone from the alt-text police in the future, so you'd better follow them to a tee already now. Of course, when two rules contradict each other, you must know which one to follow.

    Also, you must know that the requirements and quality standards for good alt-texts and image descriptions on Mastodon are different from the entire rest of the Web. What's good enough for the Web isn't necessarily good enough for Mastodon.

    Lastly, you must know your audience. And normally, your audience can be anyone anywhere in the Fediverse or even on the Web. There are only very few places in the Fediverse where you can control who will be able to read your stuff, and Mastodon isn't one of them. You must know your audience, and you must at least be able to estimate what they know about the contents of your image, what they don't know and what they need to know. If your audience doesn't necessarily know what something is, explain it, but please do so in the post text and not in the alt-text! If your audience doesn't necessarily know what something looks like, but it may want to know, describe what it looks like.

    As for my own images, my strategy is to write two image descriptions for each image. One is the short image description; it goes into the alt-text. I'm going to limit that to a maximum of 512 characters because Misskey and its forks delete alt-texts that are over 512 characters long. The other one is the long image description; it goes into the post text. The long image description is fully detailed, it contains all explanations necessary to understand the image and its descriptions, and it contains transcripts of every last bit of text anywhere within the borders of the image, readable in the image or not.

    Posting memes is a bit easier. There is only one image description that's hopefully short enough to go into the alt-text. But I still need to explain a whole lot of things, and as I can't always rely upon links to websites like KnowYourMeme for explanations, I often have to write a whole lot of explanations into the post.

    Ideally, the worst that could happen to me is being criticised for my alt-text exceeding 200 characters or my post exceeding 500 characters or being blocked for the latter. I reduce the chance for that to happen with a summary that includes a long post content warning with the rough length of the post and the hashtags #Long, #LongPost, #CWLong and #CWLongPost that can be filtered. I almost always add hashtags for folks to filter.

    But I hope that nobody can say I haven't tried hard enough.

    #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
  8. @Brett Coulstock You should care if you think that Gargron has invented the Fediverse as a pure Mastodon network. If you think that e.g. Friendica and Hubzilla came into the Mastodon Fediverse after the fact. If you use this thinking as a justification to force Mastodon's rules and Mastodon's culture upon Friendica and Hubzilla users because you take them for intruders in a place where they don't rightfully belong.

    Because Friendica and Hubzilla did not intrude into Mastodon's Fediverse. They were in the Fediverse before Mastodon.

    You should care if you think that posting more than 500 characters is bad behaviour as it goes against "the Fediverse culture".

    Because that "Fediverse culture" is only Mastodon's culture. And the culture on Friendica and Hubzilla, which pre-dates Mastodon itself by years, knows no character limits.

    You should care if you think that Gargron is evil for introducing quote-posts to the Fediverse.

    Because it was actually Mike Macgirvin, creator of Friendica and Hubzilla, who did that. In 2010. 16 years before now. Almost 6 years before Mastodon was even made.

    And because just about everything that isn't Mastodon could quote-post Mastodon toots before Mastodon users even considered quote-posts evil.

    You should care if you wish for "the Fediverse" to introduce certain new features. Like reply control. Or better list handlings. Or groups. Or even only more characters.

    Because "the Fediverse" does have all these features. Just Mastodon doesn't have them. But Mastodon is not the Fediverse.

    You should care if you don't want "the Fediverse" to ever introduce certain features. Like a higher default character limit. Or text formatting.

    Because the Fediverse already has such features. As in, it can use these features in posts which it then sends to Mastodon. And there's nothing, absolutely nothing that Mastodon and its users can do against it. Except for muting and blocking.

    You should care if you find it easier to use "Mastodon" and "Fediverse" synonymously, and all this "nitpicking" about when it's "Mastodon" and when it's "Fediverse" enrages you.

    Because it enrages users in the non-Mastodon Fediverse when people say right into their faces that they toot. And/or that they're on Mastodon and therefore bound to the exact same rules and the exact same culture as everyone else on Mastodon. And they will so very much not let you have your way.

    All these are things which, unfortunately, those who have never experienced anything else in the Fediverse than Mastodon will hardly ever understand.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
  9. @craftxbox No, it's about more than every other Mastodon user thinking that the Fediverse equals Mastodon.

    Most of the rest still think (or they think they know):
    • The Fediverse started with Mastodon. Gargron has invented the Fediverse.
    • Everything that isn't Mastodon is either designed as a Mastodon add-on (Pixelfed, PeerTube etc.), or if it clearly isn't that, it's an intruder into the Mastodon Fediverse.
    • If Mastodon doesn't have a feature, the Fediverse doesn't have that feature. This also means that if they succeed at keeping Mastodon from introducing a feature that they don't want, the whole Fediverse will never have it.

    There are Mastodon users who wish for "the Fediverse" (they mean Mastodon because that's all they know) to introduce some feature, blissfully unaware that this feature is all over the Fediverse outside of Mastodon.

    There are Mastodon users who "know for a fact" that Mastodon has just introduced quote-posts to the Fediverse, including an opt-out that works Fediverse-wide. They're blissfully unaware that a) Friendica and Hubzilla have been able to quote-post literally every single last public Mastodon toot since Mastodon's launch in 2016, and b) they both still are, opt-out or not.

    And then there are those who spend two years or more thinking the entire Fediverse is a 500-character microblogging service, and who shit brix in sheer terror and hammer on the block button in sheer panic whenever a "toot" with more than 500 characters shows up in their timeline.

    And, of course, those who try hard to force Mastodon's culture and Mastodon's rules, both of which are geared towards Mastodon and Mastodon only, upon users of server applications that are very very much not Mastodon. Because they think that Mastodon culture = Fediverse culture. And who, at the same time, fight everyone who suggests they do something that isn't inline with their perception of Mastodon's culture and rules.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
  10. CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
    When you see it, you'll shit brix: The Hubzilla timeline.

    The "it" that you're supposed to see is:
    • The Fediverse did, in fact, not start with Mastodon.
      There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
      Mastodon came into an already existing Fediverse with servers and users and content and a culture.
      The Fediverse has never been only Mastodon. And it will never be.
    • The Fediverse had quote-posts almost 6 years before Mastodon.
      (Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.)
    • The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
    • The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
    • The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
    • The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
    And if you've really paid attention:
    • The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
      The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters.
    • The Fediverse had full rich-text formatting almost 6 years before Mastodon.
      The Fediverse could generate bold type, italics, underline, code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.

    Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
  11. What should a person do when they are typing up a Mastodon thread, and it's already almost 400 words before you've started to wrap it up? I estimate this will be over 5 posts.

    I need a blog. I doubt I will get any readers or subscribers, but at least I can use it as a journal. Hopefully my Fediverse followers would open a link with a good enough teaser.

    Followers, what are you doing when you want to post something long?

    #Blogging #Blogging2026 #LongMastodonPosts #500Characters

  12. @Hazelnoot My goal is to get alt-texts and image descriptions right. As right as possible.

    My goal is to not be sanctioned and/or lectured by the alt-text police for allegedly being lazy and/or careless.

    In order to achieve that, I must be ahead of everyone's requirements. Whatever these requirements may be.

    But in order to achieve that, I must know their requirements. Everyone's requirements.

    If you want me to follow your rules, I need to know your rules.

    Right now, I'm probably vastly overcompliant with everyone's rules with only a few exceptions that I can't comply with (alt-texts must not be longer than 200 or 125 or 100 characters, posts in the Fediverse must not be longer than 500 characters, all of the text in an image must always be transcribed in the alt-text etc.).

    This way, I hope that my image posts will stay in compliance with existing image description quality standards for a few years, and when they no longer are, they're so old that nobody demands I upgrade my image descriptions to then-current standards.

    tl;dr: "Just do it" doesn't cut it. Just doing it is likely to get you sanctioned because you don't do it well enough. And something is no longer better than nothing.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #AltTextPolice #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #MastodonCulture
  13. @[18+!!] saph I'm not an artist, but I really need to know the definition of "helpful" in the context of "helpful alt-text". What are the requirements for alt-text to count as "helpful"?

    It must be 100% accurate, I guess that's a given. This also means that it must be 100% written by hand as opposed to AI-generated.

    But what are the minimum requirements in terms of details for an alt-text to be helpful?

    Can alt-text be too long/too detailed to be helpful?

    I'm going to limit my alt-texts to a maximum of 512 characters. Misskey, Sharkey, Iceshrimp-JS and the other Misskey forks automatically delete any alt-text that's longer than 512 characters, making it appear like I hadn't provided any alt-text to begin with, that's why. Newspaper scans aside, can alt-text with no more than 512 characters be too lacking in detail to be helpful?

    What if, in addition to an alt-text with a maximum of 512 characters, I also provide a much longer and much more detailed image description in the post text? (My character limit is not 500, but over 16.7 million. I can post long descriptions with tens of thousands of characters in one piece, and I have done so in the past.)

    Would that be acceptable to provide the details in description that do not fit into an alt-text of no more than 512 characters?

    Or is that unacceptable because the description in the alt-text must be as detailed as required, and additional descriptions in the post don't count?

    Or is that unacceptable because there must only be one description to each image, namely in the alt-text and only in the alt-text?

    Or is that unacceptable because it makes my post longer than 500 characters?

    Are explanations and other additional information about the image allowed in the post text? Because they are not allowed in the alt-text because some people cannot access alt-text.

    Or must explanations etc. absolutely be in the alt-text in order for the alt-text to be "helpful" enough?

    Must they even be only in the alt-text so that the post never exceeds 500 characters?

    What if I can't describe and explain my images in a maximum of 512 characters? What if I can't describe and explain my images in a maximum of 1,500 characters either, but I absolutely must describe and explain them in the alt-text?

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters
  14. @hosh The alt-text police of the Mastodon Home Owners' Association (Mastodon HOA) have a tendency to be overzealous. And they don't talk to each other. They all act for themselves as lone wolves with exactly no coordination amongst each other whatsoever. You never know what kinds of rules they whip up for themselves.

    Chances are that they only let image descriptions count that come directly with the image. If they acknowledge an image description outside the alt-text, it must be in the post itself. Not as an external link, but the description text itself.

    Besides, at least some in the Mastodon HOA have problems with external links. And I don't just mean that they don't trust embedded links whose URL they can't see in plain sight, the kind that Hubzilla can create and Mastodon can't (not that Hubzilla couldn't fake a plain-sight link by embedding a different URL than the visible).

    I don't mean either that probably a majority of Mastodon users don't even recognise embedded links without a visible URL as such because they don't know that such a thing can exist in the Fediverse, because Mastodon can't make them.

    No, what I mean is the notion that external links for explanations are inherently bad from an accessibility point of view. "Mastodon" (as in how Mastodon users experience the Fediverse, i.e. the Mastodon Web UI or any of the popular mobile phone apps) is sufficiently accessible. But the Web outside of "Mastodon" (same definition again) may not be accessible enough.

    A few years ago, I've literally read a Mastodon toot in which someone said that explanations must not be linked to. Linked websites have a risk of not being accessible. Explanations must always be directly in the same post. Apparently, they thought that everything and anything can be explained and broken down until everyone understands it within 500 characters.

    This is also why Mastodon users tend to explain their images in the alt-text. It's only there where they have at least halfway enough characters for an explanation, 1,500 per image as opposed to usually only 500 in the post text. (On Mastodon, much unlike Hubzilla, the alt-text is a separate database field that exists separately for each of the up to four images per message.)

    That is, explanations must never go into the alt-text because there are people who cannot open alt-texts to read them. But nobody on Mastodon knows that.

    It should be obvious that what counts for explanations counts for visual descriptions just as well.

    And in fact, regarding Hubzilla articles, they're actually right. I've once pointed an actually blind screen reader user to an article on my Hubzilla channel. She said she couldn't even navigate the Web interface. She literally couldn't get to the text body of the article to have it read out by her screen reader.

    Hubzilla's Web interface, no matter which app is opened, is not accessible. It does not work with screen readers. It's largely still stuck in 2012 when nobdy made any ruckus about the accessibility of hobbyist Web projects.

    The only reason why at least some blind or visually-impaired users can read our Hubzilla posts and comments and DMs is because they're all on Mastodon, and they read our content either on Mastodon's Web UI or a Mastodon app that supports screen readers. But they do not read our content at the source. Because they can't.

    I actually took into consideration linking to my long image descriptions. But my idea was not to link to a Hubzilla article, nor to a Hubzilla wiki or a Hubzilla card. No, my idea was to write a plain HTML document, upload it to my file space and link to that.

    I've dropped that idea for various reasons:
    • Generally, still, external links are frowned upon.
    • I don't know if plain HTML is accessible without a CSS. And I can't add a CSS to this HTML if the HTML document is not served to the recipient by a Web server, but by a file server.
    • I don't know how Google Chrome on Android or Safari on an iPhone will react when they access an HTML document on a file space. Will they display it as a website? Or will they download it onto the device as a file without opening it because, again, it is served to them not by a Web server, but by a file server?
    • Mobile users dislike opening websites from apps because they dislike their browser popping open. And on Mastodon, much unlike Hubzilla, almost everyone is on a phone and a dedicated app almost all the time.
    • This also means that mobile users would have the image and the description in two separate apps. The image in their Mastodon app, the description in their browser.
    • I would need much more description.
      Right now, when I have multiple images, my long descriptions consist of a preamble that contains all necessary explanations and, if applicable, visual descriptions of elements that are common to all images. The individual descriptions for each image follow.
      But if I had one image description file per image, then each image description would need the whole preamble included. I can't just add the preamble to the first description file.
      What if someone opens the third description file first? They'll only have a very incomplete description. And linking to the first description file is inconvenient. I would have to know the URL of the first file before completing and uploading the other files because I'd have to include the URL of the first file in them. And the users would have to have three documents open (the image post, the description of the image they're interested in, the description of the first image with the preamble) just to experience one image. Spread across two phone apps.

    And that's why I can't put my additional long description in an external document.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #AltTextPolice #MastodonHOA #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #MastodonCulture
  15. CW: Long posts vs insufficiently described images: I can't win either way; CW: long (over 3,500 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, alt-text meta, image description meta, content warning meta, character limit meta
    On the one hand, I have to go out of my way and write two image descriptions for each one of my original images. One is short and goes into the alt-text, and I'm going to limit all my future alt-text to a maximum of 512 characters (otherwise users on Misskey, Sharkey etc. will believe I haven't written any alt-text because they won't receive any due to a bug).

    The other one is enormous degrees of magnitudes longer than anything most Fediverse users have ever read in the Fediverse. It also contains all explanations necessary to understand the image and its description, and if there's text anywhere within the borders of the image, readable or not, it contains verbatim transcripts of said text.

    The nature of my original images requires such long descriptions. Besides, the only way to really be safe from the alt-text police of the Mastodon HOA is to overcomply with whatever minimum standards for good image descriptions anyone of them may have.

    On the other hand, the self-same Mastodon HOA is likely to sanction me for the self-same posts. The reason: The posts are way too long. They exceed the limit of 500 characters that's so deeply engrained into Mastodon's culture that many Mastodonians are eager to defend it. Even if I hide them behind a summary with a content warning about the post being long. If I were to appease these Mastodonians, I'd have to underdescribe my images, and I wouldn't be able to explain them at all.

    Speaking of underdescribing, I think at least some members of the alt-text police actually don't let image descriptions in the post count. What counts is only the image description in the alt-text. It must be accurate, it must be sufficiently detailed, and it must contain all the text transcripts. In fact, I wouldn't wonder if they demanded sufficient explanations in the alt-text, not knowing that explanations in alt-text are actually a big no-no.

    Even if all requirements of a good alt-text by alt-text police standards are met or even exceeded by the image description in the post, chances are the alt-text police will still sanction me if the alt-text doesn't meet these criteria.

    When it comes to my original images, even squeezing all that into the 1,500-character limit for alt-texts imposed by Mastodon is pretty much impossible. Squeezing it into the 512-character limit for alt-text imposed by Misskey and its forks is even more impossible.

    The only winning move is to not play at all. Curiously, some people are even upset about me rarely posting any images. Although they don't follow me. Although the channel that I use for original images (@Jupiter Rowland's (streams) outlet) has next to no reach, so even if I were to post images again, practically nobody would notice. Although it doesn't even seem that there's much interest in that kind of images in the first place.

    But apparently, according to some, posting images with only rudimentary alt-text whipped up in a minute, no long description and no explanations is always so much better than not posting images because it takes so much time and effort to describe them.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #AltTextPolice #MastodonHOA #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CWContentWarningMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #MastodonCulture
  16. @C. I have two major issues with the Mastodon HOA.

    One, they try hard to force "Mastodon standards", Mastodon culture and Mastodon's unwritten rules upon the whole Fediverse. Including places that not only aren't Mastodon, but that are very much not Mastodon. Simply because they can't see where a message is from. In fact, many of them are still fully convinced that the Fediverse is only Mastodon.

    And so you have members of the Mastodon HOA yelling at someone who is allegedly "doing Mastodon wrong", but that someone is actually on Friendica and has been since as early as 2011. As in about five years longer than Mastodon has even existed. And seriously, the only places in the Fediverse that are even more different and farther away from Mastodon than Friendica (without specialising in something that Mastodon absolutely can't do) are Friendica's own descendants: Hubzilla, (streams), Forte.

    The Mastodon HOA probably don't know that Friendica exists. They definitely don't know that either of the other three exists. They definitely don't know that any of the four is significantly different from Mastodon in any way. And frankly, they don't care a bit. If it appears on any Mastodon timeline, it's Mastodon to them, and it has to adapt to Mastodon's culture and follow Mastodon's rules.

    Two, they don't coordinate anything among each other. They're just a bunch of lone wolves. Everyone has got their own standards, but everyone thinks their personal standards are the one and only Mastodon/Fediverse gold standards, and everyone enforces their own standards. And, of course, everyone thinks their standards can and must apply always, including in the most obscure edge-cases.

    For example, they've got standards for describing real-life photos on Mastodon with a character limit of 500. And they try to enforce these standards always and everywhere. However, these standards don't necessarily work perfectly when I post a rendering from a super-obscure 3-D virtual world on (streams) with a character limit of over 24 million where I've got loads of room to write an additional long image description and put it into the post text.

    The Mastodon HOA, or at least some of their members, appear to be constantly raising their minimum quality requirements for image descriptions. They must be absolutely accurate, and they must be sufficiently detailed that nobody will ever have to ask for a detail description. Oh, and they must explain whatever the audience may not know about the image or the description. (At this point, it's fair to mention that explanations must never go into the alt-text.)

    Sure, I can do that. I have done so in the past. But I can't do that within Mastodon's alt-text character limit of 1,500 (Mastodon truncates longer alt-texts from outside). I can do that even less within Misskey's alt-text character limit of only 512 (Misskey and the Forkeys should truncate longer alt-texts, but due to a bug, they delete them entirely instead, giving the impression that you haven't written an alt-text at all). I can only do that in the additional long description in the post text.

    If the Mastodon HOA demand I transcribe literally any and all text within the borders of an image, I can do that, too. In fact, I have done so in the past. I can transcribe bits of text verbatim which the Mastodon HOA can't even read. Which the Mastodon HOA couldn't even find in the image because they're so tiny. But there's no way that I can squeeze 20+ individual text transcripts into 1,500 characters of alt-text along with the rest of the visual description, much less into only 512 characters. The text transcripts will have to go into the long description in the post text, whether the Mastodon HOA want or not.

    This means that the post will exceed the holy limit of 500 characters by huge magnitudes. This, in turn, means that when I've satisfied one Mastodon HOA member, another one comes and sanctions me for exceeding the holy 500-character limit. That is, chances are it's actually the same Mastodon HOA member.

    In other words, if the content of an image is obscure enough and requires enough description, the only winning move when I want to post such an image is to not post it at all.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #MastodonCulture #MastodonHOA
  17. @Pino Carafa An additional advantage of this would be that I could first ask just how detailed a description they need. Like, if they really want me to spend two full days, morning to evening, to write something that'll take their screen reader three hours to read out loud.

    The problem, however, is that the virtual worlds that I frequent change a lot. Everything is built by users. A place that I've shown in an image may change mere days or hours after I've been there, so when I go back to take a closer look for a detailed description, it doesn't look like on the image anymore.

    Or that place may be gone entirely. For example, I could post some images from an in-world event, from places specifically built for this event. Then, two months later, someone asks for a more detailed description. But I can't write a more detailed description because I can't go back to these places, simply because these places were closed and shut down a few days after I had posted the images.

    Lastly, my impression of Mastodon is still that a significant number of users do not want to ask. Whatever information they may need, they expect it all to come with the post immediately. Having to ask for a detail description or for an explanation appears to be about as bad style as having to ask for a description in the first place.

    I've literally seen Mastodon toots in which people say that if they don't understand a post or an image in a post, they want an explanation to come with the post.

    I've also seen a Mastodon toot in which someone said that it isn't sufficient to just say what's in an image, but you also have to describe what it looks like. Right away. And in my case, this is actually absolutely justified.

    It's a catch-22: If I don't describe my images sufficiently, I risk being sanctioned by the Mastodon HOA for not describing my images sufficiently. But if I do, I risk being sanctioned by the Mastodon HOA for exceeding 500 characters in one post.

    Oh, and if I chop my image descriptions into tiny chunks of no more than 500 characters, it's disturbing for my own ilk, the users of Friendica, Hubzilla, (streams) and Forte, who are used to not having any character limits and everything being in one message, no matter how long it is. Besides, how many Mastodon users are willing to read a thread of 120 or more posts and find that more convenient than one post with 60,000 characters?

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #MastodonHOA
  18. @Mastodon Migration
    Basically telling other people how they should be using Mastodon is not cool unless they are violating some instance rule.

    As, by the way, is telling Fediverse users who are not on Mastodon to use whatever they use instead like Mastodon users are expected to use Mastodon.

    Please don't be a Mastodon HOA enforcer.

    Especially since the alt-text police of the Mastodon HOA have much higher alt-text and image description minimum standards than blind or visually-impaired people. And they seem to be raising their standards further and further.

    I always try my best to be way ahead of anyone's image description minimum standards, also in order to demonstrate to the Mastodon HOA that I'm not a lazy bum, and that I do try hard to describe my images properly. For my own original images, this means that I have to describe each one of them twice, with a fairly short description in the alt-text and a much longer one in the post itself.

    This, however, clashes with the Mastodon HOA, too, because they also enforce Mastodon's default 500-character limit Fediverse-wide by generously blocking everyone whom they catch exceeding it at first strike.

    CC: @🅰🅻🅸🅲🅴  (🌈🦄)

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #AltTextPolice #MastodonHOA
  19. @Walrus 🏴󠁧󠁢󠁷󠁬󠁳󠁿 @Ben Royce 🇺🇦 🇸🇩 That's actually a problem if you're on vanilla Mastodon with only 500 characters per toot and only 1,500 characters of alt-text per image. Your only chance would be to spread the transcripts across a massive thread.

    If you regularly have to post images with well over 1,500 characters of text in them, you could move elsewhere in the Fediverse that offers more characters, but that's still federated with Mastodon. Examples:
    • Misskey has a hard-coded limit of 3,000 characters.
    • Sharkey has a configurable limit that defaults to 3,000 characters.
    • Pleroma and Akkoma have configurable limits that default to 5,000 characters.
    • Friendica and Hubzilla (I'm commenting from the latter right now) are limited to over 16.7 million characters by their databases.
    • (streams) (where I post my images nowadays) and Forte are limited to over 24 million characters.
    On all of these, you could put text transcripts into the post text body and maybe mention in the alt-text that the texts in the images are transcribed in the post itself.

    The downside of this, however, is that your posts will exceed 500 characters. And this means you'll lose a whole lot of reach. There are lots and lots of Mastodon users who block everyone who ever posts over 500 characters at once at first strike because they want Mastodon/the Fediverse to be and remain a 100% pure microblogging "service" with no more than 500 characters.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Sharkey #Friendica #Hubzilla #Streams #(streams) #AltText #AltTextMeta #CWAltTextMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters
  20. @Arnan It doesn't fit the timelines in the official Mastodon phone app. Which has the only Fediverse user interface out there that cannot fold longer posts in.

    The Mastodon Web UI can do that. All third-party Mastodon apps can do that. The Web UIs of just about the whole rest of the Fediverse from Pleroma and Misskey to Friendica and Hubzilla can do that. Phone apps for stuff that isn't Mastodon can do that.

    Only the haphazardly developed official Mastodon app can't do that because it's geared towards a Fediverse with only 500 characters, a Fediverse of a kind that has never existed.

    Mastodon is not the reference implementation of the Fediverse. And the official Mastodon app is not the reference implementation of Mastodon apps, much less of Fediverse apps. It only exists for there to be something official named "Mastodon" in the Apple App Store and the Google Play Store.

    Just because Mastodon tossed out a lack-lustre app in 2022 for those who absolutely need something named "Mastodon" on their phones to access the Fediverse, doesn't mean that Fediverse software that has existed for almost six years longer than Mastodon and twelve years longer than that app must adapt to the existence of that app and cut down its character limit from 16,777,215 to 500 for all those who can't use Mastodon through something with another name on it than "Mastodon".

    By the way: Mastodon's way of cutting longer posts up into tiny chunks of no more than 500 characters goes onto the nerves of users of Pleroma, Akkoma, Misskey, Calckey, Firefish, Iceshrimp-JS, Iceshrimp.NET, Sharkey, CherryPick, GoToSocial, snac, Hollo, Socialhome, Friendica, Hubzilla, (streams), Forte and others. But they are not allowed to complain about that, much less tell Mastodon users who do that to move someplace that offers them more characters.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #MastodonApp #MastodonApps #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters
  21. CW: Six assumptions which influence the way I describe my images; CW: long (almost 5,700 characters), Fediverse meta, alt-text meta, image description, ableism meta
    When I describe my images, I do so under a few assumptions.

    One: My audience is not limited to my following contacts. It's absolutely everyone who comes across any of my posts.

    It isn't sufficient to make my posts accessible to those who have chosen to follow me. I must make them just as accessible to a random stranger who receives them after they've been boosted a dozen times over. I must make them just as accessible to a random stranger who stumbles upon them on the public timeline of whatever server they're on.

    Two: If an element in an image is mentioned, it must also be described visually.

    Blind or visually-impaired people always need to know what something in my images looks like. This goes doubly for my typical original images; I mean, how are they supposed to know what something looks like in a specific 3-D virtual world?

    So if there's a building in one of my images, and I mention that this building is there, I also have to give a visual description of it. A full, detailed description.

    If there's an image in one of my images, e.g. a preview image on a teleporter that shows the place where the teleporter would take me, I have to fully describe that image. An image in my image that doesn't even take up 200 pixels in my image. (Something that I've refused to do in my longest image description so far because that would have led me to going at least four levels deep: describing loads of infinitely small images in several dozen infinitely small images in an image in my image.)

    In fact, this isn't an assumption. I have written confirmation for it. I can't find it right now, otherwise I'd share it here, but I have it somewhere.

    Three: Image descriptions must always deliver all information that someone may need right away.

    Not everyone wants to ask for a description of a certain detail in an image. Not everyone wants to ask for an explanation of what they don't understand or what they're unfamiliar with. Having to look things up yourself isn't much better. Some may go as far as likening not having an image description that contains everything they need to know to not having any image description.

    By the way: It's a fact that some Mastodon users consider linking to external information ableist because linked websites aren't necessarily sufficiently accessible themselves. Instead of linking to information, the information must go into the post itself. (And I can't even use any character limit as an excuse not to do that because my "limit" is over 16.7 million.)

    In other words, the only way for me not to be ableist is to give any and all information that anyone out there may require in my image post immediately.

    Of course, this will clash with the demand by other Mastodon users (or maybe even some of the same) to never post more than 500 characters at once. But I can't do both. And I've never read anywhere that posting more than 500 characters is allegedly ableist.

    Four: Someone somewhere out there may be interested in even small details in my image. And they may not be sighted.

    Maybe you aren't. But someone somewhere out there may be. And they matter every bit as much as you or everyone else.

    If they need a full description of all details, regardless of why, I have to deliver it. Immediately. See above.

    Five: Any and all text within the borders of the image must be transcribed verbatim, no exception.

    Most importantly, this even extends to text that's unreadable in the image if I can read and/or source it.

    The assumptions further up apply here as well: If I mention it (the text in this case, and be it as part of the visual description of something else like a teleporter), then I must describe (as in transcribe) it. And someone somewhere out there may be interested in it.

    If this means that I have to transcribe not one or two, but 20, 30, 40 bits of text in one image, then so be it, so are the rules.

    Just because nobody on Mastodon does it, doesn't mean they're doing it right, and I'm doing it wrong. Maybe they don't know what that unreadable text says. Maybe they don't know that someone wants to know what's written there.

    Six: All images must have an accurate and sufficiently detailed proper alt-text.

    I can spend two days, morning to evening, working on an image description of 60,000 characters. 10,000 words. Three hours worth of reading. I can put the whole thing into the same post as the image. As in the post text body. As opposed to the alt-text for which this description is way too long.

    But if the image in the post doesn't have an actual alt-text (and, again, it doesn't because the image description is in the post text itself), Mastodon's alt-text police is likely and fully justified to sanction me regardless.

    So no matter how long and detailed and well-researched the long image description in the post is, I still have to distill an additional, shorter image description for the alt-text from it. And I have to do so without cutting too much information. Ideally, without cutting any information. If any of my images need a long description in the post, they need two descriptions, the long one in the post, the shorter one in the alt-text.

    Leaving the several dozen individual text transcripts out of the description for the alt-text is risky already because text transcripts belong into the alt-text.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #500Characters #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Ableist #Ableism #AbleismMeta #CWAbleismMeta #Inclusion #Inclusivity #A11y #Accessibility
  22. @RS, Author, Novelist, Prosaist Yup. Mastodon clings hard to being purist, minimalist, old-school, original-gangsta microblogging. It's a miracle actually that Mastodon 4.0, released in October, 2022, introduced the displaying of some text formatting.

    It says a lot that the character limit of 500 is hard-coded. It is not configurable. Digging into the source and modifying a file that'll be overwritten by git upon the next upgrade is not configuration, it's a fork. Also, Mastodon apparently keeps changing the way of raising the character limit, probably to keep admins from diverging from The Mastodon Way.

    There is no technological reason within the Fediverse itself to limit posts to this length.

    The software that I'm posting through is older than Mastodon by almost four years. It has been what it is now for ten months longer than Mastodon has existed. It was the first Fediverse software to adopt ActivityPub, two months before Mastodon. And, unlike Mastodon, it plays ActivityPub by the book as far as possible/feasible.

    Still, it has a character limit of, wait for it, 16,777,215. That's the maximum size of the database field for the post text. These characters include alt-texts because images are embedded into posts by hotlinking to them rather than being file attachments, but they do not include summaries (= Mastodon CWs) because they've got their own database field.

    Not only is it possible to practically not have a character limit at all, but it has actually been done, and it's fully compatible with Mastodon (only that Mastodon rejects posts with over 100,000 characters AFAIK, another arbitrary design decision which makes even less sense).

    CC: @Cory Doctorow

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Hubzilla #CharacterLimit #CharacterLimits #500Characters
  23. @C.Suthorn :prn:
    And note: this toot has more than 500 characters, but comes from mastodon (as you can see), in case you didn't know that toots on mastodon can have more than 500 characters.

    I know that. But I also know that not exactly few Mastodon users completely freak out when they see something longer than 500 characters.

    #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #CharacterLimit #500Characters
  24. @utopiArte I wasn't only posting this with raw technology in mind. I was also thinking about cultural differences that arose from the technological differences.

    Friendica and Hubzilla are technologically very different from Mastodon. Friendica, Hubzilla and (streams) users are rather used to that. They try to cope with it the best they can, although this alone brings its own bunch of issues with itself.

    Mastodon users, on the other hand, are not used to it. Many of them have come to Mastodon from Twitter over the last two years, believing that Mastodon is only one Web site. And pretty much all of them, every last one of them, came to Mastodon, believing that the Fediverse that everyone talks about is Mastodon. And nothing else.

    Those who have invited them to Mastodon have not told them that Mastodon is connected to things that aren't Mastodon, much less that Mastodon is connected to things that are very much not Mastodon.

    Nearly all Twitter refugees on Mastodon have spent their first several months on Mastodon in this belief. They've settled into and gotten used to a Fediverse that's only Mastodon.

    Many, not all of them, but many have since found out that there are things in the Fediverse that are very different from Mastodon. For not exactly few, it was a disturbing, if not outright traumatising experience to see that some Fediverse users can post over 500 characters at once. Or that some Fediverse users can easily "quote-toot" Mastodon toots, using something which is used on 𝕏 to harass members of marginalised minorities.

    They didn't want that. They still don't want that. They want to make it go away again, so disturbing is it.

    By and by, at least some Mastodon users face other differences between Mastodon on the one side and things like Friendica, Hubzilla and (streams) on the other side. For example, what the way these three handle conversations means in practice for users of Mastodon which doesn't have a concept of conversations. Or that Friendica, Hubzilla and (streams) users do not react when someone on Mastodon mentions them out of the blue. Everyone on Mastodon would notice it, so it's beyond a Mastodon user's comprehension that Friendica and Hubzilla users don't notice it by default.

    So on the one hand, Mastodon users are increasingly stressed out by Friendica being Friendica and Hubzilla being Hubzilla. They ask themselves: "Why did they make everything so different from Mastodon? Why couldn't they have made it all just like Mastodon in the first place?"

    It's incomprehensible to them that Friendica and Hubzilla were both made before Mastodon. For how can something in the Fediverse possible pre-date Eugen Rochko's invention of the Fediverse? It's also incomprehensible to them that something in the Fediverse can be something else than a Twitter clone. Or they simply don't know how Facebook, which Friendica aims to be an alternative to, works differently from Twitter as well.

    On the other hand, Friendica, Hubzilla and (streams) users are increasingly stressed out by Mastodon users trying to force Mastodon's culture upon them, along with Mastodon's limitations. Not few Mastodon users try to make Friendica, Hubzilla and (streams) behave more like Mastodon by putting pressure on their users to a) always do everything the Mastodon way and b) stop making use of features that Mastodon doesn't have.

    If you've never come across a Mastodon user complaining about a post or comment of yours being too long because you've exceeded the holy limit of 500 characters, then I'm very certain that you will.

    Food for thought: This entire conflict would disappear with a split. Mastodon users would be spared from utterly non-Mastodon things. And non-Mastodon uers would be spared from demands to stop making use of 90% of all features they have at hand just because Mastodon doesn't have them.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #CharacterLimit #CharacterLimits #500Characters #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate
  25. @Lunawawa :neofox_snug: :therian:
    vanilla mastodon is somehow the only software that doesn't allow admins to adjust the character limit.

    They can adjust the character limit. But it requires digging into the source code because the limit is hard-coded. Basically, if you as an admin want a higher character limit, you have to soft-fork Mastodon.

    And whenever you upgrade your instance to a new version, it's force-rebased to vanilla, and you have to soft-fork it and apply your changes again.

    Better yet: Changing the character limit by modifying the source code is, technically speaking, illegal. It would only be compliant with the GNU Affero General Public License if the admin uploaded the modified code to GitHub as a fork of vanilla Mastodon. But no Mastodon admin even only goes through the hassle of learning git just to have more characters.

    CC: @Elena Brescacin

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AGPL #Mastodon #CharacterLimit #CharacterLimits #500Characters
  26. @Spooky Panda Bear 🌈 Quick and easy solution:

    Move away from Mastodon. Go someplace else in the Fediverse that doesn't have a 500-character limit.

    Move to Pleroma (5,000 characters, configurable by admin).
    Or Akkoma (5,000 characters, configurable by admin).
    Or Misskey (3,000 characters, hard-coded).
    Or one of the several Misskey forks (thousands of characters again, configurable by admin).
    Or Friendica (unlimited characters).
    Or Hubzilla (unlimited characters).
    Or (streams) (unlimited characters; that is, the database can handle a bit over 65,000 characters on older instances with no database upgrade and over 24,000,000 characters otherwise).

    All of them are in the Fediverse. The Fediverse is not only Mastodon. All of them are connected to Mastodon. Proof: This comment comes from Hubzilla.

    And then do something that nobody on Mastodon would even come up with the idea to do:

    Put the excerpt into the post.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Firefish #Iceshrimp #Sharkey #Catodon #Friendica #Hubzilla #Streams #(streams) #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CharacterLimit #CharacterLimits #500Characters
  27. @AVILIFE
    I want to write longer posts though.

    You've got lots of options for longer posts in the Fediverse, just not on Threads and most Mastodon instances.

    One would be a Mastodon instance with a "hacked" character limit, but you'd have to ask around to find these. There are Mastodon forks which allow the admins to change the character limit without editing the source code, but at least the instances of Glitch identify as Mastodon instances, so I think they aren't listed separately elsewhere.

    The farther you move away from Mastodon, the better its gets, but the more different it becomes from Mastodon.
    • Misskey is hard-coded to 3,000 characters (careful with Misskey instances; their lighthouse instance, misskey.io, is hosted in Japan with rather lax rules and banned by just about all Western Fediverse instances).
    • Misskey forks (such as Firefish, Iceshrimp, Sharkey or Catodon) usually have configurable character limits which AFAIK start at 4,000 to 8,000 characters and can be configured.
    • Both Pleroma and Akkoma have defaults of 5,000 characters and can be configured.
    • Friendica has no limit, other than how many characters the database can handle at once, and I guess that's millions. However, it's here where we aren't talking about Twitter-like microblogging anymore. This is "Facebook alternative meets long-form blogging with all bells and whistles plus built-in cloud file hosting plus federation with everything that moves" territory, not to mention five and a half years older than Mastodon.
    • Hubzilla is a fork (of a fork?) of Friendica by Friendica's own creator. It's unlimited, too. Its predecessor introduced concepts like multiple fully independent identities on the same login, extensive permission settings and nomadic identity, and it adds a big pile of extra features on top of Friendica.
    • Lastly, there is also the streams repository which contains an officially nameless and brandless fork of a fork of three forks of a fork (of a fork?) of Hubzilla, created and still developed by the same guy who created Friendica, Hubzilla and all forks in-between. It has lost most of the extra features Hubzilla has that Friendica doesn't (articles, wikis, Web pages...), but it evolved the extra technology that Hubzilla had introduced over Friendica. Its permission settings have been improved, it works even better with ActivityPub, and it's currently introducing native nomadic identity via ActivityPub. Instances launched before June with no database upgrade are limited to ca. 65,000 characters and don't fail gracefully if that limit is exceeded; instances with database upgrades and newer instances can handle over 24,000,000 characters. However, (streams), as it is being nicknamed by its users, is still a handful. Its UI is a little better than Hubzilla's, it still handles very differently from Mastodon, it's currently in a state of technological flux, and there are no official or third-party instance lists and exactly zero mobile apps that work with (streams), save for generic mobile Web browsers.

    Be warned, by the way: Some Mastodon users strongly dislike things that aren't possible with vanilla Mastodon. This especially includes posts over 500 characters.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #GlitchSoc #Glitch_Soc #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Firefish #Iceshrimp #Sharkey #Catodon #Friendica #Hubzilla #Streams #(streams) #500Characters #CharacterLimit #CharacterLimits
  28. Writing in my journal just now, and my internal/mental alarm just went off.

    Guys, this is just stupid. Make it 5000 characters already.