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:

60
active users

#CWFediverseMeta

3 posts2 participants0 posts today
Replied in thread
@Chris Alemany🇺🇦🇨🇦🇪🇸 The Mastodon devs are talking as if either the Fediverse is only Mastodon, or the Fediverse as a whole doesn't have quote-posts.

Neither of this is true. The Fediverse has had quote-posts since July 2nd, 2010 when Mistpark (now known as Friendica) was launched. Mastodon toots have been quote-post-able since Mastodon itself was launched, for when Mastodon was launched, it immediately federated with at least two Fediverse server applications that have quote-posts, namely Friendica and Hubzilla, a fork of a fork of Friendica by Friendica's own creator.

Nowadays, at least Pleroma, Akkoma, all other Pleroma forks, Misskey, Calckey, Firefish, Iceshrimp-JS, Iceshrimp.NET, CherryPick, Sharkey, all other Misskey forks, Mitra, Friendica, Hubzilla, (streams) and Forte can quote-post Mastodon toots with no problem.

And Mastodon won't be able to stop them. No, seriously, it won't. Not with a non-standard, proprietary, home-brew opt-in or opt-out switch that doesn't tie into anything that the other Fediverse server apps have. And whatever switch Mastodon is working on will not tie into anything that already exists.

Let me put it this way: Hubzilla has the second-most advanced and fine-grained permissions system in the Fediverse. It goes well beyond most people's imagination. It works on three levels: for the whole channel (that's similar to a Mastodon account), for individual contacts (that's "followers" in Mastodon lingo, but Hubzilla doesn't distinguish between followers and followed), for individual content. (streams) and Forte are the only ones with an even more advanced and fine-grained permissions system.

But even they don't have a quote-post permission setting. And they have permission settings for just about everything. You want reply control in the Fediverse? Hubzilla has reply control, and (streams) and Forte have reply control on steroids. But what they don't have is a quote-posting permission because that's next to impossible to control across the Fediverse even with the most advanced permissions system.

As @Mike Macgirvin ?️ (professional software developer for almost half a century, designer of two Fediverse protocols, creator of Friendica and Hubzilla, inventor of nomadic identity, creator and maintainer of (streams) and Forte) says: The only way to make your posts un-quote-post-able is by not posting in public and not allowing everyone in the Fediverse full access to your posts. Set your "Who can quote" however you want, I'll always be able to quote-post all your public posts with no problem and with no resistance.

So what chance does Mastodon have then? Mastodon which doesn't even know what permissions are? Developed by Eugen Rochko who actually has a history of head-butting with Mike Macgirvin, and who would never take any step towards anything that Mike has ever developed?

I'm commenting from Hubzilla right now, and I'm also on (streams). And I can tell you: If you make any of your posts "un-quote-post-able", this still won't make my Share buttons on Hubzilla and (streams) disappear.

CC: @Stefan Bohacek @FinchHaven sfba

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Calckey #Firefish #Iceshrimp #Iceshrimp.NET #CherryPick #Sharkey #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotePostDebate #QuoteTootDebate
friendi.cafriendica – A Decentralized Social Network
More from Tobias
Replied in thread
@Bob Tregilus Only that "my best" has actually led to unimaginable extremes.

They say an image is worth a thousand words. I've once described one image in over 10,000 words. Over 60,000 characters. The post is so long that, I think, Misskey and its various forks have rejected it, as have Pleroma and Akkoma. It took me two full days, morning to evening, to describe that one image, in-world research included.

And I actually had to limit myself. For once, I did not give in-depth descriptions of the images within that image, especially not beyond what's actually visible in these images. That's because I've discovered that if I were to do that, I'd have to describe dozens of images in one particular image (in my image) and potentially over a hundred images in these, even though they're so small that they're technically invisible. It would have taken me months to write all that. And it would have been futile anyway. My character limit is over 16 million, but Mastodon rejects posts over 100,000 characters, and in the few places that do accept posts with millions of characters, next to nobody cares about image descriptions.

