and at 62.

Probably mainly those whom Mastodon shits on by

ignoring existing standards
re-inventing stuff that already exists in the Fediverse, but re-inventing it in an incompatible way to what already exists
forcing its own ways upon them, no matter how much different they are from Mastodon, no matter if they've been in the Fediverse before Mastodon
at the same time, making everyone on Mastodon believe that Mastodon is either the one and only Fediverse gold standard or the Fediverse proper
thus fostering a culture that's built around Mastodon, but that forces itself upon the whole Fediverse to the point of trying to displace existing, differing cultures in other places

Just go ask anyone on Friendica or Hubzilla or (streams). Especially the guy who created all three and still maintains and advances the latter, Mike Macgirvin .
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon Und wenn man die in seinen eigenen Posts alle mit abzudecken versucht, regen sich die Leute darber auf, da man zuviele Hashtags (= mehr als vier) verwendet.
Ich kenne das. Mehr als die Hlfte der Hashtags, die ich verwende, dient auch oder ausschlielich dazu, Filter auszulsen, denn solche Filter, die sogar CWs erzeugen, sind da, wo ich bin, schon ewig Teil der Kultur. Nur hufen die sich dann eben.
Und dann springen nicht nur die im Dreieck, die im Kopf immer noch auf Twitter sind, sondern auch die, die partout keine Posts mit ber 500 Zeichen lesen wollen. Nur sorgen bei mir schon mal die Hashtags fr berlnge und noch einmal, je nach Sprache, 36 oder 62 Zeichen mehr fr vier oder sechs Extra-Hashtags wegen berlnge.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Filter #FiltersSo I've run until yesterday. The question was whether the Fediverse has quote-posts.
20 users voted for yes, 8 users voted for no.
Of course, this poll wasn't representative. I dare say my "bubble" is more Fediverse-savvy than the average, and I know I had quite a number of voters from Hubzilla and (streams). So the result is greatly skewed towards "yes". And still, 40% of all voters thought the Fediverse had no quote-posts.
This shows how well especially Mastodon users know the Fediverse.
Oh, and by the way: The Fediverse does have quote-posts. Just about everything that isn't Mastodon can quote-post, and it all can even quote-post Mastodon toots with next to zero resistance. And in fact, quote-posts in the Fediverse are about six years older than Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares

This is hypothetical, as you cannot say what is safe or not for people like me.

Okay, basic question: What is your idea of safety

And I did not say Mastodon was the safest. What I did say is that I understand why people are hesitant to explore the larger fedi.

That's because a common implication towards members of minorities who have fled from Twitter to Mastodon is that everything that isn't Mastodon is potentially chock-full of racist, sexist, homophobic, transphobic, fascist subhumans who are just waiting for their next victim. And Mastodon is the only place guaranteed to be safe for them.
I mean, it's understandable. I guess what they're looking for primarily is a place where there simply is nobody who'd harass them. Guaranteed.
Mastodon appears to be just that to them, what with how welcoming it is in general, and how the vast majority of users is very left-wing. At the same time, they know exactly zilch about the rest of the Fediverse, maybe except a few names they happen to catch. So they don't know if it's safe.
Well, and if someone like me comes along and throws into the room the fact that just about everything in the Fediverse that isn't Mastodon has quote-posts built in, it doesn't exactly make the rest of the Fediverse look sympathetic, now, does it After all, they associate quote-posts with harassment. So what motivation would a Fediverse project have to implement them, seeing as Mastodon has so staunchly refused to do so until recently

I'm open to whatever, but your anger towards Mastodon is of no interest to me as I have no loyalty to it.

So it's a purely pragmatic approach because Mastodon is what your target audience is used to, and you simply don't want them to re-learn everything again
Maybe in combination with taking Mastodon away from the GmbH, the Inc., the self-imposed "this is what microblogging is" restrictions and the "we are the Fediverse" attitude For this part sounds sympathetic if it's done right.
See, I'm looking at the Fediverse differently from most other Fediverse users. I'm looking at it from a mostly technological point of view. Also, my first contact with the Fediverse was not Mastodon. It was Friendika before it was renamed, and that was in 2011. So my experiences are different, especially technological experiences.
When I'm looking for solutions for Fediverse problems, it's only natural that I look beyond Mastodon first and foremost.
And seeing how Mastodon treats the rest of the Fediverse, especially the projects from the years before Mastodon's own launch, I can impossibly not be biased.

And that's a poor way of showing how your part of the fedi is allegedly safer.

Well, I could rattle down the permission settings available on Hubzilla, including which options you have, and then tell you that (streams) goes even beyond that. But I guess that isn't what you want to read either.
If you're looking for a social or cultural solution, I'm not the one to discuss that with.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta And parts of the Fediverse are actually safer than Mastodon or any Mastodon hard-fork could ever hope to be.
That's not because they're devoid of white cishet males, but that's because they've got advanced anti-harassment, anti-stalking, anti-just-about-everything-unpleasant countermeasures that have been developed, advanced, evolved for longer than Mastodon itself, and that go way beyond not only what Mastodon has now, but even what minorities want to have on Mastodon.
Again: Follow Mike Macgirvin . Read what he has to say.
Yes, he's a privileged white cishet male living in a fairly wealthy country with a Western culture. But he's the only one who is working on actually making the Fediverse safer. And he has been successfully doing that since when Eugen Rochko was still a school kid. This guy has been developing software since before Rochko was even born. So I guess it's pretty safe to assume that he is competent and experienced, and he knows what he's doing.
Yes, he holds a grudge against Mastodon. But he also points out that, no, Mastodon is not the safest possible place in the Fediverse.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMetaErschwerend kommt dann ja immer noch dazu, da viele eben nur Mastodon kennen, inklusive smtlicher Techmedien. Auenstehende haben hufig zwar schon von Mastodon gehrt, aber noch nie vom Fediverse, und ansonsten glaubt man vielfach, Mastodon und Fediverse seien ein und dasselbe, 100% deckungsgleich, Threads vielleicht ausgenommen.
Wenn Mastodon jetzt enshittifiziert wird, auch weil in der amerikanischen Mastodon, Inc. ein KI-Datensammler-Shill und eine VC-Heuschrecke sitzen, wo sollen die Leute dann hingehen Threads und Bluesky sind ja noch schlimmer, sowieso.
Klar, du und ich, wir knnten beide stapelweise Alternativen herunterrattern, die allesamt im Fediverse und miteinander und mit Mastodon verbunden sind, und die praktisch durchweg Features haben, von denen man auf Mastodon nur trumt. Teilweise auch Features, die das Vorstellungsvermgen der meisten Mastodon-Nutzer komplett berflgeln. Und viele deiner Kontakte knnten das wahrscheinlich auch.
Aber ich schtze inzwischen, mindestens die Hlfte der Mastodon-Nutzer wei bis heute nicht einmal, da es berhaupt noch etwas anderes im Fediverse gibt als Mastodon. Oder da es berhaupt noch andere dezentrale, unkommerzielle soziale Netzwerke bzw. Microblogging-Projekte gibt. Geschweige denn welche es gibt.
Fr viele ist der Ausweg entweder, zu etwas anderem Kommerziellen zu wechseln, oder soziale Netzwerke ganz zu verlassen. Oder sie ertragen weiterhin zhneknirschend Mastodon, weil's dazu ja keine Alternativen gibt.
Andere scheinen darber nachzudenken, ganz neue Projekte zu starten. Erst gestern lief mir der Post von jemandem ber den Weg, der sich einlesen will ins Thema ActivityPub, vor allem, wie Mastodon es implementiert hat, weil er sein eigenes mastodonartiges Projekt starten will.
Als gbe es so etwas noch nicht.
Und was aktuell ein Riesenthema ist, wenn man dem englischsprachigen Fediverse-Flurfunk folgt: Hard Forks von Mastodon. Also Mastodon, aber es ist nicht von der Mastodon (g)GmbH.
Auch hier fragt man sich: wozu Es gibt tonnenweise Zeugs im Fediverse, das nicht Mastodon ist, nie Mastodon war und besser ist als Mastodon. Aber es gibt eben leider Leute, die knnen nicht ohne Mastodon-UI und Mastodon-UX.
Der Optimist in mir sieht in solchen Hard Forks die Mglichkeit, Mastodon ohne Rochkos Walled-Garden-Politik weiterzuentwickeln und an den Rest des Fediverse anzunhern, statt sich weiterhin oder gar noch mehr dagegen einzumauern. Es gibt zumindest einen Hard-Fork-Untersttzer, der schon fast berall im Fediverse war und ist, von daher ist das nicht ganz unwahrscheinlich.
Aber es gibt auch die, die einfach nur ein Mastodon haben wollen, das nicht mehr unter der Kontrolle der GmbH und der Mastodon, Inc. steht und ein paar Extrafeatures eingebaut bekommt, die die Community haben will. Bei denen wird dann mitunter klar, da ihnen der ganze Rest des Fediverse ziemlich egal ist oder sie gar mit dem Rest des Fediverse nichts zu tun haben wollen.
Am Ende wird es noch mehr Mastodon-Forks geben als jetzt schon. Und wahrscheinlich wird ein einziger Fork, der auf den Rest des Fediverse zugeht, um die Gunst der Mastodon-Nutzer buhlen mit einem ganzen Haufen Forks, die auf den Rest des Fediverse "literarisch keinen Fick geben".
Aber sich dann wundern, wenn Leute auerhalb von Mastodon ein Problem mit Mastodon zu haben scheinen.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Fork #HardFork

