veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.

Administered by:

Server stats:

297
active users

#CWLongPost

2 posts2 participants0 posts today
@Hajoda Für Twitter-Flüchtlinge ist es natürlich "möglichst einfach", ihnen nur Mastodon zu zeigen und sie dann am besten auch noch nach mastodon.social zu railroaden, damit sie ein paar Monate brauchen, um zu begreifen, daß Mastodon keine einzelne Website ist, und noch länger, um zu begreifen, daß mit Mastodon auch noch andere Sachen verbunden sind.

Aber selbst das birgt schon Risiken, die Mastodon-Nutzer bisher noch nie auch nur wahrgenommen haben, die aber allen anderen im Fediverse sehr sauer aufstoßen.

Und wenn jetzt jemand von Facebook oder Instagram kommt, dann ist Mastodon für die nicht die einfachste Lösung. Die einfachste Lösung ist nicht immer die mit den wenigsten Features bzw. die, die am meisten "für Doofe" ist. Sondern das ist die, bei der der Umstieg am einfachsten ist.

Leute von Instagram nach Mastodon zu holen, weil man selbst Mastodon "soooooo einfach" findet, ist kompletter Blödsinn. Dafür gibt's Pixelfed. Wer nur Mastodon kennt, wird Pixelfed "kompliziert" finden, weil es sich nicht wie Mastodon oder Twitter bedient. Aber wer von Instagram kommt, wird sich schnell zurechtfinden. Warum? Weil Pixelfed ein Instagram-Klon ist. Von vornherein gedacht als 1:1-Drop-in-Instagram-Ersatz.

Pixelfed ist tausendmal dichter an Instagram dran als Mastodon. Noch dazu kann man Instagram-Konten nach Pixelfed importieren.

Ähnlich ist das bei Facebook-Nutzern. Da ist man als jemand, für den das Fediverse im Grunde primär Mastodon ist, natürlich auch versucht, die nach Mastodon zu holen, weil man glaubt, das ist am einfachsten.

Aber die erste Frage, die gestellt wird, wenn jemand von Facebook nach Mastodon gekommen ist: "Wo Gruppen"? Tja, Mastodon hat keine Gruppen. Mastodon weiß eigentlich gar nicht, was Gruppen sind.

Mastodon kann auch keine vernünftigen Konversationen (nein, kann es wirklich nicht; wer das als Mastodon-Nutzer bestreitet, hat noch nie echte Konversationen im Fediverse gesehen), sondern nur Stückwerk aus Einzeltröts wie auf Twitter. Mastodon hat auch noch so ein lächerliches Zeichenlimit, das Facebook nicht hat. Und so weiter und so fort.

Wer von Facebook nach Mastodon kommt, hat es tatsächlich sehr schwer. Warum? Weil das eine ganze Menge Umdenken bedeutet. Weil alles ganz anders funktioniert. Weil das Konzept ein ganz anderes ist. Das ist, wie von Facebook nach Twitter umzuziehen.

Wer dagegen von Facebook auf das ach-so-komplizierte Friendica umzieht, wird sich schneller zurechtfinden. Warum? Weil Friendica vor 15 Jahren explizit als Facebook-Ersatz entwickelt wurde. Weil Friendica daher alles hat, was ein gut funktionierendes Social Network braucht. Weil Friendica keine lächerlichen Einschränkungen hat, die Twitter hat, die Mastodon hat, die Facebook aber auch nicht hat. Und weil Friendica sehr viel von dem hat, was Facebook-Nutzer brauchen, was Mastodon aber nicht hat. Gruppen zum Beispiel.

Friendica ist tausendmal dichter an Facebook dran als Mastodon. Auch weil es konzeptionell dasselbe ist wie Facebook, Mastodon aber nicht.

Mastodon ist eben nicht das "Schweizer Taschenmesser" des Fediverse, das alles kann und für jeden Nutzer und jeden Einsatzzweck paßt.