I haven't posted a new in-world image in over half a year. I've been working on-and-off on the descriptions for a series of rather simple avatar portraits since last autumn.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
hub.netzgemeinde.euUniversal Campus: The mother of all mega-regionsOpenSim's famous Universal Campus and a picture of its main building; CW: long (62,514 characters, including 1,747 characters of actual post text and 60,553 characters of image description)
Replied in thread
@Bob Tregilus Of course, this means that the more obscure the content of your image is, the more in-depth you will have to go. At worst, there's nothing in your image of which non-sighted people know what it looks like unless you describe it. Simply mentioning that it's there is not sufficient.

My own original images aren't even photographs, nor are they pieces of art that represent real life. They're renderings from 3-D virtual worlds, very obscure 3-D virtual worlds even. Nobody knows what anything in these world looks like unless they can see it in my images. At the same time, however, chances are that they become so curious about these virtual worlds that they also become curious about everything in the image, not just what matters within the context of the post. That is, sometimes the image itself as a whole is the context. Either way, this means I can't just focus on certain elements in the image in my descriptions. I have to describe everything.

So I've gotten to a point at which even filling the alt-text character limit forced by Mastodon, Misskey and their respective forks (they cut longer alt-texts off at the 1,500-character mark) doesn't cut it. All my original images have two descriptions now. In addition to the one in the alt-text that's very limited, there is another one in the post that's more or less fully detailed, that contains transcripts of all text within the borders of the image, and that also comes with all explanations that I deem necessary. Since I don't have a character limit to worry about (the limit is defined by the database field rather than a hard-coded or configurable number), this description is likely to grow well over a hundred times longer than typical alt-text.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
hub.netzgemeinde.euNetzgemeinde/Hubzilla
Replied in thread
@Justin Derrick The question, however, is: What is "high-quality"? How is it defined?

Would the bot go by the definition valid for commercial/scientific/technological websites and blogs, i.e. ideally no more than 125 characters, and only a short and concise visual description with no further information?

