Find the latitude of any place.  

Ruby Walshs Saturday ITV Racing best

Ruby Walshs Saturday ITV Racing best bets

Rubys giving the dual Derby winner another chance in the St Leger. Ruby Walshs Saturday Racing Tips 13:15

How Ukrainian Drones Are Crippling Russias Oil Refineries

Fire at the Afipsky refinery in Russia, August 28, 2025 Photo: Astra Ukraine is waging a campaign to
-rangedrones

I guess if a Fediverse actor uses ActivityPub, regardless of whether or not it's that actor's base protocol, that actor should count.
Still, there are various issues and open questions as has already pointed out.
Of course, one question is, where does the Fediverse end Especially if the definition of Fediverse is "Mastodon and whatever connects to it"
Hubzilla is not based on ActivityPub. Its creator (who now maintains (streams) and Forte) says it's based on Nomad whereas its maintainers insist that Hubzilla's base protocol is still named Zot. Anyway, it does support ActivityPub. However, like almost all non-nomadic protocols and connectors, ActivityPub support is an add-on that's optional and off by default on new channels. At hub level, ActivityPub is still optional, but on by default when you set up a new hub.
This can mean three things:

But if Hubzilla is not part of the Fediverse, am I even allowed to communicate with you all
(streams) is a bit different. It's based on Nomad and not on ActivityPub. But ActivityPub is part of the core and no longer an add-on, and it's on by default both at server level and at channel level. ActivityPub can still be deactivated both at channel level and at server level.
Forte is identical to (streams), except that it's based on ActivityPub, support for Nomad has been removed, it has a name, it has a brand, it's a project, it's MIT-licensed, and it has nodeinfo (which is intentionally absent from (streams)).
But these two have another "nefarious" feature plus one more that has yet to be rolled out to the release branch, both of which may put them on the edge of the Fediverse.
One, at server level, is the "Uafilter" which is short for "User Agent Filter". It can filter out entire Fediverse server applications by user agent. Its main purpose is to keep Threads out without having to enter new URLs or IP addresses into a filter all the time. However, it's not only capable of locking out the entirety of Mastodon in one fell swoop with no collateral damage, but that's also explicitly a secondary purpose.
The other one, also at server level and currently only available in dev, is "FedUp" which is short for "Federate Upstream". When activated, it only allows federation with servers that provide managed threaded conversations. In other words, it locks out all microblogging servers.
If the Fediverse is defined as "Mastodon and whatever connects to it", these two are features that'd lock at least certain (streams) and Forte servers out of the Fediverse because they are disconnected from all of Mastodon in one way or another.
# # # # # # # # # # # # # # To my best knowledge, this is a feature that only Mastodon has.
But the Fediverse is not only Mastodon. I'm not on Mastodon myself. I'm on Hubzilla which has nothing to do with Mastodon, and which has been developed independently from Mastodon since over five years before Mastodon was launched.
And while , it does not have per-post language setting.
So no, I can't set any language for my posts, comments and DMs.
CC:
# # # # # # # # # # # # #
I've had to sit through it all again, why shouldn't you

