jupiter_rowland@hub.netzgemeinde.eu
@jupiter_rowland@hub.netzgemeinde.eu@hub.netzgemeinde.eu
This is a remote user, information on this page may be incomplete. View original ↗
An avatar roaming the decentralised and federated 3-D virtual worlds based on OpenSimulator, a free and open-source server-side re-implementation of Second Life. Mostly talking about OpenSim, sometimes about other virtual worlds, occasionally about the Fediverse beyond Mastodon. No, the Fediverse is not only Mastodon.
If you're looking for real-life people posting about real-life topics, go look somewhere else. This channel is never about real life.
Even if you see me on Mastodon, I'm not on Mastodon myself. I'm on Hubzilla which is neither a Mastodon instance nor a Mastodon fork. In fact, it's older and much more powerful than Mastodon. And it has always been connected to Mastodon for as long as Mastodon has existed.
I regularly write posts with way more than 500 characters. If that disturbs you, block me now, but don't complain. I'm not on Mastodon, I don't have a character limit here.
I rather give too many content warnings than too few. But I have absolutely no means of blanking out pictures for Mastodon users.
I always describe my images, no matter how long it takes. My posts with image descriptions tend to be my longest. Don't go looking for my image descriptions in the alt-text; they're always in the post text which is always hidden behind a content warning due to being over 500 characters long.
If you follow me, you may notice that I'll follow you back, and then I'll unfollow you again. That's because we don't have unidirectional "following" here on Hubzilla, only bidirectional "contacts". I can't just allow you to follow me. I have to approve a full bidirectional connection. But if you don't post anything interesting, and I don't know you from OpenSim, and you're on something that has unidirectional "following", I'll delete you from my contact list again. If you may post something interesting occasionally, I may keep the connection, but I'll probably filter it heavily. Yes, I can filter individual contacts here on Hubzilla.
If you're on Friendica, Hubzilla, (streams) or Forte, all of which have bidirectional "contacts", I have to keep the connection. But I'll either not grant you permission to send me your posts (I can do that, yes), or I'll filter you.
My "birthday" isn't my actual birthday but my rezday, the day that my first avatar appeared in-world for the first time.
If you happen to know German, maybe my "homepage" is something for you, a blog which, much like this channel, is about OpenSim and generally virtual worlds.
#OpenSim #OpenSimulator #VirtualWorlds #Metaverse #SocialVR #fedi22
If you're looking for real-life people posting about real-life topics, go look somewhere else. This channel is never about real life.
Even if you see me on Mastodon, I'm not on Mastodon myself. I'm on Hubzilla which is neither a Mastodon instance nor a Mastodon fork. In fact, it's older and much more powerful than Mastodon. And it has always been connected to Mastodon for as long as Mastodon has existed.
I regularly write posts with way more than 500 characters. If that disturbs you, block me now, but don't complain. I'm not on Mastodon, I don't have a character limit here.
I rather give too many content warnings than too few. But I have absolutely no means of blanking out pictures for Mastodon users.
I always describe my images, no matter how long it takes. My posts with image descriptions tend to be my longest. Don't go looking for my image descriptions in the alt-text; they're always in the post text which is always hidden behind a content warning due to being over 500 characters long.
If you follow me, you may notice that I'll follow you back, and then I'll unfollow you again. That's because we don't have unidirectional "following" here on Hubzilla, only bidirectional "contacts". I can't just allow you to follow me. I have to approve a full bidirectional connection. But if you don't post anything interesting, and I don't know you from OpenSim, and you're on something that has unidirectional "following", I'll delete you from my contact list again. If you may post something interesting occasionally, I may keep the connection, but I'll probably filter it heavily. Yes, I can filter individual contacts here on Hubzilla.
If you're on Friendica, Hubzilla, (streams) or Forte, all of which have bidirectional "contacts", I have to keep the connection. But I'll either not grant you permission to send me your posts (I can do that, yes), or I'll filter you.
My "birthday" isn't my actual birthday but my rezday, the day that my first avatar appeared in-world for the first time.
If you happen to know German, maybe my "homepage" is something for you, a blog which, much like this channel, is about OpenSim and generally virtual worlds.
#OpenSim #OpenSimulator #VirtualWorlds #Metaverse #SocialVR #fedi22
- Comment on Mentions to ActivityPub users 1 week ago: This is not a bug. It's entirely by design, and it has been for many years longer than Mastodon has even existed.
It's how Mike Macgirvin, original creator of Hubzilla, intended it when he created what's Friendica today back in 2010.
It just happens so that Mastodon doesn't expect this and doesn't handle it gracefully. After all, Mastodon is some six years younger than Friendica and, depending on what counts as Hubzilla's start, some four years younger than Hubzilla.
In other words: The Friendica/Hubzilla way of mentioning was here first. Mastodon and its users have to deal with it. Just like with Friendica and Hubzilla having no character limit before Mastodon had 500 characters. - Comment on Spam free social media 3 weeks ago: @Der Pepe (Hubzilla) ⁂
(what exactly is a ‘sensitive domain name’?)
A domain name that looks good as part of your Hubzilla ID on a professional business card that you hand over to business clients or business partners.
A domain name that looks like it's the name of a multi-million-Euro corporation or at least owned by a multi-million-Euro corporation. Not even "Hubzilla" itself does that.
<NAME>.com
<NAME>® is a registered trademark of <NAME> Digital Business Solutions GmbH. All rights reserved. - Comment on clerk wrote the following post Sat, 17 Oct 2026 00:10:47 +0200 4 weeks ago: There's no way to stop unread messages being announced as such and added to the unread counter. Also, there's no way to get rid of the start post and the thread.
There's only thing you can possibly to do reduce the chance of this happening in the future.
Let's suppose you have contacts on Mastodon who really behave like Mastodon users. They boost everything they like. They clutter your stream with tons of uninteresting boost spam. One of the reasons why your unread counter goes to "99+" in no time.
If you want to get rid of that boost spam from certain contacts, do as follows:- Go to Connections.
- Click on the cogwheel on the navbar, a bit to the right of your channel menu.
- Activate the per-connection filters. They're the only option available.
- Go back to Connections.
- Find the contacts that spam you with boosts.
- Edit each one of them, one by one.
You'll now find two filter lists, an allowlist and a blocklist, just like for your channel, only that these only affect the content coming in from/through this particular contact. - Add the following line to the blocklist:
?verb == Announce
This will filter out all boosts/renotes/reposts/repeats from that contact.
- Comment on starterpacks 5 weeks ago: @𝓒𝓱𝓻𝓲𝓼 I'm not a coder, so I can't answer this more precisely.
FediDevs was designed to latch onto Mastodon's profile fields, Mastodon's database fields and Mastodon's inner workings.
When enough people begged for it to also support e.g. Misskey, the developers had to add code that would latch onto Misskey's profile fields, Misskey's database fields and Misskey's inner workings.
Same with Pleroma. Same probably with Friendica. And so on.
So if FediDevs wants to support Hubzilla, it would have to dig into Hubzilla, latch onto the profile fields in Hubzilla's public profiles, it would have to latch onto database fields that probably only Hubzilla has, it would have to latch onto Hubzilla's very specific inner workings. And that'd be a whole lot of work because Hubzilla is more different from Mastodon than Misskey is.
Then, and only then, will FediDevs be able to support adding Hubzilla channels to starter packs. - Comment on starterpacks 5 weeks ago: The website is called Fedidevs, but it used to be built against only Mastodon. Not the Mastodon client API, but Mastodon's very specific inner workings.
The issue wasn't just that starter packs only worked on Mastodon. It was also that starter packs could only contain Mastodon accounts, and only Mastodon users were even able to join the site because the technical process of joining explicitly looked for features that are only present on Mastodon and nowhere else.
It was blatantly obvious that the maintainers of this site firmly believed that the Fediverse is only Mastodon when they built it, and that they refused to accept the truth when someone pointed out that there's more to the Fediverse than Mastodon later on.
Eventually, after quite a while of operation, they added specific code for certain Fediverse server applications. They added specific code so that Misskey accounts could be added to starter packs. They added specific code so that Pleroma accounts could be added to starter packs. And so on.
The whole thing is not built against any API, much less against ActivityPub. It's built against the inner workings of specific Fediverse server applications. Changing that would require a complete rewrite of the entire backend.
So in order for Hubzilla channels to be added to starter packs, the FediDevs maintainers would have to add specific code to FediDevs so that it supports Hubzilla channels. - Submitted 1 month ago to adminsforum@hubzilla.org | 0 comments
- Submitted 1 month ago to adminsforum@hubzilla.org | 0 comments
- Comment on Accessibility improvement needed 1 month ago: @Harald Eilertsen Very nice!
The sliding toggles are fancy, but confusing even to sighted users who aren't used to Hubzilla. - Comment on Accessibility improvement needed 1 month ago: Allow me to chime in here, everyone.
First of all, accessibility is a basic human right.
There actually are blind or visually-impaired users in the Fediverse, also because they're more welcome here than in the corporate silos.
This also means: Just like alt-texts, a Web UI that works with screen reader software (JAWS, NVDA, VoiceOver, TalkBack, Narrator, Orca etc.) is not just another dumb Mastodon fad.
If activists like @Robert Kingett (who, by the way, is blind, and who has some significant range in the Fediverse) criticise Hubzilla for being unusable, this has to be taken seriously. Even though, admittedly, Hubzilla's Web UI using the Redbasic theme isn't even that friendly towards sighted users.
In my opinion, Hubzilla has two options now.
One, carry on as usually, consider it a Mastodon fad that must under no circumstances be adopted, shrug it off, chase all the blind users away back to Mastodon and eventually be branded utterly ableist.
Two, if that's possible in any way, make the Redbasic-based default Web UI accessible to screen reader users and become one of the currently not exactly many Fediverse server applications that do care for UI accessibility.
The latter explicitly welcomes blind users. The former flips the bird at them, now that the "Hubzilla is inaccessible" cat is out of the bag.
Combine this with Hubzilla's notoriously condescending attitude towards Mastodon (where just about everyone who is blind hangs out because they literally don't have much of a choice), and you get a condescending attitude towards disabled people.
Ideally, at least @Saiwal should do the same with his themes. Even though many hub admins refuse to install them because they were written entirely by AI, especially Solidified appears to make using Hubzilla much easier in general.
I can see many veterans who have come from Facebook or nothing at all to Friendica to Hubzilla, whose contacts are all on Hubzilla, Friendica, (streams) and/or Forte, or who have intentionally left PubCrawl uninstalled, shrug it off. We've never needed accessibility. Even if it comes back to bite Hubzilla because the whole platform is being ostracised, sanctioned or even gradually blocked from lots of other Fediverse servers, they'll say that's no loss. For it's no loss to them.
But they mustn't wonder then how come Hubzilla can't get enough of a foothold in the Fediverse for more people to come over from all that underequipped stuff. Especially if Hubzilla not only ignores, but explicitly rejects accessibility.
And no, third-party add-ons can't fix this. Many Hub admins won't install these either.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Inclusion #A11y #Accessibility - Submitted 1 month ago to adminsforum@hubzilla.org | 0 comments
- Submitted 1 month ago to adminsforum@hubzilla.org | 0 comments
- Comment on [Bug] Boolean lines in contact allowlists with more than one OR don't work 2 months ago: As of Hubzilla 11.4.1, the behaviour seems to have changed.
If you have a chain of criteria with OR (||) between them on the allowlist, only the first and last criteria will pass.
If you have?body ~= foo || ?body ~= bar || ?body ~= bazas an allowlist line:- Messages with "foo" will pass
- Messages with "bar" will not pass
- Messages with "baz" will pass"
Likewise, if you have?body ~= foo || ?body ~= bar || ?body ~= baz || ?body ~= qux || ~body ~= quuxas an allowlist line:- Messages with "foo" will pass
- Messages with "bar" will not pass
- Messages with "baz" will not pass
- Messages with "qux" will not pass
- Messages with "quux" will pass"
Test cases:'incl: three criteria with OR, all keywords expected in the body, first one present in the body' => [
'?body ~= grasshopper || ?body ~= rosencrantz || ?body ~= guildenstern',
'',
true
],
'incl: three criteria with OR, all keywords expected in the body, second one present in the body' => [
'?body ~= rosencrantz || ?body ~= grasshopper || ?body ~= guildenstern',
'',
true
],
'incl: three criteria with OR, all keywords expected in the body, last one present in the body' => [
'?body ~= rosencrantz || ?body ~= guildenstern || ?body ~= grasshopper',
'',
true
],
'incl: three criteria with OR, all keywords expected in the body, first one present in the body; excl: item must not be a repeat' => [
'?body ~= grasshopper || ?body ~= rosencrantz || ?body ~= guildenstern',
'?verb == Announce',
true
],
'incl: three criteria with OR, all keywords expected in the body, second one present in the body; excl: item must not be a repeat' => [
'?body ~= rosencrantz || ?body ~= grasshopper || ?body ~= guildenstern',
'?verb == Announce',
true
],
'incl: three criteria with OR, all keywords expected in the body, last one present in the body; excl: item must not be a repeat' => [
'?body ~= rosencrantz || ?body ~= guildenstern || ?body ~= grasshopper',
'?verb == Announce',
true
],
The second and the fifth test case should fail, the others should pass. - Comment on [Bug] Boolean lines in contact allowlists with more than one OR don't work 2 months ago: Here are six test cases for your convenience:
'incl: two criteria with OR, both keywords in the body' => [
'?body ~= grasshopper || ?body ~= summer',
'',
true
],
'incl: three criteria with OR, all keywords in the body' => [
'?body ~= grasshopper || ?body ~= summer || ?body ~= ant',
'',
true
],
'incl: three criteria with OR, one keyword in the body, one check if the item is public, one check if the item is not a comment' => [
'?body ~= grasshopper || ?item_private == 0 || ?item_thread_top > 0',
'',
true
],
'incl: two criteria with OR, both keywords in the body; excl: item must not be a repeat' => [
'?body ~= grasshopper || ?body ~= summer',
'?verb == Announce',
true
],
'incl: three criteria with OR, all keywords in the body; excl: item must not be a repeat' => [
'?body ~= grasshopper || ?body ~= summer || ?body ~= ant',
'?verb == Announce',
true
],
'incl: three criteria with OR, one keyword in the body, one check if the item is public, one check if the item is not a comment; excl: item must not be a repeat' => [
'?body ~= grasshopper || ?item_private == 0 || ?item_thread_top > 0',
'?verb == Announce',
true
],
As of now, due to the bug, only the first and the fourth test case will pass because they only have two criteria linked with||inincl. The second, third, fifth and sixth one will fail because they've got more than two criteria linked with||inincl.