Or would the bot go by Mastodon's culture and Mastodon's standards, i.e. the longer and more detailed, the better, any and all extra information is welcome in alt-text (because it doesn't fit into the toot), and the limit is 1,500 characters?

That is, if it were for me, the bot would go look both for alt-texts and for image descriptions in the post text body and judge both. Because I do both at the same time for my original images. An extremely detailed long image description in the post itself (character limit for post and alt-texts combined here: over 16 million) that also comes with all necessary explanations and transcripts of all text in the image, plus an alt-text that's as detailed as 1,500 characters (minus notification about the long description in the post) allow, but with no explanations, and I usually have to leave out text transcripts as well because they're too many.

You may say the alt-text is superfluous if it's just a much shorter version of the long description. But as long as the Mastodon HOA demands there be an alt-text to every image, no matter what (especially seeing as I always hide my image posts behind summaries/content warnings, so you can't see right of the bat that there's a long image description in the post), I add alt-texts to my original images.

I'm actually curious about how the bot would judge my descriptions. Maybe it'd flag them "inadequate" because it notices that the bits of text in the image are not transcribed in the alt-text. Maybe it'd be irritated because I have headlines in my long image descriptions, because they're so long that they need two levels of headlines. Maybe it'd flag them "inadequate" because it goes strictly by WCAG, and a) the alt-texts exceed 200 characters, b) long image descriptions do not belong into the text body by any known official accessibility standards, and c) neither my alt-texts nor my long descriptions are limited to what's supposed to be important within the context of the post.

Anyway, in the meantime, you can follow the account @Alt Text Hall of Fame and the hashtag #AltTextHallOfFame.

CC: @Simon Brooke

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #MastodonHOA #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
hub.netzgemeinde.euNetzgemeinde/Hubzilla
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
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
Replied in thread
@masukomi @iFixit And this is only mostly a transcript of the spoken words.

What if someone actually took upon themselves the effort to describe a video with a timestamped/timecoded combination of visual description, spoken word transcript and non-spoken word audio description? Especially if the visual description is on the same high level of detail that's expected in the Fediverse?

CC: @GunChleoc

#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #MediaDescription #MediaDescriptions
hub.netzgemeinde.euNetzgemeinde/Hubzilla
@Joseph Meyer
When you read exceptional alt text, do you ever compliment its author? What is the epitome of alt text, either in general terms or using a specific example?

I'd really like to know that myself, also to up my own game further and always stay way ahead of image description quality requirements.

I mean, I've learned a lot about describing images in and for the Fediverse over the last two years. But I guess I can still learn something new, even if I think I already take care of everything, even if the technical possibilities I have here on Hubzilla for describing images surpass those on Mastodon by magnitudes.

Maybe, if I learn something new from those who reply, I can weave it into the image descriptions for a series of images that I've been working on since late last year (the descriptions, not the images which are ready to go).

Alt text sometimes merely explains what I am viewing; other times it draws my attention to special details in a photo that I would have otherwise missed.

I never explain in alt-text. I do always explain a whole lot because I always have to explain a whole lot. For my original images, it takes me over 1,000 characters alone to explain where an image was made.

But I only ever give explanations in the long, detailed image descriptions that go into the post text body (in addition to shorter and purely visual descriptions in the alt-texts).

Or if there's no additional long image description in the post itself which is the case for my meme posts, I still supply enough explanation in the post text body (still not in the alt-text) for just about everyone in the Fediverse to understand them without having to look anything up themselves. If I can link to external information, e.g. KnowYourMeme for the template I've used, I do so. If I can't, I write the missing explanations right into the post myself.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
hub.netzgemeinde.euImage descriptions in the FediverseI have learned a lot about describing images according to Mastodon's standards, and I want to share my knowledge, but I haven't learned enough
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)
Replied in thread
@HistoPol (#HP) 🏴 🇺🇸  🏴 Truth be told, what we could need is a feature comparison between the various mobile apps and Friendica's Web frontend to see what covers what.

I'm not quite sure if any Friendica app actually covers exactly 100% of Friendica's functionality. What they should cover is what's needed for daily driving. But I'm not sure if all of them cover, for example, all features of the built-in file manager and every last one of Friendica's own optional add-ons.

An actually, absoutely fully-featured Friendica app would be voluminous. Not as huge as a (streams) app and not as massive as a Hubzilla app, but big.

In the cases of some features, I'm not even sure how much sense they make in a mobile app. Would a mobile app need all configuration controls for the Web interface? And does it make sense for an iPhone app to brandish the full set of Friendica admin controls if it detects the logged-in account to be an admin account?

Besides, in spite of its old age, Friendica is constantly changing and sometimes introducing new features. Third-party apps will have to keep up with core and add-on development.

And once the now-growing Friendica community has settled in and attracted a few devs, and they discover that Friendica is so modular that it can attach third-party add-ons server-side, and they start developing third-party add-ons, mobile apps won't cover 100% of Friendica anymore anyway.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #FriendicaApp #FriendicaApps
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
Replied in thread
@:neuro: Pixy's Journey :v_bi: First of all, I apologise if you already know this, but there are so many who have been on Mastodon for much longer than you, and who don't know: If you want to follow Friendica users, you can do so from Mastodon. Even though Friendica and Mastodon are fundamentally different. You don't need a Friendica account just for that. You'd only need a Friendica account if you personally need Friendica's extra features.

First of all, why are they so different? Why are they so much different that it may cause friction with Mastodon? Why didn't they make Friendica more like Mastodon?

Because "they" (actually originally one man in Australia, now two guys in Germany) made it before Mastodon. Friendica first came out in July, 2010. Mastodon first came out in January, 2016. Five and a half years later. And immediately when Mastodon was first released, it was federated with Friendica. And it has continuously been ever since then.

Also, Friendica has never aimed to be a full-on, all-out Facebook clone. Its goal has always been to be "like Facebook, but better than Facebook". So it is different from Facebook. It doesn't look like Facebook, it doesn't feel like Facebook. It just does what Facebook does with extra stuff on top.

As Friendica is so much older than Mastodon and developed entirely independently from Mastodon, don't expect it to be anything like Mastodon either. Half of what you know about Mastodon you can toss out of the window when you join Friendica and re-learn it.

Now, the first difference between Mastodon and Friendica is: Mastodon being like Twitter means that it's social media. It's about following accounts and consuming their content, it's about others following your account and consuming your content.

Friendica is like Facebook. It's true social networking. It's about people connecting with people. Even though Friendica has adopted the "follower" and "followed" wording from Mastodon, its default is still the bidirectional connection. Maybe you still remember that you didn't follow people on Facebook, and they didn't follow you back, thus creating two unidirectional connections. You didn't have followers, you didn't follow, you had "friends" which always went into both directions.

"Social networking" also means that on Friendica, much unlike on Mastodon, you don't follow people because of their content first and foremost. Friendica is more geared towards connecting with people because of their profiles. A Mastodon profile has not even half a dozen text fields. A Friendica profile has well over a dozen. Including a dedicated text field for keywords.

This contributes to the directory being much, much more useful on Friendica than on Mastodon. You can search the Friendica directory for names. You can search it for keywords. It comes with a keyword cloud. And it has a "suggestion" mode in which Friendica matches other profiles with yours.

So you're into dogs. You add "dogs" to your keyword field. Someone else has "dogs" in their keyword field. And what do you know, they slide up your list of suggestions! Also, I guess (I've been out of Friendica for many years, using two of its surviving descendants instead; this comment comes from Hubzilla) that connections of your connections move to the top of the suggestions, too. Just like on Facebook. Key feature on everything that's truly social networking.