Ha, well don't you have a lot to say

Greetings from a project from before Mastodon that has never had any character limits and thus doesn't have character limits in its culture.

You seem to have a grudge against Mastodon

This isn't too atypical in my corner of the Fediverse. It comes from Mastodon not only deliberately limiting itself, but deliberately and apparently intentionally making itself incompatible to the rest of the Fediverse. It even makes its users believe first that Rochko invented the Fediverse, and Mastodon is either the Fediverse proper or the one and only Fediverse standard.
But if there's someone who really holds a grudge, it's Mike. , for example. And I can understand him.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon My first thoughts when I read about the hard-fork plans were just this. If you want stuff in the Fediverse that Mastodon doesn't have, why not use something that already has that stuff After all, my most popular post by far was about just this.
But by reading how and explained their motivation, it looks like this won't be another "Mastodon + xyz" project by people who don't know the Fediverse beyond Mastodon. I mean, tallship is on Hubzilla himself. is on Misskey as well. He's on almost everything.
If anything, it's likely that a hard fork will do away with lock-in measures and open what's essentially Mastodon up to the rest of the Fediverse. The idea is to have something that looks like Mastodon and feels like Mastodon and maybe even has Mastodon in its name, but without Mastodon's product politics and without Mastodon's "We're the Fediverse, full stop" attitude.
As first steps, I've already proposed an indicator for the instance type a post came from (Friendica has it, and I think at least one *key has it) and built-in migration on at least Sharkey's level to facilitate moving away from the original woolly mammoth.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Fork

as a writer, i take microblogging seriously. so when this became an issue here, i decided to honor the request.
it doesn't feel natural at all. there are times too much is going on in an image that i feel like am cheating by not including it all.

I'm in a similar situation, I think.
If I post images, they're either renderings from 3-D virtual worlds or memes about said 3-D virtual worlds. Either way, they're about a very very obscure niche topic that probably not even one in 10,000 Fediverse users knows something about.
When you describe real-world photographs, you can skip a whole lot of details and explanations because you can safely assume that a) people are generally familiar with them and b) they're so mundane that nobody cares anyway.
When I describe pictures from super-obscure virtual worlds, I can't assume either. Nobody is familiar with anything in them. Besides, 3-D virtual worlds are still a novelty that's likely to catch people's interest to such degrees that they might want to know everything about them. So a whole lot of describing and explaining is necessary.
What refers to as...

A few extra seconds of your time

...always ends up many hours of research and writing. The three longest times I've taken to describe one particular image were , and , and I still find the last one lacking and the former two outdated by my current standards.
This does not mean that I don't describe my images anymore. But I have to plan image posts days or even weeks in advance, and then I have to find motives that won't take me too long to describe and that I can describe in sufficient detail in the first place.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta The only way in which Mastodon is "forward-thinking" is in how to a) cosy up to even bigger players, b) railroad all Fediverse newbies not only onto Mastodon, but into the official silo and making it hard to escape from it and c) hide the rest of the Fediverse from Mastodon users' eyes or, if that fails, make it look bad and broken to them.
Otherwise, Mastodon is the most lack-lustre, underwhelming and actually out-dated of all Fediverse projects. The only reason why it's so "popular" is because 99.9% of all Fediverse newbies and at least 50% of all no-longer-newbie Mastodon users don't know that there's anything else in the Fediverse, much less what this "anything else" has to offer. Oh, and because it's so hard to move away from it unless you want to start from scratch.
and are already proposing a hard fork whose goal it is to pry Mastodon and its users away from Rochko's attempts at building a new walled garden.
So two things I suggest a hard fork like Awujo to have are:

an indicator that shows which instance type a post came from this stops the belief that the Fediverse is only Mastodon
migration on Sharkey's level this makes it easy to migrate from mastodon.social and other vanilla Mastodon instances to Awujo at the same time, make sure that it's easy enough to move away from Awujo

These should be basics.
Another thing that has just come to my mind: Implement full HTML rendering for posts so that Awujo can even display elaborate blog posts in all their glory, arbitrary number of embedded images and all. And then stop reducing Article-type objects to links. This is something that Rochko staunchly refuses to add, one of the major reasons why Friendica and Hubzilla creator and (streams) maintainer Mike Macgirvin and current Hubzilla maintainer Mario Vavti, as well as the Hubzilla and (streams) user communities, are so disgruntled about Mastodon.
Speaking of Mike Macgirvin: Follow him. Follow closely what he's working on. As said above, he is the creator and maintainer of which has 14 years of work behind it. And he is currently working on stuff that could revolutionise the whole Fediverse: nomadic identity based only on ActivityPub without having to resort to Zot or Nomad, nomadic identity across different Fediverse projects, (streams)-level permission control for ActivityPub.
The latter would provide the "better safety tools" on a level unknown to the Fediverse unless you know Hubzilla or (streams). The former two would make the dream of one identity across Fediverse projects come true and make it resilient against instance shutdowns.
Both, all by themselves, are concepts that have been implemented some four years before Mastodon was launched. What's new is only that they're being ported to ActivityPub, having required different protocols until now.
Of course, from a developer's POV, the easiest way would be to hard-fork Mastodon into nothing more than an alternative UI theme for (streams) and, ideally, write a new doc for (streams) itself once its current backend redesign is done. But even if Mastodon's UI is kept unchanged as much as possible, the backend would work so radically differently from Mastodon that the whole UX would confuse the hell out of those who thought that the Fediverse is only Mastodon and only Twitter-style microblogging ten minutes earlier.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Fork So that's the intention.
I mean, most Mastodon forks that exist today really seem to have been created for one out of two reasons.
Either someone thought the Fediverse is only Mastodon, but wanted some new features, so they also thought that the only way to get these features into the Fediverse was by forking Mastodon and adding them to the fork.
Or someone wanted to offer features only available outside Mastodon to users who absolutely have to use Mastodon for some reason.
What you're suggesting is a variation of the latter. And that's to offer people a better Mastodon than the "official" one. One that isn't controlled by Rochko and the Mastodon gGmbH.
Ideally even one that opens itself to the rest of the Fediverse instead of locking it out. One that adds features which go beyond the standard fare (over 500 characters, markdown), features that official Mastodon refuses to have for political reasons. Once Mike Macgirvin has completed his work on implementing cross-project nomadic identity and (streams)-level permissions with nothing but ActivityPub, it could include these, too.
At the very least, for starters, your fork should offer migration on Sharkey's level and show what instance type a post came from. This would really open it to the rest of the Fediverse. With these two features, people could come over from mastodon.social with ease, discover that the Fediverse has so much more to offer than Mastodon and move on to something that has never been Mastodon in the first place. So it should be positioned as competition for Mastodon, but not as competition for everything else out there (*omas, *keys, Mike's creations etc.).
Still, the problem will be to get people to use it. Rochko does everything in his power to make sure that 99.9% of all Fediverse newbies are railroaded into his wannabe monolithic silo, that it takes them as long as possible to learn that Mastodon is decentralised and that it's as difficult as possible for them to leave again, at least without starting over from scratch.
After all, the vast majority of newbies think Mastodon is Twitter without Musk, but otherwise the same. So they start like they started on Twitter, namely by installing the eponymous app on their phones. And that app is controlled by Rochko and designed to maximise the railroading to his silo.
Thus, you'll need four things. One, the hard fork. Two, a bunch of general-purpose instances that run it. Three, a mobile app that has "Mastodon" in its name, that goes along with the fork, that supports as many features which the fork has that Mastodon doesn't as possible. And four, a whole lot of publicity targeted at those who think the Fediverse is only Mastodon as well as those who have heard of Mastodon but not the Fediverse.
As for vanilla Mastodon users, keep your eyes open for those who want Mastodon to have certain features. If you have them, and you'll be likely to have them, tell them that your fork is "Mastodon, but with that feature you want". Let them discover the other goodies once they've moved. Only tell them about the other features if they aren't easily convinced to move over.
Unfortunately, you won't win those over for whom vanilla Mastodon is the be-all, end-all of social networking, those who want vanilla Mastodon's set of features to be the one and only Fediverse standard and everything that goes beyond it to be banned.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Fork

