lingo.lol is one of the many independent Mastodon servers you can use to participate in the fediverse.
A place for linguists, philologists, and other lovers of languages.

Server stats:

64
active users

#hubzilla

0 posts0 participants0 posts today

Die #Fedicamp-Website ist live! :rm_party:

Alle Infos zum diesjährigen Fedicamp findest du jetzt online:
📅 Termine, 📍 Location, Programm und vieles mehr!

🎫 Plätze können ab sofort gebucht werden – sichere dir deinen Spot und sei Teil dieses einzigartigen Events!

🌐 fedi.camp/
🎮 2025.fedi.camp/ !!Vorsicht hier flimmert es viel!!

Wir freuen uns auf dich – lass uns gemeinsam ein unvergessliches Camp erleben! :rm_love:

fedi.campFedicampFedicamp

🎉 Die heutige Fediverse-Sprechstunde ist beendet!

Ein herzliches Dankeschön geht an @Ranslite für seinen spannenden Beitrag zum Thema #Lemmy. Wir hatten eine lebendige Runde mit mehreren Lemmy-Nutzern und konnten gemeinsam einen fundierten Eindruck von der Plattform gewinnen.

Mein besonderer Dank gilt auch allen Teilnehmenden, die sich aktiv eingebracht und damit erneut zu einer gelungenen Veranstaltung beigetragen haben.

🎥 Den Link zur Aufzeichnung werde ich morgen veröffentlichen.

🗓️ Der nächste Termin steht bereits fest:
Donnerstag, 22.05.2025 um 19:30 Uhr
Das Thema wird noch gesucht – Vorschläge sind herzlich willkommen!
Weitere Infos folgen in Kürze.

Lang lebe das Fediverse! 🚀🌐
#Fediverse #Mastodon #Hubzilla #Friendica #Peertube #Lemmy

Replied in thread
@AJ Sadauskas
I mean, the Fediverse already has Lemmy, KBin, and MBin.

So there's already an ecosystem of pre-built communities out there.

/kbin is dead. Has been since last year. The last instances that haven't moved to Mbin are withering away.

However, in the "Lemmy clone" category, there's also PieFed, and Sublinks is still in development.

Also, the Facebook alternative Friendica ("Facebook alternative" not as in "Facebook clone", but as in "better than Facebook") has had groups since its launch in, 2010, five and a half years before Mastodon. Hubzilla has had groups since 2012 when it still was a Friendica fork named Red. (streams) (2021) and Forte (2024) have groups, too. All four are part of the same software family, created by the same developer. And interacting with their groups from Mastodon is somewhat smoother than interacting with a Lemmy community.

On Friendica, a group is simply another user account, but with different settings: In "Mastodon speak", it automatically boosts any DM sent to it to all its followers. In reality, it's a little more complicated because, unlike Mastodon, Friendica has a concept of threaded conversations. (No, seriously, Mastodon doesn't have it. If you think Mastodon has it, use Friendica for a year or two as your only daily driver, and then think again.)

Likewise, on Hubzilla, (streams) and Forte, it's another channel with similar settings.

CC: @myrmepropagandist @Jasper Bienvenido @sebastian büttrich @Asbestos

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #FediverseGroups #Groups #PieFed #Sublinks #Friendica #Hubzilla #Streams #(streams) #Forte
joinfediverse.wikiFriendica - Join the Fediverse
Replied in thread
@Jorge Candeias Bad idea. (Hubzilla user here.)

Hashtags are not only for discoverability (and critically so on Mastodon). They're also the preferred way of triggering the automatic generation of individual reader-side content warnings.

Content warnings that are automatically generated for each user individually based on keyword lists have a long tradition in the Fediverse. Friendica has had them long before Mastodon even existed, much less before Mastodon hijacked the summary field for content warnings. Hubzilla has had them since its own inception which was before Mastodon, too. (streams) has them, Forte has them.

On all four, automated reader-side content warnings are an integral part of their culture. And users of all four (those who are not recent Mastodon converts at least, i.e. those who entered the Fediverse by joining Friendica in the early 2010s) insist in automated reader-side content warnings being vastly better than Mastodon's poster-side content warnings that are forced upon everyone all the same.

Oh, and by the way, Mastodon has this feature, too. It has only introduced it in October, 2022, and since the re-definition of Mastodon's culture in mid-2022 pre-dates it, it is not part of Mastodon's culture. But Mastodon has this feature.