I'm so very much not going to go back through my entire Hubzilla image post log and add image descriptions to every last one of my images.
Call me ableist. Call me lazy. But I simply don't have the time and the energy. And I'd need a whole lot of time and a whole lot of energy because when I describe images, I invest more of both into describing one image than you invested into describing all images on your entire travel blog.
Each of my original images gets two descriptions: a "short" description in the alt-text (which is actually still massive even by Mastodon standards, much less by Web standards) and a "long" description in the post text which also contains all explanations necessary to understand my images as well as transcripts of all text within the borders of the image, for any definition of "text". The description in the alt-text may only contain text transcripts if they're only few and short enough.
A simple image may require a long description of 20,000-30,000 characters. A complex image may require a long description of well beyond 50,000 characters. My personal record is slightly over 60,000. If I'm also required to describe all images within my image, the long description may grow so long that the post exceeds 100,000 characters, a length at which Mastodon will reject it.
That said, if I go and add alt-texts to old posts from three years ago that are actually pretty much outdated, Mastodon won't understand it as an edit but rather as a brand-new post. I'd flood my contacts (or at least those who haven't silenced me) with old content which isn't even obviously old.
Also, if I do and alt-texts to old image posts that don't have alt-texts yet, the image description quality will decline sharply from the newest image post with freshly added image descriptions and the first image post that already had image descriptions. This means that I'd also have to go and edit and upgrade all those of my image posts that already have alt-texts so that everything is at the same level of quality. I'd have to upgrade all image posts on this channel because they're all outdated.
By the way, one of these images contains well over a dozen "persons" for any definition of "person" (actually only a handful of digital avatars and otherwise static figures), probably over 200 individual vintage album covers and a whole lot of other details. The amount of necessary visual descriptions is already staggering, but then all the necessary explanations will come on top.
I'd also have to describe images that aren't technically from me, but that are included in shares, better known as quote-posts outside of Hubzilla. (Hubzilla has had quote-posts for 13 years now, and it can theoretically quote-post anything from Mastodon toots to blog posts.) These quote-posts are only dumb copies of the originals, so I could add alt-text to images without alt-text. But for one, that'd mean to "falsify" the quoted posts because I can't add alt-text to the originals.
Besides, I can't describe the images properly anyway. See, I don't describe images by looking at the image. I describe images by looking at the real thing because the image doesn't show enough details. But I'd have to figure out where all these images in the quote-posts were made. Some of these places no longer exist, so I can't visit them for a close-enough look anymore. Ithers have changed too much, and none of them still have the same avatars in the same outfits in them as seen in the images.
Some of the images in the quote-posts are animated GIFs. That'd add an extra level of complexity in the shape of a time-coded description of what is happening in the image and when. Some images show highly complex animated art installations that even include light effects. It would take me an eternity to describe these adequately, that is, unless I fail trying.
While I'm editing these posts, I'd also have to give them proper summaries and content warnings (including "long post" when the added image descriptions inflate a post from previously only a few hundred to tens of thousands characters), bring the hashtags up to my current standards etc.
And in fact, I'd have to delete almost all image posts anyway and repost those that aren't quote-posts on my two (streams) channels, and . That's because pretty much all my old image posts contain eyes in some way, so they're eye contact triggers. But Hubzilla doesn't have any way of making certain Mastodon user interfaces hide them, not if they don't make images disappear behind content warnings as well (Mastodon before 4.4 doesn't do that either, by the way). (streams) does have such a way which is why I only use (streams) to post images nowadays, that is, if I ever get to posting new images and describing and explaining them properly.
Well, and if I deleted these old posts with their outdated or completely missing image descriptions, I'd also delete entire conversations with some very important comments in them. But if I didn't delete them and edited them, I'd trigger someone somewhere out there with eye contact.
# # # # # # # # # # # # # # # # # # # # # #
you don't understand several critical guidelines to ALT text as an accessibility tool.

What you fail to understand is that every last one of these "several critical guidelines to ALT text as an accessibility tool" is written for the Web and only for the Web. That they're all invalid in the Fediverse.
Alt-text wasn't introduced in the Fediverse by professional Web designers with accessibility certificates. It was introduced by complete laypeople who neither knew nor cared what WCAG is. These laypeople, and only them, built Mastodon's alt-text culture. Therefore, Mastodon's alt-text culture contradicts officially established Web accessibility standards. And here in the Fediverse, Mastodon's culture and Mastodon's standards supersede everything else. Everything else. Whether you want or not.
I've just added a new article to my wiki about this topic:
But everybody else is just going to use the advice provided to us by the experts in the field who have access to feedback from a wide range of users with a wide range of disabilities.

No.
Out there on websites and blogs, yes. But here in the Fediverse, especially on Mastodon, definitely no. And I've watched and examined Mastodon's culture for long enough to know.
Mastodon even works vastly differently from websites. All the features that you, as a Web designer, have at hand to make a website accessible by W3C standards and WCAG 2.2 guidelines, you do not have on Mastodon.
Mastodon doesn't have <figure><figcaption></figcaption></figure> for captions on embedded images that can be used to add explanations. Hell, Mastodon doesn't even support embedded images in any shape or form! And how are people supposed to add a long description or an explanation to a post if they've only got 500 characters at their disposal
This is why long alt-texts are part of Mastodon's culture and Mastodon's standards and here to stay, no matter what accessibility experts say.
And this is why Mastodon users often prefer long alt-texts over shorter ones, regardless of where a post actually came from, regardless of what possibilities that place has. In fact, many frontends still don't hide images behind content warnings. If a post is behind a content warning, the users of these frontends don't see the post, they don't see the long description in the post, they only see the image, and the only image description they're aware of is the one in the alt-text. And the one in the alt-text must already satisfy Mastodon users.
Just about everyone who describes images in the Fediverse either just wings it, or they go by Mastodon's culture and Mastodon's standards and what Mastodon likes.
Want to know what Mastodon likes in terms of alt-text Follow . Follow the # hashtag. I promise you that you won't believe your very eyes.
In all seriousness, I'd really like to see you use W3C standards and WCAG guidelines as weapons in a head-butting contest against members of Mastodon's alt-text police who refuse to boost an image post of yours because your perfectly W3C-and-WCAG-2.2-compliant, 160-character alt-text is not detailed enough by their standards, by Mastodon's standards. Bonus points if they dare to call you ableist for going against their enforcement of inclusivity.
The difference between the two of us, when it comes to image descriptions in the Fediverse is: You're book-smart because you try to apply standards to the Fediverse that don't work in the Fediverse, and you don't understand that they don't work in the Fediverse. I'm street-wise because I know what it's really like out there.
# # # # # # # # # # # # # # # # #
the (expected) time investment does add a bit of friction to my brain for the getting started process

Same here. In fact, worse yet: I already estimate the time needed to describe one of my images as several hours, but it actually happens again and again that this ends up an underestimation.
, for example. I thought that it's a fairly simple motive, and I'll be done in six hours or so. It actually took me two full days to describe that image.
I've only posted new original images once since then, and . I hope to get a series of new images described before the end of the year, but I've been working on these descriptions on and off since late last year, and I think I'll have to largely rewrite the big explanation block in the common preamble to reduce the jargon to an absolute minimum and explain even more instead.
CC:
# # # # # # # # # # # Long
The people who complain about it - honestly how many pictures are they posting every day How many seconds of their life are they complaining about Is it less than the amount of time they spend complaining

I've once spent over 100,000 seconds, that's some 30 hours, describing one image.
Look up the hashtag # on mastodon.social and scroll all the way down. There is that post in question.
I've only sent one more post with original images since, and that was over a year ago. That post hasn't made it to mastodon.social, so .
I've spent more time describing one image than anyone has spent complaining about having to describe images. And if I don't feel like spending hours describing an image, I don't even take images, much less post them. Easy as that.
CC:
# # # # # # # # # # # # # # # First of all: They're probably useful for sighted people as well. But just like there are people who can't see your images, . Hence, explanations always go into the post text.
That said, don't worry too much about wordiness. Maybe it's justified. Maybe it's even (provided you don't have a 500-character limit, that is).
I myself see it . My most extreme example has to be . One image. Over 60,000 characters of highly detailed image description plus explanations plus text transcripts, that's over 10,000 words, enough for a screen reader to ramble for at least three hours. It took me two full days, morning to evening, to research for this image description, to look around in-world, to see all the details, to read all the bits of text, to retrieve additional information for the explanations and to write this monster.
Early the third day, I distilled an additional, 1,400-character "short" image description from it for the alt-text to , no matter how high their minimum standards were at that time. Granted, the "short" description had no room for any text transcripts, much less all of them, and there are larger elements in the image that I couldn't even mention in the alt-text, so that could be criticised. It's about 1,400 characters because I needed some room to tell people about the long description in the post itself.
Ever since I've posted this picture, I've refrained from even taking pictures with too many details and too much scenery because I'm not too keen on spending multiple days describing one image too often. But even , my last image post so far from over a year ago, ended up with over 25,000 characters worth of explanations and descriptions in the post itself plus alt-texts with "short" descriptions that are just short of 900 characters each, leaving more room to guide people to the long descriptions.
CC:
# # # # # # # # # # # # # # # #
trying to find ways to describe pictures, gifs and videos in a way that's both easy to understand but also in-depth is always a fun challenge

In my case, "easy to understand" requires "in-depth".
See, my original images go way beyond yours in terms of obscurity. I post renderings from super-obscure 3-D virtual worlds. This means that if people can't see the images, they don't have any realistic idea what anything in my images looks like. And regardless of whether or not they can see the images, they don't have the foggiest idea what it really is that's in these images and where they are from.
Still, they may be curious. After all, my images are proof that 3-D virtual worlds are, in fact, not dead, especially since the kind of worlds that I frequent has been regularly, casually using the term "metaverse" since 2007, 14 years longer than Zuckerberg.
If they're sighted, they might not care for the context. Instead, they might take in all the big and small details in the images (if there are any) and basically go explore a whole new and unknown world just by looking at one or a few images. However, "accessibility" and "inclusion" mean that blind or visually-impaired people must have the very same chance to do the very same thing. But they can't do it if I don't describe my images in all details.
And so I end up with absolutely super-massive image descriptions, including text transcripts and all necessary explanations, in my posts plus "short" but not exactly short descriptions in the alt-text of each image.
and if it helps someone at all (may it be if they use a screen reader or don't understand some parts of whatever I share) that makes it all the better for me

This is exactly why I go to such great lengths. And in fact, I've been told at least once or twice that someone actually needed an image description at this extreme level of detail, even if it took them hours to read it.
# # # # # # # # # # # # # #
Meanwhile #
& # have some groups too.

Friendica has groups. Hubzilla has groups called "forums". Both have had groups for longer than Mastodon has even been around.
(streams), a fork of a fork of three forks of a fork (of a fork) of Hubzilla created and still maintained by Friendica's and Hubzilla's own creator, has groups.
Forte, a fork of (streams) by the same developer again, has groups.
All four are in the Fediverse. All four are federated with Mastodon (Hubzilla optionally and off by default, (streams) optionally and on by default, Friendica and Forte always). By the way, this comment comes from Hubzilla.
For self-hosters: All four are written in PHP, and they require no more than a LAMP stack. But if you don't know them, e.g. if all you know in the Fediverse is Mastodon, I recommend you try them out on a public server before setting up your own one. They're all very different from Mastodon in a lot of ways. Don't just expect Mastodon with groups because that's far from what they are.

How they work


A Friendica group is an account with special settings. Likewise, a Hubzilla forum or a (streams) or Forte group is a channel with special settings.
Speaking in Mastodon terms, what they do is take incoming posts and automatically boost them to all their followers.
An exception exists on Friendica, Hubzilla, (streams) and Forte themselves: If you're there, you must send a DM to the forum/group. Public posts to a group/forum are not forwarded, only DMs are. This ensures that a group/forum doesn't forward any and all posts that happen to mention it.

FLOSS


Friendica is open-source () and under the GNU Affero GPL v3.
Hubzilla is open-source () and under the MIT license.
(streams) is open-source () and in the public domain.
Forte is open-source () and under the MIT license.

Character limits


The character limit on Friendica and Hubzilla is over 16.7 million.
The character limit on (streams) and Forte is over 24 million.
Nobody will run out of characters anytime soon, no matter from where they post. However, this also means that neither of the four has Mastodon's character-limit-induced culture of brevity.

Moderation


Friendica groups can be co-moderated/co-administrated by users on the same server as the group.
Hubzilla forums, (streams) groups and Forte groups can be co-moderated/co-administrated by anyone on Hubzilla, (streams) or Forte.
Two of the public (streams) and Forte group types allow for new content to be moderated: Any new post or comment must be manually approved by the moderators. In both cases, this is mainly for new members. Trustworthy members can be permitted to post or comment immediately.

Privacy and security


Friendica groups, Hubzilla forums, (streams) groups and Forte groups can optionally be hidden from directories and made "secret".
Friendica groups can optionally be set to private, i.e. non-members can't see the group profile, the member list or what's going on in the group.
On Hubzilla, (streams) and Forte, the profile, the member list and the stream can be reduced in visibility separately from each other. You can make the group profile public, and at the same time, you can only permit group members to see the member list and/or the stream.
Hubzilla offers eight levels of permission for seeing the forum's main profile, additional profiles that can only be seen by members/certain members, eight levels of permission for seeing the forum's member list and eight levels of permission for seeing the forum stream. One level of permission depends on individual permissions for certain members granted by contact role.
(streams) and Forte offer four group types, one of which is private, four levels of permission for seeing the group's member list and four levels of permission for seeing the group stream. The non-public levels can be overridden by granting individual permissions to certain members.
(streams) and Forte also offer the same four levels of permission plus overrides for searching the group stream.
Note: It may not be possible to join a private group/forum with an account on Mastodon or anything else that isn't one of these four. Public groups/forums can be joined by anyone (unless they're blocked, of course).

Resilience


Hubzilla, (streams) and Forte offer , i.e. the forum/group channel can exist simultaneously on multiple servers as live, hot, bidirectional backups of each other. If one server goes down, the forum/group lives on on the other server(s).
Something like this has been announced by Bluesky as a new and revolutionary technology. Bluesky has yet to deliver. Hubzilla has had this technology since 2012.
Downside: Server software that doesn't understand nomadic identity, i.e. everything except Hubzilla, (streams), Forte and at least the development branch of Mitra, sees the instances of a cloned, nomadic channel as multiple individual, independent accounts.
CC:
CC so that everyone else in this thread will read this, even if they're on Mastodon (I wouldn't have to do this if the whole Fediverse supported threaded conversations, and everyone got this automatically anyway, but I don't want to post this several times over because someone on Mastodon hasn't received it due to Mastodon's intentional, by-design limitations):
Also:
re-toot & boost my post if you find it helpful

Twitter = Retweet
Mastodon = Boost
Twitter = Like
Mastodon = Fave
# # # # # # # # # # # # # # # # #

Long Reef shark attack: NSW suspends net removal plan pending review

He suffered critical injuries and died at the scene, leaving behind his wife and young daughter. Long Reef

The very definition of alt-text is that it's a written replacement for the image. It is meant to convey the relevant visual information in the image. It is not meant to convey any information not immediately available in the image.
Alt-text was not invented for Mastodon. It's way older than Mastodon. It was made for websites. And on a website, the alt-text describes what can be seen in the image, and if necessary, either a caption right below the image or the text in which the image is embedded explains the image.
The real problem is Mastodon's tiny character limit. Mastodon offers 1,500 characters in alt-text, but only a measly 500 in the actual post, minus the CW, minus mentions, minus hashtags. Thus, Mastodon's culture has pretty much declared it okay to put additional information into the alt-text and, when I mention that this is not accessible to the point of actually being ableist, blame all user interfaces that aren't the Mastodon 4.4.x Web interface.
What's even worse is that this is widely, namely all across Mastodon itself, considered the one and only Fediverse standard. And for newbies and people in Mastodon-only bubbles, this is not the Fediverse standard, this is the Fediverse because the Fediverse is only Mastodon.
For comparison: I'm not on Mastodon, not even on a fork. Hubzilla is ten months older than Mastodon, based on Friendica from the same creator which is about four and a half years older than Mastodon, and both are developed completely independently from Mastodon. When Mastodon was launched, it immediately federated with both. Their character limit is defined by the size of the database field that stores posts: over 16.7 million characters. And even beyond that, they've got lots of features which many Mastodon users wish "the Fediverse" had and even features that are completely unimaginable for Mastodon users.
In the early Fediverse, it was these two that set the quality standards. But then came Mastodon with its intentionally, painfully limited set of features and a character count which Twitter refugees considered huge, but which is actually tiny, and for which there is no technical reason. Not only did Mastodon present itself to new users as an enclosed network of its own named "Fediverse", but by doing so and quickly growing to a staggering size, it forced itself into the position of the (perceived) Fediverse gold standard.
Now we're in a situation where some 99% of all the millions of registered Mastodon users spent their first months or even years believing that the Fediverse is only Mastodon, and in fact, many still believe that. Those who learn the hard way (e.g. by having a 4,000-character comment full of text formatting dropped into their timelines) that there's much more to the Fediverse than Mastodon still think that Eugen Rochko has invented the Fediverse and ActivityPub, that Mastodon was there first, that Friendica, Hubzilla & Co. are "intruders" that were only recently created to connect to the Mastodon Fediverse, and that if something surprisingly turns out different from Mastodon in some way, it's broken.
This is also where Mastodon's culture came into play. Mastodon's culture as we know it today was completely coined in spring/summer 2022 by the February/March 2022 Twitter migration wave that was caused by Elon Musk's announcement to buy out Twitter. This migration wave was so huge that, at least within their own bubbles, these Twitter migrants hugely outnumbered the already present Mastodon users to the point of barely even noticing that Mastodon already had users, sometimes leading to the idea that Mastodon itself didn't exist before February 2022. And so there was no influence on Mastodon's culture from Mastodon veterans and even less from non-Mastodon Fediverse users who never had anything to say on Mastodon anyway.
And so Mastodon has a culture that's based on Mastodon 3.x, that doesn't even include new features from Mastodon 4.0. And this culture is being forced upon the whole rest of the Fediverse while disregarding how the rest of the Fediverse does things itself. To many, "the Fediverse" is a Twitter-cloning microblogging platform invented by Eugen Rochko with no more than 500 characters, full stop. Anything that's caught deviating from this, from Mastodon, is disturbing and wrong.
# # # # # # # # # # # # # # # # # # # # #

Air NZ adventure beyond sale: Discounted flights to New York, Tokyo, London and more

We know Kiwis love to dream big when it


This may come as a surprise, but: Just like not everyone can see the image in your post, , be it due to a physical disability, be it due to technical limitations. And yes, there are people in the Fediverse who really can't access alt-text.
Anything that isn't in the post text body, that isn't in the image, that's only in the alt-text, is inaccessible and therefore permanently lost to all these people.
If you absolutely need more than 500 characters, you'd better move away from (vanilla) Mastodon and to elsewhere in the Fediverse, for example:
All these are part of the Fediverse, and all these are (optionally in Hubzilla's case) federated with Mastodon, so you can post to the same people from there as from Mastodon, and you can follow the same people there as on Mastodon.
# # # # # # # # # # # # # # # # # # # # # # # #
In that case, wouldn't it be better to have an option in the client to display the alt text below each piece of media without having to click anything

The problem with this is that it would have to be built into

Altogether, that's well over a hundred user interfaces. And anyone who can't open an alt-text may use any of these, so you can't just pick one or two to modify accordingly. Way too much of an effort just so that nobody will have to change their ways.
Because sometimes we don't even have enough space to properly explain the media in the post itself due to the 500-character limit. So I guess we'd have to make a thread Does that also mean that we should only add one image per post, since some people can't click to expand it

As a short-term solution, or if you absolutely, absolutely must stay on whichever vanilla Mastodon server you're currently on, a thread is the easiest solution, although long posts cut into threads annoy some users in certain non-Mastodon parts of the Fediverse.
However, if you regularly post images that require extensive explanations, there are better solutions in the Fediverse that let you post everything in one piece, for example:
All these are part of the Fediverse, and all these are (optionally in Hubzilla's case) federated with Mastodon, so you can post to the same people from there as from Mastodon, and you can follow the same people there as on Mastodon.
# # # # # # # # # # # # # # # # # # # # # # # # If it isn't obvious what an (important) object in an image is, the information goes into the post text.
If the information is necessary for the visual description of the image, i.e. turning the image into words, the information goes both into the alt-text and into the post text.
I've got more than two years of experience at describing images that show things way more obscure than a can opener. And in fact, I always have two image descriptions, one in the alt-text and a much longer one in the post text.
# # # # # # # # # # # Unfortunately, you can't make absolutely everything 100% perfectly accessible to absolutely everyone.
It may happen that I describe one of my images with 900-1,400 characters in the alt-text and then again with 25,000-over 60,000 characters in the post text itself (actually been there, done that). I know that there are neurodivergent people who actually need such a super-detailed description with lots of explanations. If I only wrote a 200-character alt-text, I'd throw them in front of a bus.
On the other hand, there are people who do require an alt-text of no more than 200 characters. If I describe one of my images in even only a little more, I throw them in front of a bus.
The only way of being perfectly accessible would be to stop posting that kind of images, or at least to stop posting them in public and only limit them to maybe one or two dozen certain people.
# # # # # # # # # # # # # "People wondering WTF they're looking at" need an explanation.
But:
That's because , just like not everyone can see the image in an image post. And yes, this may be due to a physical disability.
Any information that's only in the alt-text, but neither in the post text nor in the image itself, is inaccessible and therefore permanently lost to these people.
Explanations always go into the post text body where everyone can access them!
Money quote-posts from someone who actually does have a physical disability that keeps her from accessing alt-texts:
Done right also means accessibility for people who might not know much about your image's subject matter either. The person who posted this is simply flat out incorrect. Alt text is INACCESSIBLE to many disabled people. If the extra text is important, it needs to be in visible text.

I have a disability that prevents me from seeing alt text, because on almost all platforms, seeing the alt requires having a screenreader or working hands. If you post a picture, is there info that you want somebody who CAN see the picture but DOESNT have working hands to know Write that in visible text. If you put that in the alt, you are explicitly excluding people like me.
But you dont have to overthink it. The description of the image itself is a simple concept.
CC so that everyone in this thread will read this, even if they're on Mastodon: christophequeretmastodon.green
# # # # # # #

for

Since the until , the against in
has been escalating. This is not something that happened
suddenly, but rather an from within each who feels
alienated and deprivedboth of their and the surrounding
over the course of many . Many have not only
witnessed but have also directly experienced this deprivation.

This has grown even more as people witness the , especially
seeing the widespread resistance in various cities across Indonesia over
the past few days. The anger intensified further after the confirmation
that 10 people had lost their lives.

The has attempted to suppress this anger through various
means, such as deploying the and forces,
, and conducting operations to control the
situation. All of these actions represent against
the ongoing resistance.

Therefore, this call for international solidarity aims to spread the
of resistance from Indonesia to the outside , so that
everyone understands that this resistance is not limited to Indonesia
but has spread far and wide, like a . Every form of , no
matter how , is incredibly meaningful to us here.

!

Ontario launches pilot to let seniors living at home use LTC resources

Descrease article font size Increase article font size The Ford government is launching a new pilot system to
-termCare

What are you expecting Do you think a totally* blind person would comment "Wow, you really captured the essence of that tree".

I'm someone who'd rather roast people's alt-texts if they don't adhere to the rules of writing alt-text. Yes, there are rules, and these rules are necessary for alt-texts to, for example, work everywhere. Granted, most of these rules are completely unknown in the Fediverse, also because there's no single place where all these rules can be found (working on that).
What I personally expect Any of these, for example:

# # # # # # # # # # # # # # # # # # # # # # # # # # Truth be told, and I speak from personal experience, sometimes feedback for image descriptions can be good.
For one, that's when you've only just begun, and you want to know if you're doing it right.
And then are the extreme edge-cases. Not the ubiquitous cat photos, but, for example, 3-D virtual world renderings because you have to assume that nobody is familiar with anything in the picture. Especially in such largely unexplored edge-cases, feedback is actually critical.
They say, "Don't worry, don't overthink it, just do it. Any image description is better than none."
Yeah, but then you "just do it" in a way that you think is good. And then these people are all like, "No, no, no, no, no! Oh my freaking gosh, not this way! This is literally worse than nothing!"
It's better to be told you're doing it completely wrong when you do it the first time than to be told you're doing it completely wrong when you've done it 50 times before.
I mean, . Next to everyone who advocates image descriptions is on Mastodon and only on Mastodon, Mastodon is horrible for discussions, and the places in the Fediverse that are good for discussions are either blissfully unaware of image descriptions, or they think alt-texts are another stupid Mastodon fad.
# # # # # # # # # # # # # # # Okay, jetzt gibt's erstmal Druckbetankung.
Neben mir ist der Oberguru wahrscheinlich , der auch betreibt. Sein Hub Whoville ist gut, aber man kommt nur auf Anfrage rein, weil er mit Spam zu kmpfen hat.
Ich bin mit noch ein paar mehr Hubzilla-Leuten verbunden, die drften das hier in Blde zu sehen bekommen (sofern nicht ausgerechnet jetzt die Netzgemeinde wieder ihre fnf Minuten hat).
Hauptschlicher Anlaufpunkt fr Hubzilla-Support ist das englischsprachige .
Am Mittwoch, dem 17. September, ab 19.30 Uhr veranstaltet (Mastodon) a.k.a. (Hubzilla) auf BigBlueButton den ersten Hubzilla-Workshop. Da ist jeder eingeladen.

Hubzilla-Workshop


 Hubzilla-Workshop


 
 
Der erste Hubzilla-Workshop!
Mit Aufzeichnung fr alle, die Hubzilla kennenlernen, souverner nutzen und bisher unbekannte Funktionen entdecken mchten.
Moderiert von , ,   und   .
Egal ob Einsteiger, Fortgeschrittene oder Entwickler gemeinsam mchten wir dazu beitragen, dass Hubzilla bekannter wird, leichter anzuwenden ist und noch mehr Freude bei der Nutzung bringt.
 


Auch wenn das jetzt der Hubzilla-Community vielleicht nicht schmecken wird: Falls dir Hubzilla doch einen Tick zu heftiger ist, gibt's vom Erfinder von Hubzilla auch eine Nummer kleiner und zugnglicher: (wird inoffiziell tatschlich in Klammern geschrieben und hat offiziell eigentlich berhaupt keinen Namen). habe ich mal ein paar Tabellen zusammengestellt, die Mastodon, Friendica, Hubzilla, (streams) und Forte, das jngste Familienmitglied, vergleichen.
Aber Vorsicht: Beide sind funktional, aber auch kulturell weit davon entfernt, Mastodon mit mehr Zeichen zu sein.
# # # # # # # # # # # # # # # # # #

ViVi Water

...

Looks like users are getting increasingly anxious that e.g. Mississippi and UK law enforcement will shut down every last OpenSim grid on the grounds of their age verification laws, what with none of them having verified the real-life age of all their users. Even if a grid runs in Kazakhstan under a Russian domain with a Kazakh and Russian admin team.
"This will so totally happen!"
The self-same people, however, appear not to be afraid at all that Linden Lab and Second Life content creators will shut down any OpenSim grid on the grounds of the Digital Millennium Copyright Act, what with almost all of them blistering with stolen Second Life content. Not even if a grid runs in the USA under a US domain with an all-American admin team.
"This will so totally never happen!"
Pray tell, why should the former wipe OpenSim out in no time while the latter hasn't even happened to one measly OpenSim grid in over ten years of copybotting tons of expensive premium luxury content in Second Life and offering it in OpenSim as full-perm freebies Not even after by Linden Lab themselves from early this year
Oh, and OpenSim cannot survive without selling the most private personal data of every last one of its users to some big, commercial, corporate age-verification service But at the same time, OpenSim cannot survive either without breaking international copyright and intellectual property laws left and right
Oh, and by the way: The most that Mississippi and the UK can do against a grid is try to fine it. The most that Linden Lab can do against a grid is Cease & Desist it out of existence.
# # # # # # # # # # # # # # # # # Es gibt immer noch Leute auf Mastodon, die sehen im Fediverse Twitter ohne Musk und mit 500 Zeichen. Die wollen, da das Fediverse Twitter ohne Musk und mit 500 Zeichen ist. Die versuchen sogar dafr zu kmpfen, da das Fediverse Twitter ohne Musk und mit 500 Zeichen ist.
Das Problem dabei ist aber: Das Fediverse ist nicht nur nicht Twitter ohne Musk und mit 500 Zeichen, sondern das war es nie, und deshalb wird es das auch nie sein. Egal, wie hart man dafr kmpft.
Den selbsterklrten Twitter-Klon Mastodon gibt es seit Januar 2016.
Friendica, das volles Rohr berhaupt nicht wie Twitter und Mastodon ist, gibt es schon locker fnfeinhalb Jahre lnger. Und als Mastodon an den Start ging, hat es sich sofort mit Friendica verbunden (und auch mit Hubzilla, einem Fork eines Forks von Friendica, der noch weniger wie Twitter und Mastodon ist).
Und das scheinen die meisten auf Mastodon nicht zu wissen. Und vom Rest wollen es viele nicht wahrhaben. Schon gar nicht, da das vllig normal ist, da das schon immer Teil der Idee hinterm Fediverse war.
Die glauben eher, Eugen Rochko hat 2016 das Fediverse erfunden, und alles andere ist entweder nachtrglich als Extra an Mastodon drangeklebt worden (PeerTube, Pixelfed etc.) oder ein bser Eindringling im Mastodon-Fediverse (Friendica, Hubzilla etc.).
Genau deswegen ist das Fediverse fr diejenigen wie ich, die nicht auf Mastodon sind, ein Minenfeld.
# # # # # # # # # # # # # # #

3,350 ERAM missiles heading to Ukraine heres how they can be used

Up to 3,350 and 3,350 navigation modules to counter spoofing will be procured

The new -range capabilities could help offensively, Whitaker said, adding: "Theyve already taken about 20% of Russias oil refining capacity last month."



<>

abgesehen davon ist PHP so wie JavaScript sehr langsam.

Ist nur komisch:
(streams) und Forte sind in PHP geschrieben und haben sehr, sehr viel mehr Features als Mastodon.
Hubzilla ist in PHP geschrieben und hat mehr Features als irgendwas anderes im Fediverse.
Trotzdem rennen alle drei Kreise um das in Ruby on Rails geschriebene, geradezu lcherlich unterausgestattete Mastodon.
Zugegeben, Pleroma und Akkoma, die in Elixir geschrieben sind und featuremig zwischen Mastodon und Forte stehen, sollen noch leichter sein.
# # # # # # # # # # # # # # # # # # # #

Passengers delayed at Auckland Airport due to heavy rain, strong winds

Its been an hour and 20 minutes since we landed now, they told the Herald. Latest update from

So, a bunch of stuff happened, not least of which was an ongoing struggle with Fibromyalgia/CFS and my apartment wound up looking like the star of one of those "Hoarders" tv shows. And that won't do, because this is the year that HUD comes around* (on September 23) and decides whether to recertify my subsidized housing complex for another decade of federal funding. And one thing HUD doesn't allow is apartment managers who allow their tenants to accumulate unreasonable amounts of clutter.
Our last few building managers (they tend to last about 1-2 years) here warned me about the clutter when they did their called-for annual inspections but they were willing to let it slide & so I was, too. So that's how I ended up here.
I've been chipping away at it, and made some progress and then yesterday a very nice lady form a local volunteer group came in to help me and we got *a lot* done.

So, today I am sore as hell. I was trying hard not to overdo it yesterday, and the helper lady was trying hard not to let me so, of course, I overdid it. My current struggle is that I need to go take a shower, which will help get all those lactic-acid fatigue toxins out of my muscles but my muscles really don't want to be marshalled up to contract & bend & so forth to get me across the room, and my nervous system doesn't want to face up to all that soreness.

But I know I'll feel better afterwards. C'est la vie/la guerre/la fibromyalogie**.

*The HUD inspectors might not even come to my apartment. There are 138 apartments, and they'll select about 10 at random for inspection so there's a roughly 7% chance I'll "win" that lottery.

**I don't speak French but I do make jokes, with tragic results as seen above.











#369 - Not sure why this needed to be three and a half hours long. I must be missing something.

Bauen die Workshops aufeinander auf oder kann man auch einfach so mal vorbei kommen

Wir haben jedes Mal Leute dabei, die zum ersten Mal bei der Sprechstunde sind und hufig auch erst seit kurzem berhaupt im Fediverse. Das ist also kein Problem. Und da baut auch nichts aufeinander auf.
Was ist Hubzilla

Oh, da mu ich weit ausholen. (Ich kommentiere brigens gerade von Hubzilla.)
Hubzilla ist das absolute, ultimative Featuremonster im Fediverse. Eine Art Allesknner, der Features hat, die fr die allermeisten Fediverse-Nutzer im Fediverse vllig unvorstellbar sind, aber auch Features, die sich viele im Fediverse wnschen. Wohlgemerkt, ohne zu wissen, da es diese Features im Fediverse lngst gibt.
Hubzilla ist im Prinzip "Facebook trifft WordPress trifft Google Cloud Services trifft noch mehr Zeug" im Fediverse, und es kann mit wenigen Mausklicks aufgebohrt werden zu "Facebook trifft WordPress trifft Google Cloud Services trifft Joplin trifft GeoCities trifft <irgendeine Wiki-Engine hier einsetzen> trifft noch mehr Zeug" im Fediverse. Ja, GeoCities. Man kann buchstblich Webseiten auf Hubzilla aufbauen.
Hier sind ein paar Links:

Hubzilla ist brigens lter als Mastodon.
Hubzillas Vater ist , ein pensionierter professioneller Software-Entwickler mit fast einem halben Jahrhundert an Erfahrung. Der hat schon 2010, noch vor dem in dem Sommer in den Himmel gehypeten diaspora*, eine extrem vielseitige und extrem leistungsfhige freie, quelloffene, dezentrale Facebook-Alternative gestartet, die ursprnglich Mistpark hie und heute als Friendica bekannt ist. Die gibt's heute hoch, sie ist Teil des Fediverse, und sie ist mit Mastodon fderiert, seit es Mastodon gibt.
Friendica ist kein Facebook-Klon, sondern eine Facebook-Alternative, die grundstzlich dieselbe Funktion haben soll wie Facebook, aber besser als Facebook ist. Friendica kann nebenher auch genutzt werden als vollwertiges Blogging-System mit allen Schikanen: Titel, Zusammenfassung, Kategorien, alles Mgliche an Textformatierung, beliebig viele Bilder mitten im Text eingebettet, ber 16 Millionen Zeichen.
Friendica wurde aufgebaut auf seinem eigenen Protokoll namens DFRN. Aber ein Killerfeature von Friendica war schon immer, da es sich in alle mglichen und unmglichen anderen Richtungen verbinden kann: Fediverse, diaspora*, Tumblr, WordPress, sogar Twitter, ein paar Jahre sogar Facebook und so weiter.
So ganz zufrieden war er damit aber nicht. Ein groes Problem war nmlich, da jedes Mal, wenn ein ffentlicher Friendica-Node dichtmachte, die Nutzer alles verloren. Auf die Lsung kam er 2011: nomadische Identitt, also die Mglichkeit, die eigene Social-Networking-Identitt gleichzeitig voll synchron auf mehreren Servern zu haben.
Dafr entwickelte er ab 2011 ein neues Protokoll names Zot, das genau diese Funktion bieten sollte. Um es zu implementieren, forkte Mike noch 2011 einen Friendica-Fork, den er im selben Jahr erstellt hatte, um mit verschiedenen Lizenzen zu experimentieren. (Deswegen steht Friendica heute unter der AGPLv3 und die meisten seiner "Nachfahren" weiterhin unter der MIT-Lizenz.)
So entstand etwas namens "Red" (von spanisch "la red" = "das Netzwerk"). 2012 wurde es komplett neu geschrieben gegen das Zot-Protokoll. Das war der eigentliche Startschu fr Hubzilla. Damals gab Mike brigens Friendica (das inzwischen auf die AGPLv3 relizensierte Original) an die Community ab. Ende 2012 wurde Red umbenannt in "Red Matrix", weil man "Red" nicht googlen kann.
Allerdings wurde die Red Matrix kaum angenommen, weil sie im Grunde Friendica mit vielleicht ein oder zwei weniger Verbindungsmglichkeiten und nomadischer Identitt war. Die meisten verstanden nomadische Identitt aber gar nicht, und von denen, die sie verstanden, glaubten viele, sie gar nicht zu brauchen, weil sie eh ihr Friendica-Konto auf ihrem eigenen Node hatten.
So gab es dann im Mrz 2015 den Schnitt. Mike und seine Mitstreiter aus der Community nahmen die Red Matrix und strickten sie um fr neue Zielgruppen, insbesondere Betreiber ffentlicher Server. Dafr wurden haufenweise neue, teilweise optionale Features drangebaut: WebDAV fr den eingebauten Filespace, ein CalDAV-Server, der das Frontend des Eventkalenders mitnutzt, ein CardDAV-Server, nichtfderierende Artikel, Planungskarten, Wikis, Webseiten usw. usf. Und das Ganze wurde umbenannt in Hubzilla.
Wir sind brigens immer noch zehn Monate vor dem Start von Mastodon.
Standardmig fderiert Hubzilla nur ber sein eigenes Zot-Protokoll. Es untersttzt immer noch einiges an nichtnomadischen Protokollen und Verbindungen, aber alles, was nichtnomadisch und bidirektional ist, ist optional und standardmig deaktiviert, mu also in einem neuen Kanal erst aktiviert werden. Darunter fllt auch ActivityPub, das Hubzilla seit Juli 2017 als allererste Software berhaupt implementiert hat, zwei Monate noch vor Mastodon.
Damit war aber das Ende der Fahnenstange noch nicht erreicht.
Mike wollte das Zot-Protokoll noch weiter entwickeln, und zwar auf Arten und Weisen, die mglicherweise die Kompatibilitt beeintrchtigten. Das konnte er nicht auf Hubzilla selbst machen.
Also gab er 2018 Hubzilla ab an zwei Entwickler aus der Community und forkte es. Erst kam Osada, das wohl zunchst als Entwicklungsplattform fr Zot6 dienen sollte, aber trotzdem noch die meisten von Hubzillas Verbindungsmglichkeiten hatte. Bei Osada wurde brigens fast alles wieder entfernt, was beim Umbau von der Red Matrix zu Hubzilla dazugekommen war.
Wie es aber zunchst aussah, wrde Zot6 nicht mit nichtnomadischen Protokollen zusammenspielen knnen. So entstand als zweiter Fork Zap ich glaube heute, Zap war ein Fork von Osada und nicht von Hubzilla. Jedenfalls behielt Osada die ganzen Verbindungsmglichkeiten, verlor aber nomadische Identitten. Zap wiederum blieb nomadisch, untersttzte aber nur Zot6.
Schlielich stellte sich heraus: Zot6 konnte sehr wohl mit nichtnomadischen Protokollen zusammenspielen. Also wurde Osada, wie es war, Anfang 2019 eingestampft. Die Idee, einen Osada-Kanal als Gateway zwischen Zap und dem Rest des Fediverse zu haben, war sowieso gaga und wenig praktikabel. Dafr wurde von Zap kurz darauf ein zweites Osada geforkt, das sich zumindest wieder mit ActivityPub verbinden konnte. Das war zunchst der einzige Unterschied zwischen Osada und Zap.
Im Laufe des Jahres wurden Osada und Zap stabil. Das heit auch, Osada war so stabil, da es keinen Grund mehr gab, warum Zap kein ActivityPub knnen sollte. Kurz darauf war der einzige Unterschied zwischen Osada und Zap neben dem Branding, da auf Osada-Servern ActivityPub standardmig aktiviert und auf Zap-Servern standardmig deaktiviert war. Weil auch das Kse war und nur unntigen Mehraufwand in der Entwicklung mit sich brachte, wurde das zweite Osada im Herbst 2019 komplett in Zap gemerget und eingestellt.
Weil Zap jetzt aber ein stabiler Daily Driver war, brauchte Mike wieder neue Entwicklungsplattformen fr Zot8. Dafr wurden 2020 ein drittes Osada, Mistpark 2020 (alias Misty) und Redmatrix 2020 geforkt. Es gab das Gercht, da sie verschiedene Stabilittsstufen darstellten. Tatschlich waren sie bis auf das Branding identisch, und es waren deshalb drei, weil Mike damit die Markenfetischisten im Fediverse trollen wollte.
Einen stabilen Release mit Zot8 gab es nie. Statt dessen kam im Frhjahr 2021 Roadhouse dazu als Fork von einem von den dreien. Das basierte eigentlich schon auf Zot11, aber Zot11 war zu Zot6 in keinster Weise mehr kompatibel. Also entschied sich Mike, das Protokoll in Nomad umzubenennen. Heute sagt Mike, alle Versionen des Protokolls heien jetzt Nomad die Hubzilla-Entwickler widersprechen ihm aber und sagen, Zot6 ist immer noch Zot.
Jetzt hatte Mike fnf Projekte, die unterschiedliche Protokollversionen nutzte, ansonsten aber dasselbe konnten und fast dasselbe UI hatten.
Up- und Crossgrades gingen brigens ganz einfach, in dem die Codebase des Servers umgestellt wurde. Man konnte von Zap nach Osada, Misty und Redmatrix 2020 upgraden. Man konnte zumindest zwischen Osada, Misty und Redmatrix 2020 hin und her crossgraden. Und man konnte von allen vieren nach Roadhouse upgraden.
Im Oktober 2011 forkte Mike Roadhouse in wieder etwas Neues. Dieses Mal ging er in eine ganz andere Richtung: Was er jetzt erschaffen hatte, hatte keinen Namen. Es hatte kein Logo. Es hatte keine Markenidentitt. Es war auch kein Projekt mehr. Alles mit voller Absicht und sehr gut begrndet. Noch dazu nahm er sogar die MIT-Lizenz weg und stellte es direktweg in die Public Domain. Damit wollte er noch grere Anreize fr Entwickler schaffen, es zu forken, um daraus etwas Eigenes zu bauen.
Das Code-Repository brauchte aber zwingend einen Namen. Also wurde es "streams" genannt (ein Stream ist von Friendica bis heute das, was auf Twitter ein Feed und auf Mastodon eine Timeline ist). Weil nun aber die Community etwas brauchte, womit sie diese neue Software bezeichnen konnte, nahm sie den Namen des Repository und packten ihn in Klammern, um klarzustellen, da das nicht der Name der Software war. Seitdem wird es seitens der Community "(streams)" genannt.
Von Zap, Osada, Misty, Redmatrix 2020 und Roadhouse konnte durch Rebasen auf (streams) geupgradet werden. Weil (streams) selbst aber keinen Namen, kein Branding und nicht mal einen festgelegten Identifier fr den Servertyp hat, bernahm es kurzerhand den Server-Identifier und das Logo von der vorherigen Software. Ich habe selbst mal einen (streams)-Server gesehen, der mit Zap angefangen hatte (wie aus der Subdomain hervorging) und zwischendurch mal Misty war (weil er als Misty gebrandet war), aber vom UI und von der Softwareversion her eindeutig (streams) war.
Zum Silvesterabend 2020 stellte Mike dann Zap, Osada, Misty, Redmatrix 2020 und Roadhouse ein. Wer noch einen Server betrieb, dem war dazu geraten, auf (streams) upzugraden.
(streams) wird heute noch von Mike weiterentwickelt. An Verbindungsmglichkeiten hat es neben Nomad auch Hubzillas Zot6 und optional, aber standardmig aktiviert ActivityPub. Sogar RSS- und Atom-Feeds werden nicht mehr untersttzt, um den Entwicklungsaufwand zu reduzieren.
Der letzte Fork kam im August 2024. Mike war ja damals einer der beiden Entwickler, die an nomadischer Identitt ber ActivityPub arbeiteten. Im Zuge dieser Entwicklung rollte Mike Portable Objects nach FEP-ef61 im Juni vom "nomadischen" Zweig von (streams) in den hauptschlichen Entwicklungszweig und im Juli von da in den stabilen Zweig aus. Was im Labor aber funktioniert hatte, sorgte im tglichen Einsatz fr Chaos, weil (streams) zuviele verschiedene Identitten zu jonglieren hatte.
Also forkte Mike (streams) im August zu Forte, entfernte jegliche Untersttzung fr Nomad und Zot6 und basierte das ganze Ding komplett auf ActivityPub, und zwar inklusive nomadischer Identitt. Das drfte hauptschlich passiert sein, um die Nomad- und Zot6-Identitten loswerden zu knnen, um das Chaos sichten zu knnen, aber auch, weil nomadische Identitt ber ActivityPub die Zukunft sein soll.
Zum 31. August warf Mike erst alle Brocken hin und wollte mit Entwicklung aufhren, weil das alles ein Riesenaufwand war. Er machte aber trotzdem weiter, weil sich in der winzigen (streams)-Community niemand fand, der (streams) und das noch instabile Forte htte bernehmen knnen.
Im September wurde erstmals ein Post von Forte durch das ffentliche Fediverse fderiert. Von da an gab es die ersten, die mit ihren eigenen Forte-Servern experimentierten. Und im Mrz 2025 erklrte Mike Forte offiziell fr stabil. (streams) lebt aber weiter, denn sein Killerfeature gegenber Forte ist, da es ActivityPub nicht braucht. Man kann es also als Zugbrcke verwenden, um das ganze ActivityPub-basierte Fediverse auf einen Schlag auszusperren.
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # Schon mal gehrt von
Das kommt von der finnischen Firma Jolla Oy, die wiederum hervorgegangen ist aus den Machern des Linux-Smartphone Nokia N9, nachdem die vom Microsoft-Handlanger und neuen Nokia-Chef Stephen Elop gefeuert worden waren, um beim Linux-Phone-Primus Nokia alle Spuren von Linux und FLOSS zu tilgen und durch Windows und Microsoft-Produkte zu ersetzen.
Sailfish OS ist ein Fork des Mer-Projekt. Mer wiederum ist ein Fork von MeeGo. MeeGo selbst entstand, indem Nokias Maemo und (ursprnglich) Intels Moblin zusammengefhrt wurden. Ein reines MeeGo ist nie auf Smartphones installiert worden auf dem Nokia N9 und dem Entwickler-Smartphone N950 mit Hardwaretastatur lief eigentlich Maemo 6 "Harmattan" mit MeeGo-1.2-Anteilen. Maemo, das zuletzt in reinrassiger Form in der Version 5 "Fremantle" auf dem legendren Nokia N900 lief, ist wiederum ein direkter Fork von Debian und enthlt tatschlich Debian-Quellen. Moblin wiederum ist eine Neuentwicklung, die RPM nutzt, der letztlich auch seinen Weg bis nach Sailfish OS schaffte.
Mit anderen Worten: Sailfish OS ist ein echtes GNU/Linux und stammt von einigen echten GNU/Linux ab.
Auf dem ursprnglichen Jolla 1, dem eigentlich als Entwickler-Smartphone gedachten Jolla C und dem fr den indischen Markt produzierten Intex Aqua Fish, das mit dem Jolla C fast baugleich ist, gibt es einen Android-Kompatibilittslayer namens Aliendalvik mit abschaltbaren Google Play Services und Google Play Store. F-Droid ist zustzlich vorinstalliert.
Auf Drittgerten, auf denen offiziell die nachtrgliche Installation von Sailfish OS von Jolla untersttzt wird (z. B. Sony-Xperia-Mittelklasse), gibt es Aliendalvik gnzlich ohne Google Play Services und Google Play Store, aber immer noch mit F-Droid vorinstalliert.
Auf Drittgerten, die nur seitens der Community untersttzt werden, gibt es Sailfish OS nur ganz ohne Aliendalvik, also gnzlich frei von jeglichen Android-Spuren, aber mit sehr viel weniger Apps zur Verfgung, also auch ohne Android-Apps im Jolla Store.
Der einzige Nachteil von Sailfish OS ist ansonsten, da die ganze grafische Benutzeroberflche bis heute closed-source ist. Das kann man ablehnen aus prinzipiellen Grnden oder aus Furcht, Jolla htte in der GUI Spyware versteckt.
CC:
# # # # # # # # # # # # # # Important to know:
You must never, ever, ever .
The reason is because . Some can't due to physical disabilities. And those who can't access alt-text can't access your extra information in the alt-text at all.
Explanations and other additional information always go into the post text itself!
# # # # # # # # # Hier noch ein paar Ergnzungen meinerseits, und ja, die sind absolut ernstgemeint:

# # # # # # # # # # # # # I keep telling people again and again and again, one by one, that because . Explanations go into the post itself, full stop.
I myself have been explaining my meme posts extensively for quite a while now, partly because they always touch very obscure niche topics that nobody knows anything about, partly because I can't expect everyone to be familiar with the templates I use. Then again, I've got more than plenty of space for characters. Where most Mastodon users only have 500 characters, I've got 16,777,215.
Don't go look for meme posts on the channel that I'm posting from right now, though. I've made a specialised channel for Fediverse memes: (fedimemesonstreamsstreams.elsmussols.net). I've even got over 24 million characters there. It isn't very active right now, though, because while I've got loads of meme pictures ready to post, describing them can end up very tedious, especially if I've got no external explanations to link to.
Speaking of which, how do you prefer explanations of meme posts Can you live with external links that take you to explanations, e.g. KnowYourMeme for meme templates and the Fediverse Wiki for Fediverse topics (if there's an article available for that topic) Or do you need all explanations in the post itself
Be warned, though: I tend to explain everything all the way down to the basics so that no prior knowledge is required to understand my explanations. This, however, means that my explanations end up massive.
I've actually explained everything myself once, and that was in (you have to click once to open the summary/content warning and then once more to open the spoiler with the image behind it). However, this post required a whole of nine explanations:
So that's
Also, all in all, that's over 25,000 characters of explanations. You can be glad that I didn't go explain The Lord of the Rings and the character Boromir in-depth as well, and I considered them common knowledge instead.
If you said you prefer explanations in the post itself, do you still prefer them if this means tens of thousands of characters at once
# # # # # # # # # # # # # # # # Im Fediverse ginge das auch eleganter als mit einer Themeninstanz von Mastodon oder was auch immer. Das Fediverse hat ja tatschlich jetzt schon Gruppen, und zwar schon fnfeinhalb Jahre lnger, als es Mastodon berhaupt gibt.
Die "Facebookartigen" von Mike Macgirvin sind ja die lteste Serversoftwarefamilie, die es so im Fediverse noch gibt: von 2010, von 2012/2015, von 2021, von letztem Jahr. Die sind alle mit Mastodon verbunden (ich schreibe hier gerade von Hubzilla), die haben alle eine mehr oder weniger ausgefuchste Gruppenfunktion, und man kann die Gruppen grundstzlich auch von Mastodon aus nutzen.
Friendica hat sogar .
Es gibt dann auch noch das sogenannte Threadiverse, das sich an Reddit und Hacker News anlehnt: , , . An sich sind die auch mit dem restlichen Fediverse verbunden, aber die Lemmy-Entwickler haben wenig Interesse daran, die Kompatibilitt mit dem Rest des Fediverse zu verbessern, so da es gerade da gelegentlich hakt. Auerdem sind die kulturellen Unterschiede gerade zwischen Lemmy und Mastodon noch grer als die kulturellen Unterschiede zwischen Friendica/Hubzilla/(streams)/Forte und Mastodon.
Fr Lemmy gibt es auch .
Wenn es eher "basic" und unmoderiert und ohne jegliche Features und ausdrcklich nachtrglich an Mastodon drangeklebt sein soll, gibt's noch . Nur ist das dann eben extremstens "basic".
# # # # # # # # # # # # # # # # # # # # # # # #
Last updated: 2025-09-15