CC: @Ralf @crossgolf_rebel - kostenlose Kwalitätsposts

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon #Instagram #InstagramErsatz #Pixelfed #Facebook #FacebookErsatz #Friendica
hub.netzgemeinde.euNetzgemeinde/Hubzilla
@Martin Holland
Aber allein im chronologischen Feed verpasst man zu viel

Die Lösung hat das Fediverse seit 2010. Und das ist kein manipulierbarer Algorithmus, der "populären" Content nach vorne spült.

Die eigentliche Lösung besteht statt dessen aus zwei Teilen.

Zum einen ein Zähler für ungelesene Mitteilungen und andere unbemerkte Ereignisse. Wenn man den aufklappt, kann man diese Mitteilungen und Ereignisse jeweils gezielt aufrufen. Tausendmal besser, als wie auf Mastodon nur eine Doomscroll-Timeline zu haben, und wo man nicht mehr schafft hinzuscrollen, davon wird man nie erfahren.

Zum anderen, um das Ganze effizienter zu gestalten, immer eine Anzeige des ganzen Thread auf einmal. Damit kann alles, was in dem Thread neu passiert ist, auf einen Schlag gelesen und als gelesen markiert werden. Und ich meine des ganzen Thread mit allen Verzweigungen. Tausendmal besser, als wie auf Mastodon alles immer nur stückchenweise zu bekommen, hier mal ein Post, da mal ein Post und immer schön ohne Zusammenhang. Denn damit wären endlich auch auf Mastodon vernünftige Diskussionen möglich.

Aus Mastodon-Sicht ist das utopische Science-Fiction. Im Fediverse im Großen und Ganzen ist beides Realität seit Juli 2010, seit Mistpark gestartet wurde, das heute Friendica heißt, die älteste noch existierende Serveranwendung des Fediverse. Und nicht nur Friendica hat das.

Nur weil Mastodon es nicht hat, heißt es nicht, daß das ganze Fediverse es nicht hat und es erst noch neu entwickelt werden muß. Das Fediverse ist nicht nur Mastodon und auch nicht Mastodon mit ein paar Extras drangeklebt.

"Das Fediverse" muß nicht verbessert werden. Es ist nur Mastodon, das so ganz allmählich mal zum Rest des Fediverse aufschließen sollte. Denn auch wenn die Mastodon-Entwickler gebetsmühlenartig anderslautende Propaganda verbreiten: Mastodon ist nicht die Krone der Fediverse-Schöpfung und auch nicht der Fediverse-Goldstandard.

CC: @Kleiner Radler - resigniert @Hiker

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon #Friendica
hub.netzgemeinde.euNetzgemeinde/Hubzilla
@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
@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
@zeitverschreib [friendica] Ich bin auf Hubzilla und (streams), und ich kann sagen, das ist nicht gut fürs Muskelgedächtnis. Aber es ist machbar.

Von Friendica ist es natürlich sowieso ein Riesenumdenken, weil (streams) nicht einfach "Red Matrix 2.0" ist, also nicht einfach Friendica mit nomadischer Identität. Schon als Zap 2018 entstand, wo das UI allmählich umgebaut wurde, hatte Friendica seit sieben Jahren neue Entwickler, die schon auf die Entwicklung von Red Matrix und Hubzilla keine Rücksicht mehr nahmen.

(streams) faßt jetzt fast alle Einstellungen unter Burgermenü > Einstellungen zusammen. Das heißt, das Herumgehühner mit den Zahnrädern oben links entfällt, wobei es /settings/features immer noch gibt und es immer noch keinen Weg über das UI dahin gibt. Jedenfalls stellst du da auch die kanalweiten Berechtigungen ein (wobei "Kanal" keine Auswahl an Inhalten ist, die reinkommen, sondern eine Identität, von der du auf einem Konto mehrere separate haben kannst, quasi wie mehrere Friendica-Konten, aber mit einem und demselben Login).

Gewisse Features sind optional; wie Hubzilla ist auch (streams) hochgradig modular. Das heißt, die wirst du erst auf der Admin-Seite als "App" aktivieren müssen und dann auf der Nutzer-Seite als "App" "installieren" müssen. Einige Sachen, die auf Hubzilla noch eine App sind, sind auf (streams) in den Kern eingebaut.