However, in order for these content warnings to be generated, there needs to be a trigger. The safest way is by hashtags: If you post content that not everyone may want to see, add corresponding hashtags, enough to cover as many people as possible. If you don't want to see certain content right away, add the corresponding hashtags as keywords to NSFW (Friendica, Hubzilla, (streams), Forte) or a CW-generating filter (Mastodon).

In fact, hashtags can also be used to completely filter out content that you don't want to see at all. And they can be used to trigger such filters. This should work everywhere in the Fediverse.

I myself post stuff that some people don't want to see all the time. Hence, I need a whole lot of hashtags.

Let me explain the "hashtag wall" at the bottom of this comment to you.

  • #Long, #LongPost
    This comment is over 500 characters long. Many Mastodon users don't want to see any content that exceeds 500 characters. They can filter either or both of these hashtags and at least get rid of my content with over 500 characters.
    Why two hashtags? Because I can't know beforehand which one of them people will filter. And because I can't know beforehand which of one of them people will search for or follow.
  • #CWLong, #CWLongPost
    The same as above, but making clear that it's supposed to stand in for a content warning ("CW: long (over 8,300 characters)"). Also, filtering these instead of the above has less of a chance of false positives than the above.
    Why two hashtags? Because I can't know beforehand which one of them people will filter. And because I can't know beforehand which of one of them people will search for or follow.
  • #FediMeta, #FediverseMeta
    This comment contains Fediverse meta content. Some people don't want to read anything about the Fediverse, not even as by-catch or boosted to them by someone whom they follow or even only on their federated timeline. They can filter either or both of these.
    Why two hashtags? Because I can't know beforehand which one of them people will filter. And because I can't know beforehand which of one of them people will search for or follow.
  • #CWFediMeta, #CWFediverseMeta
    The same as above, but making clear that it's supposed to stand in for a content warning ("CW: Fediverse meta" or, in this case, "CW: Fediverse meta, Fediverse-beyond-Mastodon meta").
    Why two hashtags? Because I can't know beforehand which one of them people will filter. And because I can't know beforehand which of one of them people will search for or follow.
  • #Fediverse
    This comment is about the Fediverse. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic. Also, the hashtag helps people looking for content about the Fediverse find my comment.
  • #Mastodon
    This comment touches Mastodon as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic. Also, the hashtag helps people looking for content about Mastodon find my comment.
  • #Friendica
    This comment touches Friendica as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic, especially if you don't know what the hell Friendica is, but you're curious. Also, the hashtag helps people looking for content about Friendica find my comment.
  • #Hubzilla
    This comment touches Hubzilla as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic, especially if you don't know what the hell Hubzilla is, but you're curious. Also, the hashtag helps people looking for content about Hubzilla find my comment.
  • #Streams, #(streams)
    This comment touches (streams) as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic, especially if you don't know what the hell the streams repository is, but you're curious. Also, the hashtag helps people looking for content about (streams) find my comment.
    Why two hashtags if they're the same on Mastodon? Because they are not the same on Friendica, Hubzilla (again, that's where I am), (streams) itself and Forte. If I have to choose between catering to the technologies and cultures of Friendica, Hubzilla, (streams) and Forte and catering to Mastodon's, I will always choose the former.
  • #Forte
    This comment touches Forte as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic, especially if you don't know what the hell Forte is, but you're curious. Also, the hashtag helps people looking for content about Forte find my comment.
  • #MastodonCulture
    This comment touches Mastodon culture as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic, including critical views upon how Mastodon users try to force Mastodon's 2022 culture upon the users of Fediverse server applications that are very different from Mastodon, and that have had their own culture for much longer. Also, the hashtag helps people looking for content about Mastodon culture find my comment.
  • #Hashtag, #Hashtags
    This comment touches hashtags as a topic. If you don't like it, you can filter it out. Otherwise, click it or tap it to find more content on the topic. Also, the hashtag helps people looking for content about hashtags and their implications find my comment.
    Why two hashtags? Because I can't know beforehand which one of them people will filter. And because I can't know beforehand which of one of them people will search for or follow.
  • #HashtagMeta
    This comment contains hashtag meta content. Some people don't want to read anything about it, not even as by-catch or boosted to them by someone whom they follow or even only on their federated timeline. They can filter either it.
  • #CWHashtagMeta
    The same as above, but making clear that it's supposed to stand in for a content warning ("CW: hashtag meta").

