joshim<p>really really really wanna spin up a [streams](<a href="https://codeberg.org/streams/streams" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">codeberg.org/streams/streams</span><span class="invisible"></span></a>) instance, but also can't be arsed.</p><p><a href="https://mastodon.social/tags/streams" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>streams</span></a> <a href="https://mastodon.social/tags/nomad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>nomad</span></a></p>
Recent searches
Search options
Administered by:
[STREAM] Wanton Attack (Swe) - Brinnande Jord [Album] (2025) https://heavymetalrarities.com/forum/viewtopic.php?f=182&t=71349&utm_source=dlvr.it&utm_medium=mastodon #Streams
@AJ Sadauskas
/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
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.
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
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
ALT
#Streams in #Java have been available since #Java8 and are still receiving new features up to #Java24. In this first blog post in the series on streams, I'll start with streams, provide an overview, and show the first steps with gatherers...
https://svenruppert.com/2025/03/29/from-java-8-to-24-the-evolution-of-the-streams-api/
Sven Ruppert · From Java 8 to 24: The evolution of the Streams APIThe introduction of the Stream API in Java marked a crucial step in the development of functional programming paradigms within the language. With Java 24, stream processing has been further consoli…
@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
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
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
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
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
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
That was when @Mike Macgirvin
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.
@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:
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
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
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Discord #DiscordAlternative #XMPP #Jabber #Matrix #Groups #Lemmy #Mbin #PieFed #Friendica #Hubzilla #Streams #(streams) #Forte
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
@pepecyb@hub.hubzilla.hu sowohl über Hubzilla als auch über Streams (von Dir ;-) gibt es ja auch Artikel auf @gnulinux@social.anoxinon.de
#Hubzilla #Streams #Fediverse
GNU/Linux.chHubzilla - die mächtige ungeschminkte Königin des FediverseVon der Entdeckung der Möglichkeiten dezentraler Netzwerke und einer leidenschaftlichen Zuneigung.