Berechtigungsrollen (Hubzilla: Kontaktrollen) sind jetzt umgekehrt standardmäßig zumindest für Nutzer nicht mehr installiert, weil man die nicht mehr braucht. Auf Hubzilla sind ja Kontaktrollen zwingend notwendig, weil sie die einzige Möglichkeit sind, die Berechtigungen eines Kontakts zu steuern. Auf (streams) kannst du bei jedem Kontakt jede Berechtigung einzeln schalten; Berechtigungsrollen sind einfach nur Presets, um dir das Leben leichter zu machen, wenn du bei gewissen Kontakten eh immer dasselbe einstellst.

Übrigens: Was "teilen" auf Friendica ist, heißt auf Hubzilla und (streams) "wiederholen". "Teilen" auf Hubzilla und (streams) dürfte auf Friendica "mit Zitat teilen" sein.

Ansonsten guck dir mal meine Mastodon/Friendica/Hubzilla/(streams)-Vergleichstabellen an.

Support für (streams) gibt's bei @Streams. Außerdem kannst du dich an @Der Pepe (nomád) ⁂ ⚝ wenden, der betreibt auch zwei Hubzilla-Hubs und je einen (streams)- und Forte-Server, oder auch mal an mich. Am aktivsten bin ich hier auf Hubzilla; auf (streams) findest du mich als @Jupiter's Fedi-Memes on (streams) (mein Outlet für Fediverse-Memes; wenig aktiv) und @Jupiter Rowland's (streams) outlet (mein Outlet für Bilder aus OpenSim; noch weniger aktiv).

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams) #Forte
hub.netzgemeinde.euMastodon vs Facebook alternativesComparison between Mastodon, Friendica, Hubzilla and (streams)
@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
@Joaquim Homrighausen @Kevin Beaumont To be fair, full data portability via ActivityPub has only been available in a stable release of anything for two weeks.

That was when @Mike Macgirvin 🖥️'s Forte, created in mid-August of 2024 as a fork of his own streams repository and the latest member of a family of software that started in 2010 with Friendica, had its very first official stable release.

And, in fact, Forte just uses ActivityPub to do something that (streams) and its predecessors all the way to the Red Matrix from 2012 (known as Hubzilla since 2015) have been doing using the Nomad protocol (formerly known as Zot). It's called nomadic identity. This is technology that's over a dozen years old on software that was built around this technology from the get-go, only that it was recently ported to ActivityPub.

Now, nomadic identity via ActivityPub was @silverpill's idea. He wanted to make his Mitra nomadic. He started working in 2023. The first conversion of existing non-nomadic server software to nomadic still isn't fully done, much less officially rolled out as a stable release.