and at 62.

The two were the first known conjoined to as different , according to .They were initially expected to only a year but had and .

The complete lack of an official (streams) website is intentional, seeing as (streams) also lacks a name and a brand identity just as intentionally. But yes, it's unfortunate, just as unfortunate as its total lack of documentation.
(streams) can be run on Yunohost, and this is constantly improving as several instances are actually running on Yunohost. However, the only way to find this out is word-of-mouth.
If someone else wants to try it, there's an official support group: Streams. It should be possible to use it from just about anywhere in the Fediverse.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Streams #(streams) If these communities cling to something, I'd say it isn't so much the UI/UX as it's the instances. After all, they've moved away from Twitter before.
The main resistance is in moving to another instance, whatever that instance runs. Granted, a secondary issue is compatibility with mobile apps made for Mastodon. And I don't see (streams) introduce the Mastodon API anytime soon, seeing as (streams) is deliberately moving away from Mastodon-specific code.
That said, if these communities aren't willing to move, if a hard fork of Mastodon is the solution, then part of the solution has to be replacing the vanilla Mastodon on which their instances is based with the hard fork. If such a community is residing on a big general-purpose instance, I can't see this happen.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Streams #(streams)

The only 3 social media that are currently surviving as Twitter alternatives are Bluesky, Mastodon and Threads.

GNU social
Pleroma
Akkoma
Misskey
Firefish
Iceshrimp
Sharkey
Catodon
Meisskey
Tanukey
Just to name a few
They're all part of the Fediverse. They're all connected to Mastodon. And they're micro-blogging projects, just like Mastodon.
Mastodon is not the Fediverse. The Fediverse is not only Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #GNUsocial #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Firefish #Iceshrimp #Sharkey #Catodon #Meisskey #Tanukey #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse

thing is though there are also many existing alternatives to Mastodon already on the Fediverse, so why fork it

Because you still don't know there's more to the Fediverse than Mastodon. I think at least every other Mastodon user doesn't.
Or if you do, you think it's all just alternative graphical frontends to the same stuff that Mastodon is.
That's why people still develop stuff only against Mastodon. Bonus points for slapping "Fediverse" on it.
That's why people still fork Mastodon to add features that are available just about everywhere else.
And that's probably why wants to fork Mastodon into what he seems to think will be the absolute pinnacle of privacy, security and permission control in the Fediverse, blissfully unaware that it's not only an attempt at re-inventing the wheel, but a far cry from what Mike Macgirvin has been developing since 2012. That was four years before Mastodon.
Seriously, I keep seeing people wish for features in "the Fediverse" (read, Mastodon), features that are readily available elsewhere in the Fediverse. Some of them have been since before Mastodon was even made.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse And why fork Mastodon, the most lack-lustre, underwhelming, underequipped and out-dated of all Fediverse projects, if the Fediverse already offers what you're looking for
Because it does.
Imagine something that gives you the power to adjust things like

who can see your posts
who can send you their posts
who can see your profile
who can see your connections
who can comment on or fave your posts
who can send you DMs (yes, this is a separate setting)
who can quote or boost your posts
and many more

Now imagine these permissions can be given to, depending on the setting, seven or eight different subsets of users, including but not limited to:

only yourself
only your own confirmed connections (yes, their logins will be recognised)
only those of your connections whom you explicitly grant that permission by adding them to a privacy group which grants that permission

