I'mma just copypasta your hashtag line below )
You wouldn't have needed at least some of them.
If you aren't afraid of going onto people's nerves by posting Fediverse content, you don't need #
CWFediMeta and #
CWFediverseMeta.
And if, without these two and without #
Long #
LongPost #
CWLong #
CWLongPost, your reply had been under 500 characters, you wouldn't have needed these four either.
I'mma just copypasta your hashtag line below ) Let's not forget, in parlance: - which arguably, might be the most etymologically correct of all of them, since most (at least masto) posts are 'notes', rather than 'articles'.
And in fact, quote-posts in the Fediverse are about six years older than Mastodon
That might be a good tidbit for Yuki to expand upon in his Fediverse history doc at
and
.
Basically, at least on Mastodon, you can create a post that's visible to "mentioned people only", tag it with a "MutualsOnly" hashtag, and not mention anyone, and only you would see it.
Here on Hubzilla, I explicitly have the option to make posts only visible to myself. And that means that even people looking through my posts won't be able to see it, login recognised by OpenWebAuth or not.
"Mutuals only" is possible here, too. I can manually select whom to send a post to. This could be single connections which would amount to a DM with no mention. But it could also be a privacy group.
So I could create an additional privacy group with all my connections in it, at least those posting to whom makes sense, i.e. excluding groups, forums, Lemmy communities, blogs, RSS/Atom feeds etc. And then I could restrict a new post to this privacy group. Again, since this post would not be public, strictly speaking, it would not appear on my wall for all channel visitors to see.
Alternatively, I could set my whole channel to Private. Then none of my posts would be public unless I explicitly made them public. All of them would only be visible to my connections by default.
There are downsides to this, though. First of all, Hubzilla assumes all connections to be either following-only or mutual unless a channel is in a kind of "soapbox mode" that doesn't require new following connections to be manually confirmed. Mastodon's Twitter-esque distinction between "follower" and "followed" does not exist here. This was inherited from Friendica, and Friendica, in turn, mimics Facebook which doesn't have one-sided connections either.
Now, Hubzilla has problems figuring out and displaying whether an ActivityPub connection is following-only or mutual. In practice, however, this isn't a problem: If someone doesn't follow me back, they won't receive that post anyway.
The other downside is that none of the ActivityPub-based projects understand permissions like Hubzilla and (streams) do. Not even Friendica does. So connections via "non-nomadic" protocols understand posts with restricted permissions as DMs that go out to a whole lot of connections. If they don't have a concept of DMs with more than two participants, this makes meaningful discussions impossible.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Mutuals #
MutualsOnly #
Hubzilla Long Ubuntu LTS 10 12
Canonical Ubuntu LTS 10 12 ()Canonical expands Long Term Support to 12 years starting with Ubuntu 14.04 LTS () 14.04 (trusty)
Today, C
#1404
You want verbose explanations (Q1). You want detailed transcripts of all text (Q3). You didn't limit Q2 to what matters within the context of the image.
What I suggested is basically Q1, but more specific and following what's actually demanded on Mastodon: an explanation of the meme that doesn't require any further external explanations. In fact, if I were to describe a meme picture nowadays, I'd do it this way.
Also, explanations never go into alt-text and always into the post text body.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
ImageDescription #
ImageDescriptions #
ImageDescriptionMeta #
CWImageDescriptionMetaIch Frage mich, wie will man ein Problem lsen, ohne die mglichen Schritte zu erklren.
Das Problem soll einfach so verschwinden, ohne da sich fr sie selbst irgendwas grundlegend ndert.
Beispielsweise BIPoC. Die einzige adquate Lsung fr rassistische Angriffe ist fr sie, wenn die Rassisten alle verschwinden. Entweder von sich aus. Oder wenn sie das nicht tun, dann sollen die Admins und Moderatoren die dauerhaft und komplett wegmachen. Und wenn die das nicht schaffen, dann ist das Fediverse eben scheie. Und dann sind soziale Netzwerke im allgemeinen scheie, weil man ja berall den Rassisten komplett schutzlos ausgeliefert ist. Dann hren sie damit eben ganz auf.
Du kannst ihnen tausendmal sagen, da sie auf (streams) ihre Sicherheit und ihr Wohlergehen in ihre eigenen Hnde nehmen knnen, was im brigen sehr viel besser funktioniert als alles, was Mastodon ihnen bietet. Das interessiert sie aber nicht. Sie wollen das Problem nicht bekmpfen, sie wollen, da das Problem von vornherein nicht da ist.
Von einem privilegierten weien Cishet-Mann lassen sie sich sowieso nichts sagen. Und wie knnen sie sich sicher sein, da (streams), das ja praktisch komplett von privilegierten weien Cishet-Mnnern genutzt wird, nicht auch mit Rassisten voll ist
Das Ganze funktioniert genauso mit Frauen und sexistischen Mnnern oder mit der 2SLGBTQIA+-Community und Homo-/Transphobikern. Solange (streams) keine erfahrenen, kompetenten Nutzer oder gar Admins hat, die schwarz oder schwul oder queer oder auch nur Frauen sind und auf Mastodon fr (streams) Werbung machen knnen, wird sich daran auch nichts ndern. Nur leider verhindert eben der Umstand, da (streams) eine einzige weie Salamiparty ist, seine eigene Beseitigung.
Die Frage ist nur, will man geholfen werden oder stellt man nur Fallen um mit mglichst viel Geschrei mit dem Finger auf andere zu zeigen
Wenn es wirklich nur eine Frage ist, niemand sonst drauf geantwortet hat, du eine wirklich hilfreiche Antwort schreibst und du dann sofort dafr attackiert wirst, was dir privilegiertem Schwein denn einfiele, kommen wirklich Zweifel auf.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Streams #
(streams) #
Minderheiten #
2SLGBTQIA+ #
FLINTA* #
BIPoC #
Mansplaining #
ReplyGuy #
ReplyGuysAber ja, dann kommen die verschiedenen Apps ins Spiel, die das Fediverse als Twitterspiegel darstellen und da echte Funktionen rauslschen
Das liegt aber oft an der Ahnungslosigkeit der Entwickler.
Erst sind sie von Twitter nach Mastodon gekommen. Dann fanden die das alles ganz toll. Dann haben sie beschlossen, eine App fr iOS oder Android zu entwickeln, weil sie dachten, sowas gibt's noch nicht/zur offiziellen App gibt's keine Alternative.
Weil sie zu dem Zeitpunkt dachten, das Fediverse sei nur Mastodon, haben sie die App hart nur gegen Mastodon gebaut. Also nicht nur gegen die Mastodon-API, sondern auch nur unter Bercksichtigung dessen, was Vanilla-Mastodon selbst kann.
Als sie das erste Mal davon hrten, da es im Fediverse auch noch was anderes als Mastodon gibt, war es zu spt. Alleine, um die grundlegendsten Features zu untersttzen, die die *omas und *keys haben, die Mastodon nicht hat, mten sie das halbe Backend und das halbe Frontend komplett umbauen. Und da rede ich noch nicht von so Spen wie Firefishs Antennen oder Sharkeys "Speak like a cat"-Modus.
Deswegen gibt's meines Wissens heute noch Apps, die Textformatierung nur erzeugen knnen, wenn man sich seine Finger an Markdown schmutzig macht, und darstellen berhaupt nicht, weil schon der Einbau der zustzlichen Features von Mastodon 4.x zu aufwendig wre.
Es gibt wohl sogar Apps, die fr "das Fediverse" sind, mit denen es aber unmglich ist, mehr als 500 Zeichen zu posten.
Es ist schon traurig, wenn eine App die Mastodon-API benutzt, es aber trotzdem Glckssache ist, ob sie mit irgendwas funktioniert, was die API auch hat, aber nicht Vanilla-Mastodon ist.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Mastodon #
NichtNurMastodon #
Apps #
MastodonApps Du kannst doch heutzutage kaum mehr jemandem helfen, der kein weier Cishet-Mann ist.
Und selbst unter denen gibt's Mimosen, die nichts vom Fediverse auerhalb von Mastodon hren wollen oder davon, da es irgendwas gibt, was irgendwas besser kann als Mastodon.
Ich habe hunderte von Mastodon-"Kontakten", aber annhernd null Reichweite. Das kann man sich mal durch den Kopf gehen lassen. Ich schtze, mindestens 250 meiner Kontakte kamen zustande, weil ich einmal einen interessanten Kommentar irgendwo gereplyguyt habe. Weitere 50 kamen zustande, weil ich einmal einen interessanten Post bers Fediverse jenseits von Mastodon geschrieben habe. Noch einmal 100 sind mir nur gefolgt, weil sie neu waren, unbedingt twittermiges Hintergrundrauschen auf ihrer persnlichen Timeline brauchten und allen folgten, die sie in der fderierten Timeline vorfanden.
Von diesen 400 Kontakten hat aber annhernd niemand je mein Profil gelesen oder sich meine anderen Posts oder Kommentare angeguckt. Entweder wuten sie nicht, wie das auf Mastodon geht, oder in ihrer App geht das berhaupt nicht, oder sie sind daran verzweifelt, da Hubzilla sich ganz anders bedient als Mastodon. Entsprechend schnell haben sie mir dann einen Maulkorb verpat, nur weil ich tat, was ich vorher schon getan hatte, was sie aber nicht wuten.
Ob ich also diese Kontakte habe oder peng. Ich glaube ja sowieso, da inzwischen etliche Grids mich shadowgebannt haben, weil ich mich so "unmastodonmig" verhalte, oder gleich den ganzen Hub, wo ich bin, weil da die Moderation nicht so funktioniert, wie man das von groen Mastodon-Instanzen kennt.
Wie es aussieht, wird so manch einer, der im November 2022 nach Mastodon gekommen ist, auch im November 2027 immer noch glauben, das Fediverse sei nur Mastodon. Warum Weil diejenigen ausschlielich mit Leuten innerhalb ihrer Bubble kommunizieren, weil alle auerhalb ihrer Bubble Reply Guys sind. Und innerhalb ihrer Bubble wei auch niemand, da das Fediverse mehr ist als Mastodon.
So einiges an Halbwissen wird auch immer unausrottbarer. Nicht nur, da alles im Fediverse, was nicht Mastodon ist, im Prinzip nur ein alternatives grafisches Frontend fr Mastodon mit ansonsten denselben grundlegenden Features ist, sondern auch, da Mastodon berhaupt die einzige perfekte ActivityPub-Implementation ist, da es im Fediverse keine Quote-Posts = Quote-Tweets = Drkos gibt, da Eugen Rochko das CW-Feld erfunden hat, da alles an Bildbeschreibung immer in den Alt-Text gehrt, und da Mastodon der einzig sichere Ort im Fediverse ist.
Ich wrde mal sagen: Viele drangsalierte und verfolgte Minderheiten wren eigentlich auf (streams) noch am besten aufgehoben. Aber es ist schon annhernd unmglich, diesen Leuten berhaupt etwas von (streams) zu erzhlen, weil (streams) eine reine Weie-Cishet-Mnner-Geschichte ist. Zum einen haben (streams)-Nutzer keine Chance, Werbung bei Minoritten zu machen. Zum anderen, weil nicht sowieso schon Minoritten auf (streams) zu Hause sind, gehen andere da auch nicht hin, weil sie sich da unsicher fhlen oder gar ein weiteres angebliches Nazi-Netz wie Pleroma wittern.
Eigentlich htte ich lngst diesen Kanal auf mindestens drei Kanle aufteilen mssen. Einen nur ber virtuelle Welten, was ja eigentlich das Kernthema hier ist. Einen als "Fedi.Tips, aber das Fediverse ist wirklich nicht nur Mastodon", also mit generellen, komplett nicht kontroversen Infoposts. Und einen mit kontroverseren, fr Mastodon-Nutzer unbequemeren Infoposts, als Reply Guy fr Leute, die zeigen, da sie vom Fediverse null Ahnung haben, und fr Kommentare, die Mastodon nicht gut aussehen lassen.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Streams #
(streams) #
Sicherheit #
ReplyGuy #
ReplyGuys #
Mansplainingthe journey from to in one
This just in from The Box on :
The Caribou Grid has shut down unannounced, and its founder, Jeanne Lefavre, has left OpenSim.
I still remember when Caribou was one big 4x4 varsim in Kitely. Much earlier, it used to be in Second Life. It moved a lot over time.
I think it was in 2022 when Caribou moved to ZetaWorlds and was turned into a bunch of 2x2 varsims, waiting to be at least partially redesigned. That wasn't too long after Stark had returned. However, Caribou relocated to OSgrid after Stark had managed to 7-days-per-week event schedule, leaving little room for Caribou's events which partly shared the same audience. I actually wanted to run a shop or two on OSgrid Caribou.
Then, in 2023, Jeanne moved Caribou to its own, brand-new grid. She brought old sims back and started redesigning what was already there, reshaping large parts of the land. Things really looked good. She even married Andron Rae of Neverworld, although that relationship wasn't really built to last, but he kept helping her with the tech. It was only recently that she started posting personal things on OSW.
And now she and Caribou as a whole are gone. I guess all the harassment had become too much.
It makes me wonder what the remaining rest of the Caribou staff will do now. Fortunately, they've got leftover avatars on a whole bunch of grids now.
#
Long #
LongPost #
CWLong #
CWLongPost #
OpenSim #
OpenSimulator #
Metaverse #
VirtualWorlds #
Kitely #
ZetaWorlds #
OSgrid #
Neverworld #
NeverworldGrid #
Caribou #
CaribouGrid that Meta's Reality Labs, responsible for Horizons, have made a loss of 3.85 billion dollars in the first quarter of 2024 alone.
Now imagine what OpenSim could have done with that much money. Give itself a thorough overhaul and debugging, even if that means at least a partially rewrite. Hire more developers for that purpose because four spare-time devs can only do so much.
Upgrade from a decades-old OpenGL standard to Vulkan. Implement a new, open-source voice system that doesn't rely on anything external. In fact, develop its own dedicated cross-platform viewer and ensure its on-going development and maintenance, thus facilitating a further split from Second Life. Also, give the Firestorm team its share so they can afford some proper OpenSim-side development.
While we're at it, fund a good alternative to OpenSimWorld, maybe even something that integrates into viewers, as well as the development of the Max bodies and matching accessories.
Dreams would come true. But sorry, old-timers, separating from Second Life won't mean returning to 2011's tech level before there was mesh.
#
Long #
LongPost #
CWLong #
CWLongPost #
Horizons #
HorizonWorlds #
Meta #
MetaPlatforms #
OpenSim #
OpenSimulator #
Metaverse #
VirtualWorlds An example for the first bullet point is Mastodon's CW field. It was originally created by repurposing the summary field from the OpenMicroBlog/OStatus standard, and it now repurposes the summary field from the ActivityPub standard.
Friendica and Hubzilla have actually been using that field for summaries since 2010 and 2015 respectively. Mastodon is from 2016 and introduced the CW field in 2017.
However, Mastodon doesn't communicate this repurposing. Instead, it implies that it has invented this field for content warnings. Thus, Mastodon users are easily irritated if someone uses it for summaries because they're on something else than Mastodon, and that field is labelled "summary" where they are.
I'd say that Mastodon's absolute refusal to support
any HTML or rich text up until version 4.0 falls under this, too. Even current Mastodon only allows for a tiny subset because going beyond that allegedly wouldn't be microblogging anymore. Everything else is stripped out by Mastodon's "sanitiser", included image embeddings, forcing projects like Friendica or Hubzilla to convert their embedded images into file attachments, only four of which Mastodon accepts.
An example for the second bullet point might become Mastodon's implementation of quote-posts.
There are currently two standards for this. The oldest one is the way Mistpark, now Friendica, did it as early as 2010. Friendica, Hubzilla and (streams) still do it this way. It's by putting a verbatim copy of the original post, including links to the original poster and the original post, into your post.
Misskey introduced its own way of quote-posting, namely as a reference to the original post. It's also used by its many forks and forks of forks as well as Pleroma and its forks. At least Hubzilla, (streams) and Threads understand it, and I think so does Friendica.
Nonetheless, Mastodon is expected to not only continue to refuse to support Misskey's way, but also create its own half-proprietary way of quote-posting to which nothing else in the Fediverse will be compatible. On top of that, it will likely include a non-standard, half-proprietary opt-in switch to which the whole rest of the Fediverse won't be compatible either.
Also, the Mastodon API falls under this. After all, ActivityPub works between clients and servers as well. Granted, the wide adoption of the Mastodon API is not unjustified because ActivityPub's C2S definitions are too vague and different from project to project. Still, everything that wants to be compatible with dedicated apps without having its own one is at Mastodon's mercy and at least partly limited to what Mastodon can do.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon (see also ) and its community have been using the term "metaverse" for actually existing 3-D virtual worlds since 2007. Entire grids have carried and still carry that word in their names. I guess that's a start.
For some glances into it, I suggest 's .
Also, , upon whose technology OpenSim is based, refers to itself as a "metaverse" now, too justifiedly because Philip Rosedale was inspired to create it by Neal Stephenson's
Snow Crash which coined the term in the first place.
#
Long #
LongPost #
CWLong #
CWLongPost #
SecondLife #
OpenSim #
OpenSimulator #
Metaverse #
VirtualWorldsGanz offen gesagt: Davon lese ich jetzt zum ersten Mal.
Das heit, du gehrst auch zu denen, die mit der zweiten Twitter-Flchtlingswelle im November 2022 zu Mastodon gekommen sind und im Mai 2023 noch dachten, das Fediverse sei nur Mastodon
Wenn der Account aber aus einer willkrlichen Zahl-Buchstaben-Folge besteht und offensichtlich beleidigend unterwegs ist, gucke ich gern mal systematischer hin, um mir und meinen Follower*innem so etwas generell vom Leib zu halten.
Ist jedenfalls sehr viel besser, als jedem sofort blind zu folgen, der einmal was Interessantes postet, ohne sich mal anzugucken, was das fr ein Account/Kanal ist.
Ich glaube, ich mache selbst oft den falschen Eindruck, und Leute folgen mir nur aufgrund eines einzigen schlauen Kommentars, ohne zu wissen, was ich sonst so poste. Wahrscheinlich haben viele mich inzwischen gemutet, weil dann vllig Unerwartetes kam und niemand mit Filtern umgehen kann.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta I think that's difficult because there's no consensus on what all virtual worlds shall be like, and each project is re-inventing existing wheels and trying to be different and individual. It doesn't help that different virtual worlds have different purposes and different UI requirements. What's absolutely essential in one world to make use of its killer features is completely superfluous in another world that neither has nor needs these features. For example, building in-world is a key feature in some worlds and completely unthinkable in others.
But it isn't like the existing wheels are all rosy, at least not to beginners. and worlds based on are pancakes they weren't made for headsets, and I've got my doubts that they'd work on headsets because they can't guarantee a steady 60fps in any given situation. Instead, they're used on run-of-the-mill desktop and laptop computers with 2-D screens.
Second Life's own standard viewer is already slimmed down some, and it's considered a viewer for newbies. At the same time, it receives a lot of criticism for being too complex for newbies who came over from e.g. MMORPGs or VR applications. However, the number one choice of Second Life power users, as well as the most popular viewer for OpenSim, is the , a third-party virtual worlds client that rivals office applications or graphics editors in complexity.
This has often been discussed. But it always boiled down to one point: It's impossible to make a newbie-friendly UI for these worlds by shaving features off the UI if even newbies will require access to these features sooner rather than later.
Instead, they've wasted precious time and resources into recreating the real world.
That step was only logical. Second Life became the first really successful 3-D environment by doing just that: mimicking the real world. I mean, it has been around for 20 years and evolving all the time, making more money per user and month than Facebook, all without spying on its users.
Virtual worlds that resemble the real world are what end users will want. If you launch a "metaverse", and you refuse to offer anything like this because you think it's stupid and backwards-oriented, people will turn their backs on you and join the competition because it offers and advertises just that.
#
Long #
LongPost #
CWLong #
CWLongPost #
SecondLife #
OpenSim #
OpenSimulator #
Metaverse #
VirtualWorlds #
UI Ernstgemeinte Frage (Achtung, jetzt wird's seeeeehr lang): Was macht ihr bei Instanzen, die nicht Mastodon sind und ganz anders funktionieren
Ein Hubzilla-Hub hat z. B. kein . Da mu man sich durch die Hilfe suchen und findet dann und darunter und . Und selbst dann findet ihr keine Regeln, weil die allerwenigsten Hubzilla-Hubs berhaupt welche haben.
brigens hat Hubzilla auch Mastodons Report-Funktion nicht implementiert, so da ihr beim Versuch, Hubzilla-Nutzer ber Standard-Mastodon-Wege bei ihren eigenen Admins zu verpfeifen, nichts erreichen werdet.
Es gibt auch kein . Ich wei nicht mal mit Sicherheit, ob Hubzilla ein Pendant zu Mastodons lokaler Timeline hat. Wenn, dann wre das der Pubstream, der ist aber standardmig und auf den allermeisten Hubs deaktiviert, weil er ebenso standardmig der
fderierten Timeline entspricht und nicht moderierbar ist. Auf (streams) kann er auf lokal umgeschaltet werden bei Hubzilla bin ich mir nicht sicher.
Aber jedenfalls gibt's ihn in den allermeisten Fllen schlicht und ergreifend berhaupt nicht. Ihr knnt also nicht sehen, was die Leute auf dem Hub so posten.
Also: keine mastodonmige About-Seite, keine mastodonmigen Regeln, keine lokale Timeline, auerdem ist nichts da, wo es "hingehrt". Und das ist kein Einzelfall, sondern auf Hubzilla normal.
Was macht ihr dann Zuckt ihr mit den Schultern und sagt, das ist dann eben anders als auf Mastodon (weil es genau das ist) Oder blockiert ihr sofort die ganze Instanz, weil er nicht vertrauenserweckend genug wirkt
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Hubzilla Hubzilla doesn't do that, regardless of where a post or a comment comes from.
However, Mastodon tries to generate a link preview from the first link in every post that comes over from Hubzilla. And Mastodon perceives both mentions and hashtags in posts from Hubzilla as links because they aren't formatted in the same way as on Mastodon itself. So if I were to link to It's FOSS right here, It's FOSS would be safe because Mastodon would probably generate a preview from one of the two mentions.
(streams) does have link previews that must have been introduced at some point since the 2018 Hubzilla-to-Osada fork. But they can be turned off per channel. Still, same behaviour on Mastodon.
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Mastodon #
Hubzilla #
Streams #
(streams) #
LinkPreview #
LinkPreviewsUnd einen Post mit einer Content Warning auszustatten sollte wohl auch irgendwie gehen, aber ich bin noch nicht drauf gekommen.
Mastodons Content Warning ist eigentlich das Summary von OStatus und ActivityPub. Meines Wissens hatte Friendica mal ein Feld dafr, das aber entfernt wurde, weil es nicht flexibel genug war, weil die Anforderungen an Zusammenfassungen fr einerseits Twitter und andererseits ganz besonders Mastodon unterschiedlich waren.
Also wird das jetzt mit BBcode-Tags gelst.
abstractHier die Content Warning eintragen/abstract
erzeugt eine Zusammenfassung/Content Warning fr alle irgendwie kompatiblen Kontakte.
abstract=apubHier die Content Warning eintragen/abstract
erzeugt eine Zusammenfassung/Content Warning nur fr Kontakte ber ActivityPub. Wenn du keine Verbindung zu Twitter hast, spielt das fr dich keine Rolle, und nach Diaspora* gehen eh keine Zusammenfassungen raus.
Der zweite Ansatz es fr macroblogging zu nutzen ist auch irgendwie unsinnig fr mich.
Fun fact, und das ist meines Wissens undokumentiert:
Wenn du einem Friendica-Post einen Titel gibst, geht der raus als Article-Type Object, genau wie ein Blogpost. Mastodon zeigt ihn dann nur als Titel, Zusammenfassung und Link zum Original an, genau wie einen Blogpost.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
CW #
CWs #
CWMeta #
ContentWarning #
ContentWarnings #
ContentWarningMeta #
Friendica Auf der Weboberflche ist es unntig kompliziert einen Alt-Text an ein Foto ran zu heften.
Na ja, "unntig" wrde ich das nicht nennen. Man mu bedenken, woher Friendica kommt.
Im Gegensatz zu Mastodon versucht Friendica ja nicht, ein Twitter-Klon zu sein. Es ist eher dafr gedacht, eine Facebook-Alternative zu sein mit Features, die auch Facebook nicht hat.
Es ist auerdem viel lter als Mastodon. Es hat seinen Ursprung im Jahr 2010 da hie es erst noch "Mistpark". Das war eine Zeit, als die Leute noch nicht alles mit Smartphones gemacht haben.
Friendica wollte und will ja auch tauglich sein fr Blogging mit allen Schikanen. 2010 hatten Blogger und auch viele Forennutzer keine Probleme damit, ihre Finger an Markup-Code schmutzig zu machen. Gerade beim Blogging gehrte es einfach dazu, da man in rohem Code schrieb, bis darauf, da es HTML war und Friendica BBcode verwendet. Auerdem war Alt-Text 2010 hchstens ein Thema fr kommerzielle Blogger, auf Friendica eher ein "Knnte man vielleicht mal brauchen"-Gimmick und in sozialen Netzwerken ansonsten gnzlich unbekannt.
Noch ein Unterschied ist, da Bilder auf Mastodon immer Dateianhnge sind, whrend sie auf Friendica auch direkt in Posts eingebettet werden knnen, genau wie in Blogs. Das macht es allerdings unmglich, fr die Bilder jeweils eigene Datenfelder fr Alt-Text und somit vollwertige Eingabefelder dafr im UI vorzusehen. Okay, beim
Erstellen von Alt-Text knnte eventuell ein Eingabefeld beim Einbetten von Bildern helfen, aber beim
nachtrglichen Bearbeiten wird man in den Code eingreifen mssen.
Auerdem: So, wie Mastodon Friendica und seine Nachfolger seit 2016 behandelt, hat man auf Friendica keine Lust, Mastodon mehr entgegenzukommen als unbedingt notwendig. Das schliet auch UI-Umbauten aus, die dazu dienen, "Mastodons Kultur" auf Friendica zu etablieren.
#
Long #
LongPost #
CWLong #
CWLongPost #
LangerPost #
CWLangerPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
AltText #
AltTextMeta #
CWAltTextMeta #
Friendica 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 In one sense, Rochko has won, namely the firm tie between "Fediverse" and "Mastodon".
My estimation is that about every other Mastodon user thinks that the Fediverse is only Mastodon, at least when it comes to being non-corporate and actually decentralised. And this actually includes people who have escaped from Twitter immediately after Musk had bought it out, i.e. they've been on Mastodon for a year and a half already. So the only two ways to have another free, open-source, non-corporate, non-commercial, decentralised project in the Fediverse seem to be either to fork Mastodon or to develop one from scratch.
Most of the rest is so firmly tied to Mastodon's UI and Mastodon's UX and Mastodon's way of doing just about everything that, even if they knew what else the Fediverse has to offer right now, they couldn't use it because it doesn't look and feel like Mastodon. Even if about 98% of them use Mastodon through a mobile app.
I mean, why else is hard-forking Mastodon such a huge topic, and moving from Mastodon to Akkoma or the Forkeys or (streams) or something else isn't a topic at all
#
Long #
LongPost #
CWLong #
CWLongPost #
FediMeta #
FediverseMeta #
CWFediMeta #
CWFediverseMeta #
Fediverse #
Mastodon #
NotOnlyMastodon #
FediverseIsNotMastodon #
MastodonIsNotTheFediverse #
Fork #
HardFork 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 #
QuotedSharesThis 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 #
HardForkHa, 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 #
Forkas 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 #
MastodonIsNotTheFediversething 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 forBecause 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
infiniteHow 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 #
ActivityPubI 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