There's even a central Friendica directory.

Discussions on Friendica are better than on Mastodon. That's because Friendica, just like Facebook, like Tumblr, like a blog, like a forum, like almost everything that isn't Twitter or Mastodon, has threaded conversations. It's fully aware of entire threads. A conversation is not loosely tied together from posts and more posts like on Mastodon. Instead, it's an enclosed object with exactly one post. The start post. And otherwise any number of comments. Which are totally not posts.

Now, what does that mean in practice? Let's play through a conversation that entirely happens on Friendica.

Imagine you're connected with Alice. Alice posts something. You receive Alice's post on your stream (= timeline).

Bob comments. You are not connected with Bob. Bob doesn't mention you. In fact, Bob doesn't mention anyone. But still, Alice knows about Bob's comment because it's listed as an unread activity. And you know about Bob's comment, too, because it's listed as an unread activity for you as well.

By the way: Unread activities. Another thing that doesn't exist on Mastodon. On Mastodon, you read your unread stuff by scrolling and scrolling and scrolling through your timeline and scrolling some more until either you hit the stuff that you've already read, or until you've got no more time and/ore spoons to read any more. If the latter, there'll inevitably be a whole lot of toots that you'll never know about. On Friendica, you have a counter and a list of posts and comments that you have not read yet. And you can go through it by and by, until there's nothing anymore that's unread. Luckily, Friendica doesn't show you posts and comments one by one, but it always shows you entire threads.

Okay, back to the conversation: Carol comments on Bob's comment on Alice's post. Carol only mentions Bob to make sure that she's replying to Bob rather than directly to Alice. Again, the mention is not needed for Bob to see her comment. She doesn't mention Alice either, she doesn't mention you, and you aren't connected with Carol.

But yet again, Carol's comment is listed as an unread activity.

Now you want to check Alice's post, Bob's comment and Carol's comment. Again, you don't have to check them one by one. If you click either, Friendica will show you the whole conversation at once. Like a post on Facebook with comments below. Like a blog post with comments below. And it will mark Alice's post, Bob's comment and Carol's comment as flagged.

This is how conversations should be. Always. You have a post on your stream, you get all the comments on it. At least all that come in after you've received the post.