By the way: Hashtags for triggering filters are even more important on Hubzilla in comments when Mastodon users may see them. That's because Hubzilla cannot add Mastodon-style content warnings to comments (= everything that replies to something else; here on Hubzilla, it's very different from a post that isn't a reply). What's a content warning on Mastodon is still (and justifiedly so) a summary on Hubzilla. But from a traditional blogging point of view (Hubzilla can very much be used for full-fledged long-form blogging with all bells and whistles), a summary for a comment doesn't make sense. Thus, the comment editors have no summary field on Hubzilla. Thus, I can't add Mastodon-style CWs to comments here on Hubzilla.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #MastodonCulture #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta
joinfediverse.wikiHubzilla - Join the Fediverse

🎉 Die heutige Fediverse-Sprechstunde ist zu Ende.

Ein herzliches Dankeschön geht an @gunchleoc für ihre Ausführungen zu #Peertube inklusive Liveupdate von PeerTube! Wir hatten eine spannende Runde mit vielseitigen Themen, die sowohl für #neuhier als auch für fortgeschrittene Nutzer interessant waren.
Mein Dank gilt auch allen Teilnehmenden der Sprechstunde, die sich aktiv eingebracht und so erneut zu einer gelungenen Veranstaltung beigetragen haben.

🗓️ Der nächste Termin steht bereits fest: Donnerstag 24.04.2025 um 19:30 Uhr
Thema: #Lemmy mit @Ranslite
Weitere Details folgen.

Lang lebe Fediverse! 🚀🌐
#Fediverse #Mastodon #Hubzilla #Friendica #Peertube

Replied in thread
@iFixit
and it doesn't look like you can attach documents to posts

You can't on Mastodon. I could, both here on Hubzilla and on (streams) where I post my images.

But I wouldn't have to. Vanilla Mastodon has a character limit of 500. Hubzilla has a character "limit" that's so staggeringly high that nobody knows how high it is because it doesn't matter. (streams), from the same creator and the same software family as Hubzilla, has a character "limit" of over 24,000,000 which is not an arbitrary design decision but simply the size of the database field.

By the way: Both are in the Fediverse, and both are federated with Mastodon, so Mastodon's "all media must have accurate and sufficiently detailed descriptions" rule applies there as well unless you don't care if thousands upon thousands of Mastodon users block you for not supplying image and media descriptions.

In theory, I could publish a video of ten minutes, and in the same post, I could add a full, timestamped description that takes several hours to read. Verbatim transcript of all spoken words. Detailed description of the visuals where "detailed" means "as detailed as Mastodon loves its alt-texts" as in "800 characters of alt-text or more for a close-up of a single flower in front of a blurry background" detailed. Detailed description of all camera movements and cuts. Description of non-spoken-word noises. All timestamped, probably with over a hundred timestamps for the whole description of ten minutes of video.

Now I'm wondering if that could be helpful or actually required, or if it's overkill and actually a hindrance.

CC: @masukomi @GunChleoc

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla #Streams #(streams) #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #MediaDescription #MediaDescriptions
joinfediverse.wikiHubzilla - Join the Fediverse

🎉 Die heutige Fediverse-Sprechstunde ist zu Ende.

Ein herzliches Dankeschön geht an Tobias tobias@social.diekershoff.de für seine Ausführungen zu #Friendica ! Wir hatten eine spannende Runde mit vielseitigen Themen, die sowohl für #neuhier als auch für fortgeschrittene Nutzer interessant waren. Im Fokus standen heute Anwendungen im #Fediverse, insbesondere zu Friendica. Mein Dank gilt auch allen Teilnehmenden der Sprechstunde, die sich aktiv eingebracht und so erneut zu einer gelungenen Veranstaltung beigetragen haben.

Diesmal haben wir den Vortrag von Tobias aufgezeichnet. Der Link kommt morgen.

🗓️ Der nächste Termin steht bereits fest: Donnerstag 27.03.2025 um 19:30 Uhr

Weitere Details folgen.

Lang lebe Fediverse! 🚀🌐 #Fediverse #Mastodon #Hubzilla

Replied in thread
@Alison Wilder Because if you want full-blown user rights and all the same features as a local user on all over 30,000 Fediverse instances, you need a local user account on each one of them.

This means two things:
  • If you come over to the Fediverse for the first time, and you register your first account on Mastodon, you automatically also register an account on 30,000+ more instances.
  • If you decide to host your own instance of whatever, and you spin it up for the first time, your instance immediately creates tens of millions of user accounts. One for everyone who has ever joined the Fediverse. Because anyone may decide to come over to your instance and use it, just like so.

For one, this is utter overkill.

Besides, this is technologically impossible. This would require all Fediverse instances to know all other Fediverse instances. With no exceptions. Like, if I start up my own (streams) instance for the first time, and half a second later, someone on the other side of the globe starts up a Gancio instance, they would immediately have to know each other. And all the other instances in the Fediverse.