It gets even better: If something is not allowed, it isn't just deleted from your timeline. It is rejected at server level.
Mind-blowing Maybe.
Utter science-fiction No. Fediverse reality since 2012, almost four years longer than Mastodon has existed.
Okay, let me add some more stuff on top.
How about a character limit of not 500, not a few thousand, but infinite
How about the option of
Now this has to be a fever dream, right
Nope. Reality since 2012 when Mike Macgirvin , already creator of the Facebook alternative , started developing more and more advanced and powerful Fediverse server applications, from 2013's Red Matrix to 2015's (which still exists, which I'm using) to 2018's Zap and finally to the most recent and most advanced incarnation, established in October, 2021 and still advancing ever since.

Whatever you may want to add to Mastodon, (streams) very likely already has it implemented right now.
Whatever marginalised, harassed groups may wish the Fediverse to have, (streams) very likely already has it implemented right now. Plus stuff they wouldn't even dare to dream of.
It has been developed, improved and advanced for 14 years, longer than any other Fediverse project, by someone who, in these 16 years, created three Fediverse protocols and about a dozen Fediverse projects, every last one of them vastly more powerful than Mastodon or any of its forks would ever dare to be.
I'll let Mike speak for himself:

A brief overview of the streams repository.

The streams repository is a fediverse server with a long history. It began in 2010 as a decentralised Facebook alternative called Mistpark. It has gone through a number of twists and turns in its long journey of providing federated communications. The fediverse servers Friendica and Hubzilla are early branches of this repository.
The first thing to be aware of when discussing the streams repository is that it has no brand or brand identity. None. The name is the name of a code repository. Hence "the streams repository". It isn't a product. It's just a collection of code which implements a fediverse server that does some really cool stuff. There is no flagship instance. There is no mascot. In fact all brand information has been removed. You are free to release it under your own brand. Whatever you decide to call your instance of the software is the only brand you'll see. The software is in the public domain to the extent permissable by law.  There is no license.
If you look for the streams repository in a list of popular fediverse servers, you won't find it. We're not big on tracking and other spyware. Nobody knows how many instances there are or how many Monthly Active Users there are. These things are probably important to corporations considering takeover targets. They aren't so important to people sharing things with friends and family.
Due to its origins as a Facebook alternative, the software has a completely different focus than those fediverse projects modelled after Twitter/X. Everything is built around the use of permissions and the resulting online safety that permissions-based systems provide. Comment controls are built-in. Uploaded media and document libraries are built-in and media access can be restricted with fine-grained permissions - as can your posts. Groups are built-in. "Circles" are built-in. Events are built-in. Search and search permissions Yup. Built-in also. It's based on Opensearch. You can even search from your browser and find anything you have permission to search for.  Spam is practically non-existent. Online harrassment and abuse are likewise almost non-existent. Moderation is a built-in capability. If you're not sure about a new contact, set them to moderated, and you'll have a chance to approve all of their comments to your posts before those comments are shared with your true friends and family. For many fediverse projects, the only way to control this kind of abusive behaviour is through blocking individuals or entire websites. The streams repository offers this ability as well. You'll just find that you hardly ever need to use it.
Because federated social media is a different model of communications based on decentralisation, cross-domain single sign-on is also built-in. All of the streams instances interact cooperatively to provide what looks like one huge instance to anybody using it - even though it consists of hundreds of instances of all sizes.
Nomadic identity is built-in. You can clone your identity to another instance and we will keep them in sync to the best of our ability. If one server goes down, no big deal. Use the other. If it comes back up again, you can go back. If it stays down forever, no big deal. All of your friends and all your content are available on any of your cloned instances.  So are your photos and videos, and so are your permission settings. If you made a video of the kids to share with grandma (and nobody else), grandma can still see the video no matter what instance she accesses it from. Nobody else can.
Choose from our library of custom filters and algorithms if you need better control of the stuff that lands in your stream. By default, your conversations are restricted to your friends and are not public. You can change this if you want, but this is the most sensible default for a safe online experience.
There are no inherent limits to the length of posts or the number of photos/videos you can attach or really any limits at all. You can just share stuff without concerning yourself with any of these arbitrary limitations.
Need an app Just visit a website running the streams repository code and and install it from your browser.
Nobody is trying to sell you this software or aggressively convince you to use it. What we're trying to do is show you through our own actions and example that there are more sensible ways to create federated social networks than what you've probably experienced.
You can find us at
A support group is provided at
Have a wonderful day.
Here is what we've created:
Conversations: communicate directly with the people in the conversation, not have completely isolated conversations with your followers and their followers shouting at each other -- and neither audience seeing the responses of the others.
Permissions: If you haven't been given permission to speak, you aren't part of the conversation.  If you have not been granted permission to view a photo or video, you won't see it.
Audience: Your choices go far beyond public and not public. Yes, we have groups. We also have circles. You can also just select a dozen people right now and have a conversation only with them.
Nomadic identity, amalgamated identities and single sign-on: Site and project/product boundaries don't exist. It's one big space and you are you - no matter what service or services you use.
Post limits, photo limits, poll limits: None.
Rich content: Use markdown, bbcode, or HTML. Any of them or all of them.
Rules: You make them.
Algorithms: You can install them if you want. You can remove them. You control them and can tweak them.
And much more.
We are the streams repository.

So why does it absolutely have to be Mastodon if the Fediverse has something so much better to offer, readily available in a stable release right now
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #FediverseSafety #Permission #Permissions #NomadicIdentity #Streams #(streams)

Whether this is actually true or not, I do not know.

It's true. Mastodon reduces Article-type objects to the title, if there is any, the summary, if there is any, and a link to the original page. It's intentional and by design.
Hubzilla managed to prove it with the 9.0 release several weeks ago. Up until then, Hubzilla posts went out as Note-type objects. The 9.0 release introduced a switch for the entire channel that defaulted to sending Article-type objects and could be switched back to Note-type objects. And all of a sudden, anything that came from Hubzilla was rendered as described above. The Hubzilla community had largely all but forgotten about it. A hotfix disabled the switch and hotwired Hubzilla to Note-type objects until 9.0.1 removed it again.
The actual reason of this behaviour is because Article-type objects tend to be blog posts with all bells and whistles. Text formatting, headlines, horizontal rules and, most importantly, an arbitrary number of images embedded anywhere within the post.
Mastodon, however, is so "original gangsta purist microblogging" that it refused to support any of this up until version 4.0. And even since version 4.0, it can only render the former two.
In other words, if Mastodon tried to render a blog post as-is, it'd fail miserably and botch it big time. Like, rip four of the embedded images out of their embedding, leave them dangling below the post, and throw all images that go beyond these four away altogether because Mastodon can't handle more than four images.
And this mangled rendering of the blog post would literally be the only way that most Mastodon users would experience the post. There wouldn't be a big button that'd take them to the source. There's a button, but stashed away in a pop-up menu that isn't labelled as containing such a button.
The next-best alternative would have been for Mastodon to include full support for everything that can be done with Markdown or HTML or Friendica/Hubzilla's expanded BBcode. But, again, that wouldn't be purist microblogging. That'd be un-Mastodon-like.
So the only alternative left was to not render the post at all and link to the original instead.
The Hubzilla community is fully convinced that Mastodon took this step to flip the bird at Hubzilla.
In order to understand this idea, there are a few things to understand. First: When Mastodon was launched, it immediately federated with Hubzilla which had already been there. Both communicated via OpenMicroBlog, the predecessor of OStatus.
Next: Hubzilla was the first Fediverse project to implement ActivityPub in July, 2017, when it wasn't even a W3C standard yet. Mastodon was the second, some two months later. For quite a while, it was just these two.
Finally: We all know how limited Mastodon is. Hubzilla, on the other hand, had inherited its text formatting capabilities from Friendica, and they're immense. If you can do it in a blog post, you can do it in a Hubzilla post.
Only that Mastodon couldn't render any of it.
AFAIK, Hubzilla kept asking Mastodon to implement full HTML rendering for posts so it'd stop mangling posts from Hubzilla and Friendica. Mastodon staunchly refused because that'd go too far beyond purist microblogging and Twitter-mimicking. Same reasoning as for hard-coding the 500-character limit.
Eventually, Mastodon introduced this switch plus the specific handling for Article-type objects. But instead of being a special mode that does have full HTML rendering capabilities as demanded by Hubzilla, it just creates a link to the original.
For Mastodon, it's keepin' it real and sticking to purist microblogging. For Hubzilla, it's a way to spite them and their silly text formatting and image embedding antics. Hubzilla still holds a grudge against Mastodon for this.

But that ought to change. The question is how, but this WG is not at the point where we start throwing around decrees and making up standards.

The only way for this to change is if you went to Mastodon's GitHub repository and filed an issue which labels this behaviour as a bug. And if as many other Fediverse projects as possible joined in on the same issue. And if the pressure on Mastodon became so big that they cave in and introduce all rendering capabilities necessary to show a long-form blog post the way it's supposed to look.
Again, Hubzilla has tried it which led to the creation of this phenomenon. Others have tried it, too. And I'm not even sure if a vast alliance of Fediverse devs could change it.
After all, Mastodon is in such a position that it doesn't even have to act. It presents itself to the majority of Fediverse users as the one and only fully-featured Fediverse standard and implies that everything that deviates from it is broken.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #ActivityPub

I Like Trains. Absolutely stunning work from best doggo!

Clover (+):
Delta ():
Xhhy: ():
Wooby ():
Doodzie ():

And while Richard MacManus is fantasising over it, Mike Macgirvin is working on literally exactly this right now. The guy who made that still blows Mastodon out of the water, and he did so years before Mastodon.
He invented , one identity on multiple instances of the same Fediverse project, in 2011. He made it reality in 2012. He rolled out the first stable release supporting nomadic identity in 2013. For reference: Mastodon is from 2016.
What Tim Berners-Lee is doing with Solid is nothing else than re-inventing Mike's wheels. Deliberately. And implementing ugly kluges that Mike has never needed.
And now Mike is working on stretching nomadic identity across instance types. And making it work with nothing but ActivityPub and technology he had invented himself years ago. No Solid involved.
Again, he is not fantasising. He is actually working on it, as in he's making progress.
Money quote-posts:
Everything you thought you knew about identity on the fediverse just changed. I'm serious as a heart attack. There's nothing you can do about it except learn how to deal with it. Who are you really It's not at all who you think you are.
In other news, everything you thought you knew about the streams repository also just changed.
What's the streams repository A fediverse server that most of you have never heard of, but it doesn't matter because we've been rocking the fediverse since Eugen was in high school popping zits.
These two events are totally unrelated. Just a coincidence really.
I'll tell you all about it once I assemble everything I know into a long blog post (most likely one for each).
At the moment I'm tying up a few loose ends and then it's off to Bluesfest. Back in a few days.

Mary Mack, dressed in black
Silver buttons all down her back
High to low, tip to toe
She broke a needle and she can't sew
Walkin' the dog
Just a-walkin' the dog
If you don't know how to do it
I'll show you how to walk the dog

(screaming guitar solo)
I understand the information content of that post was a bit sparse. I'll try and give you a high-level summary of the first claim.
You're used to identity on the fediverse being one actor per one server. If you don't like the server, you can move to another.
Some of us have nomadic identity, which is one actor and multiple servers. Same content. Same followers. You don't move servers, they're identical clones. You can post from any of them and all your followers will see the posts and be able to interact with them (assuming they have permission - that's a different topic).
But here's what's coming (the technology is already here):
One actor, multiple servers, multiple server types. Each with the same or potentially different content and the same or different followers.
In other words, if you follow 'clarence', you might suddenly find yourself following clarencepixelfed, clarencepeertube, clarencemastodon (3 instances) and clarencestreams (2 instances). Everywhere that clarence ties to that identity.
Now not all of these may accept your follow request. Because clarence has a say in all of this. And clarence might post completely different content at each and make it available to completely different audiences. But the content is also completely portable, so it actually could be duplicated across some or all of them. None of this will matter to you, because you're just following clarence and whatever content from whatever instance or project she makes available to you - and even if she moves to another instance of any or all of these projects.
Cheers.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Identity #NomadicIdentity

The Daily Picture Theme

The theme for April 24, 2024 is I participate in a photography challenge on Spoutible, a social media site, A hashtagged theme is posted each day from the account of Daily Picture Theme which describes itself as "The Big Photo Album of Our Community. The theme for today is and it is not an easy assignment. I wasn't sure whether to use "long" as a verb, adjective or name.

Long

It didn't take to make this mushroom soup. (Recipe in Alt Text.)

DailyPictureTheme

If I've understood it correctly, Mike Macgirvin is working on a concept of federated identity that shall go beyond his own 13-year-old concept of nomadic identity.
That is, of course, you'll still need to manually register accounts on all instances that you want to use. But if what Mike is working on actually comes to fruition, you'll be able to clone your identity across different projects instead of only across server instances within Hubzilla or within (streams).
Add OpenWebAuth magic single sign-on on top, another one of Mike's inventions from ca. 2018/2019, and you'll get close to what you want.
The major caveat is that this won't be easy to implement for projects that aren't nomadic already. I guess this will come with the requirement to adopt the same concept of channels as identity containers as Hubzilla and (streams). And I estimate the chances that Mastodon will implement it to be close to zero.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #OpenWebAuth #NomadicIdentity Also, if it weren't for notorious reply guys on Friendica and Hubzilla, thousands upon thousands more Mastodon users who have joined around November 2022 would believe the Fediverse is only Mastodon still today.
If you're living in a Mastodon-only bubble in which nobody else is aware of a Fediverse outside of Mastodon, the only ones who can tell you otherwise are reply guys on non-Mastodon instances with their unsolicited comments. They've got that information that nobody in your bubble has.
And , if it weren't for me reply-guying you, you'd still believe that an 1,500-character alt-text is the absolute pinnacle of long and detailed image descriptions because nothing could possibly exist beyond it.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ReplyGuy #ReplyGuys

um, sure, that's conceivable. the image may be a joke with many layers to it and at some point you either get it or you don't.

Not conceivable. It's literally the way I describe images. One image may lead to over 13 hours of research and writing and ca. 40,000 characters. , . And I actually consider these two posts outdated and lacking already.
is shorter at a bit over 25,000 characters and more up-to-date, albeit far from complete. I'm linking to it because it uses one fifth of its length, 5,000 characters, to describe one single item that doesn't exist in real life.
I barely get any reactions on them, usually none at all. Neither praise nor criticism, no likes/faves/thumbs-up, nothing. I don't know what people think about them, seeing as how high the standards can be in the Fediverse.
Maybe people silently like them. Maybe people silently ignore them. Maybe each time I post and describe an image, 500 Mastodon users and half a dozen entire instances block me for my excessively long posts. I don't know.
That's why I'm asking someone who wants images that don't explain themselves to total outsiders to be explained. I explain them, and I try to explain them the best I can without requiring too much prior knowledge because I can't expect a casual audience to have that prior knowledge.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta If there's such a thing as no explanation and too little explanation, would you say there's also too much explanation
For example, an extremely explanatory image description that's in the post text, not only because explanations don't belong into alt-text, but because it exceeds the maximum length of Mastodon's alt-text over a dozen times or even several dozen times That has to be that long because what the image shows is extremely niche and extremely obscure
Would you say that's overkill
Or do you say, the more, the merrier
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta

Is there any mechanism by which a honeypot would be revealed Is there any reason why the Fediverse cannot be completely crawled from a client

It wouldn't be an automated process to be built into, say, a Mastodon instance.
It'd be the user community noticing something's awfully fishy about that instance.
Something else that could make things at least a lot harder for authoritarian regimes is a concept invented by Mike Macgirvin in 2011 that goes way beyond what Mastodon can do: . It's currently implemented only on and , both created and the latter still maintained by Mike himself.
It has two advantages: its architecture and, I'd say, also its obscurity. Nation states are only just barely becoming aware of the existence of Mastodon. They know nothing about the Fediverse outside of Mastodon. And so they know even less about the very fringes of the Fediverse which have had such stuff readily available and in daily stable and productive use for about a dozen years now.
Any Mastodon account can be silenced by the Chinese state by blocking the server if it's outside of China or shutting the server down if it's in China. Same for almost the entire rest of the Fediverse.
Hubzilla or (streams) can be made resilient against this by making them nomadic. This means that one and the same channel resides on multiple servers. I'm not talking about dumb copies like when you move your Mastodon account. I'm talking about absolutely identical clones which are synchronised and kept identical in real-time.
I can see four possible scenarios.
One, a dissident collective in China. They create a bunch of channels and spread each one of them across one or two dozen Hubzilla or (streams) servers or even more. If one is shut down, the others carry on with the exact same content, the exact same connections etc. etc. And more can be created at any given time. In order to silence these channels, the authorities would have to find all clone servers and shut them down, one by one, faster than new clones can be created.
And as long as even only one channel backup survives on, what, a USB pen drive or a phone, disguised as e.g. an MP3 file that can easily be renamed back to what it actually is, a Hubzilla or (streams) channel can come back on new servers.
Two, channels outside of China communicating into China. Even supposing that nobody in China uses anything nomadic, e.g. everyone only uses Mastodon or Misskey, having a dozen clones of the same channel outside of China makes it possible for them to follow both the main instance of the channel and the clones. If one server that contains an instance of that channel is blocked by Chinese authorities, the same information will automatically flow through the others. And, again, new clones can be created at any given time.
Three, like one, but one of the dissidents escapes to somewhere in the West with a backup of the channel on some kind of physical storage, disguised in such a way that Chinese authorities won't find it, at least not that easily. That dissident sets up a server at home or rents some Web space capable of running Hubzilla or (streams), both of which need nothing more than a LAMP stack.
They install Hubzilla or (streams), and they create a "new" channel by uploading the channel backup created in China. This will create a nomadic clone of that channel outside of China which will immediately connect to the 20 instances of the channel which existed in China when the backup was created. If new instances have been launched in the meantime, it is made aware of that.
One nice thing about nomadic identity is that it does not work in a hub-and-spoke way, i.e. it isn't only communication between the main instance and the clones. It's communication between all clones as well, so even finding and taking out the main instance can't stop nomadic identity.
If there are 20 clones in China and 20 clones outside of China, this means:

Chinese authorities will have to find and block 20 foreign servers, one by one, to momentarily cut the cross-border connection. Momentarily because each new clone outside of China will re-establish the nomadic connection with the Chinese instances.
Chinese authorities will have to find and shut down 20 domestic servers, one by one, to momentarily silence the Chinese side of the channel. Momentarily because each new clone in China will re-connect to the foreign instances.
Each instance of the channel is connected not to one, but to 39 other instances. It's next to impossible to single them out. And shutting down the main instance won't have any different consequences than shutting down any single one of the 39 clones, other than that another clone will have to be appointed main instance which is one flick of a switch.

Four, and this is the most difficult variant, the other way around: Chinese dissidents take a foreign channel and clone it in China. It largely works the same otherwise, but the channel backup has to be smuggled into China.
The latter two would make it possible to clone anything from the Fediverse into China by nomadic identity.
You post something on mas.to.
I follow you on hub.netzgemeinde.eu, and I receive your post.
My channel has 20 clones on hub.chinesedissidentserver01.org through hub.chinesedissidentserver20.org. They all receive your post just the same.
Then I repeat (= boost) your post. So do all 20 clones in China just the same.
Anyone on chinesemastodoninstance.social or chinesemisskeyinstance.social who follows even only one of these clones receives your post. Not a dumb copy but the original, relayed through Hubzilla.
That is, I'm not entirely sure what'd happen if China blocked mas.to. But even if they did, I'd switch from repeating (= boosting) to sharing (= quote-posting). Or I could set up another channel, install Channel Sources, connect to your Mastodon account and use my connection to your Mastodon account as a channel source. This new channel would automatically repost everything you post, again, as a verbatim but otherwise dumb copy.
Then China can block mas.to all the want, but they won't be able to stop your content coming in through Hubzilla and my channel clones that way. The downside, of course, would be that it'd be one-way communication because you wouldn't receive any replies to your posts.
The biggest danger a network of clones in China (especially scenario 3 and 4) would have to face would not be blocks or forced server shutdowns. It'd be infiltration. Anyone who runs a clone has pretty much full access to it.
If you run a clone, you can post through it under the same identity as the main instance and all the other clones. None of the other clone owners can control what you post in the name of the main instance. If you run a clone, you can upload any and all content and have it cloned across the whole network of clones. If you run a clone, you can make it the main instance. If you run a clone, you can change any and all settings as you want to. Like, you could cut off any and all connections to Mastodon and almost the entire rest of the Fediverse by simply turning Pubcrawl off. Or you could make content public that was uploaded with limited permissions.
But if you run a clone, you can also delete or change content. You can delete files. You can delete connections, and connections on Hubzilla and (streams) are mutual by default there is no Twitter-like follower/followed dichotomy. You can Superblock connections if you don't want them to see what happens on the channel, and this will mean that all 40 instances of the channel Superblock that connection.
And if you run a clone, you can easily see the list of all clones of the channel.
If you only have one state infiltrator running a clone, disguising as a dissident, you're basically fucked. The infiltrator can sabotage the channel, swiftly delete any and all uncomfortable content, falsify content and spread state propaganda through the channel. They can send the list of instances of the channel to the authorities who will immediately block the servers carrying the foreign instances and do everything they can to track the domestic servers down and kill them off before a new clone can be established outside of China.
The moment all foreign instances are permanently blocked, and all domestic instances are permanently shut down, the cross-border nomadic network is basically dead. Even if someone in China and someone outside of China both install backups of this channel, they won't connect across the border. The new instance in China will only know the 20 blocked foreign instances and the 20 shutdown domestic instances, but it won't know the new foreign instance. Same for the one outside of China which won't know the new instance in China. The network can only be restarted by setting up an instance, making enough clones again and smuggling a backup across the border again.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #NomadicIdentity What you could do is as follows:

Follow your own Friendica account from your Hubzilla channel.
Activate the Channel Sources app on your Hubzilla channel.
Add your Friendica account as a source in Channel Sources.

That way, Hubzilla will always automatically repost everything you post on Friendica.
Channel Sources could be described as a kind of universal reverse cross-poster. Reverse because it isn't "Hubzilla to something else", it's "anything that Hubzilla can connect to to Hubzilla". It could serve as a Friendica-to-Hubzilla cross-poster, as a Mastodon-to-Hubzilla cross-poster, as a Diaspora*-to-Hubzilla cross-poster, as an RSS-to-Hubzilla cross-poster (been there, done that, probably angered countless Mastodon users) etc.
The obvious downside is that these reposts are dumb copies which receive their own thumbs up, thumbs down, repeats and comments. None of this is sent back to Friendica. You still have to check your Hubzilla channel once in a while and, for example, reply to comments.
Also, I'm not sure what'd happen if you commented on something on Friendica, regardless of whether your Hubzilla channel is aware of that discussion or not. It could be that Channel Sources would also cross-post your comments and do so out-of-context.
And it seems to be Hubzilla-exclusive. (streams) doesn't have it anymore.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #ChannelSources #CrossPoster It all depends on what you want.
If what you want is features that are available elsewhere in the Fediverse, go elsewhere in the Fediverse, and you've got these features.
If what you want is features that are available elsewhere in the Fediverse, but with Mastodon's UI and UX, then hard-fork Mastodon, throw everything out that isn't UI and convert what remains into an alternative UI for Misskey or Sharkey or Hubzilla or (streams).
If, however, what you want is 100% water-tight safety from Threads, you have to hard-fork the Fediverse itself. Design a whole new federated protocol, hard-fork Mastodon and re-write it against that new protocol. Oh, and keep the protocol secret so that Friendica won't adopt it because Friendica can theoretically forward anything from Bluesky and Threads to anything else it's connected to and vice versa. And Friendica is connected to just about everything.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta I'd say it's quite difficult to block the entirety of the Fediverse, if it's possible at all.
On a DNS level, it'd be a game of whack-a-mole. These regimes would have to know all instances of all projects and block them one by one. And the split-second that some new instance spins up for the first time, it'd have to be blocked immediately.
Even deep packet inspection for blocking purposes would require any and all Fediverse content to have enough in common to be recognisable against the Internet background noise and thus filterable. However, not only is the Fediverse much, much more than just Mastodon, but some Fediverse projects work vastly differently from Mastodon. In fact, some don't even use only ActivityPub. So these regimes would have to know every last Fediverse project inside-out.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMetaIch wrde sagen, erstens: Auflisten, mit welchem Account auf welchem Node es Schwierigkeiten gibt. Das ergibt sich so peu peu durch regulre Versuche der Interaktion.
Zweitens: Daraus destillieren, mit welchen Nodes es Schwierigkeiten gibt. Ich schtze, da wird es sicherlich eine Systematik geben.
Drittens: Support Forum anschreiben. Mit diesem-und-diesem Friendica-Node gibt's Schwierigkeiten, mit diesem-und-diesem nicht.
Viertens: Sich an die Friendica-Leute wenden und versuchen rauszukriegen, was die Nodes, bei denen es nicht geht, gemeinsam haben, was die, bei denen es geht, eben nicht haben. Oder umgekehrt.
Fnftens: Wenn man das wei, entscheiden, ob es ein Bug auf Friendica-Seite oder einer auf Hubzilla-Seite ist. Und dann einen Issue mit Bug Report einreichen.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost

Otoh the issue of embedding #AltText in pictures is a bit fraught. Eg though it's technically possible to do this in #Friendica, the method for non-technical users is esoteric, obscure & confusing, so is IMO highly likely to be skipped. Others like #Hubzilla have other complexities afaik.

Well, to be fair, no Fediverse project so far has been created from scratch with the greatest accessibility possible as part of its concept. Not even Mastodon. Mastodon is not so much as accessible as it is because the developers have added the necessary features as because its users made the use of these features pretty much mandatory over the last two years and firmly engrained it into Mastodon's culture.
Friendica, Hubzilla and (streams) do alt-text almost exactly the same way, only that Hubzilla and (streams) can use slightly different image and URL tags that support extra features introduced with Zot and OpenWebAuth. But this was born along with Friendica back in 2010 when Friendica was still Mistpark, long before Mastodon has a dedicated alt-text field.
Friendica's way of handling posts, comments and discussion threads is not inspired by Facebook for a change, but by long-form blogging. This is apparent first and foremost by there not being any character limit where Mastodon has 500 characters, by the wealth of text formatting features and by images being embeddable anywhere in a post as opposed to only attachable as files. Basically, anyone who chose Friendica over Facebook was given a full-blown blog with just about all bells and whistles along with it.
But like on so many other blogging platforms, Friendica's WYSIWYG editors has never had buttons for all supported features. In fact, IIRC, Friendica didn't even have a WYSIWYG option at first. Either way, just like on other blogging platforms, if you really want to go all the way, you can't rely on WYSIWYG only. You have to get your hands dirty on raw markup code.
Granted, on Friendica and Hubzilla, it's extended BBcode and not the HTML that was pretty much mandatory back in the day or the Markdown that seems to have become the standard nowadays, but still. And every serious blogger knew HTML back in the day, and today, every serious blogger still knows either HTML or Markdown or both.
Also, when Friendica came out under the name Mistpark back then, bulletin-board forums were still huge, so even if you weren't a blogger, chances were you were familiar with BBcode from using forums. In 2010, no forum had WYSIWYG editors that completely concealed the underlying code, especially not on by default. So when you clicked the "b" button, what you got in the editor was not bold letters but a pair of b/b tags.
All this is also why Friendica, as well as Hubzilla and (streams), has previews for everything, just like blogs and forums.
On all three, alt-text falls under "special features for power users and professionals", just like headlines, horizontal rules, text colour (unlike in forums), background colour, text size or typeface. When that feature was included, nobody added alt-text in privately-used social networks. Thus, it was only necessary to add this feature and to have it in some way or another, not to make it as dead-simple for casual corporate silo converts to use as possible. In the early 2010s, a graphical alt-text editor in a Facebook alternative would have been pearls before swine. The target audience for adding alt-text wasn't afraid of code, and your Facebook buddy who came over to check out Friendica had never even heard of alt-text.
And that's why we still have to manually graft alt-text into the image-embedding code today.
At least Friendica explains it in its user documentation because Friendica has decent user documentation. Hubzilla's user documentation reads like a technical specification because it has barely changed from what Friendica's documentation was like in 2012, and it's hopelessly outdated and incomplete. The community is actually considering re-writing it from scratch. And since it was that terrible in 2018 already, it was handed over as-is all the way to (streams) which eventually discarded any and all documentation because it was so bad. Neither of the two explain how to add alt-text the knowledge is spread by word-of-mouth.
On the other hand, alt-text seems to be buggy on Friendica. However, nobody ever notices it. This is partly because Friendica has been around for too long to adopt anything from Mastodon's culture, and it's partly because there's hardly any other Fediverse project whose user base is largely as hostile towards Mastodon as Friendica, perceiving it as invasive, obnoxious and completely ignorant towards the non-Mastodon Fediverse. People simply refuse to follow any kind of fad that comes from Mastodon, and this includes alt-text. And since nobody uses it, nobody notices that it's buggy, and nobody files a bug report.

Ipso facto anyone not using CWs &/or warning tags &/or AltText is a bastard

And the few who are aware that the Fediverse is more than Mastodon think that everything else in the Fediverse is basically Mastodon with extra stuff glued on. It goes beyond the imagination of next to everyone on Mastodon that something that can interact with Mastodon like more Mastodon might actually be designed and work wholly differently. The few who know have Friendica accounts or even Hubzilla channels.
The rest cannot comprehend why some users from outside Mastodon "refuse" to add CWs or flag images sensitive. As I've mentioned previously, hardly anything beyond Mastodon and (streams) can flag images sensitive for Mastodon, and (streams) has no documentation for that, much less dedicated UI elements.
CWs are even more complicated. In the cases of Friendica, Hubzilla and (streams), this has to do with how different they are from Mastodon in concept and from their long-form blogging heritage.
Mastodon got its CWs in 2017 when a user from the demo scene submitted a feature request and pull request that re-purposed StatusNet's summary field for content warnings. Mastodon didn't use the summary field until then after all, you don't need a summary for 500 characters or fewer. That pull request was accepted, and Mastodon had its CWs.
AFAIR, Friendica did have a summary field back when I used it, at least up until 2012 when Hubzilla's saga began. Hubzilla still has it, so does (streams). And summaries actually make sense on all three. After all, they're fully capable of long-form blogging, and they don't have any character limits.
Friendica must have done away with the summary field at some point in the second half of the 2010s or in the early 2020s, probably after adding ActivityPub support in 2018. Friendica users themselves are so used to overly long posts that summaries have never been part of Friendica's culture anyway, and not few Friendica users have switched summaries off entirely. Summaries were probably only a concession towards StatusNet users and a requirement for the connectivity to Twitter. After all, back in the day, Twitter was unable to handle anything longer than 140 and, later, 280 characters.
But then Mastodon and all that followed in its footsteps became more and more important and influential, and with it came Mastodon's content warnings. All of a sudden, Friendica's summaries had to serve two contradicting purposes: cutting posts down for Twitter (the original post was linked to AFAIK) and Mastodon CWs. Making two fields out of one was out of question, though.
So Friendica discarded the summary field altogether and replaced it with the abstract/abstract BBcode tags. These could be made as flexible as they have to be: abstract=twit/abstract only went out to Twitter, abstract=apub/abstract only goes out to whatever is connected via ActivityPub, including Mastodon, and both can be used at the same time.
The obvious downside is that Friendica novices don't know how to add Mastodon CWs to their posts because there isn't even a field for that.
The advantage is that these tags can be used everywhere, including comments. , this is something that you should know about Friendica, Hubzilla and (streams): On all three, a reply is something entirely different from a post that doesn't reply to anything, even though it's all the same on Mastodon. None of the three has its roots in microblogging, and everything that isn't microblogging distinguishes between (start) posts and replies/comments, all the way to having one editor for posts and one or several completely separate editors for comments whereas Twitter and Mastodon have only one for everything.
Since these editors are separate, they aren't the same either. A reply on Friendica, Hubzilla or (streams) is basically like a blog comment. You simply don't need certain features in blog comments. This includes summaries for example. Why would you need a summary for a comment
On Friendica, this isn't a problem. You can add abstract/abstract tags to comments just the same as you can add them to posts. And in fact, at least when the Twitter connection still worked, they even made sense because Friendica actually made it possible to comment on tweets, but only if there was an abstract to cut that comment down to something Twitter could swallow if it was too long.
Hubzilla, being a hard fork and under a wholly different license than Friendica, did not take this change over in spite of being able to connect to Twitter itself. (streams) doesn't have to because it can only connect through its own Nomad, Hubzilla's Zot6 and ActivityPub it can't even connect to Diaspora* anymore.
Thus, both still have a summary field. And it's actually labelled accordingly: "Summary".
For one, this confuses the hell out of newbies who have just come over from Mastodon, too. They think they can't add CWs because Hubzilla doesn't have a field for that, because nobody has told them that it's the summary field. On top of that, there's still the false information circulating around Mastodon that Friendica's title field is Mastodon's CW field from which they deduce that so is Hubzilla's title field. In fact, Friendica's title field does something wholly different on Mastodon, something that's largely unexpected, and Hubzilla's and (streams)' title field does zilch on Mastodon.
Besides, even if you know that Hubzilla's summary field is Mastodon's CW field, there's another problem: Only the post editor has a summary field. The comment editors don't. Again, what sense do summaries make for blog comments None. So why have such a field in the first place if it doesn't make any sense, at least not from a long-form-blogging or Facebook-replacing point of view And that's why there's no summary field for comments.
But if there's no summary field, you can't add Mastodon-style CWs either. I myself would have put a CW on this comment due to its excessive length, but I don't because I simply don't have the means.
And this is something Mastodon users neither know nor understand.
On top of all this, and Mastodon users don't understand this either, Mastodon CWs aren't and will never be part of the Friendica, Hubzilla and (streams) cultures. As I've written previously, all three already have NSFW, and their users prefer it a lot over Mastodon's standard-breaking kluge.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #CW #CWs #ContentWarning #ContentWarnings #CWMeta #ContentWarningMeta #Friendica #Hubzilla #Streams #(streams)

im not so technical to see all the differences even if i know there are.

To be fair, if all you know is Mastodon, and all you ever see is Mastodon, you can't know much about these differences beyond some posts looking weird or doing weird stuff that's technically impossible on Mastodon, e.g. quotes (see above), over 500 characters (see this entire comment), text formatting (see this entire comment again) or unusual-looking mentions (again, see above) and hashtags (see the end). But, for example, Mastodon doesn't tell anyone what instance type a post comes from.
If you even only want to take an outside glance at what another project is like, you have to go visit one of its instances. If you want to take a deeper look, you have to join it and use it. Again, that's natural.

already saw accounts from other non masto instances having a different communication culture. maybe its simply caused by the functionality given.

It definitely is. And the biggest differences exist between Mastodon and projects that had already been in the Fediverse for years when Mastodon was launched, especially Friendica which is about six years older than Mastodon and Hubzilla which, at its core, is about four years older than Mastodon and was made from a Friendica fork by Friendica's own creator.
is on Friendica herself as well: , so she knows what she's talking about. I myself am on Hubzilla, and I used to be on Friendica long before Mastodon took off.
Two more misconceptions common on Mastodon are than a) the Fediverse is only microblogging, even after the discovery of stuff like Akkoma or Misskey, and b) Mastodon was there first. So Mastodon users often wonder how something can possibly be so much different from Mastodon, and why "they" (the developers) haven't simply done things just like Mastodon.
But for one, Friendica and Hubzilla are much older than Mastodon. When Mastodon came out, not only did they already exist, but both had long since outgrown their experimental phase. They were fully established, they were in daily stable use, and most importantly, they had been around for long enough to have developed their very own culture.
This was the case even more whenever Mastodon experienced a growth spurt, be it in ca. 2017 when the furries and otaku were chased off Twitter, in early 2022 when Elon Musk threatened to buy Twitter and in late 2022 when he did.
On top of this, Mastodon is a Twitter clone for better or worse, even taking over some of Twitter's shortcomings because that's allegedly what microblogging is. Friendica, however, is not. It was made to be an alternative to Facebook in 2010 when it had been revealed how evil Facebook truly is. But instead of being a faithful clone, it aimed to be better while serving the same purpose.
This alone explains a whole lot of differences between Mastodon and Friendica.
Hubzilla can serve the same purpose as Friendica, maybe even better because nomadic identity can make Hubzilla channels resilient against sudden instance shutdowns which is the very same reason Hubzilla came to exist. But it actually aims to be a federated social content management system with built-in, optional features that go way beyond what Friendica offers. Nonetheless, it's culturally similar.