But Friendica goes even further: It has groups. Discussion groups. Like forums. It has always had them. I mean, Facebook has always had groups, too, right? Basically, after you've joined a group, you receive all posts from that group plus all comments under these posts. And if you post to a group, everyone in the group receives your post. All without fumbling around with hashtags and hoping people on other instances happen upon your post by searching for that hashtag.

Now you may say that Mastodon has Guppe groups. Yeah, but they're a glued-on hack made by someone who probably thought the Fediverse is only Mastodon. They can't be searched for whereas the Friendica directory also lists public groups. Speaking of public groups, they can be private. As in, outsiders can't see the profile, outsiders can't see the posts in the group, and they aren't listed in any directory. Also, Friendica groups can be moderated. Guppe groups can't.

What else? Posts. You can do more in a post on Friendica than you can see on Mastodon.

Vanilla Mastodon is limited to 500 characters. It can be raised, but not by configuration. Raising the limit requires hacking into the source code and usually having to do so after each Mastodon upgrade.

Friendica, as far as I know, is "limited" to 200,000 characters. At the same time, as far as I know, Mastodon rejects posts from outside if they're longer than 100,000 characters. Friendica lets you write posts that are so long that Mastodon refuses to even import them.

Friendica supports all kinds of text formatting. Mastodon can display bold type, italics, maybe underline, also bullet-point lists, quotes (it still can't display quote-posts which Friendica has had from the get-go as well), well, and that's about it. Friendica can create all this and more. Much more. If you can do it in a blog post, you can do it on Friendica. Maybe even more than that.

A very good example is how Friendica handles images. Mastodon can only handle images as file attachments and only four of these. If you only know Mastodon, you perceive this as the one and only Fediverse standard, and you can barely imagine that it could possibly be any different. That's because Mastodon can only handle images with these limitations in content from outside as well.

Friendica, on the other hand, is not limited in how many pictures you can have in a post. And it can actually have pictures in a post. Embedded within the post. With text above the picture and more text below the picture and another picture below that text and so forth. Just like a blog.

Since Mastodon refuses to render embedded in-line images, Friendica actually has to additionally convert all imported images into file attachments which Mastodon understands. But even then, Mastodon will throw all of them away except four if you have more than four.

How does Friendica do that? Well, part of the secret is because Friendica has its own cloud file space built into each account. If you upload an image to Mastodon, it ends up somewhere where you can't access it. If you upload an image to Friendica, it ends up in your cloud file space. With its own little file manager. Which even supports folders and subfolders.

In fact, Friendica even has image gallery functionality!

That said, as Friendica is so much different from Mastodon, and particularly, since it's so much older than Mastodon, it has its own culture which is rooted in a) its vast set of features and b) the early 2010s. Friendica has never adopted Mastodon culture, and it never will. That's because Mastodon culture clashes so much with Friendica's native culture and with Friendica's features.

For example, Friendica users happily churn out posts and comments which at least some Mastodon users perceive as so long that they're disturbing. Namely over 500 characters long. Ask a Friendica user to chop their long posts into threads with never over 500 characters, and you will not receive.

Friendica users do stuff in their posts that Mastodon won't render. This includes embedding images and more than four. If Mastodon won't render them, then from a Friendica point of view, it doesn't mean that Friendica is using some non-standard freak feature that should be avoided. It rather means that Mastodon is broken. And if the Mastodon devs refuse to fix it, then Mastodon is broken by design.

This may come as a surprise to you, but: Mastodon's CW field was not invented from scratch as a CW field. Originally, it's a summary field. It's a summary field on Laconi.ca/StatusNet/GNU social. It's a summary field on Friendica (where it's called "abstract"). It's a summary field on everything that came after Friendica. But in 2017, someone proposed to make it a CW field on Mastodon. Ever since then, everyone on Mastodon "knows" that this field is purpose-made for CWs and for CWs only.

Again, on Friendica, it's for summaries. Friendica users either use it for a summary (and even then, this involves a pair of BBcode tags), or they don't use it at all.

At the same time, Friendica historically, and to this day, handles CWs differently: It generates them on the reader's side. Automatically and only if you want to. For this, it has an optional, very basic filter-like feature named "NSFW" that comes with not much more than a keyword list. If a keyword from that list is in a post or a comment or a PM, the whole thing will be automatically hidden behind a button. Much like a Mastodon CW, but unlike a Mastodon CW, it's only rendered for you (and everyone else who has that keyword on the list) and not forced upon everyone all the same.

(By the way: Mastodon has introduced the self-same functionality to its filters with the release of Mastodon 4.0 in October, 2022. But even though this was right before the biggest Twitter-to-Mastodon migration wave ever, nobody knows about this.)

This leads to culture clash:
  • Mastodon users are disturbed because Friendica users don't add CWs to sensitive content.
  • Mastodon users are extra disturbed because Friendica users "spam" their posts with hashtags. These hashtags are used to trigger the generation of reader-side CWs which are not part of Mastodon's culture because nobody knows they exist, and because they didn't exist in mid-2022 when Mastodon's culture was (re-)defined.
  • Mastodon users are extra special disturbed because Friendica users "misuse" the CW fields for "like, titles or summaries or whatever that stuff is".
  • Friendica users are disturbed because Mastodon users misuse the abstract field for CWs without even adding an actual abstract.
  • Friendica users are extra disturbed because Mastodon users don't add keywords or hashtags to trigger their NSFW.

Also, Mastodon users mute or block Friendica users because they post over 500 characters at once. In turn, I know at least one Friendica user who blocks everyone upon first strike who chops a longer post into a thread with never more than 500 characters in one message. Friendica users are perfectly used to posts with 10,000 characters, but they find the same posts cut into threads with over two dozen tiny posts cumbersome and tiring.

Before mid-January, 2025, accessibility didn't play any role on Friendica. The old Friendica guard saw alt-text as another dumb fad from Mastodon's stupid and ignorant culture that perceives the Fediverse as only Mastodon. Not to mention that adding alt-text to images on Friendica is still kind of cumbersome because next to nobody has ever actually considered using that feature until very recently.

Interestingly, Zuckerberg's further enshittification of Facebook which triggered a slow but steady migration wave from Facebook to Friendica also coincided with the very first time ever that a Friendica veteran (the same guy who blocks thread posters) was asked to add alt-text to an image. Which must have been a rather disturbing experience for him.

Another cultural difference concerns connections with other software and platforms. Still today, over half of all Mastodon users think the Fediverse is only Mastodon. And truth be told, many many Mastodon users would love the Fediverse to actually be only Mastodon. Anything that connects with Mastodon and sends content to Mastodon is seen as rogue, culture-less intruders.

On Friendica, in a stark contrast, connection with anything and everything has been an integral part of the concept, of the philosophy and thus of the culture from the very beginning on.

Friendica doesn't only communicate through ActivityPub which it didn't even support until 2019 (it also has its own protocol, DFRN). Even then, it has a much more complete and standard-compliant ActivityPub implementation than Mastodon.

It can also connect do diaspora*, another much less feature-rich "Facebook killer" from later in 2010 which refuses to support any protocol other than its own, and which actually doesn't aim to federate with anything else (all the cross-project federation work was entirely done on Friendica's side). If you've been intensively using Friendica for at least a year or two, it's absolutely normal to have contacts on diaspora*.

It's also one of the very last Fediverse projects that still support OStatus, the old protocol used by GNU social, formerly StatusNet.

It can integrate Bluesky accounts so you can connect to Bluesky without the Bridgy Fed bridge and without Bridgy Fed's limitations. It can integrate Tumblr accounts. It could theoretically still integrate 𝕏 accounts if the node admin had the millions for an API license. In the early 2010s, it was even able to integrate Facebook accounts. It can natively crosspost to WordPress and Libertree.

It can subscribe to RSS and Atom feeds while generating Atom feeds itself. It can communicate via e-mail. And its chat has at least basic XMPP compatibility.

Friendica's credo is something like, "If it exists, we federate." Mastodon's credo rather seems to be something like, "There's Mastodon, there's evil, there's broken, and there's both broken and evil. If it isn't Mastodon, it'd better not disturb us."

In fact, most Mastodon users barely notice the Fediverse outside Mastodon, also because they barely identify content from outside of Mastodon as such. Another reason why they try to force Mastodon's culture upon non-Mastodon users: They don't even notice that these aren't Mastodon users at all.

Friendica users are fully aware of how colourful the Fediverse is, also because Friendica's Web UI actually tells you where a post or a comment came from. They still find the behaviour of many Mastodon users disturbing and tiring. But they're more aware that Mastodon has its own culture, and they don't try to force Friendica's culture upon users of something that isn't even technologically fit to adopt Friendica's culture.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #MastodonCulture #Friendica
joinfediverse.wikiHubzilla - Join the Fediverse
Replied in thread
@Droppie [infosec] 🐨:archlinux: :kde: :firefox_nightly: :thunderbird: :vegan:​ Friendica apps are generally installed and work on your local device.

Friendica's own frontend can be modified extensively with themes built into a node. But there are no full-blown third-party frontends that completely replace Friendica's built-in frontend like Phanpy fully replaces Mastodon's frontend or Mangane fully replaces Pleroma-FE and Akkoma-FE.

Currently, the only platform that gives you a selection of alternative, third-party frontends that fully replace Friendica's frontend is Android because there are quite a few dedicated, native Friendica apps available for Android.

On Windows or Linux, all you can do is install Relatica. But it's an early and not entirely open beta, it's very incomplete and unfinished, and to my understanding, it still lacks important features.

On a Mac or an iPhone, you're completely out of luck. Again, there's only Relatica which is just as unfinished and incomplete as on Android, Windows and Linux. But Relatica for macOS and for iOS is only available via TestFlight which requires an account on GitLab in order to get into contact with the Relatica developers.

CC: @morebento @Elena Rossini ⁂

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #FriendicaApp #FriendicaApps
GitLabMy Social Portal / Relatica · GitLabAn independent mobile and desktop client for Friendica written in Flutter
Replied in thread
@Juancho @Daniel Supernault Not the only one.

Mike Macgirvin, the creator of Friendica and Hubzilla, has made a whole tree of at least (...counts...) nine forks after Hubzilla, eight of which were nomadic. Two of them still exist.

One is intentionally nameless, intentionally brandless, intentionally not a project and intentionally released into the public domain. Since the community needed to address to it by something, they took the name of the code repository (which needed a name), put parentheses around it and called it (streams).

It's a fork (2021)
of a fork (Roadhouse; 2021)
of three forks (Osada, Mistpark 2020 a.k.a. Misty, Redmatrix 2020; 2020)
of a fork (Zap; 2018)
of maybe another fork (Osada; non-nomadic; 2018; if Zap was forked from Osada rather than directly from Hubzilla;)
of Hubzilla.

(streams) is reduced in features and connectivity in comparison with Hubzilla, but so were the first Osada and Zap. However, in terms of permission control and nomadicity, it's at least up-to-par with Hubzilla. In fact, it isn't quite as difficult to use as Hubzilla because permission handling has been adapted what the Fediverse of the 2020s actually requires as opposed to what a hypothetical Fediverse of the mid-2010s centred around the Red Matrix would require.

I've made a series of tables that compare Mastodon, Friendica, Hubzilla and (streams). You can find them here.

The other still existing fork is Forte from August, 2024. Forte is a direct fork of (streams). It's highly experimental because all support for the Nomad protocol was removed, and it has to rely on ActivityPub for nomadic identity. Thus, it is not officially released yet, it does not have public instances, and it is not recommended as a stable, reliable daily driver yet.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte
MastodonDaniel Supernault (@dansup@mastodon.social)6.94K Posts, 145 Following, 25.9K Followers · just a guy from canada building things for the fediverse