" Rconfort infini "Version de 7
But if the topic of my rendition of a meme is too obscure, I'll still have to explain it.
If I make a meme about how difficult it is to implement FEP-ef61 "Portable Objects", I'll have to explain what FEP-ef61 is. In order for people to understand that, I'll have to explain what nomadic identity is, what the streams repository is, what Hubzilla is and their whole history. This alone will make up over 10,000 characters because there isn't much, if anything, that I could link to.
And I'm still not quite sold on KnowYourMeme-level meme template explanations being entirely unnecessary. Or that links to explanations are better than explanations in the post.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #MemesBrad Oberwager and Philip Rosedale of have announced to take much, much mor drastic measures against content piracy within as well as originating in Second Life.
Some sources:
Linden Lab may soon act when:
And "act" means:
Now, most talk concerning these measures is in Second Life and/or only concerning Second Life. But , especially grids connected to the Hypergrid, have been flooded with stolen Second Life content for many years already. My estimation is that over 95% of all sim decoration and at least 99% of all avatar accessories were stolen from Second Life.
Granted, no-one makes any money with this content. And we're talking about over 3,000, maybe over 4,000 individual grids, the vast majority of which are connected to the Hypergrid. But the availability of even premium Second Life content as freebies in OpenSim makes OpenSim more attractive to non-creators than Second Life and gives it an unfair and illegal advantage in the competition between virtual worlds.
If Linden Lab went all the way against OpenSim, the effects would be devastating. Grid by grid would be shut down, either by their admins or by the authorities, and their admins might end up behind bars with a permanent criminal record, just because there's illegal Second Life content on them, maybe even available in freebie stores.
This would not only affect the small grids that are based around young and extremely popular freebie stores that are constantly being supplied with a stream of freshly copybotted content.
, the first public grid, the oldest still existing grid, one of the two largest grids with a bigger landmass than Second Life itself and the main testbed for OpenSim's development, would meet its end, and its entire eight-piece grid staff would be convicted for what's on externally attached sims like Agora or Nutella or, in fact, any sim that isn't 100% squeaky clean. In fact, I dare say it's hardly possible for a grid to be so aseptic that it couldn't possible be a target of such actions. One local avatar with a Second Life body, and a grid could be toast.
Better yet: The Lindens won't even have to go look for illegal content in OpenSim themselves. A new category for Second Life support tickets will be created to report cases of stolen Second Life content. If you think this won't be used with malicious intent, I have a bridge to sell you.
Philip Rosedale said that Linden Lab will take care that this won't be weaponised within Second Life. But neither he nor Brad Oberwager nor anyone else at Linden Lab would even notice if it's being used as a weapon in wars between grids, communities or single users in OpenSim. In OpenSim, this report feature could be used as a salted thermonuclear weapon that can not only permanently destroy grids of any size, but all their staff in real life along with them, even those who have never had Second Life avatars.
And believe me when I say that, especially in the German-speaking OpenSim scene, there are enough open conflicts and enough complete nutbars who would "push the button" with glee to get rid of grids and users whom they have a problem with. I think there's only one German grid that couldn't possibly be destroyed this way, and that grid is almost unknown and has spent over a decade under a rock. Our only salvation is how slow the German legal system is, and how digital legislation has yet to arrive in the 21st century.
I've recently posted .
#Long #LongPost #CWLong #CWLongPost #SecondLife #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #Piracy #Copybotting #ContentTheft That's my suggestion, too: Always describe the meme image as far as necessary. You may repeat yourself, but there may always be someone who is not familiar with that meme template.
What I'm not entirely sure about is how to explain memes, if at all. I mean, if you describe the image in the alt-text, should you also explain it in the post itself, especially if you've got lots of characters to use up Particularly if your adaptation touches an extremely niche topic that most people won't understand without enough explanation (the Fediverse beyond Mastodon, super-obscure 3-D virtual worlds etc.)
Should you give explanations for the template For your adaptation and the topic For both Not at all
Should the template be explained alone or with extra explanations for concepts included in the template (image macro, advice animal, snowclone, reaction image, 4chan, Something Awful...)
If you can link to external explanations, is it better to do that Or are external links too inconvenient, and it's better to write all explanations yourself
Just so you know what can happen when you go all the way: , I went for what I took for maximum reader convenience. I ended up with one explanation for my adaptation, one for the template, five to explain the template explanations and the template explanation explanations, one for the topic and one to explain the topic explanation. All just so that nobody in the Fediverse would have to look anything up.
I mean, not everyone is familiar with the "One Does Not Simply Walk Into Mordor" template, and next to nobody knows what FEP-ef61 is, right
But I ended up with some 25,000 characters worth of explanations. And I thought that can't possibly be that more convenient than external links.
Currently, it seems to me like people would love to have explanations for everything readily available in each meme post, but if you tell them how long these explanations will end up, they'll nope out and prefer links all of a sudden.
If my assumptions should be wrong, feel free to tell me.
Anyway, you may look around and check the alt-texts and see if the posts are explained and the images are described sufficiently.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Memes #FediMemes In OpenSim, with the exception of total newbies, everybody knows about copybotting. Everybody knows that probably over 95% of all content that's at most 10 years old was stolen from Second Life. There are even people who staunchly insist that there is literally no original OpenSim content whatsoever.
And they enjoy it. Many OpenSim users who have joined since 2015 have never touched any legal content (except OpenSimWorld beacons and Clubmasters if they're sim owners). And they don't want to. They refuse to. They consider OpenSim's original content sub-par in comparison with the premium luxury content that was copybotted from Second Life.
If I tell people my body is a Roth2 v2, some actually assume I'm either too much of a newbie or too dumb to find the "good stuff". One user has actually given me an unsolicited copybotted SLink Physique Male body. After saying right into my virtual face how COMPLETELY AND UTTERLY GUT-WRENCHINGLY DISGUSTINGLY HIDEOUS Roth2 v2 is, using a whole string of expletives.
It's too late to go and sweep OpenSim clean of illegal content. Most OpenSim users come from Second Life and want OpenSim to be Second Life for free, but with the same content or at least at the same level of quality. Remove all sales boxes with illegal content from freebie stores, and 90% of all freebie stores will be completely empty. Have sim owners remove all illegal content from their sims, and you'll end up with a lot of sims that are barren land, save for a lonely OpenSimWorld beacon that may actually even hover in the air because even the ground it used to stand on was copybotted from Second Life.
And if you take copybotted Second Life content as freebies away from people, they'll go log into Second Life with hacked or copybot viewers and export their own inventories by and by instead. Just for their own private use.
For example, you've got three ways of making an avatar in OpenSim.
One, with copybotted SL content. It's easy, it's convenient, and you'll get a gorgeous avatar with next to no effort. But it's illegal.
Two, with legal meshes. You can be certain that it's legal. But it requires a whole lot of detective work to find legal content because it's absent from most of the popular freebie sims. Most of if can only be acquired from the creators, either because it's no-transfer, or because it's too obscure for freebie sim owners to know about it, or because it isn't on par with copybotted SL content in quality, or a combination. That is, some offer Second Life content that was imported with consent from its creators. But the more recent it is, and the clearer it is that it's legal, the harder it is to find because it's no-transfer.
And then you'll have to tinker a lot. There is almost no clothing rigged for the most recent legal BoM mesh bodies (Ruth2 v4, Roth2 v2), so you have to make do with meshes made for the system body, clothes made for Ruth 2.0 RC#2/RC#3 etc. You have to learn how to make alpha masks because Ruth2 v4 and Roth2 v2 don't have fine-grained alpha HUDs they rely on alpha masks. You have to spend hours tweaking their shapes until they look good no out-of-the box sexy/badass shapes available.
In the end, you'll have an avatar that's much more unique and individual than those a-dozen-a-dime Athenas and Legacys and Adonises and Giannis. But it's still nowhere near LaraX + LeLutka EvoX + Doux + what-have-you.
Three, the classic way. System body + layer clothes + prim/sculpt attachments. It's most likely legal. But at best, with a whole lot of work, your avatar will look like 2013. It's more likely to look like 2009 because you probably can't be bothered to tweak the shape until even only the face looks more like a real human than like Ruth. Also, it has become difficult to find classic layer + prim stuff, also because it's either no-transfer and only available in one place or Linda Kellie.
I simply can't see a way to purge illegal content from OpenSim. It's ubiquitous, and people depend on it. There used to be a time when , an entire and not exactly small commercial grid, did not allow avatars with an Athena body (= copybotted 2014 Maitreya Lara) to enter. You wore an Athena, you were kicked. I think only this one mesh body was affected. But they removed that ban because it kept the vast majority of OpenSim avatars out, and back then, there were no known viable alternatives to Athena except ditching mesh and going back to around 2010.
Idealists are few and far between, and many of them don't get far. Social Mouse wanted to rebuild her entire small grid (which previously was chock-full of botted stuff) with only legal creations, even as sim decoration. She built her own buildings for residential sims. She started reworking old Selea Core rezboxes and upgrading them to modern-day OpenSim. She wanted to build a freebie sim with lots of stores that only offer legal content. But first Social Mouse disappeared, and then so did her grid.
Zoe Synclair wanted to build her own freebie sim with only legal content. I know she had quite a bit because she had already had it in store. She had her own licensed Second Life clothes, and she had gathered a whole lot of original OpenSim content (Ruth2/Roth2, classic avatars by Ina Centaur, one of the biggest Selea Core collections ever, her own Linda Kellie Clutterfly warehouse etc.). But this didn't really come to fruition either. I guess she was mobbed out of OpenSim, because she passed her grid and even her avatar and identity on to a new owner.
Aaack Aardvark had a tremendous amount of creations of his own at his ArcadiaShop. That stuff was so good that it was repeatedly copybotted, imported into Second Life and sold for money as original creations, and Aaack always had to step in. A few months ago, he practically disappeared from OpenSim entirely and shut the ArcadiaShop sim down, making most of his products unavailable. His friend Bibiana Bombinante of Encantada fame hasn't been seen for months either, but at least her Encantada sim is still online. Their products are full-perm, but the scripted sales boxes which Aaack had made aren't.
Few are left. For example, Hyacinth Jean (who used to be on Mastodon and PeerTube) only offers her own creations and some from other grid residents on the landing sim of GroovyVerse which seems to be devoid of copybotted content otherwise. Jamie Wright is working on a freebie sim dedicated to preserving older legal content, including a vast collection of boxes and items from FleepGrid, but it isn't ready to be opened yet, although I've been there a while ago.
I myself own two body shops dedicated to the Ruth2 and Roth2 families, one of which is already prepared for Max, and both of which offer some of the biggest assortments of bodies and accessories for these bodies. Next to one of them, there is a shop with increasingly harder to find layer and mesh clothing. For example, I've managed to rescue all Deva Moda clothes and make-up and other things from crumbling Klamotto as well as most Damien Fate meshes textured by Illiana Blachere and a lot of skin-tight layer clothes. In some cases, I'm the only merchant who still offers it.
#Long #LongPost #CWLong #CWLongPost #SecondLife #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #Piracy #Copybotting #ContentTheft I've written an article about this yesterday:
Essentially, if they did, and if they even did so outside the USA, some entire grids would be shut down, especially if they were built around big freebie sims in the first place. But I doubt that they'll even go after the spreading and offering of content that was stolen in the 2010s instead of only after recent cases of content theft.
#Long #LongPost #CWLong #CWLongPost #SecondLife #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #Piracy #Copybotting #ContentTheft
It's being worked on, though, and it has been since 2023 when wanted to implement nomadic identity in Mitra, but without moving to the Nomad protocol.
Current status as far as I'm informed:
The long-term goal is to make nomadic identity available for everything that uses ActivityPub. Unlike now, moving instances and cloning and sharing identities shall not be limited to within the same project, but all across the whole Fediverse. But even if this should become stable one day, and I'm pretty sure it will, the next obstacle will be adoption by the various Fediverse projects.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mitra #Hubzilla #Streams #(streams) #Forte #NomadicIdentity #MovingInstances #MovingServers I'd say not everyone would consider almost 1,000 characters of image description in a 1,500-character alt-text accessible. And even fewer people would consider a long image description in the post itself that's tens of thousands of characters long accessible if your screen reader spends an hour or several rambling it down.
My most extreme case is a post with only one image. That one image is described twice like all my halfway recent original images. The short description in the alt-text is a bit over 1,400 characters long which barely leaves any room for the note that there is also a long description in the post itself. That long description is over 60,000 characters long. I'm not kidding. It took me two full days from getting up to going to bed to research for it and write it.
Now, there are a few dozen bits and pieces of text all over the image. At the resolution at which I've posted the image, two of them are ever so barely legible for sighted people. They're on a large logo on a building. Four more, two of them on that logo, too, two more on a sign on an easel, are illegible, but still visible. At least more on signs inside the building are visible, but they can't easily be identified as text. All the others are so tiny that they're invisible. It takes the long image description to even know where they are, for example, on the control panels of teleporters.
And yet, they are all within the borders of the image. And I can transcribe them. I can't read them in the image, but I can go to the place shown in the image and take closer looks.
Unfortunately, the rule or guideline that any and all text in an image must be transcribed verbatim does not take into consideration text that can't be read in the image, but that can be sourced and thus transcribed by whoever posts the image. No confirmation, no exception. And so I have to assume that I have to transcribe illegible text as well. And so I do transcribe them all.
But there's no way for me to put all these text transcripts into the alt-text, not if I want to keep Mastodon, Misskey and their forks from chopping it off at the 1,500-character mark. I'd also have to explain where all these pieces of text are, after all. And so the text transcripts are only available in the 60,000-character monster of a long image description.
It isn't really accessible to expect blind users to have their screen readers ramble and ramble and ramble for hours, just to get information that should actually belong into the alt-text which, in turn, shouldn't be longer than 200 characters.
On the other hand, it doesn't really seem accessible to me if I expect people to ask me to describe things in the image for them. It rather feels sloppy, if not out-right ableist to not describe everything that someone could possibly want to know right away.
The problem with my images is that they're renderings from very obscure 3-D virtual worlds. This means that nobody knows what anything in these images looks like unless they can see these images. This, in turn, means that I cannot expect anyone to know what something in my images looks like anyway. They don't.
At the same time, I can't expect everyone to not care about my images. In fact, I expect the very topic of 3-D virtual worlds that actually exist to make people curious. At this point, it doesn't matter what's important in my images within the context of the post. Sighted people will go explore the new and unknown world by taking closer looks at all the big and small details in the image.
But blind or visually-impaired people may be just as curious. They may want the same chance to explore this new world by experiencing what's in that one image. Denying them the same chances as sighted people is ableist. But giving them this chance requires an absolutely titanic image description.
Sure, I describe lots of details which a sighted person can't possibly recognise when looking at the image, especially not at the resolution of the image as I've posted it. But I simply can't keep telling blind or visually-impaired people that certain things in the image can't be recognised due to the image resolution. It feels lazy, like weaseling out. I mean, I can see all these details. Not in the image, but where the image was made, simply by walking closer to them or moving the camera closer to them.
If there are two dark objects inside a building that may or may not be plants, but that can't be identified as plants by looking at the image, why shouldn't I describe them as follows: "On the sides of the teleport panel, there are two identical aa palms in square terracotta pots with wide rims. Like the other potted plants, these mostly dark green plants with long pointy leaves are kept at an indoor-compatible size, namely about three and a half metres or eleven and a half feet tall. Also, like the other potted plants, they are made of only four flat surfaces with partially transparent pictures of the plant on them, arranged in angles of 45 degrees to one another."
If there's room for improvement in my image descriptions, I improve my future image descriptions and declare my past image descriptions outdated. In fact, the 60,000-character-long description is outdated because it's bad style to describe dimension using measures. Instead, dimensions should be described by comparing them with something everyone is familiar with like body parts.
Right now, by the way, I'm upping my game at describing avatars, using rules and guidelines for describing people which I've discovered over the last few months. The last time I've described an avatar, I've done so in about 7,000 characters, but according to my new discoveries, I may have missed something.
However, I can't go into so much detail while still making my image descriptions short enough that a screen reader can read through them in under a minute.
CC:
#Long #LongPost #CWLong #CWLongPost #Metaverse #VirtualWorlds #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta I know from personal experience that many OpenSim users expect OpenSim to be Second Life, free-of-charge, but otherwise Second Life. Including the same content, but free-of-charge. Or at least that subset of the same content which they desire. For example, that's what makes female avatars look sexy (or what these people take for sexy) and male avatars look badass.
Let me put it this way: Over the last years, more female footwear with 6" platforms and 12" spike heels was stolen from Second Life than with flat soles. There are more medium-heeled female shoes made in OpenSim and rigged for Ruth 2.0 RC#2/RC#3 than there are stolen medium-heeled shoes for all female Second Life mesh bodies combined. It's magnitudes easier to dress an Athena-based avatar like a completely overdone slut than to make a veritable and credible winter outfit. And I guess you can't even dress Legacy for autumn in OpenSim.
Fully legal mesh avatars are very difficult to make and maintain, especially if you don't want to run around with the same outfit on all the time. It's possible, but very difficult. One reason for this is because it isn't really worth making mesh clothes from scratch, especially free mesh clothes. If you have a male avatar, you have to trust certain merchants when they say that they've imported Second Life content with the consent of its creators. If you have a female avatar like Juno Rowland, you have to make do with Clutterfly, textured Damien Fate meshes, skin-tight clothes as layers, and you have to know very obscure creators for the rest.
Second Life creators traditionally barely have any chance in OpenSim. This is largely due to that "Never buy in OpenSim" mantra which some seem to believe to have originated from OpenSim's own creators, but which was actually coined by the copybotting mafiya in the 2010s to get rid of legal payware merchants. Getting rid of legal freebie merchants was attempted with its own tricks.
Also, the vast majority of OpenSim users doesn't want to invest any money anyway, at least not beyond what little they pay for their sims. Most of those who cite anti-capitalism as the reason for supporting "Never buy in OpenSim" are either poor or just plain cheap.
The items that sell the best, both in Second Life and in OpenSim, are avatar accessories. You can't sell avatar accessories in OpenSim for money. There's next to nothing in this regard that isn't already available in OpenSim as illegal copies, at least not if it's actually (considered) wanted by the users. And even if you want to offer brand-new clothes, wearing them requires a stolen body. That is, unless you rig for Ruth2 or Roth2 which were made in and for OpenSim (terrible devkits notwithstanding), and doing so isn't even worth the effort in Second Life.
Lastly, if a Second Life creator offers something in OpenSim for money, and it's good in some way, you can be certain that someone else wil copybot it from Second Life and then offer it as freebies. In fact, I'm not sure if Studio Skye joined the Kitely Market before or after their beach kit was copybotted.
But I'd really like to see what happens if Linden Lab, with Second Life creators by their side, sue the owners of some of those small American or European grids that are built around massive freebie stores into submission, have their grids shut down and even make sure that they won't start new grids. I guess if the legal action that was threatened some ten years ago already is actually taken, and entire grids (albeit small ones, but with popular, significant freebie sims) fall victim to it, this may shock quite a few people. Especially if these grids don't pop up again within no time.
#Long #LongPost #CWLong #CWLongPost #SecondLife #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #Piracy #Copybotting #ContentTheft Long This is very much not a unique selling point of Mastodon. Mastodon is not the only decentralised software that lets you move servers, nor is Mastodon the decentralised software that's best at moving servers, or where it's the easiest, nor is it unprecedented.
I'm writing to you from (). It was originally created in 2012, almost four years before Mastodon. And it was created with the goal to roll out an entirely new feature to the Fediverse: ().
I can move my entire identity from one server to another in one go, including:
The only thing that I think doesn't come with me is which apps I have activated.
I can easily do so using only Hubzilla's UI, all through the wire within a few minutes, without having to export or import anything.
After moving, the channel is automatically deleted on the old server. And if the account on the old server has no more channels on it, the account is deleted, too. Moving on Hubzilla leaves no dead accounts or channels behind.
And this is just a subset of what nomadic identity was originally designed for: cloning channels. Instead of moving my channel to another server, I can also create a bidirectional, live, hot real-time backup which I can log into and use just like I can log into and use the original. I can make as many clones as I want, and they're synchronised with each other. I can declare a clone the "original" and demote the previous "original" to clone (which is part of what happens when I move). This makes my channel resilient against servers shutting down.
Again, all this has been available since 2012, almost four years longer than Mastodon. On something which is part of the Fediverse, and which has been continuously federated with Mastodon for as long as Mastodon has been around.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #NomadicIdentity #MovingInstances #MovingServers It's just a pity that if you post about an obscure enough niche topic like I do, it's the more difficult to make image posts perfectly accessible to everyone, the more obscure the topic is. For the more obscure the topic is, the more you have to describe, and the more you have to explain. (Caution: Never put explanations into alt-text! They must go where everyone can access them.)
I currently write the longest image descriptions in the whole Fediverse by a wide margin. But they may not actually be accessible enough, even though I describe all my original images twice.
The short descriptions in the alt-text don't always contain text transcripts, especially not all of them, and being only short descriptions, they aren't full, detailed visual descriptions either. The long descriptions for the same images in the post regularly end up with a five-digit character count. They may not be accessible because they're way too long. But sometimes they're the only place where all text transcripts can be found. And they are the only place where explanations can be found.
So the consequence should be that I quit posting my original images because they're impossible to make perfectly accessible to everyone, at least as long as there is no rock-solid definition for what's actually required in image descriptions in my obscure edge-case. But there isn't even any consensus on whether text that's illegible or that's so tiny that it's basically invisible must be transcribed if it can be sourced.
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Well, GoToSocial is quite different from Mastodon and Friendica in one regard: It's mainly made for hosting your own personal instance. It isn't really for more or less big public, open-registration instances. As far as I know, it doesn't even come with its own built-in UI, so if you want a Web UI on your own instance, you have to choose one and add it yourself.
Still, there are some public, open-registration GoToSocial instances. And if you're going to use it with TWBlue, the Web UI shouldn't even matter beyond registering an account because you won't touch it anymore afterwards.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #GoToSocial #TWBlue You could try and ask the developers of both TweeseCake and TWBlue to implement full support for Friendica, not via the Mastodon client API, but by also implementing Friendica's own client API.
I wouldn't hold my breath for it, though. They may not even have heard of Friendica yet. And if you tell them what it is, they may still decide that if they haven't heard of it yet because it hasn't been the talk of the town for long enough, it's too obscure to bother.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #TweeseCake #TWBlue Quote:
End quote.
It depends on where exactly your issues are rooted. If the UI is too cluttered for you, it may help, but I'm afraid that the editor itself may not be accessible. But if the UI elements themselves aren't accessible, it makes no difference if you rearrange them or remove elements that you don't need.
As I've probably already mentioned, Friendica has changed a great lot since the last time I've used it, and my more recent experience is from Hubzilla and (streams). But while they let you rearrange all pages, they don't let you modify the UI elements themselves in detail and add accessibility features.
Also, I don't know if Friendica lets you change the layouts of the pages by editing the raw Comanche code that describes them. While this means getting used to Comanche, I can imagine this actually being more accessible than a purely WYSIWYG drag-and-drop editor.
In this regard, it's interesting that (streams) doesn't offer drag-and-drop anymore. Either that, or Hubzilla introduced it after Osada and Zap were forked off.
Quote:
End quote.
Akkoma is a fork of Pleroma with a default UI that, I guess, isn't dramatically different plus compatibility with the same third-party UIs. One downside in comparison with Friendica, Hubzilla etc. is that you, as a user, can't choose a UI for your account individually because the UI is pre-defined for the whole instance. Also, both Pleroma and Akkoma are microblogging projects and closer to Twitter than to Facebook.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Akkoma Hubzilla started out as a Friendica fork by Friendica's own creator. He maintained it for twice as long as Friendica, until 2016. Since then, there are only two developers for much, much more code than Friendica has, and they're spare-time hobbyists, too, who only work on Hubzilla when they happen to find some time.
Thus, due to Hubzilla's massive backend, UI maintenance has largely fallen to the wayside. Hubzilla used to have a whole bunch of themes, but only one survived to this day because the two devs had to keep one theme alive. Its name "Redbasic" comes from Hubzilla's original name, Red. Apart from getting more settings with Hubzilla 9, it didn't change that much over time. Hubzilla kind of still looks like Friendica more than a dozen years ago.
It's mostly the backend that keeps the devs busy, too busy to take care of anything else. Example: The built-in help is half-useless because it's totally outdated and therefore partially incomplete and partially plain wrong. Features that have been available for several years aren't covered, but things that have been removed in the last decade are. Parts of it actually still refer to a "Red Matrix" which ceased to exist in 2015 when the Red Matrix became Hubzilla. The German and English help is currently being re-written by a user.
Alt-text has to be manually grafted into the BBcode that embeds an image in a post. There is no official documentation on that yet, and I'll have to check if the rewrite covers it. How it's done is only known because, I think, one of the devs looked it up in the code, then told us, and it's being passed on from user to user every once in a while.
In fact, I've once been told by a blind or visually-impaired user that at least Hubzilla's Articles app for non-federating long-form articles did not work in her screen reader at all.
Hubzilla's frontend must largely run on code from 2012 when it was matched with the completely re-written backend. Afterwards, new or changed features were only patched in. Hubzilla's UI is convoluted and confusing even for sighted users.
Also, Hubzilla has never had a run-in with blind users either because it's even more obscure than Friendica, and its community is even smaller than Friendica's.
Lastly, Hubzilla can only be used via the Web interface. There is no other way. It doesn't support Mastodon apps, and it never will.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #A11y #Accessibility First of all, I've just noticed that you seem to not have joined the Friendica support forum yet. As far as I know, you can't post to a Friendica group/forum without fully connecting to it first.
As for the accessibility issues: To most people, it appears like Friendica has only just been made since they haven't heard of it before mid-January. But actually, Friendica is from 2010. And its frontend is largely stuck in the early 2010s, including technologically.
Friendica has always been a spare-time hobbyist project. It was mostly developed by one single man for almost two years. That guy is a protocol designer and not a frontend developer. Also, I think Friendica never had more than two regular developers, and it definitely never had any developer who really knows how to make a modern and appealing user interface. I mean, you've obviously never seen Friendica's user interface, but let me tell you that it's quite old-fashioned. It's just meant to do its job.
Hobbyist, spare-time developers of such an extremely niche piece of software who are not trained in Web UI design normally don't know a thing about accessibility. And truly, they don't care. If the UI covers all features, and the users don't have to SSH or telnet onto the Web server to use it, it's often good enough.
Friendica's regularly active user community has never been more than maybe a few thousand at a time, maybe even only a few hundred, as opposed to the over two million at which Mastodon has topped out. Thus, Friendica has never encountered blind or visually-impaired users yet.
You can see it all over the place. Alt-text is not part of Friendica's culture. Some Friendica veterans staunchly refuse to describe their media because they think alt-text is another Mastodon fad that Mastodon fundamentalists want to force upon the whole rest of the Fediverse with Mastodon's entire culture. Alt-text, to them, is like limiting your posts to 500 characters.
All this is why nobody has noticed yet that Friendica is not accessible at all.
I've got a suspicion that Friendica can only be made fully accessible by throwing the entire Web frontend away, developing an entirely new one from scratch and then also making all-new themes for it.
Also, it's only natural that TweeseCake doesn't support many of Friendica's features. As it looks to me, TweeseCake's Fediverse side is built against Mastodon and only Mastodon. If Mastodon doesn't have a feature, TweeseCake doesn't cover it either. Thus, TweeseCake probably only covers about 20% of Friendica's features because Mastodon doesn't have the other 80%.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #TweeseCake #A11y #Accessibility Discord has completely warped the term "server" for entire generations of Internet users. On Discord, "server" means "chatroom".
In the Fediverse, "server" doesn't mean "chatroom". It means "". A computer.
For example, .
Or or running at someone's home, connected to their landline.
On each one of these, a big or small Twitter can be running (Mastodon).
Or a wholly different Twitter (Pleroma, Akkoma, Misskey, Calckey, Firefish, Iceshrimp, Sharkey, Catodon, Meisskey, Tanukey, Neko...).
(Here's the first important new thing for you to learn about the Fediverse: The Fediverse is not only Mastodon.)
Or a Facebook with a side of a blog and a cloud server (Friendica, (streams), Forte).
(Here's the second important new thing for you to learn about the Fediverse: The Fediverse is not only short-form microblogging. Look at this comment. Look at what I've done. Embedded links. Bold type. Impossible on Mastodon. But possible elsewhere in the Fediverse.)
Or a Facebook meets WordPress meets Google Cloud Services meets even more stuff on top (Hubzilla this is where I am).
Or an Instagram (Pixelfed).
Or a YouTube (PeerTube).
Or a Twitch (Owncast).
Or a Reddit (Lemmy, /kbin, Mbin, PieFed).
Or a Goodreads (BookWyrm).
Or whatever. There are over 150 different server applications in the Fediverse.
mastodon.social, where you are, is only one of over 10,000 big and small Twitters of the same kind (Mastodon).
If Mastodon was like Discord, all 10,000+ Mastodon servers would run in one and the same gigantic data centre in the USA, owned by Mastodon, Inc. And they would all be property of Mastodon, Inc.
If the Fediverse was like Discord, all 30,000+ Fediverse servers would run in one and the same gigantic data centre in the USA, owned by Mastodon, Inc. And they would all be property of Mastodon, Inc. Also, they would be fully identical in functionality.
But as I've said above: They're all running on their own separate machines. With their own separate owners.
And the different server applications have different developers, and they are being developed independently from one another.
Okay, now comes the kicker: These server applications are not walled up against one another. Not only are all instances of the same server applications (e.g. Mastodon) connected to each other, but all instances of one server application are also connected to all instances of all the other server applications.
Imagine you're on Twitter. But your new friend is on Facebook. You can't follow a Facebook user on Twitter, and you can't follow a Twitter user on Facebook.
In the Fediverse, you can. You can be on Twitter. And follow a Facebook user. Directly from Twitter. Without a Facebook account.
Only that they aren't named Twitter and Facebook in the Fediverse. Twitter is named Mastodon or Pleroma or Akkoma or Misskey or Calckey or Firefish or Iceshrimp or Sharkey or Catodon or... There are dozens of Twitter alternatives in the Fediverse. Well, and Facebook is named Friendica or Hubzilla or (streams) or Forte.
You can be on Mastodon. And you can follow Friendica accounts. From Mastodon. Without a Friendica account.
This comment is a very good example. You are on , created by in 2016 as an alternative to Twitter that aimed to be as close to Twitter as possible.
The server that you're on, , is owned by Mastodon, Inc. and running on one or multiple rack servers in San Francisco, California, USA owned by .
I am on , created by Mike Macgirvin in 2012 by forking his own from 2010, and currently mainly maintained by Mario Vavti and Harald Eilertsen. Hubzilla has got nothing to do with Mastodon whatsoever. It started out as an alternative to Facebook, but not a clone, rather better than Facebook, with full-blown long-form blogging capability and a built-in file storage, and it has been enhanced greatly in functionality even beyond that.
The server that I'm on, , is owned and administered by Mark Nowiasz, who has no affiliation with the Hubzilla developers, and running on a rack server in Nuremberg, Germany owned by .
And yet, you can see this comment coming from Hubzilla on Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Server #Instance #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Calckey #Firefish #Iceshrimp #Sharkey #Catodon #Meisskey #Tanukey #Neko #Friendica #Hubzilla #Streams #(streams) #Forte #Pixelfed #PeerTube #Owncast #Lemmy #/kbin #Mbin #PieFed #BookWyrm #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
I've got a few examples of image posts of my own with very detailed image descriptions. These posts are not on Mastodon, but they are very much in the Fediverse in places that are federated with Mastodon, and they all have actually ended up on Mastodon timelines. So I guess Mastodon's accessibility requirements apply to these places just as well.
Would you say they're too descriptive Or would you even say they aren't descriptive enough yet, and that there are important details missing
One example is (content warning: eye contact) with two images, my most recent one. It is not available on mastodon.online. These images also show a digital avatar, so in a sense, I've described a person.
Another example is with one image. You can also find it by searching for the hashtag #UniversalCampus and scrolling to the bottom of the results there you can see what it looks like on Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Inclusion #A11y #Accessibility
As for Hubzilla vs Friendica, I've made a series of tables that compare Mastodon, Friendica, Hubzilla and (streams). I've made them for those who are looking for a Facebook alternative in the Fediverse, but who only know Mastodon first-hand and Friendica from hearsay. But these tables are useless for blind or visually-impaired users, and I can't change that because it's in the nature of tables. Also, I don't have all data for Friendica yet. (In case someone sighted comes across this comment and wants to see the tables: ).
So I'll try to do a Hubzilla vs Friendica comparison here. Hold on and take some time, for this will be very, very, very long. 42 lines of comparison with over 10,000 characters.
Friendica was created by Mike Macgirvin in 2010.
Hubzilla started out as a Friendica fork by Mike Macgirvin himself in 2012, originally named Red (from spanish la red = the network), then renamed Red Matrix. It was repositioned, reworked, massively extended beyond Friendica's features and renamed Hubzilla in 2015.
Friendica has native Android apps, a closed beta native iOS app and support for Mastodon apps, even though Mastodon apps only cover 20% of Friendica's features at most. Hubzilla doesn't have any mobile apps, at least none for iOS, none in the Google Play Store, none that could be installed on a new Android device and none with a fully native mobile user interface.
Hubzilla also also doesn't support Mastodon apps and never will. That's mainly because a Mastodon app can't cover over 90% of Hubzilla's features, including features which you need all the time such as file upload, image embedding, handling of connections and permission controls, simply because Mastodon doesn't have these features. Hubzilla would require its very own apps, and due to Hubzilla's immense complexity and wealth of features, a fully-featured, dedicated Hubzilla app would be absolutely gargantuan and just as complex as Hubzilla itself.
On Friendica, ActivityPub federation is available from the get-go. On Hubzilla, ActivityPub federation is optional, and on newly-created channels, it is off by default.
Friendica can integrate Bluesky and Tumblr accounts. Hubzilla can't.
On Friendica, your account is your identity. Your identity is firmly tied to your account. On hubzilla, your identity is independent from your account. It resides in a container called a "channel", of which you can have multiple, fully independent ones on the same account. This also allows you to switch back and forth between channels or identities without logging out and back in.
Friendica has limited capabilities of moving your identity to another instance. Hubzilla has nomadic identity. For one, this makes it possible to relocate an entire channel with all posts, all comments, all private messages, all connections, nearly all settings, all files in your file space etc. etc. to another instance. Besides, it makes it possible to clone a channel to one or multiple other instances. This gives you live, hot, real-time, bidirectional backups of your channel, and you can log into and use any of them. That way, your channel is much more resilient against instance shutdown.
If you delete a Hubzilla channel, you cannot create a channel with the same short name on the same Hubzilla hub unless the admin fully deletes your channel from the database.
If you delete a clone of a Hubzilla channel, you cannot clone the same channel back to the same hub unless the admin fully deletes your channel from the database.
Friendica has client-side support for OpenWebAuth magic single sign-on. Hubzilla has full support. This means that Friendica logins are recognised by instances with full OpenWebAuth support, but Friendica itself doesn't recognise logins elsewhere. Hubzilla logins are recognised the same, and Hubzilla does recognise logins elsewhere.
Friendica has some basic permission control. On Hubzilla, it is much more advanced and fine-grained.
On Friendica, you can set your profile to private. On Hubzilla, you can give permission to see your profile to anybody on the internet, anybody in the Fediverse, anybody on Hubzilla or (streams), anybody on your hub, unapproved and approved connections, approved connections, only those you specifically allow by contact role or only yourself.
On Friendica, you can set your list of connections to private. On Hubzilla, you can give permission to see your connections to anybody on the internet, anybody in the Fediverse, anybody on Hubzilla or (streams), anybody on your hub, unapproved and approved connections, approved connections, only those you specifically allow by contact role or only yourself.
On Friendica, you can set your timeline to private as far as I know, this happens along with setting your profile to private. On Hubzilla, you can give permission to see your stream to anybody on the internet, anybody in the Fediverse, anybody on Hubzilla or (streams), anybody on your hub, unapproved and approved connections, approved connections, only those you specifically allow by contact role or only yourself.
I don't know if Friendica can give specific permissions to specific connections. Hubzilla has so-called "contact roles". Each contact has a contact role that grants or denies 17 different permissions. Permissions granted channel-wide from the channel role are inherited by all contact roles. Two of these permissions are for your contacts to send you their posts and for your contacts to send you private messages.
On Hubzilla, you can keep both everyone and specific contacts from sending you repeats/boosts/reposts/renotes with a line of filter syntax in a filter blacklist.
On Hubzilla, you can send any of your posts as public, only to yourself, to all members of a privacy group (which is similar to a circle on Friendica), to whoever is assigned a certain non-default profile, to one specific group/forum or to a custom selection of contacts. You can also define your default post audience, either one of your privacy groups, or your posts are public by default.
Hubzilla has three levels of reply control. At channel level, you can give permission to reply to your posts to anybody on the internet, anybody in the Fediverse, anybody on Hubzilla or (streams), anybody on your hub, unapproved and approved connections, approved connections, only those you specifically allow by contact role or only yourself. In addition, you can choose to let comments in from those who are not permitted to comment on your posts, preview them and then manually decide whether or not you accept each comment.
Reply control at per-contact level means that you can use contact roles to grant or deny permission to reply to your comments to certain connections.
Reply control at per-post level is optional and off by default. It lets you disallow comments on individual posts of yours entirely.
Likewise, there is quote-post control at channel level and at per-contact level.
On Friendica, you can report posts to the admin. On Hubzilla, you can't. This feature is currently being discussed.
I don't know about Friendica, but Hubzilla has a channel-wide filter with a whitelist and a blacklist, and optionally, it has an individual filter for each connection with a whitelist and a blacklist.
Hubzilla allows regular expressions in filter lines, but only for normal keywords, not in lines with filter syntax.
Hubzilla's filter syntax can recognise posts, comments and private messages. This is of very limited usefulness, however: If you want to whitelist certain keywords for posts, but let all comments and all private messages through, you'd have to use filter syntax in a whitelist. But in whitelists, keyword lines are connected with "or" whereas filter syntax lines are connected with "and" which means that you cannot combine keywords with filter syntax. There is also filter syntax for keywords, but these lines are connected with "and" in whitelists, too, and each line can only contain one keyword with no regular expression.
On Friendica, summaries or Mastodon-style content warnings are created with a pair of BBcode tags, either
Friendica optionally offers Markdown for text formatting in addition to BBcode. Hubzilla only offers BBcode.
Friendica doesn't have or support polls. Hubzilla has full support for basically unlimited polls.
Friendica calls reposting "sharing" and quote-posting "quoted sharing". Hubzilla calls reposting "repeating" and quote-posting "sharing".
On Hubzilla, you can optionally be notified when a stranger mentions you out of the blue outside any conversation on your stream.
On Friendica, you can make a group restricted or private. On Hubzilla, you can give a group or a forum privacy, too, but by choosing the "Custom" channel role instead of the "Community forum" channel role, and you have to adjust the level of privacy by hand. The advantage is that you have fine-grained control over what exactly you want to be private in your group or forum.
Private Friendica groups can be joined by users on Friendica, Hubzilla, (streams) and probably also Forte. Private Hubzilla groups or forums can only be joined by users on Hubzilla, (streams) and maybe Forte.
Friendica has a central directory of users, groups etc., the . Hubzilla doesn't have such a thing.
Friendica nodes have their own directories I'm not sure if they only list Friendica accounts or accounts and channels of everything that uses ActivityPub, or if they even include diaspora* users. Hubzilla hubs have such directories, too, but they only list Hubzilla and (streams) channels because they can only list what uses the built-in and permanently activated Nomad protocol.
In your Hubzilla directory, you can hide channels that are flagged not safe for work.
Hubzilla has an option that gives those who are permitted to see a post the permission to also see any media embedded in the post, regardless of the permissions set for the respective media in your file space. This was introduced due to the wide-spread issue of people uploading images and setting them or the directores the images are in to private, then embedding them into public posts and the audience of the posts not seeing the images.
On Hubzilla, you can give guest access tokens to people whom you want to access certain files or directories in your file space.
The file space built into your Hubzilla channel can be accessed via WebDAV.
Hubzilla also has a built-in CalDAV calendar server which can use the event calendar as a simple frontend and an optional headless CardDAV addressbook server.
Hubzilla optionally has "articles", long-form text posts with the same full text formatting capabilities as normal posts, but which don't federate.
Hubzilla optionally has "cards", basically planning cards with the same features as articles plus a few extra features.
Hubzilla optionally has multiple wikis per channel with multiple pages per wiki. Wikis can be set up to use either BBcode or Markdown as their markup language with a few wiki-specific additions in both cases.
Hubzilla optionally has simple, static webpages which can be formatted with either BBcode, Markdown or plain HTML. Hubzilla's own official website is a webpage on a Hubzilla channel.
I think that's about it.
As for diaspora*: Forget it. For one, it does not support ActivityPub, and it does not federate with most of the Fediverse. The diaspora* developers staunchly refuse to add any other protocols to diaspora*, especially ActivityPub. One has actually said that you don't implement ActivityPub, you implement Mastodon. And the diaspora* developers don't want to make themselves dependent on Mastodon.
Besides, diaspora* is withering away. Around December 29th, a number of major diaspora* pods shut down. According to one source, diaspora* lost over half its user accounts in three days. And the closure of diasp.org, one of the biggest pods, is scheduled for April 1st now.
Quote:
End quote.
From the same creator as Friendica and Hubzilla, there is something he created in 2021 at the end of a long and somewhat complex line of forks. It is officially and intentionally nameless, brandless, not a project and released into the public domain. Colloquially, it is named (streams) in parentheses after the name of its code repository. You can find the latter with an extensive readme . It is slimmed down in features from Hubzilla, and it doesn't offer nearly the connection and federation options of Friendica and Hubzilla. But it is easier to handle while still having a steeper learning curve than Friendica, and especially its permission system is both another bit powerful and significantly easier to use than Hubzilla's.
(streams) has no mobile apps and no compatibility with Mastodon apps either for the same reasons as why Hubzilla doesn't isn't compatible with Mastodon apps.
(streams) is included in my comparison tables, too. If you want me, I can rattle down another comparison with Friendica like the one with Hubzilla above.
In August, 2024, Mike made another fork based on (streams) named Forte. It's basically (streams), but with a name, with a brand identity, as a project, released under the MIT license and with no support for the Nomad protocol anymore. It does everything using only ActivityPub. This also means that it relies entirely on ActivityPub for nomadic identity. Since especially this is still highly experimental, Forte itself has not officially been released yet, it is not recommended as a reliable daily driver, nor does it have public, open-registration instances.
Quote:
End quote.
As far as I know, different Friendica nodes have different default themes, especially now that the Facebook-like Bookface theme may be officially included into Friendica.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #diaspora* #Friendica #Hubzilla #Streams #(streams) #Forte Not quite, and that says someone who .
Hubzilla wikis don't federate. In any way. They always stay within the Hubzilla channel which they belong to.
Not only that, but I, as the owner of this Hubzilla channel, have to manually permit other people to edit my wikis. And these have to be on something that supports client-side OpenWebAuth: Friendica, Hubzilla, (streams), Forte. And they have to be connected to my channel (in Mastodonese, that's "follow me, and I have to follow them back", but connections on Hubzilla are bidirectional by default) so I can give them permission to edit my wikis.
I've read about a federated wiki engine with ActivityPub in the making, but the name eludes me.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Wiki If you mean "groups" as in "Facebook groups", then you can't create them from your account. They aren't a separate functionality like on Facebook.
On Friendica, groups are accounts like user accounts, only with different settings. So if you want to create a group, you have to register a new account. I recommend you to do that on another Friendica node so you can be logged into both your personal account and your group account simultaneously, just in case you have to do something in your group.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Groups
There is no Facebook bridge.
I guess you must have heard from someone on Mastodon who has heard from someone on Mastodon etc. something about Friendica and Facebook being connected. Chinese whispers, Fediverse-style. But that's only a tiny chunk of the true story.
There was a Facebook connector. And it wasn't a bridge. It was fully natively integrated into Friendica, just like Bluesky and Tumblr are fully natively integrated into Friendica today. But they require a Bluesky or Tumblr account, and the Facebook integration required a Facebook account. (Source: I've actually used it back in the day.)
Also, Facebook disallowed third-party apps to extract content from Facebook in 2012. And in 2013, Facebook made extracting data impossible, thus ending the functionality of the Facebook integration add-on.
Facebook integration on Friendica has been gone for three years longer than Mastodon has been around.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Facebook #Friendica
I do have a few questions, specifically because my image posts have gone unnoticed by blind or visually-impaired users so far.
Judging and assuming from the information I've gathered so far, my original images require very extensive and detailed descriptions. A full description is too long for alt-text, so what I do is write a full description with all text transcripts and all necessary explanations, put it into the post text body and then condense a shorter, but still long alt-text from it. What's your stance on this method of describing the same image twice over
Also, where would you personally prefer a long description In the post itself Or in an external document that's linked into the post If you're on a phone app, remember that the external document will inevitably open your Web browser.
Do you prefer images described, based on what a sighted person can see in the image as it is posted Or do you prefer a description that is not limited by the restriction of the image itself, for example, assuming an infinite image resolution and an infinite zoom factor that would let sighted people theoretically see even tiniest details
If I mention something in my image description of which you don't know what it looks like, do you need a detailed visual description
Concerning text transcripts: Let's assume a bit of text in an image is too small to be legible for sighted people, but I can read it at the original source, so I can transcribe it nonetheless. Shall I transcribe it What about if said text is too small to be recognisable as text or so tiny that's it's practically invisible I mean, after all, the concept of image resolution should not matter to totally blind people, so writing that a piece of text can't be read because the resolution of the image is too low ought to sound like a lame excuse for skimping a transcript.
If there's a building in one of my images, I can safely assume that you don't know what that one specific building looks like, so I guess I can also assume that you need it described. If I could, I would do so using architectural terms and then explaining all these architectural terms right after using them. Would you say that's the correct way Because that's why I avoid having realistic buildings in my images.
If there's an image in my image, do you need it described At a level that I can source right where the image is without moving away too far, or at a level that I can only source by moving farther away to the place shown in the image What about an image in an image in my image (I'm serious. I've actually described images within images within my image, but I've stopped when this was about to go out of hand due to there being too many to describe.)
I'm currently working on a series of posts with images showing a virtual-world avatar in various but similar outfits in fact, I have been since last year. I may have questions later regarding at what level of detail I have to describe that avatar.
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
I always spend more time describing my images than writing the post that they go into.
For my meme posts, that's because I have to explain the picture and find the appropriate links to external explanations (KnowYourMeme etc.) to shorten my explanation block if possible.
For my original images, it's because I have to describe them twice. There's always an alt-text which, as of late, fills the 1,500-character limit imposed by Mastodon, Misskey etc. to the brim. But that alt-text is only a shortened and slightly adapted version of an extremely long long description which goes into the post text body and which also includes transcripts of any and all text in the image, readable or not, as well as all explanations which I deem necessary for outsiders to understand the image. Since the images are about an extremely obscure niche topic, this means I have to explain a lot.
A while ago, I spent two full days, morning to evening, researching for and describing and explaining one single image. The result was . And I actually had to limit myself, otherwise the description would have been even vastly longer and taken over a month to complete. Good thing I don't have any character limit to worry about. The only exception is that Mastodon may reject posts from outside with over 100,000 characters.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Unless you need a Facebook replacement, unless you plan to use Friendica or Hubzilla or (streams) or Forte, only the first three paragraphs are of interest for you.
Basically, all Fediverse instances are separate websites. If you want to use one of them like you use pdx.social, you need an account on that instance. Your account on pdx.social won't do. It doesn't matter if that instance is a Pixelfed instance or a Loops instance or a PeerTube instance or a Misskey instance or an Akkoma instance or whatever.
So, no, with your Mastodon login, you can't just simply use Pixelfed or Loops or PeerTube. If you want to use Pixelfed (= post pictures), you need an account on a Pixelfed instance. If you want to use Loops (= upload videos), you need an account on the currently only Loops instance. If you want to use PeerTube (= upload videos), you need an account on a PeerTube instance.
Got that so far
But, and this is something that even many Twitter refugees from 2022 haven't understood yet: Mastodon and Pixelfed and Loops and PeerTube and Misskey and Sharkey and Akkoma and Friendica etc. etc. aren't walled off from one another.
You can be on Mastodon, but you can follow Pixelfed accounts from Mastodon. And you can follow Loops accounts from Mastodon. And you can follow PeerTube channels from Mastodon. And so forth. Just like you can follow accounts on other Mastodon instances from your Mastodon account on pdx.social. Just like you already do.
By the way: Right now, you do not only follow Mastodon accounts. I've looked through those you follow. There's one Neil E. Hodges (tkf.kawa-kun.com). Scroll down the list of those whom you follow. When you find him, look at his profile. Okay, now look at his profile at its source. Safari (or whatever is your default Web browser) will open. And you'll see .
This is not a Mastodon account on a Mastodon instance with a weird UI. This is an account on . A Facebook alternative from 2010 which is not Mastodon, which has never been Mastodon, which is developed completely independently from Mastodon, which is very different from Mastodon, and which is over five years older than Mastodon.
But: Just like Mastodon, Friendica is part of the Fediverse. And it has been federated with Mastodon since Mastodon was created. This means: Since Mastodon was created, it has been possible for Mastodon users to follow Friendica accounts from their Mastodon accounts. And vice versa, it has been possible for Friendica users to follow Mastodon accounts from their Friendica accounts.
You yourself are right now following someone who is on something that is not Mastodon. Very much not Mastodon, in fact.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pixelfed #Loops #PeerTube #Friendica #Federation Pixelfed is wholly separate software from Mastodon on wholly separate servers with wholly separate owners. So yes, you need a separate Pixelfed account. It's a bit easier on Pixelfed if you're already on Mastodon: Pixelfed lets you automatically create a new user account by "logging in" with your Mastodon login credentials. But only Pixelfed has this as far as I know.
Loops is wholly separate again, but there's only one instance so far because it's too unfinished to even be open-source. So you'll need a Loops account next to your Mastodon account and your Pixelfed account.
Also, you'll have different followers on Mastodon, on Pixelfed and on Loops. But what you could do if you want your followers on Mastodon to see your Pixelfed posts is: Follow your own Pixelfed account from Mastodon. And then, whenever you post something interesting on Pixelfed, wait for it to arrive on your Mastodon timeline, and then boost it.
There's one thing that exists already now: OpenWebAuth magic single sign-on. But it's only available on Hubzilla, (streams) and Forte and partially on Friendica.
What it does is recognise your login on another instance, even on an instance of another server application. Hubzilla, (streams) and Forte recognise logins from Friendica, Hubzilla, (streams) and Forte, but Friendica can't recognise logins.
However, this is only used by the permissions system. For example, someone whom I'm connected to could have made their profile only visible to a certain subset of their connections, including myself. If you visit their profile, you won't see anything. If I visit their profile, their home instance recognises my Hubzilla login, and I can see the profile.
What it does not do is give you the same full-blown rights as a user with a local account. I can't just, like, go to some (streams) instance and post away as, what, jupiterrowlandrumbly.net or go to a Hubzilla hub where I don't have an account and create a webpage or a wiki or a CalDAV calendar right away without logging in. That's not how it works.
By the way, client-side OpenWebAuth support (= your login is recognised on Hubzilla, (streams) and Forte) was proposed and actually developed to the point of a pull request for Mastodon. As far as I know, it was rejected. OpenWebAuth won't come to Mastodon.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pixelfed #Loops #Friendica #Hubzilla #Streams #(streams) #Forte #OpenWebAuth #SingleSignOn Tatschlich ist meines Erachtens dichter an Friendica dran als , weil nicht so berladen. Das kennt blo auerhalb von Hubzilla und (streams) selbst praktisch keine Sau. Da habe ich auch zwei Kanle.
Friendica wrde ich nur empfehlen, wenn jemand unbedingt, unbedingt eine Android-App braucht. Oder willens ist, eine iOS-App mit einem Riesenaufwand ber TestFlight zu installieren. Vielleicht noch, wenn jemand mit (streams) nicht klarkommt (wobei auch Friendica nicht unbedingt "registrieren und loslegen" ist).
Hubzilla, da bin ich jetzt hier gerade selber, ist schon ziemlich hardcore von der Lernkurve her und braucht zwingend einiges an Einstellungen, bevor man loslegen kann. App kann man auch vergessen, aber ich schaudere beim Gedanken einer Fully-featured-Hubzilla-App mit komplett nativem Mobilinterface.
Wenn Forte offiziell freigegeben wird, werden die Karten vielleicht neu gemischt. Aber in der Bedienung wird es sich nicht groartig von (streams) unterscheiden. Der einzige Unterschied ist, da Forte das Nomad-Protokoll nicht mehr hat, sondern nur noch ActivityPub.
Fr die, die es noch nicht wissen: Das ist alles eine Software-Familie, die derselbe Entwickler seit beinahe 15 Jahren in Entwicklung hat. Und zwischen Hubzilla und (streams) gab es noch ein Geflecht aus mindestens sieben weiteren Forks, die alle eingestellt sind.
Ich habe brigens krzlich einen tabellarischen Vergleich zwischen Mastodon, Friendica, Hubzilla und (streams) gemacht, falls es jemanden interessiert.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Facebook #FacebookErsatz #Friendica #Hubzilla #Streams #(streams) Auf Mastodon gar nicht. Mastodon hat fr Gruppen keinerlei Untersttzung und wei gar nicht, was Gruppen sind.
Hier sind ein paar Sachen, wo du nach Gruppen suchen knntest, mit denen du dich trotzdem von Mastodon aus verbinden kannst:
listet aktuell ber 220 ffentliche Friendica-Gruppen. (Falls nicht bekannt: Friendica ist eine Facebook-Alternative im Fediverse.)
listet aktuell fast 28.000 Lemmy-Communities. (Falls nicht bekannt: Lemmy ist ein Reddit-Klon im Fediverse.)
Es gibt noch einiges mehr, was Gruppen hat, aber dafr jeweils keine umfassende ffentlich erreichbare Suche.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Friendica #Lemmy #Gruppeninbal Dror 2021 collection.
Richtig.
Das ist genau wie 2022/2023. Da wurde doch die groe Masse der Mastodon-Nutzer direkt nach mastodon.social geholt, ohne da ihnen erklrt wurde, was Mastodon ist (auer dem blichen "literarisch Twitter ohne Musk") oder gar das Fediverse. Die haben teilweise Monate gebraucht, um berhaupt nur zu merken, da Mastodon keine einzelne monolithische Silo-Website ist.
Heute gibt's genau das immer noch. Zustzlich wird den Leuten erklrt:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Pixelfed #Loops #Friendica You can't connect Fediverse accounts like that and make them one, at least not generally all over the place, and especially not between Mastodon and Hubzilla. These two will always be fully separate logins.
The best you can do is follow your Hubzilla account from Mastodon, then confirm the connection request on Hubzilla which, from Mastodon's point of view, creates a mutual follower/followed connection.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla babenextdur IG
Since you're already offering multiple options to switch to, here are some more proposals:
Facebook -> ()
Facebook -> ()
-> ()
-> ()
Threads -> ()
Threads -> ()
Reddit -> ()
Reddit -> ()
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Meta #MetaPlatforms #Facebook #Streams #(streams) #Hubzilla #Twitter # #Threads #Misskey #Iceshrimp #Reddit #Mbin #PieFed #GlobalSwitchDay
A better question would be if he'll get the reach he wants with only a Pixelfed account. One could argue that he'd be better off with a Mastodon account on top to advertise for his Pixelfed posts by boosting them. But one could also argue that this may lead to people following his Mastodon account rather than his Pixelfed account. And that it'd amount to cheating.
His advantage, however, would be that he wouldn't start out all alone in the Fediverse. I think I can expect you to follow him. You are already on Mastodon, you already have a substantial amount of followers, so I guess he could leave the "plugging" to you.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pixelfed
Do you mean posts from people whom you follow on Pixelfed
If yes, then yes, you have to log into your Pixelfed account.
Do you mean your own posts which you've posted on Pixelfed
If yes, then yes, you have to log into your Pixelfed account.
There is only one way to connect a Mastodon account and a Pixelfed account: You can follow your own Pixelfed account with your Mastodon account. This doesn't make one account out of two accounts. You only become your own follower. Just like you can follow anyone else's Pixelfed accounts from Mastodon. Or just like anyone else on Mastodon can follow your Pixelfed account.
When you do so, and you post something on Pixelfed (you have to log into Pixelfed for this), you receive these posts on Mastodon. The purpose of this is e.g. to boost your Pixelfed posts to your Mastodon followers so they can see them without also having to follow your Pixelfed account.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pixelfed The Fediverse is a bunch of different, independent applications which nonetheless are connected in such a way that users of one application can follow users of another application. But they're still separate instances of different, independent applications.
If you're on Mastodon, and you want to follow a PeerTube channel and comment on the videos from that PeerTube channel, you can simply follow that PeerTube channel from Mastodon. You don't need a PeerTube account.
If you're on Mastodon, and you want to upload videos to PeerTube, then you need a PeerTube account.
What Pixelfed does, namely automagically create a Pixelfed user account for everyone who "signs in" with their Mastodon credentials, is an exception, but it misleads Fediverse newbies into thinking that they've got full user power on all instances of all Fediverse server applications with their Mastodon login.
You can. If you want to. Advantage: People can be fairly sure that it's the same you as the Mastodon you.
But you don't necessarily have to. Not if e.g. you want to represent an entirely different persona on, say, Misskey than your normal, standard public self on Mastodon.
I mean, you can also have multiple accounts on Mastodon (or anything else) under different names, with different identities, with different personas or even for different purposes. For example, if you love posting about topic A and topic B, you make an account for topic A and one for topic B with different names. That way, the people who follow you for topic A don't have their timelines cluttered with your topic B stuff that's uninteresting to them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #FediTips (streams) ist Hubzilla
Einen kompletten tabellarischen Vergleich zwischen Mastodon, Friendica, Hubzilla und (streams) habe ich gemacht.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams)
If I make a meme about how difficult it is to implement FEP-ef61 "Portable Objects", I'll have to explain what FEP-ef61 is. In order for people to understand that, I'll have to explain what nomadic identity is, what the streams repository is, what Hubzilla is and their whole history. This alone will make up over 10,000 characters because there isn't much, if anything, that I could link to.
And I'm still not quite sold on KnowYourMeme-level meme template explanations being entirely unnecessary. Or that links to explanations are better than explanations in the post.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #MemesBrad Oberwager and Philip Rosedale of have announced to take much, much mor drastic measures against content piracy within as well as originating in Second Life.
Some sources:
Linden Lab may soon act when:
- you have stolen content in Second Life
- you have uploaded stolen Second Life content somewhere
- you offer stolen Second Life content somewhere
- you host stolen Second Life content somewhere
- you tell others how to steal Second Life content
And "act" means:
- they'll terminate your Second Life account
- they'll purge any and all creations from this account from Second Life, including in-world and from other avatars' inventories
- they'll terminate every last one of your alt accounts
- they'll purge any and all creations from your alt accounts from Second Life, including in-world and from other avatars' inventories
- they'll file a DMCA notice against you
- they'll file a Cease & Desist against whatever you've done and wherever you've done it
- they might even start a criminal lawsuit against you, drag you to court and have you convicted
Now, most talk concerning these measures is in Second Life and/or only concerning Second Life. But , especially grids connected to the Hypergrid, have been flooded with stolen Second Life content for many years already. My estimation is that over 95% of all sim decoration and at least 99% of all avatar accessories were stolen from Second Life.
Granted, no-one makes any money with this content. And we're talking about over 3,000, maybe over 4,000 individual grids, the vast majority of which are connected to the Hypergrid. But the availability of even premium Second Life content as freebies in OpenSim makes OpenSim more attractive to non-creators than Second Life and gives it an unfair and illegal advantage in the competition between virtual worlds.
If Linden Lab went all the way against OpenSim, the effects would be devastating. Grid by grid would be shut down, either by their admins or by the authorities, and their admins might end up behind bars with a permanent criminal record, just because there's illegal Second Life content on them, maybe even available in freebie stores.
This would not only affect the small grids that are based around young and extremely popular freebie stores that are constantly being supplied with a stream of freshly copybotted content.
, the first public grid, the oldest still existing grid, one of the two largest grids with a bigger landmass than Second Life itself and the main testbed for OpenSim's development, would meet its end, and its entire eight-piece grid staff would be convicted for what's on externally attached sims like Agora or Nutella or, in fact, any sim that isn't 100% squeaky clean. In fact, I dare say it's hardly possible for a grid to be so aseptic that it couldn't possible be a target of such actions. One local avatar with a Second Life body, and a grid could be toast.
Better yet: The Lindens won't even have to go look for illegal content in OpenSim themselves. A new category for Second Life support tickets will be created to report cases of stolen Second Life content. If you think this won't be used with malicious intent, I have a bridge to sell you.
Philip Rosedale said that Linden Lab will take care that this won't be weaponised within Second Life. But neither he nor Brad Oberwager nor anyone else at Linden Lab would even notice if it's being used as a weapon in wars between grids, communities or single users in OpenSim. In OpenSim, this report feature could be used as a salted thermonuclear weapon that can not only permanently destroy grids of any size, but all their staff in real life along with them, even those who have never had Second Life avatars.
And believe me when I say that, especially in the German-speaking OpenSim scene, there are enough open conflicts and enough complete nutbars who would "push the button" with glee to get rid of grids and users whom they have a problem with. I think there's only one German grid that couldn't possibly be destroyed this way, and that grid is almost unknown and has spent over a decade under a rock. Our only salvation is how slow the German legal system is, and how digital legislation has yet to arrive in the 21st century.
I've recently posted .
#Long #LongPost #CWLong #CWLongPost #SecondLife #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #Piracy #Copybotting #ContentTheft That's my suggestion, too: Always describe the meme image as far as necessary. You may repeat yourself, but there may always be someone who is not familiar with that meme template.
What I'm not entirely sure about is how to explain memes, if at all. I mean, if you describe the image in the alt-text, should you also explain it in the post itself, especially if you've got lots of characters to use up Particularly if your adaptation touches an extremely niche topic that most people won't understand without enough explanation (the Fediverse beyond Mastodon, super-obscure 3-D virtual worlds etc.)
Should you give explanations for the template For your adaptation and the topic For both Not at all
Should the template be explained alone or with extra explanations for concepts included in the template (image macro, advice animal, snowclone, reaction image, 4chan, Something Awful...)
If you can link to external explanations, is it better to do that Or are external links too inconvenient, and it's better to write all explanations yourself
Just so you know what can happen when you go all the way: , I went for what I took for maximum reader convenience. I ended up with one explanation for my adaptation, one for the template, five to explain the template explanations and the template explanation explanations, one for the topic and one to explain the topic explanation. All just so that nobody in the Fediverse would have to look anything up.
I mean, not everyone is familiar with the "One Does Not Simply Walk Into Mordor" template, and next to nobody knows what FEP-ef61 is, right
But I ended up with some 25,000 characters worth of explanations. And I thought that can't possibly be that more convenient than external links.
Currently, it seems to me like people would love to have explanations for everything readily available in each meme post, but if you tell them how long these explanations will end up, they'll nope out and prefer links all of a sudden.
If my assumptions should be wrong, feel free to tell me.
Anyway, you may look around and check the alt-texts and see if the posts are explained and the images are described sufficiently.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Memes #FediMemes In OpenSim, with the exception of total newbies, everybody knows about copybotting. Everybody knows that probably over 95% of all content that's at most 10 years old was stolen from Second Life. There are even people who staunchly insist that there is literally no original OpenSim content whatsoever.
And they enjoy it. Many OpenSim users who have joined since 2015 have never touched any legal content (except OpenSimWorld beacons and Clubmasters if they're sim owners). And they don't want to. They refuse to. They consider OpenSim's original content sub-par in comparison with the premium luxury content that was copybotted from Second Life.
If I tell people my body is a Roth2 v2, some actually assume I'm either too much of a newbie or too dumb to find the "good stuff". One user has actually given me an unsolicited copybotted SLink Physique Male body. After saying right into my virtual face how COMPLETELY AND UTTERLY GUT-WRENCHINGLY DISGUSTINGLY HIDEOUS Roth2 v2 is, using a whole string of expletives.
It's too late to go and sweep OpenSim clean of illegal content. Most OpenSim users come from Second Life and want OpenSim to be Second Life for free, but with the same content or at least at the same level of quality. Remove all sales boxes with illegal content from freebie stores, and 90% of all freebie stores will be completely empty. Have sim owners remove all illegal content from their sims, and you'll end up with a lot of sims that are barren land, save for a lonely OpenSimWorld beacon that may actually even hover in the air because even the ground it used to stand on was copybotted from Second Life.
And if you take copybotted Second Life content as freebies away from people, they'll go log into Second Life with hacked or copybot viewers and export their own inventories by and by instead. Just for their own private use.
For example, you've got three ways of making an avatar in OpenSim.
One, with copybotted SL content. It's easy, it's convenient, and you'll get a gorgeous avatar with next to no effort. But it's illegal.
Two, with legal meshes. You can be certain that it's legal. But it requires a whole lot of detective work to find legal content because it's absent from most of the popular freebie sims. Most of if can only be acquired from the creators, either because it's no-transfer, or because it's too obscure for freebie sim owners to know about it, or because it isn't on par with copybotted SL content in quality, or a combination. That is, some offer Second Life content that was imported with consent from its creators. But the more recent it is, and the clearer it is that it's legal, the harder it is to find because it's no-transfer.
And then you'll have to tinker a lot. There is almost no clothing rigged for the most recent legal BoM mesh bodies (Ruth2 v4, Roth2 v2), so you have to make do with meshes made for the system body, clothes made for Ruth 2.0 RC#2/RC#3 etc. You have to learn how to make alpha masks because Ruth2 v4 and Roth2 v2 don't have fine-grained alpha HUDs they rely on alpha masks. You have to spend hours tweaking their shapes until they look good no out-of-the box sexy/badass shapes available.
In the end, you'll have an avatar that's much more unique and individual than those a-dozen-a-dime Athenas and Legacys and Adonises and Giannis. But it's still nowhere near LaraX + LeLutka EvoX + Doux + what-have-you.
Three, the classic way. System body + layer clothes + prim/sculpt attachments. It's most likely legal. But at best, with a whole lot of work, your avatar will look like 2013. It's more likely to look like 2009 because you probably can't be bothered to tweak the shape until even only the face looks more like a real human than like Ruth. Also, it has become difficult to find classic layer + prim stuff, also because it's either no-transfer and only available in one place or Linda Kellie.
I simply can't see a way to purge illegal content from OpenSim. It's ubiquitous, and people depend on it. There used to be a time when , an entire and not exactly small commercial grid, did not allow avatars with an Athena body (= copybotted 2014 Maitreya Lara) to enter. You wore an Athena, you were kicked. I think only this one mesh body was affected. But they removed that ban because it kept the vast majority of OpenSim avatars out, and back then, there were no known viable alternatives to Athena except ditching mesh and going back to around 2010.
Idealists are few and far between, and many of them don't get far. Social Mouse wanted to rebuild her entire small grid (which previously was chock-full of botted stuff) with only legal creations, even as sim decoration. She built her own buildings for residential sims. She started reworking old Selea Core rezboxes and upgrading them to modern-day OpenSim. She wanted to build a freebie sim with lots of stores that only offer legal content. But first Social Mouse disappeared, and then so did her grid.
Zoe Synclair wanted to build her own freebie sim with only legal content. I know she had quite a bit because she had already had it in store. She had her own licensed Second Life clothes, and she had gathered a whole lot of original OpenSim content (Ruth2/Roth2, classic avatars by Ina Centaur, one of the biggest Selea Core collections ever, her own Linda Kellie Clutterfly warehouse etc.). But this didn't really come to fruition either. I guess she was mobbed out of OpenSim, because she passed her grid and even her avatar and identity on to a new owner.
Aaack Aardvark had a tremendous amount of creations of his own at his ArcadiaShop. That stuff was so good that it was repeatedly copybotted, imported into Second Life and sold for money as original creations, and Aaack always had to step in. A few months ago, he practically disappeared from OpenSim entirely and shut the ArcadiaShop sim down, making most of his products unavailable. His friend Bibiana Bombinante of Encantada fame hasn't been seen for months either, but at least her Encantada sim is still online. Their products are full-perm, but the scripted sales boxes which Aaack had made aren't.
Few are left. For example, Hyacinth Jean (who used to be on Mastodon and PeerTube) only offers her own creations and some from other grid residents on the landing sim of GroovyVerse which seems to be devoid of copybotted content otherwise. Jamie Wright is working on a freebie sim dedicated to preserving older legal content, including a vast collection of boxes and items from FleepGrid, but it isn't ready to be opened yet, although I've been there a while ago.
I myself own two body shops dedicated to the Ruth2 and Roth2 families, one of which is already prepared for Max, and both of which offer some of the biggest assortments of bodies and accessories for these bodies. Next to one of them, there is a shop with increasingly harder to find layer and mesh clothing. For example, I've managed to rescue all Deva Moda clothes and make-up and other things from crumbling Klamotto as well as most Damien Fate meshes textured by Illiana Blachere and a lot of skin-tight layer clothes. In some cases, I'm the only merchant who still offers it.
#Long #LongPost #CWLong #CWLongPost #SecondLife #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #Piracy #Copybotting #ContentTheft I've written an article about this yesterday:
Essentially, if they did, and if they even did so outside the USA, some entire grids would be shut down, especially if they were built around big freebie sims in the first place. But I doubt that they'll even go after the spreading and offering of content that was stolen in the 2010s instead of only after recent cases of content theft.
#Long #LongPost #CWLong #CWLongPost #SecondLife #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #Piracy #Copybotting #ContentTheft
" Rconfort infini "
Version de 7 jours / 168 heures.
Streaming intgral et tlchargement (24.18Go) disponible cette adresse :
.
Bonne coute.
.
#7 #168
Bonjour Mastodon! Un peu de mignonnerie pour adoucir la journe.
-TailedTit
It's unfortunately a core problem with this platform, but we shouldn't pretend it's not.
It's being worked on, though, and it has been since 2023 when wanted to implement nomadic identity in Mitra, but without moving to the Nomad protocol.
Current status as far as I'm informed:
- Mitra has at least got support for nomadic identity via ActivityPub in a development version.
- (streams), a Hubzilla descendant by Hubzilla's and Friendica's creator, has had support for nomadic identity via ActivityPub in its stable release for months. It doesn't rely on it, though, because it uses Nomad for that.
- Forte, a (streams) fork by the same developer, is the first Fediverse server application to actually rely on ActivityPub for nomadic identity. It's still experimental and a "closed alpha", though.
- The building blocks of nomadic identity as implemented in Hubzilla, (streams) and Forte are being cast into ActivityPub FEPs such as FEP-ef61 "Portable Objects".
The long-term goal is to make nomadic identity available for everything that uses ActivityPub. Unlike now, moving instances and cloning and sharing identities shall not be limited to within the same project, but all across the whole Fediverse. But even if this should become stable one day, and I'm pretty sure it will, the next obstacle will be adoption by the various Fediverse projects.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mitra #Hubzilla #Streams #(streams) #Forte #NomadicIdentity #MovingInstances #MovingServers I'd say not everyone would consider almost 1,000 characters of image description in a 1,500-character alt-text accessible. And even fewer people would consider a long image description in the post itself that's tens of thousands of characters long accessible if your screen reader spends an hour or several rambling it down.
My most extreme case is a post with only one image. That one image is described twice like all my halfway recent original images. The short description in the alt-text is a bit over 1,400 characters long which barely leaves any room for the note that there is also a long description in the post itself. That long description is over 60,000 characters long. I'm not kidding. It took me two full days from getting up to going to bed to research for it and write it.
Now, there are a few dozen bits and pieces of text all over the image. At the resolution at which I've posted the image, two of them are ever so barely legible for sighted people. They're on a large logo on a building. Four more, two of them on that logo, too, two more on a sign on an easel, are illegible, but still visible. At least more on signs inside the building are visible, but they can't easily be identified as text. All the others are so tiny that they're invisible. It takes the long image description to even know where they are, for example, on the control panels of teleporters.
And yet, they are all within the borders of the image. And I can transcribe them. I can't read them in the image, but I can go to the place shown in the image and take closer looks.
Unfortunately, the rule or guideline that any and all text in an image must be transcribed verbatim does not take into consideration text that can't be read in the image, but that can be sourced and thus transcribed by whoever posts the image. No confirmation, no exception. And so I have to assume that I have to transcribe illegible text as well. And so I do transcribe them all.
But there's no way for me to put all these text transcripts into the alt-text, not if I want to keep Mastodon, Misskey and their forks from chopping it off at the 1,500-character mark. I'd also have to explain where all these pieces of text are, after all. And so the text transcripts are only available in the 60,000-character monster of a long image description.
It isn't really accessible to expect blind users to have their screen readers ramble and ramble and ramble for hours, just to get information that should actually belong into the alt-text which, in turn, shouldn't be longer than 200 characters.
On the other hand, it doesn't really seem accessible to me if I expect people to ask me to describe things in the image for them. It rather feels sloppy, if not out-right ableist to not describe everything that someone could possibly want to know right away.
The problem with my images is that they're renderings from very obscure 3-D virtual worlds. This means that nobody knows what anything in these images looks like unless they can see these images. This, in turn, means that I cannot expect anyone to know what something in my images looks like anyway. They don't.
At the same time, I can't expect everyone to not care about my images. In fact, I expect the very topic of 3-D virtual worlds that actually exist to make people curious. At this point, it doesn't matter what's important in my images within the context of the post. Sighted people will go explore the new and unknown world by taking closer looks at all the big and small details in the image.
But blind or visually-impaired people may be just as curious. They may want the same chance to explore this new world by experiencing what's in that one image. Denying them the same chances as sighted people is ableist. But giving them this chance requires an absolutely titanic image description.
Sure, I describe lots of details which a sighted person can't possibly recognise when looking at the image, especially not at the resolution of the image as I've posted it. But I simply can't keep telling blind or visually-impaired people that certain things in the image can't be recognised due to the image resolution. It feels lazy, like weaseling out. I mean, I can see all these details. Not in the image, but where the image was made, simply by walking closer to them or moving the camera closer to them.
If there are two dark objects inside a building that may or may not be plants, but that can't be identified as plants by looking at the image, why shouldn't I describe them as follows: "On the sides of the teleport panel, there are two identical aa palms in square terracotta pots with wide rims. Like the other potted plants, these mostly dark green plants with long pointy leaves are kept at an indoor-compatible size, namely about three and a half metres or eleven and a half feet tall. Also, like the other potted plants, they are made of only four flat surfaces with partially transparent pictures of the plant on them, arranged in angles of 45 degrees to one another."
If there's room for improvement in my image descriptions, I improve my future image descriptions and declare my past image descriptions outdated. In fact, the 60,000-character-long description is outdated because it's bad style to describe dimension using measures. Instead, dimensions should be described by comparing them with something everyone is familiar with like body parts.
Right now, by the way, I'm upping my game at describing avatars, using rules and guidelines for describing people which I've discovered over the last few months. The last time I've described an avatar, I've done so in about 7,000 characters, but according to my new discoveries, I may have missed something.
However, I can't go into so much detail while still making my image descriptions short enough that a screen reader can read through them in under a minute.
CC:
#Long #LongPost #CWLong #CWLongPost #Metaverse #VirtualWorlds #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta I know from personal experience that many OpenSim users expect OpenSim to be Second Life, free-of-charge, but otherwise Second Life. Including the same content, but free-of-charge. Or at least that subset of the same content which they desire. For example, that's what makes female avatars look sexy (or what these people take for sexy) and male avatars look badass.
Let me put it this way: Over the last years, more female footwear with 6" platforms and 12" spike heels was stolen from Second Life than with flat soles. There are more medium-heeled female shoes made in OpenSim and rigged for Ruth 2.0 RC#2/RC#3 than there are stolen medium-heeled shoes for all female Second Life mesh bodies combined. It's magnitudes easier to dress an Athena-based avatar like a completely overdone slut than to make a veritable and credible winter outfit. And I guess you can't even dress Legacy for autumn in OpenSim.
Fully legal mesh avatars are very difficult to make and maintain, especially if you don't want to run around with the same outfit on all the time. It's possible, but very difficult. One reason for this is because it isn't really worth making mesh clothes from scratch, especially free mesh clothes. If you have a male avatar, you have to trust certain merchants when they say that they've imported Second Life content with the consent of its creators. If you have a female avatar like Juno Rowland, you have to make do with Clutterfly, textured Damien Fate meshes, skin-tight clothes as layers, and you have to know very obscure creators for the rest.
Second Life creators traditionally barely have any chance in OpenSim. This is largely due to that "Never buy in OpenSim" mantra which some seem to believe to have originated from OpenSim's own creators, but which was actually coined by the copybotting mafiya in the 2010s to get rid of legal payware merchants. Getting rid of legal freebie merchants was attempted with its own tricks.
Also, the vast majority of OpenSim users doesn't want to invest any money anyway, at least not beyond what little they pay for their sims. Most of those who cite anti-capitalism as the reason for supporting "Never buy in OpenSim" are either poor or just plain cheap.
The items that sell the best, both in Second Life and in OpenSim, are avatar accessories. You can't sell avatar accessories in OpenSim for money. There's next to nothing in this regard that isn't already available in OpenSim as illegal copies, at least not if it's actually (considered) wanted by the users. And even if you want to offer brand-new clothes, wearing them requires a stolen body. That is, unless you rig for Ruth2 or Roth2 which were made in and for OpenSim (terrible devkits notwithstanding), and doing so isn't even worth the effort in Second Life.
Lastly, if a Second Life creator offers something in OpenSim for money, and it's good in some way, you can be certain that someone else wil copybot it from Second Life and then offer it as freebies. In fact, I'm not sure if Studio Skye joined the Kitely Market before or after their beach kit was copybotted.
But I'd really like to see what happens if Linden Lab, with Second Life creators by their side, sue the owners of some of those small American or European grids that are built around massive freebie stores into submission, have their grids shut down and even make sure that they won't start new grids. I guess if the legal action that was threatened some ten years ago already is actually taken, and entire grids (albeit small ones, but with popular, significant freebie sims) fall victim to it, this may shock quite a few people. Especially if these grids don't pop up again within no time.
#Long #LongPost #CWLong #CWLongPost #SecondLife #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #Piracy #Copybotting #ContentTheft Long This is very much not a unique selling point of Mastodon. Mastodon is not the only decentralised software that lets you move servers, nor is Mastodon the decentralised software that's best at moving servers, or where it's the easiest, nor is it unprecedented.
I'm writing to you from (). It was originally created in 2012, almost four years before Mastodon. And it was created with the goal to roll out an entirely new feature to the Fediverse: ().
I can move my entire identity from one server to another in one go, including:
- all my posts and private messages, including conversations
- all my connections (followers and followed are unified here by default) connections on Hubzilla, (streams) and Forte are even automatically re-written to my new identity on the other side (can Mastodon do that with non-Mastodon connections)
- all settings for all my connections
- all my channel-wide filter entries
- all individual filter entries for my connections
- my NSFW keyword list
- all my privacy groups (= lists) with everyone in them
- the whole channel configuration
- all my files including the directory structure in my file space
- my federated event calendar
- my CalDAV calendars
- my CardDAV addressbook
- my articles
- my wikis
- all modifications I've done to the theme on my channel
- all modifications I've done to any pages on my channel (yes, I can completely re-arrange them)
- etc.
The only thing that I think doesn't come with me is which apps I have activated.
I can easily do so using only Hubzilla's UI, all through the wire within a few minutes, without having to export or import anything.
After moving, the channel is automatically deleted on the old server. And if the account on the old server has no more channels on it, the account is deleted, too. Moving on Hubzilla leaves no dead accounts or channels behind.
And this is just a subset of what nomadic identity was originally designed for: cloning channels. Instead of moving my channel to another server, I can also create a bidirectional, live, hot real-time backup which I can log into and use just like I can log into and use the original. I can make as many clones as I want, and they're synchronised with each other. I can declare a clone the "original" and demote the previous "original" to clone (which is part of what happens when I move). This makes my channel resilient against servers shutting down.
Again, all this has been available since 2012, almost four years longer than Mastodon. On something which is part of the Fediverse, and which has been continuously federated with Mastodon for as long as Mastodon has been around.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #NomadicIdentity #MovingInstances #MovingServers It's just a pity that if you post about an obscure enough niche topic like I do, it's the more difficult to make image posts perfectly accessible to everyone, the more obscure the topic is. For the more obscure the topic is, the more you have to describe, and the more you have to explain. (Caution: Never put explanations into alt-text! They must go where everyone can access them.)
I currently write the longest image descriptions in the whole Fediverse by a wide margin. But they may not actually be accessible enough, even though I describe all my original images twice.
The short descriptions in the alt-text don't always contain text transcripts, especially not all of them, and being only short descriptions, they aren't full, detailed visual descriptions either. The long descriptions for the same images in the post regularly end up with a five-digit character count. They may not be accessible because they're way too long. But sometimes they're the only place where all text transcripts can be found. And they are the only place where explanations can be found.
So the consequence should be that I quit posting my original images because they're impossible to make perfectly accessible to everyone, at least as long as there is no rock-solid definition for what's actually required in image descriptions in my obscure edge-case. But there isn't even any consensus on whether text that's illegible or that's so tiny that it's basically invisible must be transcribed if it can be sourced.
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Well, GoToSocial is quite different from Mastodon and Friendica in one regard: It's mainly made for hosting your own personal instance. It isn't really for more or less big public, open-registration instances. As far as I know, it doesn't even come with its own built-in UI, so if you want a Web UI on your own instance, you have to choose one and add it yourself.
Still, there are some public, open-registration GoToSocial instances. And if you're going to use it with TWBlue, the Web UI shouldn't even matter beyond registering an account because you won't touch it anymore afterwards.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #GoToSocial #TWBlue You could try and ask the developers of both TweeseCake and TWBlue to implement full support for Friendica, not via the Mastodon client API, but by also implementing Friendica's own client API.
I wouldn't hold my breath for it, though. They may not even have heard of Friendica yet. And if you tell them what it is, they may still decide that if they haven't heard of it yet because it hasn't been the talk of the town for long enough, it's too obscure to bother.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #TweeseCake #TWBlue Quote:
Could this possibly help with my problems By the way, this is a fairly good article that explains some of the differences between Friendica and Mastodon.
End quote.
It depends on where exactly your issues are rooted. If the UI is too cluttered for you, it may help, but I'm afraid that the editor itself may not be accessible. But if the UI elements themselves aren't accessible, it makes no difference if you rearrange them or remove elements that you don't need.
As I've probably already mentioned, Friendica has changed a great lot since the last time I've used it, and my more recent experience is from Hubzilla and (streams). But while they let you rearrange all pages, they don't let you modify the UI elements themselves in detail and add accessibility features.
Also, I don't know if Friendica lets you change the layouts of the pages by editing the raw Comanche code that describes them. While this means getting used to Comanche, I can imagine this actually being more accessible than a purely WYSIWYG drag-and-drop editor.
In this regard, it's interesting that (streams) doesn't offer drag-and-drop anymore. Either that, or Hubzilla introduced it after Osada and Zap were forked off.
Quote:
Here is an explanation of another site that I just found, called Akkoma. It sounds interesting, but also a bit complicated.
End quote.
Akkoma is a fork of Pleroma with a default UI that, I guess, isn't dramatically different plus compatibility with the same third-party UIs. One downside in comparison with Friendica, Hubzilla etc. is that you, as a user, can't choose a UI for your account individually because the UI is pre-defined for the whole instance. Also, both Pleroma and Akkoma are microblogging projects and closer to Twitter than to Facebook.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Akkoma Hubzilla started out as a Friendica fork by Friendica's own creator. He maintained it for twice as long as Friendica, until 2016. Since then, there are only two developers for much, much more code than Friendica has, and they're spare-time hobbyists, too, who only work on Hubzilla when they happen to find some time.
Thus, due to Hubzilla's massive backend, UI maintenance has largely fallen to the wayside. Hubzilla used to have a whole bunch of themes, but only one survived to this day because the two devs had to keep one theme alive. Its name "Redbasic" comes from Hubzilla's original name, Red. Apart from getting more settings with Hubzilla 9, it didn't change that much over time. Hubzilla kind of still looks like Friendica more than a dozen years ago.
It's mostly the backend that keeps the devs busy, too busy to take care of anything else. Example: The built-in help is half-useless because it's totally outdated and therefore partially incomplete and partially plain wrong. Features that have been available for several years aren't covered, but things that have been removed in the last decade are. Parts of it actually still refer to a "Red Matrix" which ceased to exist in 2015 when the Red Matrix became Hubzilla. The German and English help is currently being re-written by a user.
Alt-text has to be manually grafted into the BBcode that embeds an image in a post. There is no official documentation on that yet, and I'll have to check if the rewrite covers it. How it's done is only known because, I think, one of the devs looked it up in the code, then told us, and it's being passed on from user to user every once in a while.
In fact, I've once been told by a blind or visually-impaired user that at least Hubzilla's Articles app for non-federating long-form articles did not work in her screen reader at all.
Hubzilla's frontend must largely run on code from 2012 when it was matched with the completely re-written backend. Afterwards, new or changed features were only patched in. Hubzilla's UI is convoluted and confusing even for sighted users.
Also, Hubzilla has never had a run-in with blind users either because it's even more obscure than Friendica, and its community is even smaller than Friendica's.
Lastly, Hubzilla can only be used via the Web interface. There is no other way. It doesn't support Mastodon apps, and it never will.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #A11y #Accessibility First of all, I've just noticed that you seem to not have joined the Friendica support forum yet. As far as I know, you can't post to a Friendica group/forum without fully connecting to it first.
As for the accessibility issues: To most people, it appears like Friendica has only just been made since they haven't heard of it before mid-January. But actually, Friendica is from 2010. And its frontend is largely stuck in the early 2010s, including technologically.
Friendica has always been a spare-time hobbyist project. It was mostly developed by one single man for almost two years. That guy is a protocol designer and not a frontend developer. Also, I think Friendica never had more than two regular developers, and it definitely never had any developer who really knows how to make a modern and appealing user interface. I mean, you've obviously never seen Friendica's user interface, but let me tell you that it's quite old-fashioned. It's just meant to do its job.
Hobbyist, spare-time developers of such an extremely niche piece of software who are not trained in Web UI design normally don't know a thing about accessibility. And truly, they don't care. If the UI covers all features, and the users don't have to SSH or telnet onto the Web server to use it, it's often good enough.
Friendica's regularly active user community has never been more than maybe a few thousand at a time, maybe even only a few hundred, as opposed to the over two million at which Mastodon has topped out. Thus, Friendica has never encountered blind or visually-impaired users yet.
You can see it all over the place. Alt-text is not part of Friendica's culture. Some Friendica veterans staunchly refuse to describe their media because they think alt-text is another Mastodon fad that Mastodon fundamentalists want to force upon the whole rest of the Fediverse with Mastodon's entire culture. Alt-text, to them, is like limiting your posts to 500 characters.
All this is why nobody has noticed yet that Friendica is not accessible at all.
I've got a suspicion that Friendica can only be made fully accessible by throwing the entire Web frontend away, developing an entirely new one from scratch and then also making all-new themes for it.
Also, it's only natural that TweeseCake doesn't support many of Friendica's features. As it looks to me, TweeseCake's Fediverse side is built against Mastodon and only Mastodon. If Mastodon doesn't have a feature, TweeseCake doesn't cover it either. Thus, TweeseCake probably only covers about 20% of Friendica's features because Mastodon doesn't have the other 80%.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #TweeseCake #A11y #Accessibility Discord has completely warped the term "server" for entire generations of Internet users. On Discord, "server" means "chatroom".
In the Fediverse, "server" doesn't mean "chatroom". It means "". A computer.
For example, .
Or or running at someone's home, connected to their landline.
On each one of these, a big or small Twitter can be running (Mastodon).
Or a wholly different Twitter (Pleroma, Akkoma, Misskey, Calckey, Firefish, Iceshrimp, Sharkey, Catodon, Meisskey, Tanukey, Neko...).
(Here's the first important new thing for you to learn about the Fediverse: The Fediverse is not only Mastodon.)
Or a Facebook with a side of a blog and a cloud server (Friendica, (streams), Forte).
(Here's the second important new thing for you to learn about the Fediverse: The Fediverse is not only short-form microblogging. Look at this comment. Look at what I've done. Embedded links. Bold type. Impossible on Mastodon. But possible elsewhere in the Fediverse.)
Or a Facebook meets WordPress meets Google Cloud Services meets even more stuff on top (Hubzilla this is where I am).
Or an Instagram (Pixelfed).
Or a YouTube (PeerTube).
Or a Twitch (Owncast).
Or a Reddit (Lemmy, /kbin, Mbin, PieFed).
Or a Goodreads (BookWyrm).
Or whatever. There are over 150 different server applications in the Fediverse.
mastodon.social, where you are, is only one of over 10,000 big and small Twitters of the same kind (Mastodon).
If Mastodon was like Discord, all 10,000+ Mastodon servers would run in one and the same gigantic data centre in the USA, owned by Mastodon, Inc. And they would all be property of Mastodon, Inc.
If the Fediverse was like Discord, all 30,000+ Fediverse servers would run in one and the same gigantic data centre in the USA, owned by Mastodon, Inc. And they would all be property of Mastodon, Inc. Also, they would be fully identical in functionality.
But as I've said above: They're all running on their own separate machines. With their own separate owners.
And the different server applications have different developers, and they are being developed independently from one another.
Okay, now comes the kicker: These server applications are not walled up against one another. Not only are all instances of the same server applications (e.g. Mastodon) connected to each other, but all instances of one server application are also connected to all instances of all the other server applications.
Imagine you're on Twitter. But your new friend is on Facebook. You can't follow a Facebook user on Twitter, and you can't follow a Twitter user on Facebook.
In the Fediverse, you can. You can be on Twitter. And follow a Facebook user. Directly from Twitter. Without a Facebook account.
Only that they aren't named Twitter and Facebook in the Fediverse. Twitter is named Mastodon or Pleroma or Akkoma or Misskey or Calckey or Firefish or Iceshrimp or Sharkey or Catodon or... There are dozens of Twitter alternatives in the Fediverse. Well, and Facebook is named Friendica or Hubzilla or (streams) or Forte.
You can be on Mastodon. And you can follow Friendica accounts. From Mastodon. Without a Friendica account.
This comment is a very good example. You are on , created by in 2016 as an alternative to Twitter that aimed to be as close to Twitter as possible.
The server that you're on, , is owned by Mastodon, Inc. and running on one or multiple rack servers in San Francisco, California, USA owned by .
I am on , created by Mike Macgirvin in 2012 by forking his own from 2010, and currently mainly maintained by Mario Vavti and Harald Eilertsen. Hubzilla has got nothing to do with Mastodon whatsoever. It started out as an alternative to Facebook, but not a clone, rather better than Facebook, with full-blown long-form blogging capability and a built-in file storage, and it has been enhanced greatly in functionality even beyond that.
The server that I'm on, , is owned and administered by Mark Nowiasz, who has no affiliation with the Hubzilla developers, and running on a rack server in Nuremberg, Germany owned by .
And yet, you can see this comment coming from Hubzilla on Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Server #Instance #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Calckey #Firefish #Iceshrimp #Sharkey #Catodon #Meisskey #Tanukey #Neko #Friendica #Hubzilla #Streams #(streams) #Forte #Pixelfed #PeerTube #Owncast #Lemmy #/kbin #Mbin #PieFed #BookWyrm #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
Please make it descriptive: tell us about colours, what the person looks like, the background, and anything else you can think of.
I've got a few examples of image posts of my own with very detailed image descriptions. These posts are not on Mastodon, but they are very much in the Fediverse in places that are federated with Mastodon, and they all have actually ended up on Mastodon timelines. So I guess Mastodon's accessibility requirements apply to these places just as well.
Would you say they're too descriptive Or would you even say they aren't descriptive enough yet, and that there are important details missing
One example is (content warning: eye contact) with two images, my most recent one. It is not available on mastodon.online. These images also show a digital avatar, so in a sense, I've described a person.
- The first image has exactly 1,500 characters of alt-text, 990 are short image description, 509 explain where the long description can be found.
- The second image has 1,499 characters of alt-text, 989 are short image description, 509 explain where the long description can be found.
- The long descriptions have almost 11,000 characters in the common preamble, over 2,800 characters specifically for the first image and almost 6,600 characters specifically for the second image because it has more surroundings. All in all, the long descriptions have almost 21,000 characters. It took me eight hours to research for and write them. The visual description of the avatar plus necessary explanations alone takes up almost 7,000 characters.
Another example is with one image. You can also find it by searching for the hashtag #UniversalCampus and scrolling to the bottom of the results there you can see what it looks like on Mastodon.
- The alt-text is exactly 1,500 characters long, 1,402 of which are the short image description. The note where to find the long description had to be shortened to the point of being half-useless.
- The long description in the post is over 60,000 characters long. It took me two full days, morning to evening, to research for and write it.
- I've actually had to limit myself in comparison to earlier image descriptions: There are no longer any detailed descriptions of images within the image, especially not at a higher level of detail than what the images within the image themselves show in-world.
- This description is outdated because I've used absolute measures rather than measures relative to what people are familiar with, and the descriptions of the colours may not be detailed enough.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Inclusion #A11y #Accessibility
What are the differences between Diaspora, Pleroma, Hubzilla, Hometown, and Glitch How do they compare to Friendica as far as features
As for Hubzilla vs Friendica, I've made a series of tables that compare Mastodon, Friendica, Hubzilla and (streams). I've made them for those who are looking for a Facebook alternative in the Fediverse, but who only know Mastodon first-hand and Friendica from hearsay. But these tables are useless for blind or visually-impaired users, and I can't change that because it's in the nature of tables. Also, I don't have all data for Friendica yet. (In case someone sighted comes across this comment and wants to see the tables: ).
So I'll try to do a Hubzilla vs Friendica comparison here. Hold on and take some time, for this will be very, very, very long. 42 lines of comparison with over 10,000 characters.
Friendica was created by Mike Macgirvin in 2010.
Hubzilla started out as a Friendica fork by Mike Macgirvin himself in 2012, originally named Red (from spanish la red = the network), then renamed Red Matrix. It was repositioned, reworked, massively extended beyond Friendica's features and renamed Hubzilla in 2015.
Friendica has native Android apps, a closed beta native iOS app and support for Mastodon apps, even though Mastodon apps only cover 20% of Friendica's features at most. Hubzilla doesn't have any mobile apps, at least none for iOS, none in the Google Play Store, none that could be installed on a new Android device and none with a fully native mobile user interface.
Hubzilla also also doesn't support Mastodon apps and never will. That's mainly because a Mastodon app can't cover over 90% of Hubzilla's features, including features which you need all the time such as file upload, image embedding, handling of connections and permission controls, simply because Mastodon doesn't have these features. Hubzilla would require its very own apps, and due to Hubzilla's immense complexity and wealth of features, a fully-featured, dedicated Hubzilla app would be absolutely gargantuan and just as complex as Hubzilla itself.
On Friendica, ActivityPub federation is available from the get-go. On Hubzilla, ActivityPub federation is optional, and on newly-created channels, it is off by default.
Friendica can integrate Bluesky and Tumblr accounts. Hubzilla can't.
On Friendica, your account is your identity. Your identity is firmly tied to your account. On hubzilla, your identity is independent from your account. It resides in a container called a "channel", of which you can have multiple, fully independent ones on the same account. This also allows you to switch back and forth between channels or identities without logging out and back in.
Friendica has limited capabilities of moving your identity to another instance. Hubzilla has nomadic identity. For one, this makes it possible to relocate an entire channel with all posts, all comments, all private messages, all connections, nearly all settings, all files in your file space etc. etc. to another instance. Besides, it makes it possible to clone a channel to one or multiple other instances. This gives you live, hot, real-time, bidirectional backups of your channel, and you can log into and use any of them. That way, your channel is much more resilient against instance shutdown.
If you delete a Hubzilla channel, you cannot create a channel with the same short name on the same Hubzilla hub unless the admin fully deletes your channel from the database.
If you delete a clone of a Hubzilla channel, you cannot clone the same channel back to the same hub unless the admin fully deletes your channel from the database.
Friendica has client-side support for OpenWebAuth magic single sign-on. Hubzilla has full support. This means that Friendica logins are recognised by instances with full OpenWebAuth support, but Friendica itself doesn't recognise logins elsewhere. Hubzilla logins are recognised the same, and Hubzilla does recognise logins elsewhere.
Friendica has some basic permission control. On Hubzilla, it is much more advanced and fine-grained.
On Friendica, you can set your profile to private. On Hubzilla, you can give permission to see your profile to anybody on the internet, anybody in the Fediverse, anybody on Hubzilla or (streams), anybody on your hub, unapproved and approved connections, approved connections, only those you specifically allow by contact role or only yourself.
On Friendica, you can set your list of connections to private. On Hubzilla, you can give permission to see your connections to anybody on the internet, anybody in the Fediverse, anybody on Hubzilla or (streams), anybody on your hub, unapproved and approved connections, approved connections, only those you specifically allow by contact role or only yourself.
On Friendica, you can set your timeline to private as far as I know, this happens along with setting your profile to private. On Hubzilla, you can give permission to see your stream to anybody on the internet, anybody in the Fediverse, anybody on Hubzilla or (streams), anybody on your hub, unapproved and approved connections, approved connections, only those you specifically allow by contact role or only yourself.
I don't know if Friendica can give specific permissions to specific connections. Hubzilla has so-called "contact roles". Each contact has a contact role that grants or denies 17 different permissions. Permissions granted channel-wide from the channel role are inherited by all contact roles. Two of these permissions are for your contacts to send you their posts and for your contacts to send you private messages.
On Hubzilla, you can keep both everyone and specific contacts from sending you repeats/boosts/reposts/renotes with a line of filter syntax in a filter blacklist.
On Hubzilla, you can send any of your posts as public, only to yourself, to all members of a privacy group (which is similar to a circle on Friendica), to whoever is assigned a certain non-default profile, to one specific group/forum or to a custom selection of contacts. You can also define your default post audience, either one of your privacy groups, or your posts are public by default.
Hubzilla has three levels of reply control. At channel level, you can give permission to reply to your posts to anybody on the internet, anybody in the Fediverse, anybody on Hubzilla or (streams), anybody on your hub, unapproved and approved connections, approved connections, only those you specifically allow by contact role or only yourself. In addition, you can choose to let comments in from those who are not permitted to comment on your posts, preview them and then manually decide whether or not you accept each comment.
Reply control at per-contact level means that you can use contact roles to grant or deny permission to reply to your comments to certain connections.
Reply control at per-post level is optional and off by default. It lets you disallow comments on individual posts of yours entirely.
Likewise, there is quote-post control at channel level and at per-contact level.
On Friendica, you can report posts to the admin. On Hubzilla, you can't. This feature is currently being discussed.
I don't know about Friendica, but Hubzilla has a channel-wide filter with a whitelist and a blacklist, and optionally, it has an individual filter for each connection with a whitelist and a blacklist.
Hubzilla allows regular expressions in filter lines, but only for normal keywords, not in lines with filter syntax.
Hubzilla's filter syntax can recognise posts, comments and private messages. This is of very limited usefulness, however: If you want to whitelist certain keywords for posts, but let all comments and all private messages through, you'd have to use filter syntax in a whitelist. But in whitelists, keyword lines are connected with "or" whereas filter syntax lines are connected with "and" which means that you cannot combine keywords with filter syntax. There is also filter syntax for keywords, but these lines are connected with "and" in whitelists, too, and each line can only contain one keyword with no regular expression.
On Friendica, summaries or Mastodon-style content warnings are created with a pair of BBcode tags, either
abstract/abstract or abstract=apub/abstract. This works for posts, comments and private messages. Hubzilla has a dedicated summary field for posts, but none for comments. In theory, it also has the BBcode tag pair summary/summary, but in practice, it is broken.Friendica optionally offers Markdown for text formatting in addition to BBcode. Hubzilla only offers BBcode.
Friendica doesn't have or support polls. Hubzilla has full support for basically unlimited polls.
Friendica calls reposting "sharing" and quote-posting "quoted sharing". Hubzilla calls reposting "repeating" and quote-posting "sharing".
On Hubzilla, you can optionally be notified when a stranger mentions you out of the blue outside any conversation on your stream.
On Friendica, you can make a group restricted or private. On Hubzilla, you can give a group or a forum privacy, too, but by choosing the "Custom" channel role instead of the "Community forum" channel role, and you have to adjust the level of privacy by hand. The advantage is that you have fine-grained control over what exactly you want to be private in your group or forum.
Private Friendica groups can be joined by users on Friendica, Hubzilla, (streams) and probably also Forte. Private Hubzilla groups or forums can only be joined by users on Hubzilla, (streams) and maybe Forte.
Friendica has a central directory of users, groups etc., the . Hubzilla doesn't have such a thing.
Friendica nodes have their own directories I'm not sure if they only list Friendica accounts or accounts and channels of everything that uses ActivityPub, or if they even include diaspora* users. Hubzilla hubs have such directories, too, but they only list Hubzilla and (streams) channels because they can only list what uses the built-in and permanently activated Nomad protocol.
In your Hubzilla directory, you can hide channels that are flagged not safe for work.
Hubzilla has an option that gives those who are permitted to see a post the permission to also see any media embedded in the post, regardless of the permissions set for the respective media in your file space. This was introduced due to the wide-spread issue of people uploading images and setting them or the directores the images are in to private, then embedding them into public posts and the audience of the posts not seeing the images.
On Hubzilla, you can give guest access tokens to people whom you want to access certain files or directories in your file space.
The file space built into your Hubzilla channel can be accessed via WebDAV.
Hubzilla also has a built-in CalDAV calendar server which can use the event calendar as a simple frontend and an optional headless CardDAV addressbook server.
Hubzilla optionally has "articles", long-form text posts with the same full text formatting capabilities as normal posts, but which don't federate.
Hubzilla optionally has "cards", basically planning cards with the same features as articles plus a few extra features.
Hubzilla optionally has multiple wikis per channel with multiple pages per wiki. Wikis can be set up to use either BBcode or Markdown as their markup language with a few wiki-specific additions in both cases.
Hubzilla optionally has simple, static webpages which can be formatted with either BBcode, Markdown or plain HTML. Hubzilla's own official website is a webpage on a Hubzilla channel.
I think that's about it.
As for diaspora*: Forget it. For one, it does not support ActivityPub, and it does not federate with most of the Fediverse. The diaspora* developers staunchly refuse to add any other protocols to diaspora*, especially ActivityPub. One has actually said that you don't implement ActivityPub, you implement Mastodon. And the diaspora* developers don't want to make themselves dependent on Mastodon.
Besides, diaspora* is withering away. Around December 29th, a number of major diaspora* pods shut down. According to one source, diaspora* lost over half its user accounts in three days. And the closure of diasp.org, one of the biggest pods, is scheduled for April 1st now.
Quote:
Are there any other networks I should know about
End quote.
From the same creator as Friendica and Hubzilla, there is something he created in 2021 at the end of a long and somewhat complex line of forks. It is officially and intentionally nameless, brandless, not a project and released into the public domain. Colloquially, it is named (streams) in parentheses after the name of its code repository. You can find the latter with an extensive readme . It is slimmed down in features from Hubzilla, and it doesn't offer nearly the connection and federation options of Friendica and Hubzilla. But it is easier to handle while still having a steeper learning curve than Friendica, and especially its permission system is both another bit powerful and significantly easier to use than Hubzilla's.
(streams) has no mobile apps and no compatibility with Mastodon apps either for the same reasons as why Hubzilla doesn't isn't compatible with Mastodon apps.
(streams) is included in my comparison tables, too. If you want me, I can rattle down another comparison with Friendica like the one with Hubzilla above.
In August, 2024, Mike made another fork based on (streams) named Forte. It's basically (streams), but with a name, with a brand identity, as a project, released under the MIT license and with no support for the Nomad protocol anymore. It does everything using only ActivityPub. This also means that it relies entirely on ActivityPub for nomadic identity. Since especially this is still highly experimental, Forte itself has not officially been released yet, it is not recommended as a reliable daily driver, nor does it have public, open-registration instances.
Quote:
Finally, will the interface of the page on Friendica change depending on my instance
End quote.
As far as I know, different Friendica nodes have different default themes, especially now that the Facebook-like Bookface theme may be officially included into Friendica.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #diaspora* #Friendica #Hubzilla #Streams #(streams) #Forte Not quite, and that says someone who .
Hubzilla wikis don't federate. In any way. They always stay within the Hubzilla channel which they belong to.
Not only that, but I, as the owner of this Hubzilla channel, have to manually permit other people to edit my wikis. And these have to be on something that supports client-side OpenWebAuth: Friendica, Hubzilla, (streams), Forte. And they have to be connected to my channel (in Mastodonese, that's "follow me, and I have to follow them back", but connections on Hubzilla are bidirectional by default) so I can give them permission to edit my wikis.
I've read about a federated wiki engine with ActivityPub in the making, but the name eludes me.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Wiki If you mean "groups" as in "Facebook groups", then you can't create them from your account. They aren't a separate functionality like on Facebook.
On Friendica, groups are accounts like user accounts, only with different settings. So if you want to create a group, you have to register a new account. I recommend you to do that on another Friendica node so you can be logged into both your personal account and your group account simultaneously, just in case you have to do something in your group.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Groups
as i said yesterday the facebook bridge is also broken
There is no Facebook bridge.
I guess you must have heard from someone on Mastodon who has heard from someone on Mastodon etc. something about Friendica and Facebook being connected. Chinese whispers, Fediverse-style. But that's only a tiny chunk of the true story.
There was a Facebook connector. And it wasn't a bridge. It was fully natively integrated into Friendica, just like Bluesky and Tumblr are fully natively integrated into Friendica today. But they require a Bluesky or Tumblr account, and the Facebook integration required a Facebook account. (Source: I've actually used it back in the day.)
Also, Facebook disallowed third-party apps to extract content from Facebook in 2012. And in 2013, Facebook made extracting data impossible, thus ending the functionality of the Facebook integration add-on.
Facebook integration on Friendica has been gone for three years longer than Mastodon has been around.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Facebook #Friendica
Don't hesitate to ask if you're unsure of something, but never think that we don't notice your effort.
I do have a few questions, specifically because my image posts have gone unnoticed by blind or visually-impaired users so far.
Judging and assuming from the information I've gathered so far, my original images require very extensive and detailed descriptions. A full description is too long for alt-text, so what I do is write a full description with all text transcripts and all necessary explanations, put it into the post text body and then condense a shorter, but still long alt-text from it. What's your stance on this method of describing the same image twice over
Also, where would you personally prefer a long description In the post itself Or in an external document that's linked into the post If you're on a phone app, remember that the external document will inevitably open your Web browser.
Do you prefer images described, based on what a sighted person can see in the image as it is posted Or do you prefer a description that is not limited by the restriction of the image itself, for example, assuming an infinite image resolution and an infinite zoom factor that would let sighted people theoretically see even tiniest details
If I mention something in my image description of which you don't know what it looks like, do you need a detailed visual description
Concerning text transcripts: Let's assume a bit of text in an image is too small to be legible for sighted people, but I can read it at the original source, so I can transcribe it nonetheless. Shall I transcribe it What about if said text is too small to be recognisable as text or so tiny that's it's practically invisible I mean, after all, the concept of image resolution should not matter to totally blind people, so writing that a piece of text can't be read because the resolution of the image is too low ought to sound like a lame excuse for skimping a transcript.
If there's a building in one of my images, I can safely assume that you don't know what that one specific building looks like, so I guess I can also assume that you need it described. If I could, I would do so using architectural terms and then explaining all these architectural terms right after using them. Would you say that's the correct way Because that's why I avoid having realistic buildings in my images.
If there's an image in my image, do you need it described At a level that I can source right where the image is without moving away too far, or at a level that I can only source by moving farther away to the place shown in the image What about an image in an image in my image (I'm serious. I've actually described images within images within my image, but I've stopped when this was about to go out of hand due to there being too many to describe.)
I'm currently working on a series of posts with images showing a virtual-world avatar in various but similar outfits in fact, I have been since last year. I may have questions later regarding at what level of detail I have to describe that avatar.
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
DSC9445 by samjstone
I often spend more time writing alt text than the text in the toot itself - not just to keep the toot itself as short as possible.
I always spend more time describing my images than writing the post that they go into.
For my meme posts, that's because I have to explain the picture and find the appropriate links to external explanations (KnowYourMeme etc.) to shorten my explanation block if possible.
For my original images, it's because I have to describe them twice. There's always an alt-text which, as of late, fills the 1,500-character limit imposed by Mastodon, Misskey etc. to the brim. But that alt-text is only a shortened and slightly adapted version of an extremely long long description which goes into the post text body and which also includes transcripts of any and all text in the image, readable or not, as well as all explanations which I deem necessary for outsiders to understand the image. Since the images are about an extremely obscure niche topic, this means I have to explain a lot.
A while ago, I spent two full days, morning to evening, researching for and describing and explaining one single image. The result was . And I actually had to limit myself, otherwise the description would have been even vastly longer and taken over a month to complete. Good thing I don't have any character limit to worry about. The only exception is that Mastodon may reject posts from outside with over 100,000 characters.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta Unless you need a Facebook replacement, unless you plan to use Friendica or Hubzilla or (streams) or Forte, only the first three paragraphs are of interest for you.
Basically, all Fediverse instances are separate websites. If you want to use one of them like you use pdx.social, you need an account on that instance. Your account on pdx.social won't do. It doesn't matter if that instance is a Pixelfed instance or a Loops instance or a PeerTube instance or a Misskey instance or an Akkoma instance or whatever.
So, no, with your Mastodon login, you can't just simply use Pixelfed or Loops or PeerTube. If you want to use Pixelfed (= post pictures), you need an account on a Pixelfed instance. If you want to use Loops (= upload videos), you need an account on the currently only Loops instance. If you want to use PeerTube (= upload videos), you need an account on a PeerTube instance.
Got that so far
But, and this is something that even many Twitter refugees from 2022 haven't understood yet: Mastodon and Pixelfed and Loops and PeerTube and Misskey and Sharkey and Akkoma and Friendica etc. etc. aren't walled off from one another.
You can be on Mastodon, but you can follow Pixelfed accounts from Mastodon. And you can follow Loops accounts from Mastodon. And you can follow PeerTube channels from Mastodon. And so forth. Just like you can follow accounts on other Mastodon instances from your Mastodon account on pdx.social. Just like you already do.
By the way: Right now, you do not only follow Mastodon accounts. I've looked through those you follow. There's one Neil E. Hodges (tkf.kawa-kun.com). Scroll down the list of those whom you follow. When you find him, look at his profile. Okay, now look at his profile at its source. Safari (or whatever is your default Web browser) will open. And you'll see .
This is not a Mastodon account on a Mastodon instance with a weird UI. This is an account on . A Facebook alternative from 2010 which is not Mastodon, which has never been Mastodon, which is developed completely independently from Mastodon, which is very different from Mastodon, and which is over five years older than Mastodon.
But: Just like Mastodon, Friendica is part of the Fediverse. And it has been federated with Mastodon since Mastodon was created. This means: Since Mastodon was created, it has been possible for Mastodon users to follow Friendica accounts from their Mastodon accounts. And vice versa, it has been possible for Friendica users to follow Mastodon accounts from their Friendica accounts.
You yourself are right now following someone who is on something that is not Mastodon. Very much not Mastodon, in fact.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pixelfed #Loops #PeerTube #Friendica #Federation Pixelfed is wholly separate software from Mastodon on wholly separate servers with wholly separate owners. So yes, you need a separate Pixelfed account. It's a bit easier on Pixelfed if you're already on Mastodon: Pixelfed lets you automatically create a new user account by "logging in" with your Mastodon login credentials. But only Pixelfed has this as far as I know.
Loops is wholly separate again, but there's only one instance so far because it's too unfinished to even be open-source. So you'll need a Loops account next to your Mastodon account and your Pixelfed account.
Also, you'll have different followers on Mastodon, on Pixelfed and on Loops. But what you could do if you want your followers on Mastodon to see your Pixelfed posts is: Follow your own Pixelfed account from Mastodon. And then, whenever you post something interesting on Pixelfed, wait for it to arrive on your Mastodon timeline, and then boost it.
There's one thing that exists already now: OpenWebAuth magic single sign-on. But it's only available on Hubzilla, (streams) and Forte and partially on Friendica.
What it does is recognise your login on another instance, even on an instance of another server application. Hubzilla, (streams) and Forte recognise logins from Friendica, Hubzilla, (streams) and Forte, but Friendica can't recognise logins.
However, this is only used by the permissions system. For example, someone whom I'm connected to could have made their profile only visible to a certain subset of their connections, including myself. If you visit their profile, you won't see anything. If I visit their profile, their home instance recognises my Hubzilla login, and I can see the profile.
What it does not do is give you the same full-blown rights as a user with a local account. I can't just, like, go to some (streams) instance and post away as, what, jupiterrowlandrumbly.net or go to a Hubzilla hub where I don't have an account and create a webpage or a wiki or a CalDAV calendar right away without logging in. That's not how it works.
By the way, client-side OpenWebAuth support (= your login is recognised on Hubzilla, (streams) and Forte) was proposed and actually developed to the point of a pull request for Mastodon. As far as I know, it was rejected. OpenWebAuth won't come to Mastodon.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pixelfed #Loops #Friendica #Hubzilla #Streams #(streams) #Forte #OpenWebAuth #SingleSignOn Tatschlich ist meines Erachtens dichter an Friendica dran als , weil nicht so berladen. Das kennt blo auerhalb von Hubzilla und (streams) selbst praktisch keine Sau. Da habe ich auch zwei Kanle.
Friendica wrde ich nur empfehlen, wenn jemand unbedingt, unbedingt eine Android-App braucht. Oder willens ist, eine iOS-App mit einem Riesenaufwand ber TestFlight zu installieren. Vielleicht noch, wenn jemand mit (streams) nicht klarkommt (wobei auch Friendica nicht unbedingt "registrieren und loslegen" ist).
Hubzilla, da bin ich jetzt hier gerade selber, ist schon ziemlich hardcore von der Lernkurve her und braucht zwingend einiges an Einstellungen, bevor man loslegen kann. App kann man auch vergessen, aber ich schaudere beim Gedanken einer Fully-featured-Hubzilla-App mit komplett nativem Mobilinterface.
Wenn Forte offiziell freigegeben wird, werden die Karten vielleicht neu gemischt. Aber in der Bedienung wird es sich nicht groartig von (streams) unterscheiden. Der einzige Unterschied ist, da Forte das Nomad-Protokoll nicht mehr hat, sondern nur noch ActivityPub.
Fr die, die es noch nicht wissen: Das ist alles eine Software-Familie, die derselbe Entwickler seit beinahe 15 Jahren in Entwicklung hat. Und zwischen Hubzilla und (streams) gab es noch ein Geflecht aus mindestens sieben weiteren Forks, die alle eingestellt sind.
Ich habe brigens krzlich einen tabellarischen Vergleich zwischen Mastodon, Friendica, Hubzilla und (streams) gemacht, falls es jemanden interessiert.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Facebook #FacebookErsatz #Friendica #Hubzilla #Streams #(streams) Auf Mastodon gar nicht. Mastodon hat fr Gruppen keinerlei Untersttzung und wei gar nicht, was Gruppen sind.
Hier sind ein paar Sachen, wo du nach Gruppen suchen knntest, mit denen du dich trotzdem von Mastodon aus verbinden kannst:
listet aktuell ber 220 ffentliche Friendica-Gruppen. (Falls nicht bekannt: Friendica ist eine Facebook-Alternative im Fediverse.)
listet aktuell fast 28.000 Lemmy-Communities. (Falls nicht bekannt: Lemmy ist ein Reddit-Klon im Fediverse.)
Es gibt noch einiges mehr, was Gruppen hat, aber dafr jeweils keine umfassende ffentlich erreichbare Suche.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Friendica #Lemmy #Gruppeninbal Dror 2021 collection.
Richtig.
Das ist genau wie 2022/2023. Da wurde doch die groe Masse der Mastodon-Nutzer direkt nach mastodon.social geholt, ohne da ihnen erklrt wurde, was Mastodon ist (auer dem blichen "literarisch Twitter ohne Musk") oder gar das Fediverse. Die haben teilweise Monate gebraucht, um berhaupt nur zu merken, da Mastodon keine einzelne monolithische Silo-Website ist.
Heute gibt's genau das immer noch. Zustzlich wird den Leuten erklrt:
- Pixelfed = literarisch Instagram ohne Zuckerberg = pixelfed.social
- Loops = literarisch TikTok,
aber in Amiland erreichbarohne Muskwas auch immer = loops.video (gerechtfertigt, da wird's bis auf weiteres nur die eine Instanz geben) - Friendica = literarisch Facebook ohne Zuckerberg = friendica.world (auch weil die meisten Amis keinen anderen englischsprachigen Node kennen, weil die anderen groen Nodes alle deutsch sind)
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Pixelfed #Loops #Friendica You can't connect Fediverse accounts like that and make them one, at least not generally all over the place, and especially not between Mastodon and Hubzilla. These two will always be fully separate logins.
The best you can do is follow your Hubzilla account from Mastodon, then confirm the connection request on Hubzilla which, from Mastodon's point of view, creates a mutual follower/followed connection.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla babenextdur IG
Since you're already offering multiple options to switch to, here are some more proposals:
Facebook -> ()
Facebook -> ()
-> ()
-> ()
Threads -> ()
Threads -> ()
Reddit -> ()
Reddit -> ()
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Meta #MetaPlatforms #Facebook #Streams #(streams) #Hubzilla #Twitter # #Threads #Misskey #Iceshrimp #Reddit #Mbin #PieFed #GlobalSwitchDay
New entry of AI-generated and added to our :
's
A better question would be if he'll get the reach he wants with only a Pixelfed account. One could argue that he'd be better off with a Mastodon account on top to advertise for his Pixelfed posts by boosting them. But one could also argue that this may lead to people following his Mastodon account rather than his Pixelfed account. And that it'd amount to cheating.
His advantage, however, would be that he wouldn't start out all alone in the Fediverse. I think I can expect you to follow him. You are already on Mastodon, you already have a substantial amount of followers, so I guess he could leave the "plugging" to you.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pixelfed
the only 3 posts on Pixelfed
Do you mean posts from people whom you follow on Pixelfed
If yes, then yes, you have to log into your Pixelfed account.
Do you mean your own posts which you've posted on Pixelfed
If yes, then yes, you have to log into your Pixelfed account.
There is only one way to connect a Mastodon account and a Pixelfed account: You can follow your own Pixelfed account with your Mastodon account. This doesn't make one account out of two accounts. You only become your own follower. Just like you can follow anyone else's Pixelfed accounts from Mastodon. Or just like anyone else on Mastodon can follow your Pixelfed account.
When you do so, and you post something on Pixelfed (you have to log into Pixelfed for this), you receive these posts on Mastodon. The purpose of this is e.g. to boost your Pixelfed posts to your Mastodon followers so they can see them without also having to follow your Pixelfed account.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pixelfed The Fediverse is a bunch of different, independent applications which nonetheless are connected in such a way that users of one application can follow users of another application. But they're still separate instances of different, independent applications.
If you're on Mastodon, and you want to follow a PeerTube channel and comment on the videos from that PeerTube channel, you can simply follow that PeerTube channel from Mastodon. You don't need a PeerTube account.
If you're on Mastodon, and you want to upload videos to PeerTube, then you need a PeerTube account.
What Pixelfed does, namely automagically create a Pixelfed user account for everyone who "signs in" with their Mastodon credentials, is an exception, but it misleads Fediverse newbies into thinking that they've got full user power on all instances of all Fediverse server applications with their Mastodon login.
Should we all be having the same handle with different instances (each instance a different UX/app) or... nah
You can. If you want to. Advantage: People can be fairly sure that it's the same you as the Mastodon you.
But you don't necessarily have to. Not if e.g. you want to represent an entirely different persona on, say, Misskey than your normal, standard public self on Mastodon.
I mean, you can also have multiple accounts on Mastodon (or anything else) under different names, with different identities, with different personas or even for different purposes. For example, if you love posting about topic A and topic B, you make an account for topic A and one for topic B with different names. That way, the people who follow you for topic A don't have their timelines cluttered with your topic B stuff that's uninteresting to them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #FediTips (streams) ist Hubzilla
- minus alle Protokolle auer Nomad (beide Versionen) und ActivityPub
- mit ActivityPub im Kern und standardmig an
- minus RSS/Atom-Aggregator
- minus Artikel
- minus Karten
- minus Wikis
- minus Webpages
- mit nur einem Profil pro Kanal
- mit Verifizieren externer Identitten (wie z. B. auch bei Mastodon und WriteFreely)
- mit einfacherer Berechtigungssteuerung und vier kanalweiten Berechtigungslevels weniger als Hubzilla
- mit Kanaltypen, die nur noch ganz wenige Berechtigungen steuern und nicht mehr alle kanalweiten Berechtigungen wie Hubzillas Kanalrollen
- ohne Custom-Kanalrolle, weil unntig
- mit vier Kanaltypen fr Gruppen/Foren
- mit der Mglichkeit in Gruppen/Foren, Posts und Kommentare von Neulingen durch Admins freizuschalten
- mit einzeln pro Verbindung schaltbaren Berechtigungen Berechtigungsrollen (Hubzilla: Kontaktrollen) sind nur noch Presets zur Bequemlichkeit und nicht mehr die einzige Mglichkeit, Verbindungen Berechtigungen zu erteilen
- mit der (optionalen) Mglichkeit, da nur deine eigenen Verbindungen auf einen bestimmten Post antworten drfen und/oder nur bis zu einem bestimmten Datum auf einen bestimmten Post geantwortet werden darf
- mit der Mglichkeit fr Nutzer, ganze Instanzen zu blockieren
- mit der Mglichkeit fr Admins, ganzen User Agents und damit auch ganze Fediverse-Projekte instanzweit zu blockieren
- mit Textformatierung in Posts per nicht nur BBcode, sondern auch Markdown und HTML
- mit Tags fr Zusammenfassungen/Mastodon-CWs statt einem Eingabefeld
- mit der Option, auch ganze Threads auf den eigenen Stream zu holen, in denen ein eigener Kontakt geantwortet hat
- mit ActivityPub-Konten und -Gruppen im Verzeichnis und nicht nur Nomad-Kanlen
Einen kompletten tabellarischen Vergleich zwischen Mastodon, Friendica, Hubzilla und (streams) habe ich gemacht.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams)
Last updated: 2025-01-29
All text and images © eLoc8.is-fabulous.com