If Mastodon actually wanted to implement nomadic identity, they would first have to wait until Mitra has a first stable nomadic release. Then they would have to wait until nomadic identity on Mitra (and between Mitra and Forte) has become stable and reliable under daily non-lab conditions. (Support for nomadic identity via ActivityPub on (streams) worked nicely under lab conditions. When it was rolled out to the release branch, and existing instances upgraded to it, it blew up in everyone's faces, and it took months for things to stabilise again.)

Then they would have to look at how silverpill has done it and how Mike has done it. Then they would have to swallow their pride and decide to adopt technology that they can't present as their own original invention because it clearly isn't. And they would have to swallow their pride again and decide against making it incompatible with Mitra, Forte and (streams) just to make these three look broken and inferior to Mastodon.

And only then they could actually start coding.

Now look at how long silverpill has been working on rebuilding Mitra into something nomadic. This takes a whole lot of modifications because the concept of identity itself has to be thrown overboard and redefined because your account will no longer be your identity and vice versa. Don't expect them to be done in a few months.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mitra #RedMatrix #Friendica #Hubzilla #Streams #(streams) #Forte #DataPortability #NomadicIdentity
Codeberg.orgforteNomadic fediverse server.
@Ben Pate 🤘🏻 Not everyone will want to offer their music on Bandwagon for money. Some may want to give it away for free for various reasons (non-commercial license, German hobbyist artists not wanting to hassle with the German tax system and GEMA etc.), and Funkwhale may not be a viable option for them. At the same time, they may not want to or even be able to pay the same prices for anything beyond basic functionality as musicians or bands who intend to actually make money with their music.

Some features should remain free for music that's offered for free. For example, it shouldn't be lossless downloads that a musician or a band has to pay for as a feature, but charging money for lossless downloads. Having everyone pay for e.g. offering FLAC downloads favours commercial artists, and the anti-capitalist parts of the Fediverse will criticise you for that.

Alternatively, you could make the license choosable from a pull-down list per song or per album or for an entire account. And when a commercial license (or any license that isn't decidedly non-commercial) is selected, certain features are greyed-out or removed unless they're paid for. At the same time, when a non-commercial license is selected, the UI elements for charging money are greyed out or removed.

Also, if you ever plan to open-source and decentralise Bandwagon, you can't expect all instances to charge the same for the same. Even if you hard-code in what must be paid for, the moment Bandwagon is open-source, there will be at least one fork where certain or all payments are not hard-coded anymore. Not only will some musicians or bands prefer that fork for their own instances, but it's even likely that public instances of such a fork will be launched.

At that point, your pricing calculation will become moot.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Bandwagon
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
@Schdadia :progresspride: Auf jeden Fall noch vorm Kauf drauf achten, daß das Ding nicht mit einem Supervisor-Paßwort verdongelt ist. Damit würdest du nämlich nicht in die UEFI-Konfiguration kommen, um die Bootreihenfolge zu ändern, und normal sind die Dinger so eingestellt, daß als erstes vom eingebauten Festspeicher gebootet wird.

ThinkPads der T-Klasse sind sehr oft Leasingrückläufer von größeren Kunden, und da ist gerne ein Supervisor-Paßwort gesetzt und nie zurückgesetzt worden. Wenn die Vorbesitzer eh nur das vorinstallierte Windows genutzt haben, dann stört sie das nicht nur nicht, sondern meistens merken sie das überhaupt nicht. Und meines Wissens braucht man zum Zurücksetzen des Supervisor-Paßworts einen Lötkolben.

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #ThinkPad
hub.netzgemeinde.euNetzgemeinde/Hubzilla
@Elegant Joy Digital Some may have moved to Bluesky because it is what they've been looking for in Mastodon: literally Twitter without Musk.

Some may have moved to other Mastodon instances.

Some may have moved to other places in the Fediverse that are not Mastodon. Maybe they needed more characters and more features and found them on Iceshrimp or Sharkey or Akkoma. Maybe they also wanted to move away from Facebook, got themselves a Friendica account, and then they discovered that a) Friendica is much more powerful, and b) you can follow Mastodon accounts from Friendica and vice versa. And they decided that their Mastodon account was now superfluous because Friendica can do just about all the same and a whole lot on top. Maybe they were even daring enough to tackle Hubzilla's massive learning curve to be rewarded with Hubzilla's massive set of features.

Either way, in the cases in the above paragraph, they couldn't mark their Mastodon accounts as moved to some other specific place, so you won't know.

Still, I think it's bad manners not to tell anyone where you've gone.

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Bluesky #Fediverse #Mastodon #Akkoma #Iceshrimp #Sharkey #Friendica Hubzilla
hub.netzgemeinde.euNetzgemeinde/Hubzilla
@vulgalour First of all, "image description" and "alt-text" don't mean the same thing.

Alt-text is what's added directly to the image. It's what screen readers used by blind or visually-impaired people read out loud as they can't "read out loud" an image. It's what people see instead of the image if the image doesn't show for them (text-based client, too slow Internet connection, whatever).

Alt-text should never convey more information than the image which it is a replacement for.

An image description that goes into the post itself is not alt-text.

I don't see any rule or part of the "Fediquette" or "Mastodon culture" that speaks against adding that additional information to a reply.

Whether it works or not depends on whether your customers accept it or not. I guess that 99% of your aspiring customers in the Fediverse will be on Mastodon, only see your start post and not be bothered to check the replies. So my suggestion is to leave room in the original post for tellling your customers that prices can be found in a reply to that post.

