Find the latitude of any place.  

' Covid may be due to

  Hubzilla-Hppchen: HQ
HQ ist die Standard-Startseite nach der Anmeldung. Sie bietet einen schnellen berblick ber die letzten Beitrge und Direktnachrichten.
Ruft man den Hubzilla-Server (Hub) auf, bei welchem man registriert ist (und loggt sich, sofern das noch nicht geschehen ist, ein), dann landet man inzwischen nicht in der normalen Grid-/, sondern auf der Seite "HQ". Der erste sprbare Vorteil ist, dass die Seite wesentlich schneller rendert.

Man erreicht das HQ aber auch aus dem Hamburger-Men oben rechts () oder, wenn die HQ-App angepinnt ist, aus der Header-Leiste.


In der linken Seitenleiste ist zunchst ein Teil des mit ffentlichen und beschrnkten Beitrgen zu sehen, bei welchen jedoch nur ein Excerpt angezeigt wird. Ein Klick auf einen dieser Eintrge bringt den Beitrag in der Hauptansicht (mitte) zur Ansicht.

Nach dem Aufrufen des HQ sind in der Hauptansicht zunchst aber die letzten nderungen in verschiedenen Berichte, wie Wiki, Webseiten, Fotos, Dateien etc. zu sehen.
Die linke Seitenleiste weist verschiedene Reiter auf, mit denen weitere Listen angezeigt werden knnen.
Der zweite Reiter dient der Listenasicht ausschlielich von (DN).

Der dritte Reiter zeigt "markierte" Beitrge, also Beitrge, die man mit einem "Sternchen" Markiert hat (das geschieht im Kontextmen des jeweiligen Beitrags).

Der vierte Reiter zeigt die Mitteilungs-Liste.

Unter dieser Listenansicht sind noch zwei Icons vorhanden, ein "Bleistift", der bei einem Klick den Beitrags-Editor ffnet um schnell einen neuen Beitrag zu erstellen, und einen "Notiz-Zettel", welcher den Editor fr Notiz-Eingaben ffnet.


#FediTips #FediverseTips #hubzilla #hubzillahppchen
#Long #LongPost #CWLong #CWLongPost
Find the latitdue and longitude of any place HQ ist die Standard-Startseite nach der Anmeldung. Sie bietet einen schnellen berblick ber die letzten Beitrge und Direktnachrichten.
Ruft man den Hubzilla-Server (Hub) auf, bei welchem man registriert ist (und loggt sich, sofern das noch nicht geschehen ist, ein), dann landet man inzwischen nicht in der normalen Grid-/, sondern auf der Seite "HQ". Der erste sprbare Vorteil ist, dass die Seite wesentlich schneller rendert.

Man erreicht das HQ aber auch aus dem Hamburger-Men oben rechts () oder, wenn die HQ-App angepinnt ist, aus der Header-Leiste.


In der linken Seitenleiste ist zunchst ein Teil des mit ffentlichen und beschrnkten Beitrgen zu sehen, bei welchen jedoch nur ein Excerpt angezeigt wird. Ein Klick auf einen dieser Eintrge bringt den Beitrag in der Hauptansicht (mitte) zur Ansicht.

Nach dem Aufrufen des HQ sind in der Hauptansicht zunchst aber die letzten nderungen in verschiedenen Berichte, wie Wiki, Webseiten, Fotos, Dateien etc. zu sehen.
Die linke Seitenleiste weist verschiedene Reiter auf, mit denen weitere Listen angezeigt werden knnen.
Der zweite Reiter dient der Listenasicht ausschlielich von (DN).

Der dritte Reiter zeigt "markierte" Beitrge, also Beitrge, die man mit einem "Sternchen" Markiert hat (das geschieht im Kontextmen des jeweiligen Beitrags).

Der vierte Reiter zeigt die Mitteilungs-Liste.

Unter dieser Listenansicht sind noch zwei Icons vorhanden, ein "Bleistift", der bei einem Klick den Beitrags-Editor ffnet um schnell einen neuen Beitrag zu erstellen, und einen "Notiz-Zettel", welcher den Editor fr Notiz-Eingaben ffnet.