And, of course, it would require a newly-launched instance to know all Fediverse users. Again, with no exception.

How and from which source are they supposed to know?

That said, there is a single sign-on system for the Fediverse. It's called OpenWebAuth. It was created by @Mike Macgirvin 🖥️ (creator of Friendica and all its descendants) in the late 2010s already for now-defunct Zap, a fork (of a fork?) of Hubzilla which, in turn, is a fork of the currently hyped Facebook alternative Friendica. It was backported to Hubzilla in 2020. Everything that came after Zap, including the still existing streams repository, got it, too.

However, first of all, OpenWebAuth is only fully implemented on Hubzilla, (streams) and Forte. Plus, it has client-side support on Friendica. This means that Hubzilla, (streams) and Forte recognise logins on all four, but Friendica doesn't recognise logins from anywhere.

As for Mastodon, OpenWebAuth implementation was actually developed to the point of an official merge request in Mastodon's GitHub repository. As far as I know, it was rejected. Mastodon won't implement OpenWebAuth, full stop.

Besides, it doesn't give you all the same power as a local user. You can't log into Friendica, go to a Hubzilla hub and create a wiki or a webpage or a CalDAV calendar, just like so.

OpenWebAuth is only for guest permissions. Because on Hubzilla, (streams) and Forte, permissions are everything.

For example, let's assume you have an account and a channel on (streams). Let's also assume that your (streams) channel and this Hubzilla channel of mine here are connected. Furthermore, let's assume that I've decided to only allow my own full connections to see my profile.

If you're logged out, and you go to my profile page, you see nothing.

But then you log in. And you come back to my profile page (provided your browser is configured so that the Hubzilla hub that I call home is allowed to create cookies). My home hub recognises your login on (streams). It identifies you as you, as one of my contacts. Thus, it identifies you as someone who is permitted to see my profile.

And all of a sudden, you see my profile.

That, for example, is what OpenWebAuth is for.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Friendica #Hubzilla #Zap #Streams #(streams) #Forte #SingleSignOn #OpenWebAuth
magicsignon.orgMagic Signon \ OpenWebAuth (OWA)

The amazing feeling of discovering that The Archive Of Our Own has a character tag for "Fediverse Network/Mastadon Platform (Anthropomorphic)", followed by the disappointment of finding only a single #fanfic using that tag. I wanted to read a bunch of erotic #Misskey #fanfiction about all that forking! Maybe a #GnuSocial #Pleroma slashfic! Or some #GoToSocial and #Mastodon lemons. A #hubzilla and #friendica hurt/comfort fanfic anyone? C'mon, people. The fact a tag exists means we should use it. archiveofourown.org/tags/Fediverse%20Network*s*Mastadon%20Platform%20(Anthropomorphic)/works

archiveofourown.orgFediverse Network/Mastadon Platform (Anthropomorphic) - Works | Archive of Our OwnAn Archive of Our Own, a project of the Organization for Transformative Works
Replied in thread
@Stefan Bohacek
And yes, I hope better reply/interaction controls are coming soon, I know some of that is planned right after quote posts are finished. Really can't wait to see that!

And that, too, will only work within Mastodon.

Also, that, too, won't be a "Mastodon first" feature. At least Hubzilla, (streams) and Forte have reply and interaction controls included in their permissions systems which, in a way, work Fediverse-wide.

Within themselves and each other, they actually make impossible what isn't allowed. For example, if you aren't allowed to repeat (= boost) or share (= quote-post) a post or a comment, you don't even have the button. These permissions aren't understood anywhere outside these three yet, but I've got higher hopes that this permissions system will be cast into FEPs than that Mastodon's hacks will be.

In fact, Hubzilla, (streams) and Forte have reply control on three levels:
  • channel-wide (who is generally allowed to reply; Hubzilla has eight levels, (streams) and Forte have three)
  • for individual connections
  • per post (on Hubzilla, commenting on a post can be disallowed altogether; on (streams) and Forte, additionally, commenting can be limited to your full connections, and a time can be defined from which commenting will no longer be allowed)

Again, within these three, if commenting is not allowed, the UI elements for commenting will be missing. Outsiders may be able to comment, but all three block disallowed comments on a server level, i.e. they aren't deleted from the inbox, they are kept from entering the inbox in the first place. And so they don't appear in the thread for all those who support threaded conversations.

It'd really be nice if this permissions system became one or a set of FEPs for others to pick up.

CC: @PaulaToThePeople

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #Forte #ReplyControls
hub.netzgemeinde.euNetzgemeinde/Hubzilla