But seeing as this will happen to you a lot, it may be worth looking for someplace that offers you more than 500 characters:
  • a Mastodon instance with a raised character limit
  • Pleroma (5,000 characters by default, configurable by the admin)
  • Akkoma (5,000 characters by default, configurable by the admin)
  • Misskey (3,000 characters, hard-coded; just steer clear of misskey.io)
  • the various forks of Misskey and forks of their forks like Iceshrimp or Sharkey (thousands of characters by default, configurable by the admin)

If you need a five-digit character count, the best you can do requires basically re-learning the Fediverse, mastering a significantly steeper learning curve and very likely abandoning dedicated apps. Here we're talking about Mike Macgirvin's creations from Friendica (200,000 characters) to Hubzilla (probably even higher) to (streams) and Forte (over 24,000,000 characters).

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pleroma #Akkoma #Misskey #Forkey #Forkeys #Iceshrimp #Sharkey #Friendica #Hubzilla #Streams #(streams) #Forte #CharacterLimit #CharacterLimits #AltText #AltTextMeta #CWAltTextMeta
hub.netzgemeinde.euNetzgemeinde/Hubzilla
@Jasper Bienvenido The only talk about a Discord "alternative" in the Fediverse comes from people who want 1:1 clones of all kinds of commercial stuff with an absolutely identical UX, but free and open-source and decentralised with ActivityPub.

Otherwise, for just simply chatting, including multi-user chatrooms, there are Matrix (iOS/Android: Element) and XMPP (iOS: Monal IM, Android: Conversations). They are not part of the Fediverse, but they are free, open-source and decentralised. And they are alternatives to iMessage, Telegram and WhatsApp as well.

For discussion groups/forums, and very much in the Fediverse as in connected Mastodon, there are
  • Lemmy (Reddit clone)
  • Mbin (like Reddit, but better)
  • PieFed (like Reddit, but better)
  • Friendica (like Facebook, but better and more powerful)
  • Hubzilla (like Facebook, but much better and much, much more powerful)
  • (streams) (like Facebook, but much better and more powerful)
  • Forte (like Facebook, but much better and more powerful)

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Discord #DiscordAlternative #XMPP #Jabber #Matrix #Groups #Lemmy #Mbin #PieFed #Friendica #Hubzilla #Streams #(streams) #Forte
hub.netzgemeinde.euNetzgemeinde/Hubzilla
@vulgalour If the prices can be read in the image, you should add them to the alt-text. A price tag is text, and text must be transcribed.

If the prices are not in the image, they go into the post text. If you only have 500 characters, make room for them. But do not only make them available in the alt-text.

Not everyone can access alt-text. There are people with physical disabilities who cannot open an alt-text. Information that is only available in the alt-text, but neither in the post text nor in the image itself, is inaccessible and lost to them. This means that information must be in the image and the alt-text or in the post text, but never only in the alt-text.

#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta
hub.netzgemeinde.euNetzgemeinde/Hubzilla
@Schafstelze
(überflüssige Details auf der einen, fehlende wichtige Info auf der anderen Seite)

Im Endeffekt ist das Beschreiben von Bildern also eine Gratwanderung, um nicht Hochseilakt zu sagen, wo man exakt das Optimum finden muß. Minimal darunter oder darüber ist schon sanktionierungswürdig.

Und kopiert es dorthin wo es hingehört, nämlich in die Medienbeschreibung direkt am Medium.

Damit wäre also auch meine Vorgehensweise "illegal": relativ kurze, aber einigermaßen detaillierte Beschreibung im Alt-Text plus zusätzlich lange, hochdetaillierte Beschreibung inklusive aller notwendigen Erklärungen und inklusive Transkripten aller Texte innerhalb der Grenzen des Bildes im Post selbst (kein erwähnenswertes Zeichenlimit hier). Genau das sehe ich bei meinen eigenen Bildern aber als notwendig an.