#FediTips #FediverseTips #hubzilla #hubzillahppchen
#Long #LongPost #CWLong #CWLongPost   Hubzilla-Hppchen: Zot
Zot ist das Protokoll, mit dem Hubzilla betrieben wird. Es ermglicht die Kommunikation, das Identittsmanagement und die Zugangskontrolle.
Die Kommunikation mittels Zot kann ffentlich oder privat sein, wobei die private Kommunikation nicht nur einen vollstndig verschlsselten Transport, sondern auch eine verschlsselte Speicherung zum Schutz vorsieht.
Zot untersttzt eine breite Palette von Hintergrunddiensten im Grid, von Freundschaftsvorschlgen bis hin zu Verzeichnisdiensten. Neue Inhalte und Datenaktualisierungen werden im Hintergrund zwischen den Hubs im gesamten Grid gem den Zugriffskontrolllisten und den von den Sender- und Empfngerkanlen festgelegten Berechtigungen weitergegeben. Die Daten werden auch zwischen einer beliebigen Anzahl von Kanalklonen synchronisiert, so dass Hub-Mitglieder auch dann auf Daten zugreifen und nahtlos weiter zusammenarbeiten knnen, wenn ihr primrer Hub nicht erreichbar oder offline ist.
Zot bietet auch eine nomadische Identitt, so dass Ihre Kommunikation mit Freunden, Familie oder anderen Personen, mit denen Sie kommunizieren, nicht durch den Verlust Ihres primren Kommunikationsknotens beeintrchtigt wird - entweder vorbergehend oder dauerhaft.
Die wichtigen Teile Ihrer Identitt und Ihrer Beziehungen knnen auf einem USB-Stick, dem Laptop oder PC gesichert werden und jederzeit an einem beliebigen Knoten im Netz erscheinen - mit all Ihren Freunden und Vorlieben.
Entscheidend ist, dass diese nomadischen Instanzen synchron gehalten werden, so dass jede Instanz bernehmen kann, wenn eine andere gefhrdet oder beschdigt ist. Dies schtzt Sie nicht nur vor greren Systemausfllen, sondern auch vor vorbergehender berlastung der Website und staatlicher Manipulation oder Zensur.
Die nomadische Identitt, die einmalige Anmeldung und die Dezentralisierung von Hubzilla gewhrleisten ein hohes Ma an Widerstandsfhigkeit und Bestndigkeit in der Internetkommunikation. Mittels magic-auth meldet man nur einmal an Ihrem Heimat-Hub (oder einem nomadischen Backup-Hub) an. Dadurch kann man auf alle authentifizierten Dienste zugreifen, die berall im Netz angeboten werden - wie Einkaufen, Blogs, Foren und Zugang zu privaten Informationen. Das Passwort wird nicht auf tausend verschiedenen Websites gespeichert, sondern auf Servern, man selbst kontrolliert oder denen man vertraut.
Zugriffskontrolle: Die Identittsschicht von Zot ermglicht es, fein abgestufte Berechtigungen fr jeden Inhalt zu vergeben, den man verffentlichen mchte. Diese Berechtigungen erstrecken sich ber das gesamte Grid. Das ist so, als htte man eine riesige Website, die aus einer Grozahl von kleinen, individuellen Websites besteht und bei der jeder Kanal im Grid seine Datenschutz- und Freigabeprferenzen fr alle von ihm erstellten Webressourcen vollstndig kontrollieren kann.
Derzeit untersttzt Hubzilla die Zugriffskontrolle fr viele Datentypen, darunter Diskussionsbeitrge und -kommentare, Fotoalben, Veranstaltungen, Cloud-Dateien, Webseiten, Wikis und mehr. Jedes Objekt und die Art und Weise, wie und mit wem es geteilt wird, unterliegt vollstndig Ihrer Kontrolle.
Im Grid braucht man keine riesige Benutzerdatenbank auf dem Rechner, denn das Grid ist die Benutzerdatenbank. Sie verfgt ber eine im Grunde unendliche Kapazitt (begrenzt durch die Gesamtzahl der Hubs, die im Internet online sind) und ist auf unzhlige Computer verteilt.
Der Zugang kann, berall im Grid, fr jede Ressource, jeden Kanal oder jede Gruppe von Kanlen gewhrt oder verweigert werden. Andere knnen auf die eigenen Inhalte zugreifen, wenn es ihnen erlaubt wird, und sie mssen nicht einmal ein Konto auf dem selben Hub haben.
Aktuell verwendet Hubzilla das Zot-Protokoll in der Version 6 (Zot6).
#FediTips #FediverseTips #hubzilla #hubzillahppchen
#Long #LongPost #CWLong #CWLongPost
Zot ist das Protokoll, mit dem Hubzilla betrieben wird. Es ermglicht die Kommunikation, das Identittsmanagement und die Zugangskontrolle.
Die Kommunikation mittels Zot kann ffentlich oder privat sein, wobei die private Kommunikation nicht nur einen vollstndig verschlsselten Transport, sondern auch eine verschlsselte Speicherung zum Schutz vorsieht.
Zot untersttzt eine breite Palette von Hintergrunddiensten im Grid, von Freundschaftsvorschlgen bis hin zu Verzeichnisdiensten. Neue Inhalte und Datenaktualisierungen werden im Hintergrund zwischen den Hubs im gesamten Grid gem den Zugriffskontrolllisten und den von den Sender- und Empfngerkanlen festgelegten Berechtigungen weitergegeben. Die Daten werden auch zwischen einer beliebigen Anzahl von Kanalklonen synchronisiert, so dass Hub-Mitglieder auch dann auf Daten zugreifen und nahtlos weiter zusammenarbeiten knnen, wenn ihr primrer Hub nicht erreichbar oder offline ist.
Zot bietet auch eine nomadische Identitt, so dass Ihre Kommunikation mit Freunden, Familie oder anderen Personen, mit denen Sie kommunizieren, nicht durch den Verlust Ihres primren Kommunikationsknotens beeintrchtigt wird - entweder vorbergehend oder dauerhaft.
Die wichtigen Teile Ihrer Identitt und Ihrer Beziehungen knnen auf einem USB-Stick, dem Laptop oder PC gesichert werden und jederzeit an einem beliebigen Knoten im Netz erscheinen - mit all Ihren Freunden und Vorlieben.
Entscheidend ist, dass diese nomadischen Instanzen synchron gehalten werden, so dass jede Instanz bernehmen kann, wenn eine andere gefhrdet oder beschdigt ist. Dies schtzt Sie nicht nur vor greren Systemausfllen, sondern auch vor vorbergehender berlastung der Website und staatlicher Manipulation oder Zensur.
Die nomadische Identitt, die einmalige Anmeldung und die Dezentralisierung von Hubzilla gewhrleisten ein hohes Ma an Widerstandsfhigkeit und Bestndigkeit in der Internetkommunikation. Mittels magic-auth meldet man nur einmal an Ihrem Heimat-Hub (oder einem nomadischen Backup-Hub) an. Dadurch kann man auf alle authentifizierten Dienste zugreifen, die berall im Netz angeboten werden - wie Einkaufen, Blogs, Foren und Zugang zu privaten Informationen. Das Passwort wird nicht auf tausend verschiedenen Websites gespeichert, sondern auf Servern, man selbst kontrolliert oder denen man vertraut.
Zugriffskontrolle: Die Identittsschicht von Zot ermglicht es, fein abgestufte Berechtigungen fr jeden Inhalt zu vergeben, den man verffentlichen mchte. Diese Berechtigungen erstrecken sich ber das gesamte Grid. Das ist so, als htte man eine riesige Website, die aus einer Grozahl von kleinen, individuellen Websites besteht und bei der jeder Kanal im Grid seine Datenschutz- und Freigabeprferenzen fr alle von ihm erstellten Webressourcen vollstndig kontrollieren kann.
Derzeit untersttzt Hubzilla die Zugriffskontrolle fr viele Datentypen, darunter Diskussionsbeitrge und -kommentare, Fotoalben, Veranstaltungen, Cloud-Dateien, Webseiten, Wikis und mehr. Jedes Objekt und die Art und Weise, wie und mit wem es geteilt wird, unterliegt vollstndig Ihrer Kontrolle.
Im Grid braucht man keine riesige Benutzerdatenbank auf dem Rechner, denn das Grid ist die Benutzerdatenbank. Sie verfgt ber eine im Grunde unendliche Kapazitt (begrenzt durch die Gesamtzahl der Hubs, die im Internet online sind) und ist auf unzhlige Computer verteilt.
Der Zugang kann, berall im Grid, fr jede Ressource, jeden Kanal oder jede Gruppe von Kanlen gewhrt oder verweigert werden. Andere knnen auf die eigenen Inhalte zugreifen, wenn es ihnen erlaubt wird, und sie mssen nicht einmal ein Konto auf dem selben Hub haben.
Aktuell verwendet Hubzilla das Zot-Protokoll in der Version 6 (Zot6).
#FediTips #FediverseTips #hubzilla #hubzillahppchen
#Long #LongPost #CWLong #CWLongPost Dir vielleicht. Den anderen hier im Thread vielleicht. Und jetzt aktuell vielleicht.
Aber auerhalb eurer Bubble gibt es jetzt schon Leute, die KI als das ultimative Werkzeug fr Beschreibungen von Bildern aller Art anpreisen. Vielleicht geben sie zu, da KI jetzt im Augenblick noch die eine oder andere Schwche bei weniger bekannten Themen hat. Aber schon bald wird sie auch die perfekt beschreiben und erklren knnen, wobei so getan wird, als wre "schon bald" = "sptestens diesen Donnerstagnachmittag".
Und ich schtze, sptestens im Sommer 2024 wird man frs Selbstschreiben als ewiggestrig ausgelacht:
"Diese Bildbeschreibung habe ich selbst geschrieben."
"Hahahahaha. Boah, bist du von gestern. Schon mal was von KI gehrt Ey, 2022 hat angerufen, es will seine handgeschriebenen Alt-Texte wiederhaben!"
Sptestens wenn eine Mehrheit auf Mastodon glaubt, KI-Beschreibungen seien detaillierter, akkurater und informativer als alle handgeschriebenen, auch als meine Zigtausend-Zeichen-Beschreibungen, sptestens dann habe ich ernsthaft ein Problem damit. Und die Frage ist nicht, ob das kommt, sondern wann.
Deswegen will ich ja auch den Vergleich mit KI machen. Auch wenn dann jemand kommt und sagt: "Ja, mit der KI, aber ChatGPT knnte das viel besser!"
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost Da, wo ich bin, sowieso nicht. Da wre es schwierig genug, mir die Mglichkeit, hndisch Alt-Text zu schreiben, gnzlich zu nehmen. Und automatisch generierter Alt-Text wird da mit sehr groer Wahrscheinlichkeit eh nie eingefhrt.
Mir geht es eher um die, die KI als das ultimative Alt-Text-Allheilmittel ansehen und anpreisen, das wirklich jedes Bild korrekt beschreiben kann. Es wird nicht mehr lange dauern, und man wird dafr ausgelacht, da man seine Bildbeschreibungen selbst schreibt, weil "man" das doch "heutzutage" von einer KI machen lt.
Ich glaube ja, da zumindest auf Mastodon einige es gern htten, da nicht nur standardmig eine Bildbeschreibungs-KI eingehngt wird, sondern da obendrein die Option, eigene Bildbeschreibungen zu schreiben, entfernt wird. Die Wahl zu haben, macht alles komplizierter, und jedes zustzliche Bedienelement auch.
Ich habe ja eventuell vor, eine KI, allerdings nicht ChatGPT, mit einem meiner Bilder zu fttern, dann die daraus resultierende Bildbeschreibung meiner eigenen schon vorhandenen gegenberzustellen und anschlieend die KI-Bildbeschreibung Stck fr Stck zu sezieren, um aufzuzeigen, wo sie Schwchen hat. Das wird ein Spa, auch wenn's mal wieder keiner lesen wird, weil das nicht in unter 500 Zeichen gehen wird.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPostNow I'm pondering on how to demonstrate the differences between an AI-generated image description and my hand-made one for the same picture.
Should I do it in a post that federates, even though it'll definitely exceed 500 characters by magnitudes Or should I do it in an article and then link to the article I'm afraid Mastodon users won't read it either way, but this can't be done in 500 characters or less, unless I made it a massive thread.
Should I include my own description in the post, or should I link to it Both would be inconvenient. And I'm talking about descriptions of 25,000 to 40,000 characters, by the way. Each of them. For one image each.
But if I included the image itself, I would have to give a full, detailed description, so I would have to include my own description at its full extent. Another reason why this can't be done in 500 characters or less.
Should I dissect the AI-generated description, review it bit by bit and point out missing, inaccurate and out-right false information
#Long #LongPost #CWLong #CWLongPost #AI #AIsOfTheBlind #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta   Hubzila-Hppchen: Foren
Foren sind , die von der Funktion einem normalen Internet-Forum bzw. Gruppen aus anderen Sozialen Netzwerken hneln. Wenn man sich mit einem Forum verbindet, hat man drei Mglichkeiten, Beitrge im Forum zu posten:








Die Teilnahme an Hubzilla-Foren ist auch mit einem (streams)-, einem Friendica- und einem Mastodon-Account mglich. Mit Forkeys-Diensten ist es derzeit (Hubzilla Version 8.x) mit Einschrnkungen mglich, es kann zu Fehlern (kein Verteilen der Postings) kommen. Mit Version 9 von Hubzilla soll es dann auch mit diesen Diensten funktionieren.
#FediTips #FediverseTips #hubzilla #hubzillahppchen
#Long #LongPost #CWLong #CWLongPost
Foren sind , die von der Funktion einem normalen Internet-Forum bzw. Gruppen aus anderen Sozialen Netzwerken hneln. Wenn man sich mit einem Forum verbindet, hat man drei Mglichkeiten, Beitrge im Forum zu posten:








Die Teilnahme an Hubzilla-Foren ist auch mit einem (streams)-, einem Friendica- und einem Mastodon-Account mglich. Mit Forkeys-Diensten ist es derzeit (Hubzilla Version 8.x) mit Einschrnkungen mglich, es kann zu Fehlern (kein Verteilen der Postings) kommen. Mit Version 9 von Hubzilla soll es dann auch mit diesen Diensten funktionieren.
#FediTips #FediverseTips #hubzilla #hubzillahppchen
#Long #LongPost #CWLong #CWLongPost
The Fediverse needs a shared AI.

The Fediverse must never, under no circumstances whatsoever, have to firmly rely on something centralised. Ever.
What the Fediverse "needs" is better permission control for its users over who can send them what. Hubzilla has it. (streams) has even more of it. The reason why neither of the two felt the spam wave is not because they're so small. But Mastodon in particular is too much geared towards people who don't want to use anything that's more complicated than Twitter.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta The high risk is that people come straight from Mastodon, the only Fediverse project they're used to, to Hubzilla in expectation of something that works and handles like Mastodon plus whatever extra stuff on top Hubzilla has that attracted them. I mean, there are people who came to Hubzilla simply because they wanted more than 500 characters.
And then they end up tripping over things that make Hubzilla not more than Mastodon but unexpectedly different from Mastodon. The one-post-many-comments conversation model. The permissions settings that don't even default to the same behaviour as Mastodon which doesn't even really know such a thing as permissions. "Quote-toots" but no boosts. No content warning field until they find out that it's that thing labelled "Summary" for some reason. No alt-text field. Hopelessly outdated user documentation that also reads like a tech spec. No local timeline, no federated timeline. Everything being named differently. Generally, Hubzilla not mollycoddling its users, not even newbies. And so on.
I mean, some return to Mastodon with a "Hubzilla sucks" verdict because they failed to connect to even one of their old Mastodon acquaintances, because nothing and nobody told them right off the bat that they have to turn ActivityPub on first, much less how to do that.
If many more Mastodon users tried out Hubzilla and really tried, there would be more voices demanding Hubzilla be much more like Mastodon. Just like there are Twitter refugees on Mastodon who, after many months of using Mastodon, still can't get used to its differences from Twitter and demand things be just like on Twitter, including a secret-sauce algorithm that automagically fills their personal timeline with exactly what they want to read without themselves having to do anything (not that actually did that) and sends their post to the local timelines of everyone who's interested in that.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla
I'm guessing you won't even see this but I will give it a try anyway.

I can see this with no problem. Don't worry.
First, you seem to be under the impression that Mastodon doesn't allow long posts, but in fact the length is determined by the instance. The one I use (infosec.exchange) allows 11000 charactrer posts. I do wish there was a listing of instances that allow long posts, so people could find them more easily.

Well, to be fair, my latest information was that the character limit is semi-hard-coded in the source code. There is no setting for that on the admin UI. So basically, if a Mastodon admin changes the character limit of their instance, they create a soft fork of Mastodon.
Besides, the reason for my long-post warning hashtags wasn't you. It was those thousands upon thousands of users of vanilla Mastodon who are highly irritated whenever they encounter a post that's over 500 characters long. I give them a chance to filter at least my long posts out.
Second, you mentioned a bunch of #Fediverse projects that you say allow quote-toots. But you don't say which, if any, of them also allow long posts (when clearly that is important to you - it is to me also) AND have publicly available web-based interfaces. I don't want to run a private instance.

All of them have public instances with open registration and Web interfaces I think even fairly new Catodon has at least one.
I expect Catodon to be listed by Fediverse instance listers sooner or later. The only one that will never appear there is (streams).
Character limits:
*The amount of alt-text that can actually be read is limited by how much alt-text the Web interface on one's own device can show at once because the alt-text cannot be scrolled.
The is one of the other big problems with #Mastodon and the Fediverse - there is really no good way, especially when you first sign up for Mastodon, do discover the differences between instances. Do they allow quote-toots Do they allow long toots Do they have an administrator that doesn't go around blocking other instances on a whim, or for personal reasons (I'm okay with some blocking, such as fascist or hate instances) Does the instance have more than just a handful of users If I use that instance, am I likely to be blocked by other Fediverse sites (I don't want to be blocked because some asshole is using the same instance I use to spam or spread hate) None of that is publicly available information.