the nsfw hashtag and the option to mark pictures as sensitive are a fedi wide standard though

The #NSFW hashtag actually seems to be more of a Friendica/Hubzilla/(streams) thing.
The reason is because all three have their own solution for content warnings which happens to be named "NSFW". It's a special word filter that only does one thing: It searches posts etc. for keywords (substrings actually which might cause false alerts) entered in its word lists, and if it finds one, it hides the whole post or comment or DM behind a content warning. Unlike on Mastodon, this includes all images, and at least on Hubzilla and (streams), it even includes the hashtags.
Not only does this feature pre-date Mastodon's content warnings by almost seven years, but Friendica, Hubzilla and (streams) users see it as superior to Mastodon's content warnings. The advantage is that NSFW doesn't put content warnings on content when it's being posted. It puts content warnings on content after it's received. It happens on the reader's side.
Thus, everyone only receives warnings for content they personally need to be warned about, provided a post or comment or DM contains the appropriate keywords or hashtags. Unlike Mastodon's content warnings, NSFW does not, for example, force "food" content warnings on people who don't have an eating disorder or "depol" content warnings on people who couldn't care any less about German politics.
In Mastodon's culture, the #NSFW hashtag doesn't really serve a specific purpose. People simply use it to have another hashtag on their toots. Filtering doesn't come to mind because filters aren't an integral part of Mastodon's culture. Content-warning-generating filters are even less because they have only been around for less than a year. If anything, the hashtag increases visibility of NSFW content to those who are searching for it.
Mastodon's option to flag images sensitive, on the other hand, is a non-standard, home-brew, exclusive Mastodon development. I'd go as far as calling it proprietary. Not only has it never been part of the specification of either of the protocols Mastodon has used, but I think it doesn't even have an official technical specification, much less an official API for other projects to use.
Thus, most other Fediverse projects do not support it. I know (streams) supports it by automatically adding that flag to images in posts with a #nsfw or #sensitive hashtag and even that only when sending it out through ActivityPub. I think Mastodon's sensitive flag actually had to be reverse-engineered to make this possible.
Both Hubzilla and (streams) have their own sensitive flag for images which is built into their included file server, and I think Friendica has it, too I'm wondering why it seems to be impossible to translate that flag to Mastodon.
This is actually a pity. Here on Hubzilla, I can have Hubzilla and (streams) users click up to four times until they can see a sensitive image: first the NSFW button if they have NSFW activated, then the summary, then a spoiler tag, then the actual image which is blurred out until then. The exact same post, on Mastodon, immediately shows the exact same image in its full glory to everyone or at least to those who don't have any filters for any of the hashtags in the post. And the vast majority of Mastodon users don't.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams)