Das Problem ist hier nur: Zumindest Erklärungen gehören niemals in den Alt-Text. Manche Menschen haben körperliche Behinderungen, die es ihnen unmöglich machen, Alt-Texte aufzurufen. Wenn Informationen nur im Alt-Text zu finden sind und weder im Post noch im Bild, dann sind diese Informationen für sie verloren.

CC: @Groschenromanautorin

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #AltText #AltTextMeta #CWAltTextMeta #Bildbeschreibung #Bildbeschreibungen #BildbeschreibungenMeta #CWBildbeschreibungenMeta
hub.netzgemeinde.euNetzgemeinde/Hubzilla
@Hiker @[Friedi Rūpintojė♡] @Christiane Brauch :calckey: @crossgolf_rebel - kostenlose Kwalitätsposts Und vor allem dann auch noch diese "Weisheit" mit Zähnen und Klauen zu verteidigen.

Die allermeisten Nutzer im Fediverse kennen in der Praxis nur Mastodon. Sie kennen das ganze Fediverse nur aus Mastodon-Sicht und durch die Mastodon-Brille. Für sie sind Sachen völlig normal und legitim wie,
  • "Mastodon" zu sagen, wenn man das ganze Netzwerk meint
  • "Fediverse" zu sagen, wenn man nur die Serveranwendung Mastodon bzw. deren Instanzen meint
  • Leuten außerhalb des Fediverse nur von Mastodon zu erzählen und entweder das Fediverse zu verschweigen oder direktweg wortwörtlich zu behaupten, das Fediverse bestünde nur aus Mastodon
  • zusätzliche Onlinedienste nur und ausschließlich auf Mastodon auszulegen und zum gesamten restlichen Fediverse inkompatibel zu machen, dann aber womöglich trotzdem "Fediverse" oder "Fedi" in den Namen einzubauen
  • zusätzliche Onlinedienste zwar generell fürs ganze Fediverse oder große Teile davon brauchbar zu machen, aber nur "Mastodon" oder "Masto" in den Namen einzubauen
  • zusätzliche Onlinedienste fürs Fediverse von vornherein nur für Mastodon zu bauen, auch wenn sie allen nutzen könnten
  • Mastodon als alleinigen Goldstandard im Fediverse und Maßstab für alle anderen Fediverse-Serveranwendungen darzustellen
  • sogar Unterschiede, die andere Fediverse-Serveranwendungen zu Mastodon haben, als Bugs oder Designfehler zu erachten, die abgestellt gehören (außer die jeweilige Serveranwendung hat in der Verwendung null Überschneidung mit Mastodon, und dann sehen sie sie als Zusatz an, der nachträglich an Mastodon drangeklebt wurde, z. B. PeerTube, Pixelfed, Funkwhale, Castopod)

Was dagegen im Fediverse aus ihrer Sicht absolut nicht okay ist und bekämpft gehört:
  • darauf hinzuweisen, daß das Fediverse mehr ist als nur Mastodon
  • darauf hinzuweisen, daß man selbst nicht auf Mastodon ist
  • gegenüber Mastodon-Nutzern Fediverse-Serveranwendungen auch nur zu erwähnen, die nicht als Erweiterung zu Mastodon angesehen werden (siehe oben)
  • auf Leute zu antworten, die einen nicht erwähnt haben und denen man auch nicht folgt
  • mehr als vier Hashtags, egal, wie man die rechtfertigt
  • Textformatierung in irgendeiner Form, weil Textformatierung in Mikroblogging nichts zu suchen hat und Mastodon-Nutzer selbst ihre Tröts nicht formatieren können
  • nicht an jeden Post oder Kommentar genau die CWs dranzubauen, die irgendein individueller Mastodon-Nutzer braucht
  • das CW-Feld (auch) für etwas anderes als CWs zu nutzen, weil Mastodon das CW-Feld ja erfunden hat, und zwar als solches
  • mehr als 500 Zeichen in einem Post
  • überhaupt irgendwelche Features zu nutzen, die Mastodon nicht hat (oder von denen sie nicht wissen, daß Mastodon sie auch hat), deren Nutzung Mastodon-Nutzer aber mitbekommen
  • generell irgendwas zu machen, was in der Mitte 2022 neu definierten Mastodon-Kultur so nicht vorkommt und so nicht vorgesehen ist

