I don't want to rattle down the features of Hubzilla and (streams) and their whole history from Mistpark in 2010 to Forte in 2024 just to explain a meme image. It's bad enough already that I have to explain nomadic identity.
But I guess there's no other way if I want everyone to understand the image without requiring them to resort to external sources of information.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Mistpark #
Hubzilla #
Streams #
(streams) #
Forte #
NomadicIdentity #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta #
Memes #
A11y #
Accessibility Can you please answer my questions alreadyIf I choose to curate my stream by topic and thereby refuse to follow users regardless of what they have to say, even if these users are Black,
is that racist Yes or noIf I mention the existence a safer alternative to Mastodon that's still in the Fediverse to Black users, unsolicitedly,
is that racist Yes or no If it's racist, in how many and which ways (I could count at least two.)
If I refuse to support Mastodon instances because I hate specifically Mastodon with a burning passion, even if the instance admins are Black,
is that racist Yes or noNew question: If I use Hubzilla like Hubzilla, if I refuse to use Hubzilla like Mastodon, and this leads to no additional support for the Black community,
is that racist Yes or noI honestly, sincerely do not know whether you consider any of this racist. No, I don't. So please stop acting like it was all clear to me.
Because it isn't.CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Racist #
Racism I wasn't only posting this with raw technology in mind. I was also thinking about
cultural differences that arose from the technological differences.
Friendica and Hubzilla are technologically very different from Mastodon. Friendica, Hubzilla and (streams) users are rather used to that. They try to cope with it the best they can, although this alone brings its own bunch of issues with itself.
Mastodon users, on the other hand, are
not used to it. Many of them have come to Mastodon from Twitter over the last two years, believing that Mastodon is only one Web site. And pretty much all of them, every last one of them, came to Mastodon, believing that the Fediverse that everyone talks about
is Mastodon. And nothing else.
Those who have invited them to Mastodon have not told them that Mastodon is connected to things that aren't Mastodon, much less that Mastodon is connected to things that are
very much not Mastodon.
Nearly all Twitter refugees on Mastodon have spent their first several months on Mastodon in this belief. They've settled into and gotten used to a Fediverse that's only Mastodon.
Many, not all of them, but many have since found out that there are things in the Fediverse that are very different from Mastodon. For not exactly few, it was a disturbing, if not outright traumatising experience to see that some Fediverse users can post over 500 characters at once. Or that some Fediverse users can easily "quote-toot" Mastodon toots, using something which is used on to harass members of marginalised minorities.
They didn't want that. They still don't want that. They want to make it go away again, so disturbing is it.
By and by, at least some Mastodon users face other differences between Mastodon on the one side and things like Friendica, Hubzilla and (streams) on the other side. For example, what the way these three handle conversations means in practice for users of Mastodon which doesn't have a concept of conversations. Or that Friendica, Hubzilla and (streams) users do not react when someone on Mastodon mentions them out of the blue. Everyone on Mastodon would notice it, so it's beyond a Mastodon user's comprehension that Friendica and Hubzilla users
don't notice it by default.
So on the one hand, Mastodon users are increasingly stressed out by Friendica being Friendica and Hubzilla being Hubzilla. They ask themselves: "Why did they make everything so different from Mastodon Why couldn't they have made it all just like Mastodon in the first place"
It's incomprehensible to them that Friendica and Hubzilla were both made
before Mastodon. For how can something in the Fediverse possible pre-date Eugen Rochko's invention of the Fediverse It's also incomprehensible to them that something in the Fediverse can be something else than a Twitter clone. Or they simply don't know how Facebook, which Friendica aims to be an alternative to, works differently from Twitter as well.
On the other hand, Friendica, Hubzilla and (streams) users are increasingly stressed out by Mastodon users trying to force Mastodon's culture upon them, along with Mastodon's limitations. Not few Mastodon users try to make Friendica, Hubzilla and (streams) behave more like Mastodon by putting pressure on their users to a) always do everything the Mastodon way and b) stop making use of features that Mastodon doesn't have.
If you've never come across a Mastodon user complaining about a post or comment of yours being too long because you've exceeded the holy limit of 500 characters, then I'm very certain that you will.
Food for thought: This entire conflict would disappear with a split. Mastodon users would be spared from utterly non-Mastodon things. And non-Mastodon uers would be spared from demands to stop making use of 90% of all features they have at hand just because Mastodon doesn't have them.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Friendica #
Hubzilla #
Streams #
(streams) #
CharacterLimit #
CharacterLimits #
500Characters #
QuotePost #
QuotePosts #
QuoteTweet #
QuoteTweets #
QuoteToot #
QuoteToots #
QuoteBoost #
QuoteBoosts #
QuotedShares #
QuotePostDebate #
QuoteTootDebate Find the latitdue and longitude of any place FX: CFTC data show that and have flipped their long-standing short position and are now net of the currency for the first time since March, 2021, chart ReutersJamie ReutersBiz
unfortunately, no, I don't think you've learned from me. In fact you're repeatedly distorted my words.
If I choose to curate my stream by topic and thereby refuse to follow Black users regardless of what they have to say, is that racist or not
If I mention the existence a safer alternative to Mastodon that's still in the Fediverse to Black users, unsolicitedly, is that racist or not, and if so, in how many and which ways (I could count at least two.)
If I refuse to support Black-led Mastodon instances because I hate
specifically Mastodon with a burning passion, is that racist or not
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Racist #
RacismYour choice of technology is not my problem.
It quickly becomes a problem for Mastodon users who expect Hubzilla to act exactly like Mastodon if Hubzilla
doesn't act exactly like Mastodon.
And my choice of technology is also a problem for Mastodon users because, due to being so much different and older than Mastodon, Hubzilla has its own culture which is very different from Mastodon's, and Hubzilla's users don't want to give up their culture and adopt Mastodon's culture instead, especially not if that means abstaining from using features which Hubzilla has and Mastodon doesn't. Quote-posts, for example. Or no character limits.
If you don't want to federate in that manner, then either defederate from masto instances or choose software that works the way you want.
Hubzilla
does work the way I want. Otherwise I would long since have moved away.
The problem is that Hubzilla doesn't work the way
Mastodon users want.
The very same features can be perfectly normal from Hubzilla's POV and actually the reason why Hubzilla users use Hubzilla
and outright disturbing from Mastodon's POV.
That you assume there are no black people with anything interesting to say is very telling.
I am actually following at least one Black woman who is active in OpenSim, . Not sure about right now I can't always tell the real-life skin colour of the user behind a 3-D avatar right off the bat.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Hubzilla #
OpenSim #
OpenSimulator No mechanism. Only the very nature of cloning and clones and nomadic identity.
A clone is not a separate entity from the main instance or the other clones. A clone does not have its own individual identity. Mastodon thinks a clone is a separate account with its own identity, but it isn't.
A nomadic clone
is the main instance, just elsewhere.
Again:
The Fediverse ID of my main instance, , is
jupiterrowlandhub.netzgemeinde.eu
.
The Fediverse ID of my clone, , is
jupiterrowlandhub.netzgemeinde.eu
, too.
Open both. Look at them. Compare them. They're
identical.
And they're acting
as one because they
are one.
They are not like two connected Mastodon accounts. They are like
one Mastodon account simultaneously residing on two Mastodon instances.
I could log onto hub.hubzilla.de where the clone is and send a post. This post would still come from
jupiterrowlandhub.netzgemeinde.eu
. And the post would be sync'd over to hub.netzgemeinde.eu to make sure that the main instance is identical with the clone again.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Hubzilla #
NomadicIdentityI could post the entire context of this for better understanding.
But for one, this would require sharing (= Friendica/Hubzilla/(streams) lingo of quote-posting) a whole number of very long (= way over 500 characters) comments on a not exactly short post. And besides, I guess quote-posting an anti-racist activist falls under harassment and therefore racism itself. Because quote-posts are
always harassment.
In fact, I'm now waiting for hub.netzgemeinde.eu to be added to Fediverse blocklists. I can already see Mastodon users try to have the hub.netzgemeinde.eu moderation sanction me, only to fail because
- Mastodon-style reports to remote instances are probably not implemented on Hubzilla
- no Mastodon interface tells you who the admin of hub.netzgemeinde.eu is
- the hub website itself doesn't tell you either
- even if they figured out who the admin is, he won't notice being mentioned by a non-contact out of the blue because this behaviour is off by default on Hubzilla
So from a Mastodon point of view and by Mastodon standards, hub.netzgemeinde.eu is not sufficiently moderated to silence such an utterly, deeply racist pig as me. And being undermoderated has always been a valid reason for a Fediverse instance to be Fediblocked.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Hubzilla #
QuotePost #
QuotePosts #
QuoteTweet #
QuoteTweets #
QuoteToot #
QuoteToots #
QuoteBoost #
QuoteBoosts #
QuotedShares #
QuotePostDebate #
QuoteTootDebate #
Racist #
Racism #
FediblockMeta That post is by me. And it's completely sincere. All I've written there, I've learned from a very avid anti-racist, . The thread in which I've learned it starts .
Also, claiming that
I, quote, "don't see the racism on the Fediverse", end quote, is a strawman all in itself. I have never said anything like it.
I'm someone who takes a closer look at Fediverse culture and tries to fulfill people's needs as much as possible. You want CWs, I CW everything that might go on your nerves. Even though Mastodon-style CWs aren't part of the culture of Hubzilla where I reside. And I double my CWs with hashtags.
You want quality image descriptions, I write the longest, most detailed, most informative image descriptions in the whole Fediverse. You insist in there always being an image description in the alt-text, I write a
second image description in addition to the super-long one in the post and squeeze it into the alt-text.
So when wrote the start post I've linked above, I took a closer look at it to see what of it I can do to which extents. But it turned out I couldn't really do anything on it.
Point one: "Listen more to more Black people and amplify their voices"
Now you're wondering what my problem with this is. Why can't I just simply follow a couple more Black users and especially Black activists
For two reasons.
One, my channel specialises in two topics. The primary topic is OpenSim particularly and 3-D virtual worlds in general. The secondary topic is the Fediverse beyond Mastodon. This is not a personal, all-purpose outlet.
Two, I'm not on Mastodon. I'm on Hubzilla. It has a bunch of significant differences from Mastodon.
For example, on Mastodon, you go to your timeline, and you scroll down as far as you want to. Everything else you can safely ignore as if you've never received it. On Hubzilla, however, I have a counter of unread messages which unfolds to a list with links to all unread messages.
If I let all kinds of people pump posts that I'm not interested in within the scope of this channel onto my stream, it'll a) end up filled with hundreds upon hundreds upon hundreds of unread messages every morning, and b) most of it is completely uninteresting cruft.
I already have a problem with random Mastodon users who want to follow me. What they don't know is that Hubzilla mainly only knows mutual connections like Facebook friends. If I allow them to follow me, I must inevitably follow them back. So in order to keep them from spamming my stream, I don't allow them to send me their posts. I have a setting for that. Some 85% of my contacts are not allowed to send me posts.
For many of the remaining 15%, I have per-contact filters. These usually start with filter lines that remove boosts because some people boost like there's no tomorrow, and it's always uninteresting rubbish to me. Some even have filter lines beyond that to weed out more uninteresting cruft.
If I could, if Hubzilla's filters weren't too broken for that right now, I'd only let posts through which contain keywords that indicate that these posts contain something interesting for me.
Well, and now I shall follow people who have nothing interesting to say within the scope of this channel just because of the colour of their skin. And, of course, this means I must grant them permissions to send me
everything. I guess I'm not even allowed to filter their boosts out.
My refusal to allow magnitudes more messages to flood onto my stream, none of which are even remotely interesting to me within the scope of this channel, was called racist.Or point four: "Support Black people and Black-led instances and projects"
"Black-led instances". Sorry, but every last single one of them is on Mastodon.
Again, I'm not on Mastodon. I'm on something that's both older than Mastodon and vastly more powerful than Mastodon. I don't even like Mastodon. I
hate Mastodon and its "we rule supreme over the whole Fediverse, adapt to our will and our self-imposed limitations
OR ELSE" attitude.
The only way I'd ever support Mastodon is with bug reports on their GitHub repository when Mastodon causes trouble in connection with Hubzilla or (streams) again. But I will
never support a Mastodon
instance. I will
never support someone in using Mastodon.
This has nothing to do whether such an instance has a Black admin. It has
everything to do with it being Mastodon and with Mastodon being what it is.
Still, I was called a racist for refusing to support Black-led Mastodon instances.
I mean, I would like to help the Black community in the Fediverse. But I'd like to do it my way. And my way is to show them that the Fediverse is not only Mastodon. That Mastodon is not the be-all, end-all Fediverse project either. That there are places that are much safer than Mastodon
by design and by technology. Places which can empower people to protect themselves.
Guess what
This is actually racist several times over.First of all, I can't tell these people about the Fediverse outside Mastodon by sitting and waiting for them to address me directly in a DM. I can only tell them by discovering their threads and then joining these threads and replying.
Replying to someone who hasn't mentioned you first, and who isn't mutually connected to you.
On Hubzilla, this is absolutely, perfectly normal due to the way conversations work here. And Hubzilla has inherited it from Friendica which has introduced it as early as 2010. Five and a half years before Mastodon was launched.
On Mastodon, however, it's a deadly sin. It's reply-guying and mansplaining, completely regardless of what you actually have to say. It's so unimaginably reckless that if your "victim" is Black, you're clearly a racist.
But wait, there's more: By mentioning a non-Mastodon place in the Fediverse that these people have never heard of, I practically try to nudge them into this place.
Why that's bad
Because I practically try to nudge them into their own secluded space. Practically a
ghetto. I allegedly want to segregate them from the rest of the Fediverse that way, rather than letting them mingle with all other kinds of people on general-purpose Mastodon instances.
And that's every last bit as racist as separate seating in buses.
Lastly, my approach is wrong anyway. What Black people seem to need is not empowerment to defend themselves. It is for any and all racism and harassment to fully cease to exist
now, no matter where they are, so that there's nothing they'd have to defend themselves against anymore. That's the only goal
allowed to fight for.
Basically, I guess this post of mine has branded the entire non-Mastodon Fediverse one big homogenous racist hellhole even more than a bunch of openly, full-blown Nazi instances on Pleroma could ever have. The Black community will avoid it even more than they did until now.
And yes, I've also actually read that members of marginalised minorities refuse to check out the non-Mastodon parts of the Fediverse because they simply don't trust them.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Hubzilla #
Racist #
Racism There is no more and no less impersonation protection than within Mastodon and pre-nomadic ActivityPub. At least not from Mastodon's perspective.
After all, neither Zot nor Nomad nor the current development to introduce nomadic identity to ActivityPub is built against Mastodon in any way.
Mastodon was launched in 2016, ActivityPub was first used in 2017 and standardised in 2018. Zot was designed in 2011 and first implemented in 2012.
FEP-ef61 and Mike Macgirvin's project to add nomadic identity to ActivityPub are much more recent. But unlike many other things in the Fediverse, they were not designed with Mastodon in mind, especially not with Mastodon staying as it was at that time. Mike does not want Mastodon's proprietary, non-standard elements influence his development, and he does not want Mastodon's unwillingness to implement anything they haven't invented themselves weigh him down.
The goal of nomadic activity was simply to protect your online ID and your data from vanishing when your home server shuts down.
That said, if the whole Fediverse went fully nomadic one day, it would be senseless to claim that you're a clone of someone else's account or channel or whatever. That would obviously be fake. Clones can't act autonomously from their main instances and their other clones.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
ActivityPub #
Zot #
Nomad #
Mastodon #
Hubzilla #
Streams #
(streams) #
NomadicIdentityAMD punta al vertice dell'IA: maxi-acquisizione da 4,9 miliardi per ZT Systems
amd ZTSystems
Ich habe gelernt, da man, um wirklich inklusiv zu sein, alle Beschreibungen und Erklrungen fr einen Post bzw. ein Bild direkt vor Ort mit dem Post und dem Bild liefern mu.
Ich schreibe ja extrem lange Bildbeschreibungen. Ich beschreibe normalerweise jedes Bild zweimal. Einmal vergleichsweise kurz (oft immer noch deutlich ber 1000 Zeichen) und rein visuell im Alt-Text. Und vorher einmal sehr ausfhrlich und detailliert mit Erklrungen und Text-Transkripten im Post.
Ich habe ja kein 500-Zeichen-Limit. Ich habe gar kein Zeichenlimit fr Posts. Also packe ich auch schon mal fr ein einzelnes Bild in den Post, der auch das Bild enthlt.
Mich hat schon ein paarmal jemand gefragt: "Warum ldst du die lange Beschreibung nicht irgendwo gesondert hoch und verlinkst sie dann Dann sind deine Posts nicht so monstrs lang."
Weil, soweit ich das von anderen Quellen her beurteilen kann, die Beschreibung und Erklrung eines Bildes nicht irgendwo extern liegen und verlinkt sein sollte. Die sollte immer da sein, wo das Bild ist. Text-Transkripte sowieso. Und Text-Transkripte mssen bei mir in eine visuelle Beschreibung des Bildes eingebaut sein, damit die Leute auch wissen, wo der Text drauf ist, z. B. ein Schild, ein Poster, ein Teleporter oder dergleichen.
Das, was ich so gelernt habe, bertrage ich jetzt auf Meme-Posts.
Ich werde nur eine visuelle Beschreibung brauchen, weil ich da nicht so ins Detail gehen mssen werde, und die wird in den Alt-Text passen.
Aber ich mu ja das Meme auch erklren, damit die Leute das verstehen. Klar knnte ich die Leute auch mit Links abspeisen oder sie gar googlen lassen. Aber das wre nicht inklusiv. Inklusiv ist nur, wenn man alles direkt im Post erklrt.
Wenn ich jetzt also ein Bildmakro poste, auf dem Boromir "One does not simply implement FEP-ef61" sagt, habe ich sehr viel zu erklren.
Ich mu natrlich erklren, warum er das sagt und was er meint.
Dann mu ich das Template erklren. Das kennt ja nicht jeder.
Dann mu ich erklren, was ein Snowclone ist, weil ich in meiner Erklrung geschrieben habe, da das ein Snowclone ist.
Dann mu ich erklren, was ein Bildmakro ist, weil ich in meiner Erklrung geschrieben habe, da das ein Bildmakro ist.
Dann mu ich erklren, was ein Advice Animal ist, weil ich in meiner Erklrung geschrieben habe, da das Zge eines Advice Animal hat.
Dann mu ich erklren, was Something Awful ist, weil ich es in meinen Erklrungen zu Snowclones und Bildmakros erwhnt habe.
Dann mu ich erklren, was 4chan ist, weil ich es in meinen Erklrungen zu Bildmakros und Advice Animals erwhnt habe. Dazu mu auch eine Erklrung gehren, was Imageboards sind.
So, dann mu ich erklren, was FEP-ef61 ist. Dazu gehrt, da ich erklre, was nomadische Identitt ist, denn FEP-ef61 soll nomadische Identitt nach ActivityPub bringen.
Dann werde ich auch noch erklren mssen, was Hubzilla ist und was das streams-Repository ist, weil ich beide in meiner Erklrung von nomadischer Identitt erwhnt habe. Ich wei, da drei von vier Mastodon-Nutzern noch nie von Hubzilla gehrt haben.
Im Zuge dessen mu ich auch Friendica erklren und den ganzen Fork-Baum von Friendica bis Forte aufdrseln, um a) zu erklren, woher Hubzilla kommt, b) zu erklren, woher Red kommt, das ja als erstes nomadisch war, und c) zu erklren, woher das streams-Repository kommt.
Und das mu alles direkt im Meme-Post passieren. Das darf ich nicht extern verlinken. Klar knnte ich mir die Meme-Erklrerei sparen und einen einzelnen Link auf KnowYourMeme setzen, wie ich es frher getan habe. Das wrde Stand jetzt ber 11.000 Zeichen sparen. Aber das wre nicht inklusiv.
Die Leute ziehen es einfach vor, alle Beschreibungen und Erklrungen direkt vor Ort am Bild zu haben. Also sollen sie die bekommen. Du mut bedenken: Die meisten im Fediverse nutzen Smartphone-Apps. Wenn die einen externen Link antippen, geht auch noch der blde Browser auf, und sie mssen stndig zwischen zwei Apps hin- und herwechseln.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
Bildbeschreibung #
Bildbeschreibungen #
BiBesch #
BildbeschreibungenMeta #
CWBildbeschreibungenMetathats really vague.
It really isn't.
When you want to clone a channel, Hubzilla asks you for
- the ID of the channel
- the e-mail address that belongs to the account on which the main instance of the channel resides
- the password to the account on which the main instance of the channel resides
- whether you want to import objects and files
- whether you want to make the new instance of your channel the new main instance if not, it becomes a clone
- if you want or have to, a new internal ID for the clone on this hub, especially in case the short name of your channel is already occupied on this hub
So if someone wants to make a clone of your channel without your consent, they need the e-mail address and the password of whichever account you use to log onto the hub where your main instance resides.
But apart from you and maybe the hub admin if they're willing to dive into the underlying database,
nobody knows about the account that your channel is connected to.Hubzilla and (streams) channels give no hints about the underlying accounts. They don't give out e-mail addresses (look through and try to find my e-mail address good luck) or anything else that tells you about the account underneath.
The account is not part of your nomadic identity. The domain of the server that hosts the main instance of your channel is. But the account is not. Identity-wise, the channel is fully independent from any one account.
Even if you have multiple channels on the same account, nobody except a hub admin willing to manually dig through the database can tell that they're on the same account and belonging to the same user unless the user explicitly tells them.
Cloning someone else's channel requires extortion or otherwise theft of login information and credentials. There's no other way to even find out
the account underneath a channel.
Never forget that channels aren't accounts. They don't have logins, and they don't have passwords.
I can imagine an oauth-like interaction with an existing clone to create the relationship, but that only addresses that pair of instances, not how the rest of the network sees the change.
Again, this would require channels to have login credentials. And it would require a clone to be a dumb copy of some sort for at least a while. It would require a clone to be its own entity.
But a clone is not its own entity. Within the network, a clone
is the original, only elsewhere, with the exact same ID as the original. The clone only has its own URL, but its ID is the same as that of the original. The Zot6 and Nomad protocols see a main instance plus no matter how many clones as one entity. And ActivityPub with nomadic identity will do the same.
I can imagine requiring mutual follows
Within a purely nomadic ecosystem, this doesn't work either. Reasons see above.
Hubzilla and (streams) channels, both nomadic by means of Zot6 and Nomad respectively, cannot connect to the main instance of my channel on hub.netzgemeinde.eu and my clone on hub.hubzilla.de separately. For them, there's only one actor,
jupiterrowlandhub.netzgemeinde.eu
. The main instance is
jupiterrowlandhub.netzgemeinde.eu
, and the clone is
jupiterrowlandhub.netzgemeinde.eu
just the same.
jupiterrowlandhub.netzgemeinde.eu
cannot follow
jupiterrowlandhub.netzgemeinde.eu
.
And again, none of this is new. This hasn't only been invented recently. Nomadic identity as provided by the Zot protocol has gone live on Red in 2012, almost four years before Mastodon was launched, five years before Hubzilla became the first Fediverse project to adopt ActivityPub, six years before ActivityPub was standardised.
What's new is only the implementation in ActivityPub of something that has been done for a dozen years already, three quarters of the lifetime of the Fediverse.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Hubzilla #
Streams #
(streams) #
NomadicIdentity To probably not exactly few on Mastodon, if someone replies to them who isn't mutually connected to them, and whom they haven't mentioned earlier in the same thread, it's reply-guying, mansplaining and out-right, full-blown harassment.
No matter if this behaviour has been totally normal in the Fediverse outside of Mastodon since at least 2010. For comparison, Mastodon is from 2016.
No matter how many people would still think the Fediverse = Mastodon if nobody from outside Mastodon had ever done this to tell them otherwise.
I'm seriously, the only reason why there isn't a huge outcry and a massive campaign to try and have everything that isn't Mastodon Fediblocked from Mastodon is because every other Mastodon user doesn't even know that there's anything else than Mastodon in the Fediverse, and most of the rest don't know what "disturbing", non-Mastodon-like things the non-Mastodon Fediverse is capable of doing.
And to everyone who thinks they can pressure the non-Mastodon Fediverse into abandoning its own cultures and adopting Mastodon's post-Twitter takeover culture, along with also abandoning all the features they have which Mastodon doesn't, I have a bridge to sell.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
FediblockMeta #
NotOnlyMastodon #
FediverseIsNotMastodon #
MastodonIsNotTheFediverse #
ReplyGuy #
ReplyGuys #
Mansplaining #
Harassment Motorbiking Hokkaido! Beautiful Water & Jumping Fishies! Motorbiking Hokkaido! Beautiful Water & Jumping Fishies
I'm working on a new meme-posting format.
I haven't posted a meme with an image since around the turn of the year, and a lot has happened since then. The reason why I've stopped posting meme images is because I decided to no longer post images with potential triggers such as eyes or faces in plain sight, but for Mastodon users, Hubzilla leaves me no choice but to post images in plain sight. Unless I want to make them go through the extra hassle, click/tap a link and open the image separately. I can post meme images now I've got two (streams) channels for that, and (streams) can make Mastodon blank out sensitive images.
Over the past eight years, however, I've improved my image-describing technique some further and raised my own standards. For example, I've learned that memes need to be explained so that everyone gets them. At the same time, I'm aware that externally linked sources of information are not inclusive, only providing all needed information right with the image is.
Just like with my virtual world pictures, I have to explain absolutely everything that I can't assume to be common knowledge. And this can actually end up being even more than when I post a virtual world picture. I guess I don't have to go all the way and explain the whole history of everything and give examples at the same level as KnowYourMeme. But I can't link to any external sources either. I've already mentioned that everything must be explained in the same place as the image. Besides, KnowYourMeme as a Web site isn't as reliable as I remember it anymore.
So on the one hand, I don't have to go through the entire history of the "One Does Not Simply Walk Into Mordor" meme. On the other hand, in order for people to understand the explanation of this meme, I also have to explain what a snowclone is. And I have to explain what an image macro is. And I have to explain what an advice animal meme is. And I have to explain what Something Awful is so that people understand my snowclone and image macro explanation digressions. And I have to explain what 4chan is and what imageboards are so that people understand my image macro and advice animal explanation digressions.
So my first new meme post with an image will come with...
- a explanation of the template
- a digression with an explanation of snowclones
- a digression with an explanation of image macros
- a digression with an explanation of advice animals
- a digression with an explanation of Something Awful
- a digression with an explanation of 4chan
- an explanation of this particular image macro
- a digression with an explanation of nomadic identity and its history
...in the post text body, right below the embedded in-line image.
All in all, I expect the explanations to have some 15,000 characters.
Since the image macro is based on what's essentially a real-life photograph, and the explanations are not tied to any visual description of the image in the post, I'll probably only need one image description in the alt-text. And it'll probably be short enough to leave room for the text transcripts and the note that there is an explanation in the post. In fact, I only have one template based on OpenSim in-world pictures, and these are fairly simple.
The first new meme image post will take especially long because I have to write all explanations from scratch. Later meme posts will save time because I can at least copy-paste the necessary but already available digressions, and eventually, I guess I won't have to write new meme digressions anymore. When I re-use a template I've used before, I can re-use its entire template explanation as well, and I'll "only" have to explain the context.
The context explanation will always require quite some work and some time, though, regardless of whether I meme OpenSim or the Fediverse. I can never expect everyone who comes across one of my meme posts to be well-informed enough about the Fediverse to get the joke. As for OpenSim, I can hardly ever expect
anyone to know what I'm meming about.
I hope to be able to copy-paste a lot of context explanations later as well, but I can't count on that.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
OpenSim #
OpenSimulator #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta #
Memes First of all, nomadic identity via ActivityPub is still quite experimental and only implemented on (streams) and Mitra. Just because ActivityPub has it, doesn't mean Mastodon has it. This also means that I don't know what nomadic identity would look like, should Mastodon actually implement it.
So I'm going to explain this not using Mastodon as an example where your account is your identity with everything in it.
Instead, I'm going to explain it using Hubzilla and (streams) which have it implemented and in daily use right now, but where your identity is in a container called a "channel", and your account is only necessary to log onto a server and access your channel(s).
whats a clone here
A clone is a 1:1, absolutely identical, real-time, bi-directional, live, hot backup of your channel (= your identity container).
With nomadic identity, your channel has always got exactly one main instance and any number of clones from zero to as many as you can find servers to clone to.
A clone contains everything that your channel contains:
- all your posts
- all your comments
- all your DMs
- all posts, comments and DMs that you have received
- all your contacts (Hubzilla and (streams) work like Facebook and not like Twitter contacts are generally mutual this means that, yes, your followers are mirrored)
- all your settings
- all your files (yes, they have file storages this is optional on Hubzilla)
- Hubzilla-exclusive stuff like articles, wikis or Web pages
- etc.
Whatever happens on the main instance of your channel, is automatically mirrored to all clones.
In fact, you can use your clones just like you can use your main instance. Whatever happens on one clone, is automatically mirrored to the main instance and all other clones.
If one instance goes down and comes back up, it's automatically sync'd with the others. Regardless of whether it's the main instance or a clone.
What the ID of a clone is depends on what looks at it.
For example, I've got my main instance on hub.netzgemeinde.eu and a clone on hub.hubzilla.de.
The ID of my main instance is
jupiterrowlandhub.netzgemeinde.eu
.
As for my clone, if something that understands nomadic identity (Hubzilla, (streams)) looks at the clone, the ID it sees is still
jupiterrowlandhub.netzgemeinde.eu
. It's one and the same channel, one and the same Fediverse identity.
If Mastodon or anything else that doesn't understand nomadic identity looks at it, the ID is
jupiterrowlandhub.hubzilla.de
. Mastodon takes my clone for a wholly separate account.
That said, there will be one limitation in nomadic identity via ActivityPub: The syncing between instances of an identity will not happen in near-real-time. It will probably be triggered by a timer at certain rates, e.g. once every couple of minutes or so.
How do they get created
It's important to know that a new Hubzilla or (streams) channel doesn't immediately start out with clones. Your new channel always starts with only one instance when you create it, the main instance which also lends its domain to your ID. You have to create all clones yourself, manually.
First of all, you need an account on another server. If you don't have one on the server to where you want to clone, you create it.
Mind you, creating an account doesn't work like on Mastodon. On Hubzilla and (streams), an account is
not an identity. It's just a login that grants you access to that server. (That is, I think Hubzilla requires you to create one new channel because a Hubzilla account can't exist without at least one channel.)
Then you can clone an existing channel. You've got two options for that.
Either you clone the channel across the network. Then the target server will download that channel with everything in it. On Hubzilla, taking files with you is optional.
Or you clone by creating backup files of your channel where it currently resizes and then uploading them on the server that you want to clone your channel to. Hubzilla and (streams) will know that this is not a dumb copy, but a clone of a live channel, and automatically create a link.
Once the clone is there, it will be kept in sync with the main instance and, if you have any, all other clones.
What happens to all of these clones when mastodon.social disappears
Okay, let's go with Mastodon.
First, you log into an instance where you have a clone. You still have that clone, and the clones still sync with each other if you have multiple ones.
Let's assume you have a clone on mas.to. So you log into mas.to.
Then you go to where your clones are managed.
There, you select your clone on mas.to to be your new main instance.
One of the first things that happen will be that your Fediverse ID will change from
ShadSterlingmastodon.social
to
ShadSterlingmas.to
, on your mas.to instance which you have just changed from a clone to your main instance as well as on all your other clones.
Then mas.to will go through all your followers and followed. Check whether they're on something that understands nomadic identity. If so, it will automagically re-write their following and/or being-followed connection from
ShadSterlingmastodon.social
to
ShadSterlingmas.to
.
You've read that right. mas.to will go manipulate stuff on other, remote Mastodon servers. This is how Hubzilla does it, this is how (streams) does it, this is how it has been done since Red in 2012. It's normal.
As for non-nomadic instances, I guess it'd depend on how Mastodon implements nomadic identity. They can't be remote-manipulated.
One issue on Mastodon is the Twitter-style dichotomy of followers and followed. Mastodon could send new follow requests to all your non-nomadic followed connections. But it obviously can't send new "follow me" requests to all your followers on non-nomadic instances because Mastodon doesn't have "follow me" requests.
Nomadic identity was designed against the same bidirectional concept as Facebook friends. Only after 12 years of successful operation with bidirectional connections, there may come a situation in which it will have to work with the same unidirectional concept as Twitter followers and followed which it has never been designed before.
If mastodon.social were to become a Nazi bar can I rename myself so I dont look like a Nazi
See above. You simply take one of your clones and switch it to your main instance. Your ID will change accordingly.
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Hubzilla #
Streams #
(streams) #
NomadicIdentity Ich glaube ja, die werden hier auf Granitkeks beien.
Erstens sind Fediverse-Nutzer noch weniger bereit, Geld fr ihr Social Networking in die Hand zu nehmen, als die Nutzer amerikanischer oder chinesischer Silos.
Zweitens sind die ganzen Famehuren doch eh in den Silos, weil da die Famehurerei viel besser geht.
Drittens, wenn ein Mastodon-Account, der gerade mal ein paar Wochen alt ist, schon mehr Follower hat als Rochko und Takei zusammengenommen und jeder, aber auch jeder Post binnen Minuten tausende Faves hat, dann kann da was nicht stimmen. So jemand hat binnen krzester Zeit
nur noch knstliche Follower. Plus ein paar doofe Newbies.
Viertens lebt das Fediverse im Gegensatz zum Vogelkfig nicht davon, wieviele Follower man hat, sondern von der Interaktion mit den Followern. Und zwar mit echten Menschen und nicht mit KIs. Die kann man nicht erkaufen, vor allem nicht in solchen Mengen.
Und fnftens dienen massenhafte knstliche Follower und Likes vor allem dazu, die Algorithmen auszutricksen. Solche Algorithmen gibt's hier aber an den meisten Orten nicht und auf Mastodon definitiv nicht. Wer abertausende Euronen in Fake-Follower und -Likes investiert, um den Mastodon-Algorithmus zu manipulieren, kann das Geld auch durch den Lokus jagen.
Vor allem, wenn sich drittens und fnftens als Erkenntnisse herumsprechen, will keiner mehr Geld ausgeben fr Fake-Follower und -Likes im Fediverse, und das Geschft lohnt sich nicht mehr.
Das knnte sich aber alles ndern, wenn Rochko viel Geld dafr geboten wird, einen entsprechenden Algorithmus in Mastodon einzubauen und den entweder als "cooles neues Feature" zu verkaufen oder ganz einfach zu verschweigen.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
FakeFollowers I'm not speaking only for myself. I'm speaking for non-Mastodon Fediverse users all over the place from Pleroma to Iceshrimp to Friendica to Hubzilla.
If you're on something that's sufficiently not Hubzilla, and you've got connections to Mastodon in some way, chances are you've had run-ins with Mastodon users who neither know nor care that the Fediverse extends beyond Mastodon.
Mastodon users who want to force e.g. Friendica users to fully adopt Mastodon's culture and throw away Friendica's culture which includes abstaining from using any Friendica features that Mastodon doesn't have. Just like European settlers forcing natives to forget their own native cultures and adopt European culture and convert to Catholic Christianity instead.
Mastodon users who, upon discovering there are non-Mastodon places in the Fediverse, want to make the whole Fediverse only Mastodon, not by defederating from non-Mastodon instances, but by nagging and forcing everything that isn't Mastodon to mutate into Mastodon itself.
Mastodon users for whom only Mastodon and the way Mastodon does things (or whether it does things at all) is the one and only Fediverse gold standard, and everything that deviates from this gold standard is broken and wrong and must be corrected, by force if necessary.
I know I'm not the only one who has ever experienced such people. I know a (streams) forum that actually has intentionally turned ActivityPub off, and I know that this kind of Mastodon users is the reason.
I myself will leave ActivityPub on.
I was only giving some food for thought.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Mastodon #
FediverseFood for thought: Maybe the Fediverse should actually split.
Leave Mastodon to its own devices. Leave them the term "Fediverse". Let Mastodon "be the Fediverse". Let "the Fediverse" and "the Mastodon network" be all the same. Just what absolutely every last newbie who came over from the Birdsite thought is the case. Just what many Mastodon users still think is the case. And exactly what not exactly few Mastodon users want the Fediverse to be.
Let Mastodon's many proprietary, non-standard, Mastodon-only solutions work perfectly with no interference from outside.
And leave Mastodon to be EEE'd by Threads.
Everything else could throw out all Mastodon-specific kluges and hacks and finally concentrate on pure standard ActivityPub plus FEPs. It could make full use of object types, regardless of how Mastodon renders them. It could introduce nomadic identity via ActivityPub without constantly having to check how well it works with Mastodon. It could implement a standard permissions system with no regard for how it'll work with Mastodon. For Mastodon will never implement anything they can't claim having invented themselves.
It could assume the name "Social Web" in the place of "Fediverse".
Its users could finally live the cultures of wherever they are and make use of the features available to them. They would longer have to deal with Mastodon users who try hard to force them to adopt the Mastodon culture and throw away the culture and most of the features of their home.
It could become acceptable for Social Web projects to introduce by-server-type filters and use them to block Mastodon as a whole. This could keep out the invaders who try to enforce their own foreign culture.
Such a step would also show which Fediverse projects are actually independent and which ones are nothing but add-ons bolted onto Mastodon. Because they will have to choose a side.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Mastodon #
Fediverse #
SocialWeb What will
actually happen once is rolled out across the whole Fediverse is:
Your Fediverse ID will remain
ShadSterlingmastodon.social
, that is, if the main instance of your identity remains on mastodon.social.
You can have a clone on mastodon.online. But since it's a clone, its Fediverse ID is still
ShadSterlingmastodon.social
. It is not a separate entity with a separate ID. It's the exact same thing.
You can have another clone on mas.to. Again, its Fediverse ID is
ShadSterlingmastodon.social
.
You can have a clone on, for example, (streams) although (streams) is drastically different from Mastodon. You can have it on rumbly.net. Even the Fediverse ID of this clone is
ShadSterlingmastodon.social
.
Across your main instance and all your clones, it will have one and only one ID, no matter where a clone may be.
It's hard to understand from a Mastodon/non-nomadic "instance login/account = identity" point of view, I know. And I feel it's easier to explain how it works on Hubzilla and (streams) where your identity does not reside directly in the account, but in a container referred to as "channel" to which the account only provides login access. It's this container which nomadic identity clones and syncs between servers.
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Hubzilla #
Streams #
(streams) #
NomadicIdentity We need to get to identities that aren't tethered to particular instances. Various approaches have been discussed, all more or less valid IMHO, we just need to get them implemented.
We have had one working implementation for 13 years now. In the Fediverse. In stuff that's federated with Mastodon.
Mike Macgirvin , creator of (2010), creator of Hubzilla (2015), creator and maintainer of (2021) and, most recently, creator and maintainer of (all four are being actively maintained, part of the Fediverse and federated with Mastodon), invented the concept of in 2011.
The same year, he implemented it in his own Zot protocol. Zot came to use first in 2012 in a Friendica fork named Red, later the Red Matrix, which became Hubzilla in 2015. Hubzilla still uses the latest stable version of the Zot protocol that's still called Zot. Everything that Mike did since 2012, with the exception of the first Osada from 2018, featured nomadic identity, including (streams) which is based on an "offspring" of Zot called Nomad.
I'm writing to you from a Hubzilla channel that simultaneously resides on two server instances. Not in the shape of a dumb copy, but in the shape of a real-time, bidirectional, live, hot backup.
It's basically what Bluesky has claimed to be a revolutionary new and never-done-before feature in the AT protocol, only that a) it's even more advanced, b) it's older than Bluesky, c) it has been proven to actually work in daily use, and d) it
is in daily use.
Right now, Mike is working on implementing nomadic identity using only ActivityPub, specifically . Even this has advanced beyond theoretical. (streams) has it implemented already. All channels created on accounts that were registered on versions 24.07.20 and newer are made compatible with nomadic ActivityPub. I have two such channels, although neither has a clone yet.
In fact, it could be that at least Forte, which is in a very early stage right now, will have Nomad and maybe even support for Zot6 removed and go nomadic using only ActivityPub. Mike said he wants to sunset Nomad and Zot6 once nomadic identity via ActivityPub is ready for prime time.
is working closely together with Mike to implement nomadic identity via ActivityPub on . It has taken the switch to nomadic ActivityPub itself.
Just because Mastodon doesn't have it, doesn't mean it doesn't exist.
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Mitra #
Hubzilla #
Streams #
(streams) #
Forte #
FEPef61 #
NomadicIdentity The problem with this is that any given image would not necessarily
always get
the exact same alt-text.
The alt-text, or generally the image description, depends not only on the image, but also on
- the context (what is essential within the context, what is important, what isn't)
- the audience (what does the audience need to know to get the image, what does the audience already know, what may the audience want to know about the image, what is the audience likely not to care about)
So when you post the exact same image twice in two different contexts to two different audiences, you are likely to have to supply two very different image descriptions.
#
Long #
LongPost #
CWLong #
CWLongPost #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta Ideally, an instance picker would help pick a
project along with the instance.
But what we have right now seems to be
- either "Choose a project, then we'll go from there"
- or railroading to Mastodon because only Mastodon instances can be recommended
Just about everyone who has joined the Fediverse in the last two years was railroaded to Mastodon and not being told what the Fediverse
actually is. Some of them it took months to learn that there's stuff in the Fediverse that's connected to Mastodon but so very much
not Mastodon itself. And when they learned it, some of them were shocked out of their minds. Others still don't know, sometimes after well over a year.
It cannot continue this way. We must no longer sweep everything under the rug that doesn't have an Inc. and a CEO.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
NotOnlyMastodon #
FediverseIsNotMastodon #
MastodonIsNotTheFediverse Keep in mind that hashtags can be and
are used to trigger filters as well.
And where I am (Hubzilla), we've been using keywords or hashtags to automatically generate CWs since before Mastodon was even made. Depending on how much sensitive or potentially disturbing content there is in a post, it may need a lot of hashtags.
Notice the hashtags at the bottom of this comment that start with "CW".
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Hashtag #
Hashtags #
HashtagMeta #
CWHashtagMetaIt feels to me like a good portion of debate on M. about features is motivated at least partly by diverging views on the value of reach, and people may associate moving to less well-known fediverse projects with decreasing reach
The trouble with moving is that it'll reset your reach to zero. But it always does, regardless of whether you move to another Mastodon instance or something as obscure and not like Mastodon as (streams).
You can re-follow those whom you already follow. You may even be able to import your list of followed actors so you don't have to do that manually. But until nomadic identity becomes available all over the Fediverse, you can't take your followers with you. That'd require remotely and forcibly re-writing their following connections to your new home.
It's true as well that it depends on how busy the place is where you end up how quickly you build up a solid followership. If you want Mastodon followers, you have to make yourself known on Mastodon. But if you
aren't on Mastodon, your posts won't end up on any local Mastodon timeline yet.
Then you only have three options. One, refollow those whom you have followed on Mastodon, maybe also follow new Mastodon users, and hope they'll follow you back. Two, wait for someone who follows you to repeat/repost/renote any of your posts to their own Mastodon connections and then for someone on Mastodon to find one of these posts and decide to follow you. Three, use the search to manually import Mastodon posts and reply to them. Gives you quick exposure, but let's face it, it's a dirty trick and on the verge of reply-guying.
Also, your move is likely to attract a new audience. This may or may not be pleasant. So after you've moved to Friendica, you won't have hundreds of Mastodon followers within no time. Instead, you'll have three or four Friendica connections who'll judge you by how you use Friendica as if it's Mastodon or even Twitter.
AFAIK, Friendica, like its descendants Hubzilla and (streams), at least has a nice feature that not only suggests new contacts to you, Facebook-style, but also suggests you to others as a new contact if you want to. But for one, Friendica doesn't suggest you to Mastodon users, of course. And besides, this feature is usually only used by newbies who are desperate for new contacts. It's uninteresting for established users who already have dozens or hundreds of contacts.
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMetawhy the hell would anyone not include colour in descriptions
Because blind people can't see them, and that information is useless to them, yada yada.
I say to Aira agents, they are humans btw, who write the alt text descriptions for my photos to include everything they can see to the finest detail. there is a character limit, but use it to its max. I am looking at AI generated descriptions too, just for comparison. if a sighted person can see it, a blind person should be able to read about it.
And if a sighted person may feel like wandering around the image and go exploring in it rather than focusing on whatever may be important within some context, then a blind person should be able to do the very same, aided by a sufficiently detailed image description.
This is the very reason why I generally describe my images
twice: What they show are worlds completely unknown to almost everyone in the Fediverse. Thus, sighted people may take closer looks at the images and their details, that is, as far as the fairly low resolution allows them.
A sufficiently detailed description for my own images does not nearly fit into the 1,500-character limit imposed by Mastodon, Misskey and their forks upon essentially the whole Fediverse because they chop longer alt-texts off.
So I write one long, detailed image description with all necessary explanations and all text transcripts. It goes into the post text body because it's
magnitudes longer than 1,500 characters. I don't have any character limit to worry about.
In addition, I write another, shorter, purely visual image description which, along with the note where to find the long description, fills the alt-text up to almost or exactly 1,500 characters.
Maybe, if my experiments are successful, I'll be able to get away with only one image description for memes. That's because an established image macro doesn't require nearly as extensive a visual description, and I can explain it without having to describe visuals along with the explanation.
As for colours, I say they
must be mentioned, but they must be described using a few basic colours plus brightness plus saturation. Even if it makes sense to name the colour, it must be described this way afterwards.
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMeta That's it exactly. Most of the time, when people say they want "the Fediverse" to develop into a certain direction, they mean they want Mastodon to develop into a certain direction. When people say they want certain features "in the Fediverse", what they mean is they want them on Mastodon.
This can have three causes.
One, some people simply think the Fediverse is only Mastodon. My estimation is that this still applies to at least every other Mastodon user. They wouldn't take into consideration moving somewhere that has what they're looking for because the very thought of there being something else in the Fediverse than Mastodon is utterly unimaginable to them.
Two, another group knows that the Fediverse is more than Mastodon. But at most, they've heard some names of other Fediverse projects, Pixelfed, PeerTube, maybe Misskey. What these other projects can do, however, beyond Pixelfed being Instagram in the Fediverse and PeerTube being YouTube in the Fediverse, they have no idea. So they still ask for features for "the Fediverse" of which they don't know that the Fediverse already has them, only Mastodon doesn't.
Three, the rest actually wants these features
all over the whole Fediverse. Or at least right underneath their feet. They may be well-educated about the Fediverse to even know what Hubzilla is capable of. But they hold on to the Mastodon instance they call home for their dear lives. They don't want to move for whichever reason. Instead, they want the features they ask for
on their home instance. On by default for their convenience even.
One reason why people are often unwilling to move even if they have heard that there are greener pastures out there is the difficulty of moving. They need easy-peasy moving between projects with
everything, but at most, they can move between Mastodon instances with some of their stuff, and even that is a hassle. Fediverse-wide, ActivityPub-based nomadic identity is at its earliest stages of development, and even when it's ready for prime time someday, the projects will still have to adopt it.
The other major reason is the mobile app ecosystem. The vast majority of Mastodon users is on phones and on dedicated Mastodon apps. It feels like next to nobody on Mastodon ever uses a Web browser. So before they move someplace else, they ask if there's an app.
But often enough, there is none. There are gajillions of iOS apps and even a bunch of Android apps built against Mastodon and Mastodon only with no support for anything else. If you're lucky, something else that has the Mastodon API implemented can connect to one of these apps, but then you only have Mastodon's feature set, and you can't use the cool extra features for which you've moved to your new home.
I think Fedilab is the sole exception that has support for other projects with the Mastodon API built in, but even that is limited in features by the UI. And Fedilab is Android-only. So if you're on an iPhone, I think all you can really sensibly use through an app is Mastodon plus a couple very specialised projects. As for everything else ranging from Mastodon's own forks to Pleroma and its forks to Misskey and its forks to Friendica, you don't have much of a choice beyond Safari or a third-party Web browser.
It's especially the iPhone users whom you won't get to move to e.g. Friendica until the first stable release of Relatica has hit the Apple App Store. And as for Friendica's descendants, they
actually leave you no choice but to use them as PWAs through the Web interface or directly in the browser.
And truth be told, there are actually some Mastodon users who don't move anywhere that doesn't have an official app with the same name as the project. They can't imagine using Iceshrimp without first loading an app named "Iceshrimp" from the App Store.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta If I had any way to add another click-to-open level that works on Mastodon as well without mobile users having to deal with their Web browser popping open, I would.
Things would be way easier if sensitive Mastodon users got used to the concept of filters, though, and learned how to set them up. That's one reason for my many hashtags.
But it's strange to see someone from chaos.social irritated by
too many CWs.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Mastodon #
CW #
CWs #
CWMeta #
ContentWarning #
ContentWarnings #
ContentWarningMetaSo I've just learned the other day that curating your timeline/stream according to your personal interests and/or the topic of your account/channel is utterly racist. No matter how specialised your account/channel is.
Everyone in the Fediverse is basically
required to follow a substantial amount of Black users, especially Black activists. If you're on Hubzilla or (streams),
you must actually follow them, i.e. you must give them full permissions to send you anything and everything unhindered and unlimited. You must
not use account/channel-wide or per-contact filters on them. Even if each one of them boosts 100 posts per day, you must
not filter or disallow their boosts.
Also, if you're on Friendica, Hubzilla or (streams), all of which count and list unread messages, you must
not simply mark what has come in from them as read. You must read it all and be interested in it all. This includes all comments on these posts. And yes, you must re-read everything whenever it tries to catch your attention again, e.g. if someone has liked/faved or boosted/reposted/renoted/repeated it.
But even if you receive thousands of comments along with those hundreds of extra posts,
you must not comment on these comments. Not unless either a comment mentions you explicitly, or you're mutually connected to whoever wrote the comment. As you wouldn't even receive that comment on Mastodon, replying to it counts as reply-guying and mansplaining on Mastodon, completely regardless of
how you comment. It's highly disrespectful, and if Black people are involved, it's racist.
It doesn't matter if this has allegedly been perfectly normal, the standard and part of the culture since five and a half years before Mastodon was launched. Mastodon rules supreme over the whole Fediverse, and only Mastodon's culture has any validity anywhere in the Fediverse. Any culture that differs from Mastodon's is toxic and evil and must be abolished.
Speaking of which, let's suppose you come across one of these many threads in which Black Mastodon users talk with other Black Mastodon users and Mastodon-using allies about how the Fediverse needs to be made safer. In this case, no matter how blatantly obvious it is that all people involved in this thread have no idea of the Fediverse outside Mastodon, you are
not allowed to chime in and tell them about places which are safer due to their technological design and how they work.
First of all, it'd be mansplaining and reply-guying. Second, there's a tendency for Black Mastodon users to trust the rest of the Fediverse even less than Mastodon, what with e.g. Nazi instances on Pleroma. And third, your suggestion is likely to be taken for an attempt at nudging them into moving to one specific place, essentially trying to hoard them in a ghetto and segregate them from the rest of the Fediverse. In short, there's letting them wait for the Mastodon instances they're on to improve, and there's racism.
While we're at it: Even if you're on Friendica, Hubzilla or (streams), and you hate Mastodon with a burning passion for very good reasons, you must support Black-led Mastodon instances. Otherwise you're a racist.
Lastly, while I don't have proof for it, I'm pretty sure that everything that counts as racism towards Black users may also count as
- racist towards everyone else who isn't white
- sexist towards everyone who isn't cis-male
- homophobic towards everyone who isn't heterosexual
- transphobic towards trans people
- generally queerphobic towards everyone who isn't cisgender
- ableist towards disabled people, no matter what else you do to include them
- Islamophobic towards Muslims
- anti-Semitic/anti-Judaist towards Jews
- and generally hostile and xenophobic towards all marginalised minorities anywhere in the Fediverse.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
Friendica #
Hubzilla #
Streams #
(streams) #
FediverseSafety #
Mansplaining #
ReplyGuy #
ReplyGuys #
Racist #
Racism #
Sexist #
Sexism #
Homophobic #
Homophobia #
Transphobic #
Transphobia #
Queerphobic #
Queerphobia #
Ableist #
Ableism #
Islamophobic #
Islamophobia #
AntiSemitic #
AntiSemitism #
Xenophobic #
Xenophobia Das ist doch in den kommerziellen Silos wie Facebook und vllig normal, da Paare einen gemeinsamen Account haben. "Hach ja, wir machen
alles gemeinsam, und wir haben
keine Geheimnisse voreinander." Man spricht sich sogar ab, wem man folgt. Eine gemeinsame E-Mail-Adresse haben die beiden auch.
Das gibt's stndig, auch wenn die Weitergabe von Login-Daten eigentlich meistens gegen die Nutzungsregeln verstt. Aber wenn es keine deutschsprachigen Moderatoren gibt, merken die Fremdsprachler das nicht.
Manchmal glaube ich, das Ganze sieht dann in der Praxis so aus, da
sie bestimmt, was auf dem Account luft, derweil
er nur dabei ist, um einerseits den Account zu administrieren und sich um die Technik zu kmmern, und andererseits, damit sie seine ganze Kommunikation ausschnorcheln kann.
Auf WhatsApp sind sie nur deshalb getrennt, weil sie kein gemeinsames Handy und keine gemeinsame Handynummer haben und WhatsApp auch brauchen, um miteinander zu kommunizieren. Aber sie hat natrlich auch die PIN seines Smartphone und manchmal auch ihm die PIN ihres Smartphone gegeben. Und auf dem gemeinsamen Windows-Laptop gibt's ja eh nur das eine Admin-Konto.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost Na ja, Bluesky hat ja vier Vorteile.
Erstens ist es wirklich ein Beinahe-1:1-Klon von Pr-Musk-Twitter bis hin zur offiziellen Fully-Featured-App. Die Leute suchen ja auf der Flucht vor Musk nichts vllig anderes, wie uns die Erfahrung vom November 2022 gelehrt hat, sondern Twitter ohne Musk.
Zweitens ist es einfacher zu handhaben, weil es trotz aller Ankndigungen bis heute ein zentralistischer, monolithischer Silo ist. Man braucht kein Instanz auszuwhlen und sich keinen Kopf um Dezentralitt machen.
Drittens hat es als kommerzielle Plattform ein Werbebudget.
Und viertens drfte auch die Presse es prferieren, weil es ja so viel einfacher ist.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
BlueskyIch bin gerade dabei, die Hilfe fr die Fediverse-Software #
hubzilla neu zu schreiben. Nun sind die geplanten Kapitel vorerst "fertiggestellt". Aber sind sie das wirklich
Ich habe mich benht, die einzelnen Beitrge nglichst so zu formulieren und Dinge so zu erklren, dass auch Menschen ohne Erfahrung mit Hubzilla hoffentlich verstehen, wie was funktioniert.
Nur... ich nutze Hubzilla seit 2016... ohne Unterbrechung. Fr mich sind viele Dinge also selbstverstndlich. Obwohl ich mich bemht habe, zu vermeiden, solche "Selbstverstndlichkeiten fr mich" nicht auch auf den unbedarften Nutzer zu bertragen, bin ich mir sicher, dass ich an der einen oder anderen Stelle durch die Brille eines langjhrigen Hubzilla-Nutzers geblickt habe und manches womglich doch nicht so leicht verstndlich ist.
Deshalb brauche ich dringend "Hilfe bei der Hilfe". Von Helfern, die nicht mit Hubzilla vetraut sind... aber auch von Helfern, welche das System schon kennen, aber womglich daran gescheitert sind oder es aufgegeben haben, weil die Hilfe schlicht nicht ausreichend war. Und natrlich auch von Hubzilla-Spezialisten.
Ich habe die Hilfe zunchst in meiner Muttersprache, also in Deutsch, geschrieben. Sobald diese in einem guten Zustand (fr Hilfesuchende) ist, wird sie auch ins Englische bersetzt. Ich richte mich hier also zunchst berwiegend an deutschsprachige "potenzielle Helfer".
Auerdem bitte ich zu beachten: Es handelt sich um ein Hilfesystem fr eine Software, die fr die Teilnahme am Fediverse genutzt werden kann und soll. Wie soziale Netzwerke funktionieren, wozu sie dienen, wird darin nicht erklrt. Ich setze voraus, dass jemand, der solch einen Account und einen Kanal bei Hubzilla erstellen mchte, wei, wie social Networking funktioniert, wofr man es nutzen kann und was das Fediverse ist. Erfahrungen mit anderen Fediverse-Diensten, wie z.B. #
mastodon, #
pleroma, #
misskey oder einem #
forkey, #
friendica etc. sind also kein Hinderungsgrund, die Hilfe zu beurteilen, sondern durchaus auch von Vorteil.
Nun ist das Hilfesystem von Hubzilla eine Sache fr sich, was die technische Umsetzung betrifft. Weil ich weder an meinem Produktivsystem etwas ndern wollte und auch noch nicht bereit bin, meine Arbeit direkt in das Software-Repository von Hubzilla einzubauen (dafr msste die detsche Hilfe erstmal soweit, dass sie passt, und dann mindestens auch die englische Version fertiggestellt sein). Auerdem habe ich fr die Erstellung ein von mir geschtztes System (mdBook) verwendet, weil es mir in erster Linie um Struktur und Inhalt ging und man nderungen unmittelbar begutachten kann.
Damit nun Interessierte die Hilfe in der Praxis nutzen und testen knnen, habe ich das "Handbuch" auf eine eigene Domain hochgeladen, von wo aus sie fr jeden aufruf- und nutzbar ist:
Meine Bitte nun: Knnten sich mglichst viele das Hifesstem anschauen Nutzer von Hubzilla sind willkommen, Nutzer andere Fediverse-Dienste sind aber genau so willkommen. Wer mag, kann das Hilfesystem auch nutzen, es einfach mal mit Hubzilla zu probieren. Hubzilla-Instanzen (Hubs) zu finden, ist nicht schwer:
https://hubzilla.fediverse.observer/ . Wer mag, kann sich z.B. einen Account bei meinem frei zugnglichen Hub "Klackernet" (
https://klacker.org) erstellen.
Und wenn's gar nicht passt oder das Experiment beendet werden soll, ist ein Account auch rasch rckstandslos gelscht (steht auch in meinem Handbuch ).
Und dann bitte Rckmeldungen, Kritik, Wnsche... entweder im Fediverse als Direktnachricht an mich, als ffentliches Posting, in welchem ich getaggt werde (pepecybhub.hubzilla.hu), in meinem Forum "Pepes Hubzilla-Sprechstunde" (hubzillasprechstundehub.hubzilla.hu) oder via Matrix (. oder, wenn's unbedingt sein muss, auch per Mail (pepecybpepecyb.hu).
Bitte diesen Beitrag teilen, weitersagen, boosten, wie auch immer, so dass die Chance besteht, dass sich vielleicht zwei, drei Hand voll Nutzer die Hilfe anschauen.
#
Long #
LongPost #
CWLong #
CWLongPost Makes me wonder how Zot6 and Nomad would fit in there.
Notes: Zot6 is the newest stable version of the Zot protocol and 's main protocol. Hubzilla also optionally supports ActivityPub, and thus it's part of the Fediverse. Both Zot and Hubzilla are older than both Mastodon and ActivityPub.
Nomad is a descendant of Zot, and it's still the main protocol used by the nameless, brandless software in , itself a descendant of Hubzilla with optional, but on-by-default ActivityPub support.
Both protocols support . This means you can clone your identity with all content, all connections, all settings etc. etc. onto other instances. A clone is not a dumb copy. It's a real-time, omnidirectional, live, hot backup, and you can "move instances" by declaring any of your clones your main, and you can use any of your clones like your main anytime.
So the order would have to be NomadZot6 / Nostr / ATproto / ActivityPub.
And once the development of nomadic identity on ActivityPub using (the streams repository is the main testbed) is completed, ActivityPub will overtake both Nostr and ATproto and, as its nomadicity will not stop at project borders, probably also Zot6 and Nomad.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Hubzilla #
Streams #
(streams) #
Protocol #
Protocols #
ActivityPub #
FEPef61 #
NomadicIdentity #
Zot #
Zot6 #
Nomad #
ATproto #
Nostr Noch ein Problem dabei: Wenn die meisten Mastodon-Nutzer vom "Fediverse" reden, meinen sie Mastodon.
Von den Leuten, die unbedingt ganz viel mehr Leute und Institutionen usw. ins Fediverse holen wollen, sind 99,99% nur auf Mastodon. 98% von denen kennen auch nur Mastodon.
Und mindestens 50% von denen sind der felsenfesten berzeugung, "Fediverse" und "Mastodon" sind eh Synonyme, weil das Fediverse ja das Mastodon-Netzwerk ist. Die wissen berhaupt nicht, da es noch was anderes im Fediverse gibt als Mastodon. Die ahnen es nicht mal. Es ist fr sie unvorstellbar.
Das fhrt dann dazu, da nicht nur jeder, der neu ins Fediverse gelockt wird, direktweg auf Mastodon landet, egal, was sie vorher gemacht haben, sondern da auch keiner von denen erfhrt, wie gro das Fediverse wirklich ist.
Die ersten zwei Monate wissen sie nicht mal wirklich, da das Fediverse dezentral ist. Sie glauben, mastodon.social, oder wo auch immer sie gelandet sind, ist "die Internetseite vom Fediverse", also "
das Fediverse".
Und frhestens nach fnf Monaten, hufig eher nach einem Jahr, wenn berhaupt, stoen sie erstmals darauf, da das Fediverse nicht nur Mastodon ist. Erst ist das fr sie komplett unvorstellbar. Wenn bei ihnen dann aber der Groschen fllt, kacken sie vor Schreck darber Ziegelsteine.
Vorher wiederum fhren sie sich natrlich selbst entsprechend auf und behandeln "Mastodon" und "Fediverse" als exakt deckungsgleich und gleichbedeutend. Und selbst wenn sie gelernt haben, da das Fediverse mehr ist als nur Mastodon, glauben sie immer noch, alles, was nicht Mastodon ist, ist schlimmstenfalls eine Alternativ-App fr Mastodon, d. h. Friendica hat denselben Stellenwert wie Mona oder Tusky, nur eben als Webfrontend. Bestenfalls sehen sie das tatschlich als eigene Projekte, aber sie glauben, die sind alle nachtrglich an Mastodon angeschraubt worden, weil Mastodon ja zuerst da war, weil das ja gar nicht anders sein kann.
CC:
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
NichtNurMastodonPeople with drug addictions living in B.C. long-term care homes raises red flags
The number of people suffering acute brain injury due to drug use that are being housed in residential care homes has risen, and this is a cause for concern in smaller facilities.
-termcarehome -termCare
Bernie Sanders:
America Must Confront Its
People with drug addictions living in B.C. long-term care homes raises red flags
The number of people suffering acute brain injury due to drug use that are being housed in residential care homes has risen, and this is a cause for concern in smaller facilities.
-termcarehome -termCare
People with drug addictions living in B.C. long-term care homes raises red flags
The number of people suffering acute brain injury due to drug use that are being housed in residential care homes has risen, and this is a cause for concern in smaller facilities.
-termcarehome -termCare
People with drug addictions living in B.C. long-term care homes raises red flags
The number of people suffering acute brain injury due to drug use that are being housed in residential care homes has risen, and this is a cause for concern in smaller facilities.
-termcarehome -termCare