you know what

There seems to be everything for WordPress. Even including a plug-in that connects WordPress to : . .
It actually goes beyond blogging. It adds grid management tools to WordPress, including access to avatar creation and search management. And it's based on Olivier van Helden's .
One planned feature is the integration of the of the Hypergrid events calendar which even comes in the shape of an in-world panel showing the next events to happen on participating grids.
Both projects are sponsored by the grid and promoted by its grid admin, Gudule Lapointe, who has presented both at Hypergrid International Expo tonight.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #SpeculoosWorld #W4OS #2do #WordPress

But is it a QP or a link to the post Does the author get a notification

Depends because there are currently two ways of quote-posting.
The Friendica way from 2010, also used by Hubzilla and (streams), generates a dumb copy of the original post from a reference written in a pair of special BBcode tags which includes a link to both the poster, even with their profile picture on compatible instances, and the original post.
share=55993487/share
becomes

But is it a QP or a link to the post Does the author get a notification
I think that's what is being discussed here. Anyone can link anything. I see it every day on my timeline, but those show up as links to a toot, and the embedded display generally doesn't even show the toot that is being "quoted". I doubt the author can get notified from that type of interaction.
And the author is notified. I've tested just that with a Mastodon user.
The Misskey way, I don't know from when that is, consists of "RE:" plus the URL of the quoted post from which compatible frontends are expected to generate the actual quote-post.
RE: https://mas.to/thylacoleo/112305011343985452
I don't know whether the author is notified.
However, what Mastodon is working on right now is very likely to be something entirely new and completely incompatible with anything that has existed. So I can't say how it'll work.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #Mastodon #Friendica #Hubzilla #Streams #(streams) #Misskey #Forkey #Forkeys #Firefish #Iceshrimp #Sharkey #CatodonA couple hours ago, I tried my hand at making Mastodon users shit brix in by telling them that the same quote-posts they don't want on Mastodon are readily available already now all over the Fediverse except for Mastodon.
That just about everyone in the Fediverse outside of Mastodon can quote-post everything on Mastodon right now.
And that no non-standard, proprietary opt-in or opt-out on Mastodon can stop them from quote-posting Mastodon toots.
Either most of those whom I've replied to haven't noticed yet, or they've blocked me on the spot for posting stuff that scares them. Including that the Fediverse is not only Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuotedShares #QuotePostDebate #QuoteTootDebate #Mastodon When I quote-post a Mastodon toot on Hubzilla, the tooter is notified. I know for certain, I've tested it.
Same goes for Friendica and (streams) which use the same quote-posting technique. Not sure about Misskey and the Forkeys, though, and about Pleroma and its forks.
And the only way for Mastodon to stop this would be for all Mastodon instances to Fediblock all non-Mastodon instances. Which is a game of whack-a-mole.
Mastodon can never be 100% safe from quote-posts. That's the way it is. Deal with it.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate What if I told you:
Pleroma has quote-posts already now.
Akkoma has quote-posts already now.
All the other Pleroma forks have quote-posts already now.
Misskey has quote-posts already now.
Firefish has quote-posts already now.
Iceshrimp has quote-posts already now.
Sharkey has quote-posts already now.
Catodon has quote-posts already now.
All other forks of Misskey, Firefish and Iceshrimp have quote-posts already now.
Friendica has quote-posts already now.
Hubzilla has quote-posts already now.
(streams) has quote-posts already now.
Only a few examples.
And all of them can quote-post everything and everyone on Mastodon already now.
And no, they haven't introduced quote-posts because Mastodon doesn't have them. Friendica has had quote-posts since it was made, and Friendica is 6 years older than Mastodon. Same for Hubzilla which is 4 years older than Mastodon. Both could quote-post Mastodon toots from the moment that Mastodon was launched.
The Fediverse is not only Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #MastodonIsNotTheFediverse #FediverseIsNotOnlyMastodon #NotOnlyMastodon

research , also areas managed by Public Sector:

Residential gardens could help insects declining due to habitat loss.

Long grass and flowering ivy increase butterfly populations.

Gardens with benefit butterflies most in highly urban areas.

LINK to paper below...

Last updated: 2024-05-02

and at 62.

donate