Some instances publicly advertise their raised character limit, but only on their Web frontend. If you're on a phone, and you see your Web browser as a nuisance, and you register via an app, you can't see it.
Also, siteinfo sadly doesn't transmit such information. Otherwise it could be included in automated instance lists.
As for quote-posts, all Mastodon instances that have upgraded to 4.x can display them. Only those that are still on 3.x can't, but I guess most of them are fediblocked because they're so undermaintained that there's no admin to stop the spam they're spewing. But I'm not sure if there are forks that can generate quote-posts.
And honestly, I think that may wind up being what relegates Mastodon to also-ran status. I'm not saying it will go away, but it will always be as Linux is to computer operating systems - only used by the select few that are willing to put up with its eccentricities. Even just asking people to pick an instance, or in the alternative putting them into one of the least-fully-featured instances by default, is always going to be a big turnoff for some users.

To be fair, mastodon.social isn't exactly one of the least-fully-featured instances. It's usually the second to get new features. mastodon.online gets them first, and if they don't break it, mastodon.social is next.
Of course, mastodon.social only has features which Rochko wants to see on Mastodon.
But generally, I think it's still having to pick an instance instead of having only one to begin with, or instead of having a Hogwarts Sorting Hat-style AI that automatically picks the ideal instance for them by reading their minds, that scares people away. This is also why Fediverse newbies are being mollycoddled until they've settled in and made themselves comfortable, even if it means that it takes them three months to find out that Mastodon is not a centralised silo and half a year to find out that even the Fediverse isn't only Mastodon.
The strength of Mastodon is that it is decentralized, but that can also be its major weakness, because PEOPLE run instances and people have their own biases, and some people can be real assholes if given even a small bit of power (think: some Reddit moderators).

Speaking of which, see also those many first-wave Reddit refugees who had piled onto lemmy.ml because that was all they knew, and who then came to the realisation that the instance is run by two staunch tankies.
But I have a feeling you will never see this anyway, because you use Hubzilla which apparently blocks rerplies by default.

Again, no problem. Unless I've explicitly disallowed someone to reply to me (and I'd have to jump through hoops to do that) or muted, blocked or Superblocked someone, I can see their replies all right. In fact, I automatically follow all threads that appear on my channel stream, and if someone in such a thread mentions me and/or directly replies to me, I get a special notification or two.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta  


Die App Kontakt-Rollen dient dazu Rollen (also eine Sammlung von Rechten und Mglichkeiten) fr Kontakte zu erstellen. Diese Rollen knnen dann einem Kontakt oder allen Kontakten einer Privacy Gruppe (nicht der Gruppe selbst) zugewiesen werden. Damit werden die Mglichkeiten von Kontakten eingeschrnkt oder erweitert.

Die Rollenberechtigungen sind:

Bei der Auswahl der Rollenberechtigungen ist zu beachten, dass einige Berechtigungen durch die Kanal-Berechtigungen vererbt werden. Diese vererbten Berechtigungen haben Prioritt, knnen also hie nicht berschrieben werden.
In der App kann man bestehende Rollen bearbeiten und neue Rollen erstellen.


Mit dem Button "Absenden" werden die Berechtigungen der Rollen gespeichert.
#FediTips #FediverseTips #hubzilla #hubzillahppchen
#Long #LongPost #CWLong #CWLongPost

' Covid may be due to leaky , study finds

If barrier controlling substances entering and exiting brain is off balance, it can drive changes in neural function''

You say...
the #fediverse and #Mastodon
...but you obviously only mean Mastodon.
More Fediverse projects support "quote-toots" than not right now. Misskey does. Firefish, Iceshrimp, Sharkey, Catodon and all the other Forkeys do AFAIK. Friendica does and has basically done so since 2010, almost six years before there was even Mastodon. Hubzilla indirectly inherited that feature from Friendica, still as early as 2015. And (streams) has it, too.
Here, let me "quote-toot" you as a demonstration, although I'm on Hubzilla, thus I don't toot, and I "share" instead:
The one thing I really wish that the and offered, particularly in their web-based clients, is . But failing that, when boosting a toot I truly wish there were a way to add a or even several . So often I see toots that probably should be seen by a wider audience, but because they contain no hashtags, even if I boost them they probably don't go very far. If I could add relevant hashtags at the time of boosting, I think it would help.
However I can see how this could be misused, so such a feature would need to identify excatly who added the hashtags with some kind of credit/blame line, such as "hashtag(s) added by userinstance"

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Firefish #Iceshrimp #Sharkey #Catodon #Forkey #Forkeys #Friendica #Hubzilla #Streams #(streams) #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuotePost #QuotePosts #QuoteBoost #QuoteBoosts #QuotedShares   Hubzilla-Hppchen: Mein Profil
Bei Hubzilla gibt es keine Klarnamenpflicht und man muss in seinem Profil keine zustzlichen Angaben machen.
Klickt man im Hauptmen (oben links) auf den Menpunkt Profile bearbeiten, dann werden die vorhandenen Profile angezeigt. Das Standard-Profil ist immer vorhanden. Whlt man dies per Klick, landet man in den Profil-Einstellungen. Hier kann man (man muss aber nicht das kannst Du selbst bestimmen) mehr oder weniger persnliche und auch allgemeine Angaben zu sich selbst festlegen. Bei den Einstellungen kann man brigens festlegen, wer welche Profilangaben sehen kann und wer nicht das kann ffentlich sein oder auf Nutzer beschrnkt, mit denen man verbunden ist etc.
Etliches wird man nicht angeben wollen das ist ok die Angaben sind optional.
Wirklich sinnvoll ist es aber, dort unter Verschiedenes das Feld Schlsselwrter, die in Verzeichnis-Auflistungen verwendet werden mit Begriffen zu befllen. Diese Schlsselwrter werden im Verzeichnis verwendet und erleichtern es anderen, den eigenen Kanal anhand von Interessen zu finden.

Weil viele, bevor die sich mit einem Kanal verbinden, im Profil schauen, mit wem sie es da evtl. zu tun haben, kann es auch von Vorteil sein, das Feld Erzhle uns ein wenig von Dir mit einigen Informationen zu versehen.
Auch ein Profilbild macht einen Kanal persnlicher, einfacher zu erkennen und kann zu interessanten Verbindungsanfragen fhren.
Aber wie gesagt ALLE Angaben sind freiwillig
Ist man mit der Verfeinerung des Profils fertig, sollte man sein Hubzilla organisieren dazu mehr im Eintrag .
#FediTips #FediverseTips #hubzilla #hubzillahppchen
#Long #LongPost #CWLong #CWLongPost
Bei Hubzilla gibt es keine Klarnamenpflicht und man muss in seinem Profil keine zustzlichen Angaben machen.
Klickt man im Hauptmen (oben links) auf den Menpunkt Profile bearbeiten, dann werden die vorhandenen Profile angezeigt. Das Standard-Profil ist immer vorhanden. Whlt man dies per Klick, landet man in den Profil-Einstellungen. Hier kann man (man muss aber nicht das kannst Du selbst bestimmen) mehr oder weniger persnliche und auch allgemeine Angaben zu sich selbst festlegen. Bei den Einstellungen kann man brigens festlegen, wer welche Profilangaben sehen kann und wer nicht das kann ffentlich sein oder auf Nutzer beschrnkt, mit denen man verbunden ist etc.
Etliches wird man nicht angeben wollen das ist ok die Angaben sind optional.
Wirklich sinnvoll ist es aber, dort unter Verschiedenes das Feld Schlsselwrter, die in Verzeichnis-Auflistungen verwendet werden mit Begriffen zu befllen. Diese Schlsselwrter werden im Verzeichnis verwendet und erleichtern es anderen, den eigenen Kanal anhand von Interessen zu finden.