Wer im Fediverse nicht auf Mastodon ist, wird nicht unerheblich diskriminiert. Derweil behaupten sehr viele auf Mastodon, daß niemand im Fediverse dafür diskriminiert ist, welche Serveranwendung man nutzt, und zwar, während sie selbst weiterhin unbewußt oder gar absichtlich Nicht-Mastodon-Nutzer weiter diskriminieren.

Das kommt übrigens tatsächlich daher, daß diese Leute selbst am Anfang "wußten", daß das Fediverse nur Mastodon ist. Folglich haben sie sich an ein in sich geschlossenes reines Mastodon-Netzwerk gewöhnt und monate- oder gar jahrelang gefühlt in einem in sich geschlossenen reinen Mastodon-Netzwerk gelebt. Und das war schön.

Dann aber haben sie auf die harte Tour erfahren, daß das Fediverse eben nicht nur Mastodon ist. Im allgemeinen sind sie irgendwann auf einen Post oder Kommentar gestoßen, der sich auf verstörende Art und Weise von dem unterschied, was sie von Mastodon gewohnt waren. Der hatte mehrere tausend Zeichen. Oder Fett- oder Kursivschrift, und es war keine Unicode-Trickserei. Oder die Erwähnungen sahen "irgendwie komisch" aus, also verstörend komisch.

Wie auch immer: Dieser Post oder dieser Kommentar war so dermaßen kein Mastodon-Tröt, daß sie vor Schreck Ziegelsteine gekackt haben. Sie waren so gestört und verstört, daß sie das auf gar keinen Fall tolerieren konnten und nie angefangen haben, es zu tolerieren. Sie wollen, daß das Fediverse wieder nur Mastodon ist. Was es übrigens nie war. Oder zumindest, daß sich alles andere komplett an Mastodon anpaßt und wie Mastodon wird (oder wahlweise gefediblockt wird) und sich das ganze Fediverse zumindest wie nur Mastodon anfühlt.

Und dann heißt es, daß "Haltet einfach eure Schnauzen und macht alles ganz genau so, als wärt ihr selbst auf Mastodon" nicht diskriminierend sei. Als Mastodon-Nutzer darf man sowas äußern und muß es sogar.

Als Nicht-Mastodon-Nutzer läuft man im Fediverse dagegen, sobald Leute auf Mastodon von einem etwas mitbekommen, auf Eierschalen oder gar durch ein Minenfeld, weil es dann doch wieder irgendwelche ungeschriebenen mastodonzentrischen Regeln gibt, die auf Mastodon "jeder" kennt und beherzigt, von denen aber außerhalb von Mastodon nie jemand gehört hat.

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon #MastodonKultur #MastodonZentrizität #MastodonNormativität
hub.netzgemeinde.euNetzgemeinde/Hubzilla
@David Mitchell :CApride:
Mostly, just imagine you’re telling your friend over the phone about image you’re looking at and what they would need to know.


Let's just say I'm a bit critical about that because, in my opinion, it doesn't work in the Fediverse.

Jupiter Rowland schrieb den folgenden Beitrag Fri, 04 Oct 2024 23:30:02 +0200

You can't describe images in Fediverse posts like over the phone

Allegedly, a "good" advice for image descriptions is always to describe images like you'd describe them to someone on a landline phone.

Sorry, but that's non-sense. At least for anything that goes significantly beyond a real-life cat photo.

If you describe an image through a phone, you describe it to one person. Usually a person whom you know, so you've at least got a rough idea on what they need described. Even more importantly, you can ask that person what they want to know about the image if you don't know. And you get a reply.

If you describe an image for a public Fediverse post, you describe it to millions of Fediverse users and billions of Web users. You can't know what they all want, nor can you generalise what they all want. And you can't even ask one of them what they need described before or while describing, much less all of them. In fact, you can't ask at all. And yet, you have to cater to everyone's needs the same and throw no-one under a bus.

