Notices by Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu), page 2
-
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Sunday, 17-Mar-2024 21:26:21 JST Jupiter Rowland
Things to know about Hubzilla:
You may come across posts from Hubzilla with images with sensitive content which nonetheless aren't blanked.
That's because Hubzilla can't flag images sensitive in a way that Mastodon understands.
Mastodon has its very own way of flagging images sensitive. There's an ActivityPub standard, but Mastodon ignores it completely and only supports its own non-standard flag.
1/2
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #FediTips #FediverseTips #Hubzilla -
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Saturday, 09-Mar-2024 19:02:25 JST Jupiter Rowland
Things to know about Hubzilla:
Both Mastodon and Hubzilla can let someone who doesn't follow you know if you mention them.
The difference is:
On Mastodon, it's on by default. When you mention someone who doesn't follow you, they know.
On Hubzilla, it's off by default. When you mention someone who doesn't follow you, they don't know unless you do so in a thread they know/follow.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #FediTips #FediverseTips #Hubzilla -
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Monday, 04-Mar-2024 15:35:25 JST Jupiter Rowland
@Regezi This could have one or several out of many reasons.
One, people on certain projects prefer to interact with people on the same or similar projects anyway, also due to overarching cultures. For example Misskey and Sharkey which have "UwU kawaii desu" written all over them while Mastodon doesn't.
Two, similarly, a refusal to let Mastodon users connect because this increases Mastodon's pressure on non-Mastodon projects to abandon their own culture in favour of Mastodon's.
Three, vice versa, Mastodon and its users rejecting the culture of non-Mastodon projects whenever it differs from Mastodon's. Many Mastodon users want everything that is "un-Mastodon-like" banned all across the whole Fediverse because it disturbs them, be it posts over 500 characters, be it quotes, be it "quote-tweets", be it text formatting in any way. However, all this stuff is perfectly normal and absolutely part of the culture everywhere outside of Mastodon.
So on the one hand, you have Mastodon users blocking everyone who does stuff that's alien to Mastodon upon first strike, depriving them of exposure and range on Mastodon. Plus everyone who ever talks about the Fediverse without only talking about Mastodon. On the other hand, you have non-Mastodon users who refuse to post to Mastodon users in the first place in order to avoid this kind of drama. And at least some projects actually allow you to select whom to post to, and yes, including Hubzilla.
Four, for the reasons mentioned above, some non-Mastodon users never even expose their accounts/channels to Mastodon, so nobody on Mastodon knows them. Some Hubzilla and (streams) users go another step further: If they're on (streams), they turn ActivityPub off altogether to keep themselves away from all the drama on Mastodon, and if they're on Hubzilla, they intentionally don't turn it on in the first place. This shields them from Mastodon practically entirely.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta -
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Monday, 04-Mar-2024 15:33:10 JST Jupiter Rowland
@Scott M. Stolz It's a bit murky what exactly happened back then.
Friendica started as Mistpark before a German told Mike what a German understands when reading that word, namely manure park. It was then renamed to Friendika because the desired Friendica domain was still blocked.
Free Friendika was a fork of Friendika by someone who wasn't content with Friendika's license. Free Friendika was on GitHub right away while Friendika wasn't. The fork involved copying Friendika's whole repository to GitHub.
Friendika was renamed Friendica in 2011 or 2012 when that name had become available.
It was afterwards that Friendica's own code repository was migrated to GitHub. Due to a GitHub "quirk", Friendica was automatically declared a fork of Free Friendika which is technically false.
What exactly happened license-wise is murky to me. Friendica can't have started under the AGPL because that'd exclude re-licensing a fork. But interestingly, Hubzilla is MIT-licensed.
So whatever license Friendica started out under, it might have been the community which put it under the AGPL after taking over from Mike who was now tinkering with the Zot protocol.
Looking at the licenses, it's very likely that Mike didn't fork Friendica Red off Friendica but off Free Friendika, itself a hard fork of Friendika. Thus, some improvements on Friendica never made it to Friendica Red.
I also guess it was named Friendica Red first and then renamed Red (from spanish la red = "the net") after the whole backend had been re-written against Zot, and the whole thing had stopped being Friendica in the first place. The re-naming to Red Matrix must have been a kind of marketing decision.
It's even unclear what exactly was the base for Osada later. Case in point: Well after the release of Hubzilla, Mike's own instances were still all branded "Red Matrix" although this project should have been abandoned in early 2015 when Hubzilla was created from it.
So either the Red Matrix was renamed Hubzilla and reworked into what was Hubzilla 1.0 in July, but Mike kept the "Red Matrix" brand for his own instances. In this case, Osada was forked from Hubzilla, and most everything added from the Red Matrix to Hubzilla was removed again from Hubzilla to Osada.
Or Hubzilla was forked from the Red Matrix, mostly soft-forked, the Red Matrix became Hubzilla's smaller and more experimental brother, and Mike's own instances all became testbeds for development that would have been more difficult with the extra Hubzilla cruft in the way. In this case, chances are bigger that Mike forked Osada from the Red Matrix which had never had all that extra Hubzilla stuff that Osada never had either.
Either way, the path from Mistpark to Hubzilla is both very complicated and very murky, and so I guess it's kind of justified to simplify it a bit. At the same time, it's too short to simplify it the same the path from either the Red Matrix or Hubzilla to (streams) can be simplified because the latter has had many more forks in it ("a fork of a fork... of a fork of {Hubzilla|the Red Matrix}").
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Forks #Mistpark #Friendika #FreeFriendika #Friendica #RedMatrix #Hubzilla -
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Monday, 04-Mar-2024 15:12:36 JST Jupiter Rowland
Maybe I should start an irregular series of "What Hubzilla is like" posts for people in the Fediverse, Mastodon specifically, who don't know anything about it. Not for those who want to switch, but for those who assume that Hubzilla is just like whatever else they know. Like, for Mastodon users who blindly assume that Hubzilla is just like Mastodon with a different UI and then act accordingly. Thus, it'd mostly focus on how Hubzilla is different from Mastodon.
The difficult part would be to limit these posts to only 500 characters. Minus what I'll need for the hashtags, namely #Hubzilla, #FediTips and #FediverseTips to increase discoverability for those who are interested and #FediMeta, #FediverseMeta, #CWFediMeta and #CWFediverseMeta so that these posts are automatically removed or hidden behind generated content warnings by already existing filters. Because I know for a fact that many Mastodon users won't touch anything that goes even a smidge over 500 characters. And I know that there are Mastodon users for whom any and all Fediverse meta is too nerve-gratingly techy.
#Long #LongPost #CWLong #CWLongPost #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta -
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Monday, 04-Mar-2024 15:12:33 JST Jupiter Rowland
@Regezi
which perhaps other networks can do...
...and have to do.
Next to nobody on Mastodon talks about anything that isn't Mastodon or whatever Mastodon doesn't want to federate with (Threads, Bluesky).
The only exceptions are devs who advertise their Fedi projects. And even they only use Mastodon if a) their project isn't ready yet, and/or b) it's too much different from Mastodon to be used for advertising.
Everyone else who talks about the non-Mastodon Fediverse isn't on Mastodon. -
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Monday, 04-Mar-2024 15:12:29 JST Jupiter Rowland
@eshep There were another two threads about Bridgy Fed creating a bridge to Bluesky. And again, people loudly demanded the Fediverse be ActivityPub only.
Thing is, the Fediverse has never been ActivityPub only. Mastodon started in 2016 with OStatus because, like Pleroma earlier the same year, it started as an alternative frontend for GNU social. So GNU social was based on OStatus, and both Friendica and Hubzilla already knew it, too. At that point, the term "Fediverse" was already some four years old.
It was only in September of 2018 that Mastodon announced the introduction of ActivityPub as an additional protocol. Hubzilla had done so two months earlier, so Mastodon has never even been the only ActivityPub project.
But the vast majority of Mastodon users seems to think that Eugen Rochko invented a) Mastodon, b) ActivityPub and c) the Fediverse and d) did so in 2022 as a reaction upon Musk's announcement to take over Twitter. And literally everything else in the Fediverse was made after Mastodon.
Not only that, but the Bluesky bridge threads made it painfully obvious that a two-digit percentage of Mastodon users is still fully convinced that the Fediverse is actually nothing but Mastodon. Because they clearly want to fight for it remaining that way, unaware that is isn't that way.
I think when Hubzilla and Friendica users joined the threads and started commenting, these folks either ended up deeply disturbed with their worldviews shattered to rubble upon the revelation that there's more in the Fediverse than Mastodon already now. Or they didn't even notice that these posts a) talked about non-Mastodon Fediverse projects which are reality now and b) came from outside of Mastodon, no matter how blatantly obvious it was that these posts could impossibly have been sent from Mastodon.
The rest might be aware that there's more to the Fediverse than Mastodon. But this "more" is limited to Pixelfed and PeerTube and what they think must essentially be Mastodon with a different UI.
It was just as painfully obvious that just about none of the Mastodon users who posted on these threads and railed loudly against bridges of any kind knows that stuff is bridged to Mastodon already now and has been bridged to Mastodon since Mastodon's own launch. This stuff currently is Hubzilla and (streams), none of which are based on ActivityPub.
Granted, in these cases, we aren't talking about one big third-party bridge for everyone. The bridge in question is named "PubCrawl", it's a first-party add-on to both Hubzilla and (streams) that comes with the server application itself, so while not firmly baked into their cores, it's an official part of them, and there's one individual bridge for each channel. But yes, there are bridges.
This is one thing I'd like to explain in such a "snippet". Other things would be, for example:- Mastodon was launched in 2016. Hubzilla was both launched and had its first stable point release in 2015, and it's a fork of the now-defunct Red Matrix from 2012 which is a fork of Friendica from 2010. Also, Mastodon announced ActivityPub integration in September, 2018; Hubzilla did so in July. In both cases, Hubzilla was there first. It is not an intruder. Deal with it.
- Mastodon generally has a 500-character limit; its whole culture is built around this limit. Hubzilla doesn't have any character limit; its culture doesn't know any character limits.
- Mastodon has a dedicated content warning field. But that content warning field is actually a re-appropriated summary field because nobody needs a summary for 500 characters. On Hubzilla, it still is a summary field. And Hubzilla does content warnings reader-side and automatically by detecting keywords in posts, and optionally so. Thus, writing Mastodon-style content warnings is not part of Hubzilla's culture. But giving summaries for long posts in what Mastodon perceives as a content warning is part of Hubzilla's culture.
- An explanation why Hubzilla can't add Mastodon-style content warnings to replies which includes a description of Hubzilla's conversation model in comparison with Mastodon's.
- Hubzilla has always had full-text search with no opt-out. This is, of course, limited to whatever any given hub knows, but it does never exclude Mastodon toots.
- Hubzilla has always had text formatting. It has always been part of its culture. And large parts of its text formatting capabilities aren't even shown on Mastodon.
- Hubzilla's weird-looking mentions and hashtags are hard-coded and have been since six years before Mastodon.
- "Quote-tweets" have always been part of Hubzilla's culture because Hubzilla does that instead of "retweeting" or "boosting" because it can't boost (again yet). It always links to both the original post and the original poster. There will never be a way for anyone on Mastodon to opt out of it.
- Hubzilla can quote anyone anywhere in the Fediverse with no resistance whatsoever. It has always been able to do that. There will never be a way for anyone on Mastodon to opt out of it.
Now, this is not meant to be advertisement. It's more like a series of public service announcements to raise Hubzilla awareness.
I'm well aware that it could also have the effect of triggering or increasing anti-Hubzilla campaigning on Mastodon. I mean, most Mastodon users probably don't even know that Hubzilla exists, and most of who do don't know what Hubzilla can do. And large parts of what it can do fall under "atrocities" and "breaking the Fediquette" from a Mastodon point of view. Mastodon doesn't riot against that stuff because it doesn't know about that stuff.
But if such riots broke out because Hubzilla is so not like Mastodon and even refuses to be more like Mastodon, that'd tell a lot about Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla - Mastodon was launched in 2016. Hubzilla was both launched and had its first stable point release in 2015, and it's a fork of the now-defunct Red Matrix from 2012 which is a fork of Friendica from 2010. Also, Mastodon announced ActivityPub integration in September, 2018; Hubzilla did so in July. In both cases, Hubzilla was there first. It is not an intruder. Deal with it.
-
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Sunday, 03-Mar-2024 18:56:48 JST Jupiter Rowland
Things to know about Hubzilla:
This may come as a surprise to some of you, but: The Fediverse is not only Mastodon.
Hubzilla, for example, is inarguably a part of the Fediverse just like Mastodon.
But Hubzilla is not a Mastodon instance.
Hubzilla is not a Mastodon fork either.
Hubzilla is developed fully independently from Mastodon.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #FediTips #FediverseTips #NotOnlyMastodon #MastodonIsNotTheFediverse #FediverseIsNotMastodon #Hubzilla -
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Sunday, 03-Mar-2024 04:12:49 JST Jupiter Rowland
I'm going to start a series of posts titled Things to know about Hubzilla.
The target audience is mostly Mastodon users, so each post will be 500 characters (raw number, not Mastodon count) or fewer.
It will not be advertisement for those who want to switch, though. It is to help Mastodon users understand what this Hubzilla is that they may have to deal with, e.g. in their timelines.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #FediTips #FediverseTips #Hubzilla -
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Wednesday, 28-Feb-2024 20:55:55 JST Jupiter Rowland
On the one hand, FediGroups is kind of lacking from a Hubzilla/(streams) POV. Forums on Hubzilla and (streams) can be made fully private, i.e. nobody from outside the forum can even read them. Not possible on FediGroups because not possible on Mastodon, not to mention that it'd be somewhat inconvenient without server-side OpenWebAuth support.
Also, it's not only possible for Hubzilla and (streams) users to post to Hubzilla and (streams) forums without also posting to their own connections, it's standard. Hubzilla and (streams) forums only forward posts to their connections that come in as direct messages. This does not apply to comments, only to posts.
The same thing is impossible with FediGroups because it rejects direct messages outright.
On the other hand, both features make Hubzilla and (streams) forums harder to use for Mastodon users as they want to use everything in the Fediverse as if it's all Mastodon. Even if a forum is configured to be read by any logged-in user, Hubzilla and (streams) don't recognise logged-in Mastodon users because Mastodon still doesn't have client-side OpenWebAuth support either.
And the very reason why Hubzilla and (streams) forums are being perceived as incompatible with Mastodon is because it's too inconvenient for Mastodon users to start threads on them. I'm not even sure if this has been tested because there's no documentation on this.
Either Mastodon users have to send a DM to the forum which is completely unnatural to Mastodon users who are used to @-mentioning everything unless it's actually private. Or they actually have to mention Hubzilla and (streams) forums with @!, the Hubzilla/(streams) prefix for DMs, which is completely unknown and completely alien to Mastodon, not to mention completely unsupported.
That said, there are even more shortcomings from a Hubzilla/(streams) POV.
It's impossible to make threads with titles because Mastodon doesn't support titles on Note objects. By the way, this might hit the Friendica crowd hard: FediGroups won't work with posts from Friendica with titles because these go out as Article objects (like blog posts) instead of Note objects (like Mastodon toots), and I'm not sure how FediGroups will handle Article objects.
Generally, it seems a crazy idea to build groups on top of something that not only doesn't have a concept of groups, but that doesn't have a concept of conversations either. But then again, at least two thirds of the Fediverse don't have a concept of conversations. Users of these two thirds can only follow threads if everyone in that thread keeps mentioning them in every last post. At least on Hubzilla and (streams), this is completely unnecessary.
Moderation will be unnecessarily difficult because Mastodon also doesn't have a concept of permissions beyond Mute and Block, and because all replies to posts are posts themselves and exclusively owned by whoever posts them and thus can't be moderated by the thread starter.
Also, FediGroups are so far the only "groups" in the Fediverse that don't present themselves as Group actors. Thus, they're the only ones which Hubzilla and (streams) don't list as forums. Even Guppe groups are listed as forums on Hubzilla and probably also on (streams). This can only change if FediGroups actually soft-forks Mastodon and at least adds Group actor identification, no matter how much of Mastodon's code will have to be changed for that.
I'll be honest: I hope that when the redesign of conversations on (streams) goes stable, it'll become a good base for Fediverse-wide forums, even for Mastodon users who think the Fediverse is only Mastodon and for notoriously stubborn Misskey plus Forkeys.
@Various Fediverse features
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla #Streams #(streams) #Groups #Forums #FediGroups -
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Wednesday, 28-Feb-2024 20:55:41 JST Jupiter Rowland
@julais Essentially, @Mike Macgirvin 🖥️ (creator of the now-defunct DFRN protocol, Friendica, the Zot protocol and Hubzilla, inventor of nomadic identity and creator and maintainer of both the Nomad protocol and the streams repository) is redesigning (streams)' conversation model into something that's more compatible with ActivityPub and easier to understand for projects built against the ActivityPub protocol.
It's called Conversation Containers.
If you can take a lot of technobabble: Here's the original post.
It's worth mentioning at this point that (streams) is not based on ActivityPub itself. It's based on an advanced version of the Zot protocol named Nomad, and it only supports ActivityPub as an optional secondary protocol.
CC: @Various Fediverse features
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ActivityPub #Streams #(streams) -
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Saturday, 24-Feb-2024 05:07:10 JST Jupiter Rowland
@Tokyo Outsider (337ppm) The high risk is that people come straight from Mastodon, the only Fediverse project they're used to, to Hubzilla in expectation of something that works and handles like Mastodon plus whatever extra stuff on top Hubzilla has that attracted them. I mean, there are people who came to Hubzilla simply because they wanted more than 500 characters.
And then they end up tripping over things that make Hubzilla not more than Mastodon but unexpectedly different from Mastodon. The one-post-many-comments conversation model. The permissions settings that don't even default to the same behaviour as Mastodon which doesn't even really know such a thing as permissions. "Quote-toots" but no boosts. No content warning field until they find out that it's that thing labelled "Summary" for some reason. No alt-text field. Hopelessly outdated user documentation that also reads like a tech spec. No local timeline, no federated timeline. Everything being named differently. Generally, Hubzilla not mollycoddling its users, not even newbies. And so on.
I mean, some return to Mastodon with a "Hubzilla sucks" verdict because they failed to connect to even one of their old Mastodon acquaintances, because nothing and nobody told them right off the bat that they have to turn ActivityPub on first, much less how to do that.
If many more Mastodon users tried out Hubzilla and really tried, there would be more voices demanding Hubzilla be much more like Mastodon. Just like there are Twitter refugees on Mastodon who, after many months of using Mastodon, still can't get used to its differences from Twitter and demand things be just like on Twitter, including a secret-sauce algorithm that automagically fills their personal timeline with exactly what they want to read without themselves having to do anything (not that 𝕏 actually did that) and sends their post to the local timelines of everyone who's interested in that.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Hubzilla -
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Saturday, 17-Feb-2024 16:03:19 JST Jupiter Rowland
@F4GRX Sébastien Back in 2016, the very moment he launched Mastodon, @Eugen Rochko himself forced Friendica and Hubzilla upon all Mastodon users without ever letting them opt in.
They've been causing discomfort and blocks ever since with their cultural differences, their un-Mastodon-like behaviour and their staunch refusal to become like Mastodon.
Oh, and they, too, were connected to Mastodon through bridges, and while Friendica has since switched to ActivityPub, Hubzilla still is.
And where was the protest when (streams) forced itself upon Mastodon in October of 2021 in the same way as Hubzilla? Through ActivityPub-to-Nomad bridges and with largely the same non-Mastodon-like culture?
CC: @Scott M. Stolz
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams) #Bluesky #Bridge #BridgyFed #BlueskyBridge -
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Friday, 16-Feb-2024 21:23:49 JST Jupiter Rowland
@HistoPol Well, technically speaking, image sources don't belong in alt-text, but in the post text itself where everyone can access them.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText -
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Friday, 16-Feb-2024 10:16:04 JST Jupiter Rowland
@HistoPol
That sucks. Why would @Gargron waste limited resources on (I guess?) FOSS that could be used?
I don't necessarily think that Mastodon development intentionally aims for as little compatibility with the rest of the Fediverse as possible. It might just as well be a case of refusing to acknowledge that the Fediverse is more than Mastodon or a case of not even knowing what the rest of the Fediverse can do.
However: Mastodon is notorious for ignoring a) standards and b) stuff that already exists. Mastodon does not fulfill the ActivityPub standard to a tee. It's just as close to it as it has to be and diverts from it wherever it feels like it.
One example is the sensitive flag for images. There's something for this in the official ActivityPub standard. And yet, when Mastodon adopted ActivityPub, it decided to not only have its own home-brew, non-standard, undocumented sensitive flag but to also not support the ActivityPub standard flag at all.
AFAIK, (streams) lets you flag images in your file space as sensitive because Hubzilla does. However, when you flag an image as sensitive, and you embed it into a post that also goes to Mastodon, then Mastodon will treat this image as unflagged. (streams) jumps through a hoop now and puts Mastodon's non-standard sensitive flag on all images in posts that have the hashtag #nsfw and/or #sensitive.
Also, it's strange how long it takes Mastodon to implement quote-posts or groups. Both things that have been around since 2010 when Friendica was launched. There's a whole bunch of Fediverse projects that have groups/forums, for example, the various Reddit replacements. Misskey and all its forks have quote-posts. Friendica, Hubzilla and (streams) have always had both.
So, given Mastodon's track record, chances are that Mastodon's implementation of groups becomes incompatible both with how Lemmy communities and /kbin magazines work and with how Friendica, Hubzilla and (streams) have groups/forums implemented.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Groups -
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Friday, 16-Feb-2024 08:37:17 JST Jupiter Rowland
@HistoPol
I pay attention to such thinks, but even with hindsight, I do not see such a group reference.
That's because Mastodon doesn't tell you that- it's a group (because Mastodon doesn't understand the concept of groups)
- it's on Friendica (because Mastodon does its best to shield the existence of non-Mastodon Fediverse projects from its users)
On #Mastodon, groups are also possible, but I forgot how to use them, as I used them so little.
Not yet. They're working on it. And everything else that has working groups/forums now is afraid that Mastodon will re-invent the wheel in a way that's the most incompatible possible to what already exists on more than half a dozen Fediverse projects.
What you mean is probably Guppe, but that isn't built into Mastodon and a far cry from what's possible on Friendica.
CC: @Jamie Booth @Oli @Ryan Barrett @Luca Sironi @Andre @chronohart
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #Friendica #Groups - it's a group (because Mastodon doesn't understand the concept of groups)
-
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Friday, 16-Feb-2024 04:26:53 JST Jupiter Rowland
Since the BridgyFed drama, there might be four more reasons for Mastodon users to want Friendica, Hubzilla and (streams) out of the Fediverse. I mean, aside from their usual atrocities like their users writing well over 500 characters, using text formatting, quoting and quote-posting like it's totally normal. Because it is for them. And aside from no instance on any of the three having rules and moderator numbers on par with Mastodon.
One, they aren't based on ActivityPub. They're technically bridged to Mastodon. They're bridged one instance at the time, and the bridge is a plug-in on the instance and therefore part of the project. But still, it isn't that much different from BridgyFed connecting Bluesky to the rest of the Fediverse.
Two, since they aren't based on ActivityPub, they're aliens. Aliens of basically the same kind as Bluesky, only that they've mostly got those features that Mastodon has that Bluesky doesn't. But the BridgyFed drama isn't about Bluesky's features or lack thereof, and it isn't only about Bluesky being commercial either. It's also about Bluesky being too different in technology, functionality and culture. But let me tell you a secret: Bluesky is probably much closer to Mastodon than Hubzilla. I mean, I've already mentioned how Friendica, Hubzilla and (streams) users "misbehave" from a Mastodon point of view. You won't see any of this come from Bluesky anytime soon.
Three, Friendica is already fully federated with Bluesky. It's a feature that was introduced with the latest stable release.
Four, speaking of Friendica, that allegedly "hate-fuelling" Fediverse News is a public group account on Friendica. Only that the user who started that particular thread is on Firefish, and Fediverse News only automatically forwarded what he had posted.
So where's the outrage?
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams) #BridgyFed #Bluesky #Bridge #BlueskyBridge -
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Tuesday, 30-Jan-2024 19:58:00 JST Jupiter Rowland
tl;dr:
@Tokyo Outsider (337ppm)
Also your post sets out two options then the poll has four.
Each option for sighted and for non-sighted users.
And people who want the description in the alt text have no way to vote for it. 🤔
Not an option. Explanations never go in alt-text. And Mastodon has a hard limit of 1,500 characters in alt-text and chops longer alt-texts off while my own image descriptions may have 5,000+ characters of explanations (necessary due to the niche topic) + 30,000+ characters of visual descriptions. -
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Tuesday, 30-Jan-2024 19:28:27 JST Jupiter Rowland
After 2 days, this poll has got half as many votes as it has options although I've launched it on a Sunday?
Have so many Mastodon users or instances muted me or blocked me? Or can't Mastodon users wrap their minds around having over 500 characters and/or describing images elsewhere than in alt-text?
Seriously, I've asked all of you for your opinions on something related to accessibility, and I want to see them in this poll. So please boost/"retoot" the start post of this thread once more. -
Embed this notice
Jupiter Rowland (jupiter_rowland@hub.netzgemeinde.eu)'s status on Monday, 29-Jan-2024 11:14:22 JST Jupiter Rowland
@Tokyo Outsider (337ppm) It runs on a LAMP stack as-is, and it's even available for YunoHost.