Weil viele, bevor die sich mit einem Kanal verbinden, im Profil schauen, mit wem sie es da evtl. zu tun haben, kann es auch von Vorteil sein, das Feld Erzhle uns ein wenig von Dir mit einigen Informationen zu versehen.
Auch ein Profilbild macht einen Kanal persnlicher, einfacher zu erkennen und kann zu interessanten Verbindungsanfragen fhren.
Aber wie gesagt ALLE Angaben sind freiwillig
Ist man mit der Verfeinerung des Profils fertig, sollte man sein Hubzilla organisieren dazu mehr im Eintrag .
#FediTips #FediverseTips #hubzilla #hubzillahppchen
#Long #LongPost #CWLong #CWLongPost Open a Web browser if you haven't already.
Go to .
Log in.
Burger menu near the top left, below the search field, next to your name, above the post editor.

On the sidebar to the left,
Click or tap the button "Add new filter" in the top right corner.
Write "Long-ass posts" under Title.
Under Filter contexts, check Home and lists, Notifications, Public timelines, Conversations.
Under Filter action, if you want them hidden behind an automated CW, leave Hide with a warning selected. If you want them gone, choose Hide completely.
Further down, under the sub-headline KEYWORDS, write "#LongPost" under Keyword or phrase.
Click or tap Add keyword.
Write "#CWLong" under Keyword or phrase.
Click or tap Add keyword.
Write "#CWLongPost" under Keyword or phrase.
Click or tap the big SAVE NEW FILTER button at the very bottom.
Congrats, you have a filter against my long posts.
CC:
#Long #LongPost #CWLong #CWLongPostScott M. Stolz It's a bit murky what exactly happened back then.
Friendica started as Mistpark before a German told Mike what a German understands when reading that word, namely manure park. It was then renamed to Friendika because the desired Friendica domain was still blocked.
Free Friendika was a fork of Friendika by someone who wasn't content with Friendika's license. Free Friendika was on GitHub right away while Friendika wasn't. The fork involved copying Friendika's whole repository to GitHub.
Friendika was renamed Friendica in 2011 or 2012 when that name had become available.
It was afterwards that Friendica's own code repository was migrated to GitHub. Due to a GitHub "quirk", Friendica was automatically declared a fork of Free Friendika which is technically false.
What exactly happened license-wise is murky to me. Friendica can't have started under the AGPL because that'd exclude re-licensing a fork. But interestingly, Hubzilla is MIT-licensed.
So whatever license Friendica started out under, it might have been the community which put it under the AGPL after taking over from Mike who was now tinkering with the Zot protocol.
Looking at the licenses, it's very likely that Mike didn't fork Friendica Red off Friendica but off Free Friendika, itself a hard fork of Friendika. Thus, some improvements on Friendica never made it to Friendica Red.
I also guess it was named Friendica Red first and then renamed Red (from spanish la red = "the net") after the whole backend had been re-written against Zot, and the whole thing had stopped being Friendica in the first place. The re-naming to Red Matrix must have been a kind of marketing decision.
It's even unclear what exactly was the base for Osada later. Case in point: Well after the release of Hubzilla, Mike's own instances were still all branded "Red Matrix" although this project should have been abandoned in early 2015 when Hubzilla was created from it.
So either the Red Matrix was renamed Hubzilla and reworked into what was Hubzilla 1.0 in July, but Mike kept the "Red Matrix" brand for his own instances. In this case, Osada was forked from Hubzilla, and most everything added from the Red Matrix to Hubzilla was removed again from Hubzilla to Osada.
Or Hubzilla was forked from the Red Matrix, mostly soft-forked, the Red Matrix became Hubzilla's smaller and more experimental brother, and Mike's own instances all became testbeds for development that would have been more difficult with the extra Hubzilla cruft in the way. In this case, chances are bigger that Mike forked Osada from the Red Matrix which had never had all that extra Hubzilla stuff that Osada never had either.
Either way, the path from Mistpark to Hubzilla is both very complicated and very murky, and so I guess it's kind of justified to simplify it a bit. At the same time, it's too short to simplify it the same the path from either the Red Matrix or Hubzilla to (streams) can be simplified because the latter has had many more forks in it ("a fork of a fork... of a fork of Hubzillathe Red Matrix").
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Forks #Mistpark #Friendika #FreeFriendika #Friendica #RedMatrix #Hubzilla There were another two threads about Bridgy Fed creating a bridge to Bluesky. And again, people loudly demanded the Fediverse be ActivityPub only.
Thing is, the Fediverse has never been ActivityPub only. Mastodon started in 2016 with OStatus because, like Pleroma earlier the same year, it started as an alternative frontend for GNU social. So GNU social was based on OStatus, and both Friendica and Hubzilla already knew it, too. At that point, the term "Fediverse" was already some four years old.
It was only in September of 2018 that Mastodon announced the introduction of ActivityPub as an additional protocol. Hubzilla had done so two months earlier, so Mastodon has never even been the only ActivityPub project.
But the vast majority of Mastodon users seems to think that Eugen Rochko invented a) Mastodon, b) ActivityPub and c) the Fediverse and d) did so in 2022 as a reaction upon Musk's announcement to take over Twitter. And literally everything else in the Fediverse was made after Mastodon.
Not only that, but the Bluesky bridge threads made it painfully obvious that a two-digit percentage of Mastodon users is still fully convinced that the Fediverse is actually nothing but Mastodon. Because they clearly want to fight for it remaining that way, unaware that is isn't that way.
I think when Hubzilla and Friendica users joined the threads and started commenting, these folks either ended up deeply disturbed with their worldviews shattered to rubble upon the revelation that there's more in the Fediverse than Mastodon already now. Or they didn't even notice that these posts a) talked about non-Mastodon Fediverse projects which are reality now and b) came from outside of Mastodon, no matter how blatantly obvious it was that these posts could impossibly have been sent from Mastodon.
The rest might be aware that there's more to the Fediverse than Mastodon. But this "more" is limited to Pixelfed and PeerTube and what they think must essentially be Mastodon with a different UI.
It was just as painfully obvious that just about none of the Mastodon users who posted on these threads and railed loudly against bridges of any kind knows that stuff is bridged to Mastodon already now and has been bridged to Mastodon since Mastodon's own launch. This stuff currently is Hubzilla and (streams), none of which are based on ActivityPub.
Granted, in these cases, we aren't talking about one big third-party bridge for everyone. The bridge in question is named "PubCrawl", it's a first-party add-on to both Hubzilla and (streams) that comes with the server application itself, so while not firmly baked into their cores, it's an official part of them, and there's one individual bridge for each channel. But yes, there are bridges.
This is one thing I'd like to explain in such a "snippet". Other things would be, for example:

Now, this is not meant to be advertisement. It's more like a series of public service announcements to raise Hubzilla awareness.
I'm well aware that it could also have the effect of triggering or increasing anti-Hubzilla campaigning on Mastodon. I mean, most Mastodon users probably don't even know that Hubzilla exists, and most of who do don't know what Hubzilla can do. And large parts of what it can do fall under "atrocities" and "breaking the Fediquette" from a Mastodon point of view. Mastodon doesn't riot against that stuff because it doesn't know about that stuff.
But if such riots broke out because Hubzilla is so not like Mastodon and even refuses to be more like Mastodon, that'd tell a lot about Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla This could have one or several out of many reasons.
One, people on certain projects prefer to interact with people on the same or similar projects anyway, also due to overarching cultures. For example Misskey and Sharkey which have "UwU kawaii desu" written all over them while Mastodon doesn't.
Two, similarly, a refusal to let Mastodon users connect because this increases Mastodon's pressure on non-Mastodon projects to abandon their own culture in favour of Mastodon's.
Three, vice versa, Mastodon and its users rejecting the culture of non-Mastodon projects whenever it differs from Mastodon's. Many Mastodon users want everything that is "un-Mastodon-like" banned all across the whole Fediverse because it disturbs them, be it posts over 500 characters, be it quotes, be it "quote-tweets", be it text formatting in any way. However, all this stuff is perfectly normal and absolutely part of the culture everywhere outside of Mastodon.
So on the one hand, you have Mastodon users blocking everyone who does stuff that's alien to Mastodon upon first strike, depriving them of exposure and range on Mastodon. Plus everyone who ever talks about the Fediverse without only talking about Mastodon. On the other hand, you have non-Mastodon users who refuse to post to Mastodon users in the first place in order to avoid this kind of drama. And at least some projects actually allow you to select whom to post to, and yes, including Hubzilla.
Four, for the reasons mentioned above, some non-Mastodon users never even expose their accounts/channels to Mastodon, so nobody on Mastodon knows them. Some Hubzilla and (streams) users go another step further: If they're on (streams), they turn ActivityPub off altogether to keep themselves away from all the drama on Mastodon, and if they're on Hubzilla, they intentionally don't turn it on in the first place. This shields them from Mastodon practically entirely.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMetaMaybe I should start an irregular series of "What Hubzilla is like" posts for people in the Fediverse, Mastodon specifically, who don't know anything about it. Not for those who want to switch, but for those who assume that Hubzilla is just like whatever else they know. Like, for Mastodon users who blindly assume that Hubzilla is just like Mastodon with a different UI and then act accordingly. Thus, it'd mostly focus on how Hubzilla is different from Mastodon.
The difficult part would be to limit these posts to only 500 characters. Minus what I'll need for the hashtags, namely #Hubzilla, #FediTips and #FediverseTips to increase discoverability for those who are interested and #FediMeta, #FediverseMeta, #CWFediMeta and #CWFediverseMeta so that these posts are automatically removed or hidden behind generated content warnings by already existing filters. Because I know for a fact that many Mastodon users won't touch anything that goes even a smidge over 500 characters. And I know that there are Mastodon users for whom any and all Fediverse meta is too nerve-gratingly techy.
#Long #LongPost #CWLong #CWLongPost #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta
Also, ich versteh das sehr gut, solange das nicht automatisiert luft. Es ist eine Krcke, sowas sollten die Computer FR UNS lsen.

So etwas wird KI niemals fr alle 100% perfekt und akkurat ohne menschliche Interaktion hinbekommen. Hashtags nicht, Inhaltswarnungen nicht und Bildbeschreibungen schon mal erst recht nicht.
Perfekt schon deshalb nicht, weil keine KI je sekundenaktuell allwissend sein wird. Das wird sie aber sein mssen, um selbst das obskurste, nischigste Nischenthema perfekt behandeln zu knnen und z. B. beim automatisierten Verhashtaggen eines Posts notfalls auch neue Hashtags wie #OSCC24 erzeugen zu knnen (doch, ich wei, was das ist).
Und fr alle perfekt deshalb nicht, weil jeder im Fediverse andere Bedrfnisse und Prferenzen hat. Da gibt's keinen Konsens. Die einen sind von Twitter nach Mastodon abgehauen und wollen, da das ganze Fediverse so ist, wie sie Twitter kennengelernt haben, wo praktisch niemand Hashtags benutzt hat. Die anderen sitzen seit zehn Jahren auf Friendica und brauchen bestimmte Hashtags zum automatischen Erzeugen von Inhaltswarnungen per Textfilter, aber genau diese Hashtags sind dann fr die meisten Mastodon-Nutzer Unsinn.
Natrlich, der Idealfall wre, wenn du eine allmchtige, allwissende KI auf deinem iPhone httest. Die wrde dir auch ohne Hashtags genau die Posts von berall, aber auch wirklich berall im Fediverse zuspielen, die dich interessieren, noch zuverlssiger, als es der Twitter-Algorithmus angeblich tun soll. Die wrde genau wissen, was fr dich Reizthemen sind, und dann entscheiden, ob sie dir einen Post berhaupt nicht serviert oder hinter einer individuellen Inhaltswarnung versteckt.
Und die knnte auch jedes noch so obskure, nischige Bild fr dich individuell perfekt beschreiben und erklren. Die wte zum einen sekundenaktuell, was du weit, was du nicht weit, was dich interessiert und was dich nicht interessiert. Die wrde erkennen, worauf du in einem Bild gerade zoomst und worauf exakt in dem Bild deine Augen gerade blicken, und daraus selbstndig ermitteln, ob du willst, da sie dir dieses Detail des Bildes im Detail beschreibt und/oder erklrt. Und natrlich htte sie sekundenaktuell das absolute Detailwissen ber jedes Nischenthema berhaupt.
Selbstredend wrde diese KI deinem iPhone trotzdem nicht mal eine Minute an Akkulaufzeit klauen.
CC:
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #CW #CWs #ContentWarning #ContentWarnings #ContentWarningMeta #AltText #Bildbeschreibung #Bildbeschreibungen #BiBesch #AI #KIThis came as a surprise a couple days ago: Opengrid World with and even has re-emerged.
Zoe Synclair, originally the creator and owner of Bernicia/Uzuri, has left OpenSim altogether several months ago, shutting her grid down seemingly for good and thus even making certain content no longer available anywhere. But in a twist of fate, not only the OARs have been handed over to new ownership and management, but so has Zoe's account on OpenSimWorld.
Uzuri Virtual still shows traces of Zoe's idealistic attempt at making a sim that only offers legal freebies.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #Grid #UzuriVirtual #OpengridWorld

weekend

Ich wrde schon fast sagen, das einzige, was es da zu entwickeln gbe, wre eine ansprechendere UI und eine anstndige Dokumentation fr (). Und zumindest eine bessere UI ist sogar schon in Entwicklung, wenngleich auch nicht mageschneidert fr Hochschulen und Forschungseinrichtungen.
Oder wenn man unbedingt etwas Mageschneidertes haben will, dann mu man sich auch nicht hinsetzen und ganz von vorne bei null anfangen. (vom Macher von Hubzilla) nehmen, eigene Add-ons dafr entwickeln und dranhngen, fertig. Genau dafr war das eigentlich immer gedacht.
Ein paar Vorteile von beiden gegenber Mastodon:

Zustzliche, optional aktivierbare Features von Hubzilla, die im Hochschulumfeld interessant wren:

Mit einem einzigen Kanal kann man also sehr, sehr viel auf einmal erschlagen.
Und was auch immer man letztlich nutzt: Ein Umdenken und Umlernen bedeutet es sowieso. Daher ist "Ersetzen wir 'erstmal' durch etwas, was mglichst nahe an ist, und dann sehen wir weiter" ziemlicher Kse, vor allem, wenn man dann versucht, alles Mgliche und Unmgliche an Mastodon anzukleben und anzupassen, weil man ja eben jetzt Mastodon nutzt.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #NichtNurMastodon #Hubzilla #Streams #(streams) Not without starting over from scratch.
Also, I'm always a bit cautious about recommending Fediverse users who came from Mastodon to move directly to Hubzilla. They're likely to expect "Mastodon + xyz" and end up irritated because they find themselves on what might be the polar opposite of Mastodon. Something that handles vastly different from Mastodon through a UI perpetually stuck in 2012 and not even really user-friendly for 2012's standards.
And you might want to ask yourself if you really need (long-form articles, wikis, webpages, admittedly simple graphical front-end for two separate built-in calendar systems etc. etc.).
A better solution would be what's commonly called as mentioned by Mike Macgirvin in this very thread he has created it and maintains it, and he has created all its ancestors all the way to Friendica as well, including Hubzilla.
It has the same spam safety as Hubzilla, but it adds even more on top because it gives you even better control over permissions. It has better ActivityPub integration, and unlike Hubzilla, it doesn't confuse people by having it off by default. It has a similar, but less cumbersome UI, also due to lots of unnecessary features having been cut.
However, public instances are very few and far between and extremely hard to find because it's absent from all Fediverse instance lists. I only know two public instances with open registration, Brazil-based and Waitman Gobble's US-based .
I'm not sure, but I think that (streams) did have an importer for exported Mastodon accounts at some point in the past.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams)Fediverse spam doesn't work as easily here on Hubzilla.
Spammers can try to mention-spam me all they want. I won't even notice. If someone whom I don't follow mentions me outside any thread I follow, I'm neither notified, nor do I receive the mention in my channel stream (= local timeline). Unlike on Mastodon. That is, I could turn this behaviour on on Hubzilla if I wanted to, but it's off by default.
If you want to spam my channel stream, the following criteria have to be met:

Spamming a thread that started on Hubzilla can be prevented by the thread starter. On Hubzilla, the thread starter owns the whole thread, all comments included. If you comment on this post, it's still me who's the owner of your comment within my thread. And I can turn off comments for either specific comments or for the post itself and thereby the whole thread.
And yes, this keeps even Mastodon users from commenting. It may not keep them from sending a post in reply. But that post will not appear in the thread at least for anyone using a project that understands Hubzilla's one-post-many-comments conversation model, myself included.
If bad came to worse, I could even only allow certain users to comment on my posts in the first place. But that'd be overkill.
Oh, and by the way, even if a thread was started by someone else and appears in my channel stream, I can turn off comments for myself, but otherwise the same way that I can turn them off for my own threads. Yes, even if the thread was started on Mastodon.
If it's one bad actor or a few spamming streams and threads: Again, there's Superblock which works regardless of whether I'm connected to someone.
And if bad really came to worse, my last resort would be to pull up the drawbridge and turn ActivityPub off entirely for as long as needed. Then nothing would even be able to come in, not from Mastodon, not from Misskey, not from anything else that uses ActivityPub to communicate with Hubzilla.
Poor Mastodon users who only have "mute", "block" and "hope for mods to step in" at their disposal.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Spam #FediSpam #FediverseSpam #SelfModeration My issue with this is that it'll be something cooked up only by Mastodon admins amongst Mastodon admins with other Mastodon admins, but for the whole Fediverse.
So far, this sounds perfectly fine to Mastodon ears, I know. But very often, these Mastodon admins don't know the first thing about anything in the Fediverse that isn't Mastodon. They blindly assume that everything else is basically Mastodon with a different UI or Mastodon with an extra feature or two, but otherwise just like Mastodon. Just like, when they arrived here, they assumed that Mastodon is Twitter without Elon Musk, but otherwise just like Twitter.
Okay, it still sounds perfectly fine to Mastodon ears. But the Fediverse outside of Mastodon is not just like Mastodon. For one, different projects have different features and different ways of doing things. This, in turn, leads to these projects having different cultures from Mastodon's.
If these projects were developed independently from Mastodon because they're either actually older than Mastodon or direct or indirect forks of something that's older than Mastodon, and if their focus is vastly different from Mastodon's, and if their underlying technology is vastly different from Mastodon's, their culture may be absolutely nothing like Mastodon's.
Yes, such projects actually exist, first and foremost Friendica, Hubzilla and (streams). They differ from Mastodon in ways that are completely unimaginable for people who basically think the Fediverse is only Mastodon. For example, this concerns touchy topics on Mastodon like post length, quote-posts, alt-text and content warnings. But even their threads are designed and structured differently because, unlike Mastodon, they didn't take any inspiration from Twitter.
Also, Hubzilla and (streams) in particular require much less moderation. That's because they give their users very powerful and fine-grained access and communications permission settings and even allow them to moderate any thread they've started themselves. Their groups/forums are moderated by default, and what moderation features are available to groups/forums are available to personal channels all the same. Thus, Hubzilla hubs and (streams) instances never have dedicated moderators.
For those who measure everything by Mastodon's standards, however, they'll appear undermoderated to a degree that justifies or actually requires the defederation of the entire instance for being undermoderated.
I know all this is well-meaning. But it's another case of confusing the Fediverse with Mastodon, a dangerous case even that could lead to the complete defederation of entire Fediverse projects from Mastodon just because of technical differences.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #CodeOfConduct #NotOnlyMastodon #MastodonIsNotTheFediverse #FediverseIsNotMastodon

. This is cruelty and insanity. Cruelty in refusing to take any measures to protect the many people who are immunocompromised. Insanity in refusing to acknowledge the many diseases that are linked with , whether that is OVID, disease, , and more.