If I see a realistic chance that someone might be interested in some detail in one of my images, I will describe it. It won't be in the shorter description in the alt-text; instead, it will be in the long description which I've always put directly into the post so far, but whose placement I'm currently reconsidering. If something is unfamiliar enough to enough people that it requires an explanation, I will explain it in the long description.

Right now, only meme posts are an exception. They don't need as much of a visual description as long as I stick to the template, and a poll has revealed that people do prefer externally linked third-party explanations over my own ones blowing the character count of the post out of proportion. This is the one time that I can safely assume that I actually know what most people want.

@accessibility group @a11y group

#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Inclusion #A11y #Accessibility

CC: @Monstreline @Claire (sometimes Carla) @qurly(not curly)joe

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #QuotePost #QuoteTweet #QuoteToot #QuoteBoost
@Martin Holland Ditch Mastodon.

Move to Friendica.

Refollow everyone on Friendica whom you follow on Mastodon.

Integrate your Bluesky account directly into Friendica. Your Bluesky contacts will become Friendica contacts. No Bridgy Fed bridge needed.

Then you have one unified timeline stream with Friendica and Mastodon and the whole rest of the Fediverse and Bluesky. And diaspora*. And Tumblr (yes, right now already). And Libertree. Etc.

Better yet: You can send one and the same post to the Fediverse and to Bluesky and to diaspora* etc. all at once and receive comments from all these places under the same post.

Even better yet: A Friendica post can be as long as 400 Mastodon toots. And it can contain just about every kind of text formatting that's possible with HTML, up to and including a virtually unlimited number of images embedded in-line (instead of a maximum of four images always only dangling under the post as file attachments). And it can have a title.

Only two caveats: You'll probably need an account on a Friendica node in the USA to be able to federate with Threads. Even then you're at Meta's mercy because it's up to them whether that node is allowed to connect to Threads or not, and Friendica nodes are very likely to not be allowed to connect because Friendica's culture may collide with Threads' federation requirements.

Also, Friendica can't do polls.

#Long #LongPost #CWLong #CWLongPost #Fediverse #Mastodon #Bluesky #Threads #diaspora* #Tumblr #Friendica
@Muckz Es gibt auch noch etwas, das ganz offiziell und mit voller Absicht namen- und markenlos ist, aber von der Community (streams) genannt wird.

Das ist ein Fork eines Forks dreier Forks eines Forks (eines Forks) von Hubzilla, aber vom Erfinder von Friendica und Hubzilla. Es ist moderner und praktischer in der Handhabung als Hubzilla und liegt von der Lernkurve her zwischen Friendica und Hubzilla.

Was dabei aber zu bedenken wäre:
  • Es gibt dafür ebensowenig Smartphone-Apps wie für Hubzilla. Und es gibt ebensowenig Unterstützung für Mastodon-Apps, weil das ebensowenig sinnvoll wäre bei etwas, was so fundamental anders ist als Mastodon. Also Browser oder Progressive Web App.
  • An Verbindungsmöglichkeiten gibt's nur das hauseigene Nomad-Protokoll, das auch Hubzilla einschließt, und ActivityPub. Also nix diaspora*, nix RSS/Atom-Feeds abonnieren usw.
  • Es gibt in ganz Europa nur eine einzige Instanz mit offener Registrierung: Nomád. Serverstandort ist Ungarn, aber der Admin ist ein ausgewanderter Deutscher, @Der Pepe (nomád) ⁂ ⚝ (alias @Der Pepe (Hubzilla) ⁂ ⚝), ein Hubzilla-Veteran, der auch @Pepes Hubzilla-Sprechstunde und @PepeCyBs Welt betreibt.
  • Mit Dokumentation ist es auch noch nicht weit her. Pepe will noch eine schreiben, so, wie er die Hubzilla-Dokumentation auf Deutsch und Englisch komplett neu geschrieben hat.
  • Ähnlicher wie Facebook als Friendica mit dem Bookface-Theme ist es auch nicht.

#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #FacebookAlternative #Streams #(streams)
Codeberg.orgstreamsConsent based public domain federated communications server. Provides a feature rich ActivityPub and Nomad communication node.
@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)