Meines Wissens ist alles, was es da an Anleitungen, Tutorials etc. gibt, hoffnungslos veraltet, weil schon ewig niemand nichts Neues mehr in der Richtung gemacht hat.
Da passiert ja auch stndig was. Seit Version 0.9.3.0 luft OpenSimulator ja unter Linux nicht mehr mit Mono, sondern es braucht jetzt dotnet6. Das wiederum heit, du mut Microsoft weit genug vertrauen, um mindestens eine Paketquelle von denen unter Debian einzuhngen. Anders kommst du da nicht ran.
Mehr kann ich dir auch nicht sagen. Bisher hatte ich nicht mal eine eigene Sim, geschweige denn ein eigenes Grid am Laufen.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #OpenSim #OpenSimulator One developer has actually taken this into consideration: Mike Macgirvin , creator of (2010), (2012, officially discontinued in 2015) and (2015) and creator and maintainer of .
(streams), as what comes out of this repository is colloquially called while actually being intentionally nameless, has a vastly different conversation model than Mastodon. It has inherited it from Hubzilla which has inherited it from Friendica which, in turn, was inspired by Facebook rather than by Twitter. All three define conversations as one (1) post plus many comments firmly attached to that post whereas Mastodon defines them as a bunch of posts loosely tied together.
Also, all three have always had support for groups/forums which are nothing but user accounts/ with specific permission settings plus automatic forwarding of incoming posts under certain circumstances. And they've got means of moderation that go beyond what everything else in the Fediverse has to offer and way beyond what Mastodon has.
At least on Hubzilla and (streams), maybe also on Friendica, if you post something, you're the moderator of your own comments thread. You can decide who gets to comment and who doesn't, and you can delete comments. That's because it's you who owns the comments and not whoever writes them.
As Mike has found out, all this can be done in standard ActivityPub, not only to the extents like on Friendica which has successfully switched from its own DFRN to ActivityPub, but even on (streams) which goes the farthest of the three.
However, this still won't work with Mastodon. For starters, Mastodon doesn't know groups, so it doesn't understand groups. This goes to the point where Mastodon users interact with e.g. the Friendica forum , thinking they're interacting with a single Mastodon user who manually boosts everything that comes from there. User-moderated content is even more alien to Mastodon.
Mike is currently reworking (streams)' conversation model into containers that work with the ActivityPub standard without requiring any hacks, also to increase (streams)' compatibility with ActivityPub. But how making it more compatible with standard ActivityPub would make it even less compatible with Mastodon which doesn't even support these parts of ActivityPub because it hasn't implemented them itself.
So he had the choice. Either he'd include a bunch of nasty hacks so that Mastodon understands it. Or he flips Mastodon the bird and sticks to the ActivityPub spec.
Practically all Hubzilla and (streams) users who commented on this encouraged him to do the latter. It might mean that (streams) will appear "broken" to Mastodon users, most of whom think that Mastodon = the standard. But precious few Mastodon users use groups in the first place anyway.
Mike himself reconsidered and because Mastodon needs groups after almost eight years of not having any.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMetaI've read an interesting comparison the other day: Mastodon is the Internet Explorer 6 of the Fediverse.
It's underwhelming. It's underequipped. It lacks features that are standard just about everywhere else. It's actually hopelessly outdated. In fact, it's even insecure, also due to how it lacks security features that competitors have readily available. And it ignores officially defined standards and tries hard to force the whole FediverseWeb to adopt its own non-standard solutions instead.
At the same time, however, for many many users, it is the FediverseInternet, full stop.
For the vast majority of FediverseInternet users, it was the first Fediverse projectWeb browser they came across because that's what they were mouth-fed when they started with the FediverseInternet. For quite a long time, it was the only Fediverse projectWeb browser they even knew existed, and for many, it still is. Alternatives are only known to and used by the tech-savvy, and they're also the only ones who are aware of how dangerously lacking it is.
Thus, it has vastly more users than all its alternatives combined. Its market share is such that its developers don't even have to care for standards compatibility or what advantages the competition has. They can force their way upon everyone and everything.
Even many websites are built hard against only Mastodonthe Internet Explorer and malfunction or completely refuse to work with any of its alternatives, not seldomly because their developers don't even know that alternatives exist. And few developers dare to build websitesFediverse projects only according to HTMLActivityPub standards, even if that means breaking compatibility with Mastodonthe IE6.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Comparison #Fediverse #Mastodon #NotOnlyMastodon #MastodonIsNotTheFediverse #FediverseIsNotMastodon #InternetExplorer #InternetExplorer6 #IE6 Such transcripts don't go into alt-text. I mean, into the alt-text of what should they even go
They go into the post itself, of course. At least I hope that there's enough room for that on Funkwhale and/or Castopod. And nobody would host a podcast on Mastodon which, except for Threads, is the only Fediverse project with a 500-character limit.
As for my image descriptions, as I've said, these monsters go into the post text body. Right where you have a 500-character limit, and I don't have any limit whatsoever at all. The three links in my previous comment should demonstrate how I do it.
It isn't very accessible to have blind or visually-impaired users open a separate webpage just to have an image described, especially if they're on a phone, and they have the post with the image in one app (their Mastodon app) and the description in another (their browser). It's always best to have the image and the description in the same place.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts #MediaDescription #MediaDescriptions #Accessibility #A11y I'm serious in everything.
When I said I write extremely long image description, .
And just like visuals need to be described for non-sighted people, audio needs to be described for people without or with impaired hearing. At least, pure spoken word audio needs verbatim transcripts. But I'm pretty sure there are people in the Fediverse who demand written descriptions for all audio in the Fediverse.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Transcript #Transcripts #MediaDescription #MediaDescriptions #Accessibility #A11y Does "native" in the first option only stand for ActivityPub as the base protocol of a project, something that is not optional and cannot be turned off
In that case, Hubzilla and (streams) do not fall into this category.
Or does it stand for protocols that have their own ActivityPub support, be it as the primary protocol, be it as a secondary protocol in their core, be it as an optional plug-in which nonetheless is an official, first-party plug-in
In that case, Hubzilla and (streams) do fall into this category.
The poll would have been more interesting if set up someplace else than Mastodon with more than four options:

The third option includes e.g. Friendica and GoToSocial which add support for other protocols/projects such as Diaspora*.
The fourth option includes Hubzilla and (streams) which aren't based on ActivityPub, but which support ActivityPub through an official add-on that comes with the installation.
The fifth option includes everything that needs Bridgy Fed.
The sixth option includes e.g. Diaspora* and GNU social, both of which are federated with Friendica and Hubzilla which, in turn, can use ActivityPub. They can't directly communicate with Mastodon, but Diaspora* and Mastodon users can comment on the same Friendica or Hubzilla post.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #ActivityPub

We Know How High,
Now
Scientists Reveal How Long a Cannabis High Actually Lasts


That sucks. Why would Gargron waste limited resources on (I guess) FOSS that could be used

I don't necessarily think that Mastodon development intentionally aims for as little compatibility with the rest of the Fediverse as possible. It might just as well be a case of refusing to acknowledge that the Fediverse is more than Mastodon or a case of not even knowing what the rest of the Fediverse can do.
However: Mastodon is notorious for ignoring a) standards and b) stuff that already exists. Mastodon does not fulfill the ActivityPub standard to a tee. It's just as close to it as it has to be and diverts from it wherever it feels like it.
One example is the sensitive flag for images. There's something for this in the official ActivityPub standard. And yet, when Mastodon adopted ActivityPub, it decided to not only have its own home-brew, non-standard, undocumented sensitive flag but to also not support the ActivityPub standard flag at all.
AFAIK, (streams) lets you flag images in your file space as sensitive because Hubzilla does. However, when you flag an image as sensitive, and you embed it into a post that also goes to Mastodon, then Mastodon will treat this image as unflagged. (streams) jumps through a hoop now and puts Mastodon's non-standard sensitive flag on all images in posts that have the hashtag #nsfw and/or #sensitive.
Also, it's strange how long it takes Mastodon to implement quote-posts or groups. Both things that have been around since 2010 when Friendica was launched. There's a whole bunch of Fediverse projects that have groups/forums, for example, the various Reddit replacements. Misskey and all its forks have quote-posts. Friendica, Hubzilla and (streams) have always had both.
So, given Mastodon's track record, chances are that Mastodon's implementation of groups becomes incompatible both with how Lemmy communities and /kbin magazines work and with how Friendica, Hubzilla and (streams) have groups/forums implemented.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Groups
I pay attention to such thinks, but even with hindsight, I do not see such a group reference.

That's because Mastodon doesn't tell you that

On #Mastodon, groups are also possible, but I forgot how to use them, as I used them so little.

Not yet. They're working on it. And everything else that has working groups/forums now is afraid that Mastodon will re-invent the wheel in a way that's the most incompatible possible to what already exists on more than half a dozen Fediverse projects.
What you mean is probably Guppe, but that isn't built into Mastodon and a far cry from what's possible on Friendica.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Groups
Last updated: 2024-02-26






joke Divorce document