do not usually when i am

do not usually when i am .
before i the and i'm looking at my 's .

I'm all for moving away from non-standard hacks and towards the actual ActivityPub standard. I mean, if everyone built their server apps against the ActivityPub standard, the Fediverse would cause a whole lot less headache.
The major problem with this, however, is that the worst offender is also two thirds of the whole Fediverse and perceived as the actual Fediverse standard. Just about everyone who joins the Fediverse now spends weeks, if not months, only exposed to Mastodon and thinking the Fediverse is only Mastodon. Some have joined in the second Twitter migration wave in November, 2022, but they still think the Fediverse is only Mastodon. For most of those who don't, the Fediverse is Mastodon and weird, alien non-Mastodon stuff, and only Mastodon counts as normal.
This actually goes as far as Mastodon users thinking that whenever something is different from Mastodon on another project, that's a bug that should be fixed. And I'm talking about things like Friendica not having Mastodon's alt-text field. That's something that doesn't disrupt communication, and it's independent from the ActivityPub standard. But if actual communication fails because one side strictly adheres to the ActivityPub spec, and the other side is Mastodon, a majority of Fediverse users will believe it's the non-Mastodon side that's broken.
It doesn't help that all kinds of news outlets simplify the Fediverse down to "Mastodon and stuff that doesn't matter" or even actually only Mastodon while stating that Mastodon is built against ActivityPub and thus implying it's cleanly built against ActivityPub.
Thus, playing by the official rulebook only and ignoring Mastodon's non-standard quirks is playing with high stakes.
It could work out, though. The "strictly ActivityPub" side just needs more projects to join. More server apps to make themselves independent from Mastodon by going the pure ActivityPub way. Even clients that exchange the Mastodon API for actual ActivityPub.
It probably wouldn't be that much work for Friendica and Hubzilla. I can also see *key developers turn their backs on Mastodon if they perceive it as toxic and show it by joining the "strictly ActivityPub" side. The best case would be if Iceshrimp or even Misskey itself did that because they'd drag a whole number of soft forks along.
If only (streams) goes pure ActivityPub while everything else sticks to "but muh Mastodon compatibility", (streams) will be seen as broken by design, even if someone filed a bug on Mastodon's GitHub repository because of some incompatibility with (streams), even if that bug report includes proof that it's Mastodon that goes against the ActivityPub standard while (streams) sticks to it.
But if someone filed a bug on Mastodon's GitHub repository because Mastodon ignoring the ActivityPub standard can be proven to break compatibility with 15 different server applications, at least five of which aren't "never heard of that" material but actually well-known, and a bunch of popular iPhone and Android apps on top, all of which chose to stick to ActivityPub only, it's obvious that it's Mastodon that's broken.
In this regard, the thought of the Fediverse splitting in two becomes kind of interesting. One side is fed up with Mastodon's antics and sticks to the W3C spec, even if it breaks compatibility with Mastodon. The other side is Mastodon which has just lost control over one third of the free, non-commercial Fediverse, and which is left with Threads as its only playmate.
Unfortunately, Threads is not being built against the W3C ActivityPub standard, but only against Mastodon which makes breakage with everything that isn't Mastodon highly likely already now. It'd be fun if Meta had decided to go by the ActivityPub spec only and then openly declared that Mastodon is faulty because of how utterly incompatible it is to something that follows the spec to a tee.
On the other hand, the breakage might keep Threads at a distance from the non-Mastodon Fediverse and more so from the "strictly ActivityPub" Fediverse.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #ActivityPub It most likely won't. I guess it'd be "un-Mastodon-like".
My advice to Mastodon users who crave certain features that Mastodon doesn't have, but that are readily available elsewhere in the Fediverse is: Don't sit and wait until your Mastodon instance introduces that feature. If you want it, go where you can have it.
I've written a very long post on this topic almost a year ago.
Might open in Mastodon:
Original:
If you really want to be able to quote, it isn't worth waiting for quotes to be implemented on Mastodon. Try Iceshrimp or Sharkey instead the latter even lets you import your post backlog from Mastodon AFAIK.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta It's called a quote. Standard feature on Friendica, Hubzilla (where I am), (streams), the now-deceased rest of the family, Misskey and all its forks etc., basically everywhere that isn't Mastodon.
Within Friendica, Hubzilla and (streams), it's handled basically the same way as on good old bulletin-board forums: in BBcode.
quoteif the process is really that involved and if they can fix it/quote
(streams) also has ways of doing that with Markdown or HTML.
There are various different ways of getting that code, also depending on whether one replies to a post or a comment.
ActivityPub uses Rich Text for formatting. So Friendica converts this into the corresponding formatting in Rich Text, and on Hubzilla and (streams), the optional ActivityPub bridge PubCrawl does that.
Mastodon, in turn, has introduced some Rich Text displaying capabilities with version 4.0.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #Streams #(streams) #TextFormatting #BBcode #RichText If you mean an update that makes Friendica handle 100% like Mastodon to make things easier for Mastodon converts, then no. That'd sacrifice image embedding.
Essentially, Friendica would need an alt-text field for Mastodon-style file attachment images, and it'd need an even more advanced WYSIWYG post editor which includes some kind of alt-text field for each embedded image.
Also, AFAIK, there are no dedicated mobile apps for Friendica, and Friendica doesn't support the Mastodon API due to both being so vastly different from Mastodon in its architecture and six years older than Mastodon. What few general Fediverse apps work with Friendica only work barely so and don't even support a tiny fraction of what Friendica can do. Friendica is typically used in a standard Web browser.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #AltText It does support alt-text, technically speaking. It just doesn't have Mastodon's easy-peasy alt-text entry field. And I think if you want to have alt-text on Friendica, you must not handle images the Mastodon way by uploading them to a post draft as file attachments, but you must upload them to your file storage and then embed them, blog-style.
Once you have the image embedding code in your post draft, you must manually graft the alt-text into that code. I'd walk you through it step by step if I could, but I don't know how exactly the code in Friendica looks like.
I can tell you what it looks like and how it works on Hubzilla, though, and since Hubzilla is Friendica's descendant, it should be similar, only that Friendica probably still uses url=/url and img=/img instead of zrl=/zrl and zmg=/zmg.
So when you embed an image into a post on Hubzilla, the code looks like this:
zrl=URL of image viewing page in your file storagezmg=WidthxHeightURL of Image file/zmg/zrl
The first thing you do is cut the image file URL and paste it over the image size in the zmg= tag. The image size is usually quite unnecessary, and it degrades the quality of the image.

zrl=URL of image viewing page in your file storagezmg=WidthxHeightURL of Image file/zmg/zrl
                                                          
                                                              
zrl=URL of image viewing page in your file storagezmg=URL of Image file/zmg/zrl

Now you've got a place for the alt-text, namely in-between zmg= and /zmg.
zrl=URL of image viewing page in your file storagezmg=URL of Image fileAlt-text/zmg/zrl
On Hubzilla, this works absolutely well. I've done it myself countless times already.
I think Friendica works largely the same, only that it uses url=/url instead of zrl=/zrl and img=/img instead of zmg=/zmg.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Friendica #Hubzilla #AltTextImplementing encryption in ActivityPub would require a way to find out which instance or which actor supports which ways of encryption, if any.
Encryption would break compatibility more than nomadic identity ever could. If one project implements mandatory, no-opt-out encryption, and another project doesn't implement it at all, then actors using the second project won't be able to communicate with those using the first project.
And there will be projects that won't implement encryption as well as projects that won't even implement nomadic identity. Not exactly few Fediverse projects are highly opinionated what their creators don't like and/or don't find useful enough and/or think makes things too complicated won't be implemented. Sadly, Mastodon is one of the worst, also because it shows this "we don't implement what we haven't invented ourselves" mindset, and because it can afford becoming incompatible with the rest of the Fediverse.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #ActivityPub #NomadicIdentity Looks like many mobile apps for Mastodon were made by people who were new to Mastodon, totally giddy about it, eager to improve the mobile experience, but at the same time clueless. They didn't distinguish much between ActivityPub and the Mastodon API, and at that point, they didn't even know that the Fediverse is more than just Mastodon.
That's also why there are apps that technically support everything that uses the Mastodon API, but that don't have any features beyond vanilla Mastodon 3.x and don't even support over 500 characters.
At the same time, I think, there isn't a single app purely built against the ActivityPub standard and for the Fediverse in general. It simply wouldn't be compatible with Mastodon. Even supporting the full ActivityPub standard next to the Mastodon API seems unattractive.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #ActivityPub #MastodonThe recent statistics:

OpenSim area continues growth streak

The total land area on OpenSims public grids reached the equivalent of 132,969 standard regions this month, an all-time high and the third month in a row that OpenSim land area has broken records. There was an increase of 1,089 standard region equivalents compared to last month. Meanwhile, the View article View summary OpenSim area continues growth streak
The total land area on OpenSims public grids reached the equivalent of 132,969 standard regions this month, an all-time high and the third month in a row that OpenSim land area has broken records.
There was an increase of 1,089 standard region equivalents compared to last month. Meanwhile, the total number of registered users went up by more than 1,338. The number of active users fell, however, by over 2,100, partly due to grid outages. , for example, which reported over 400 active users last month, was down this month. And two other grids that reported drops of more than 500 active each may have had database issues, including and .
Im now tracking a total of 2,654 public grids, of which 308 were active, and 244 published their statistics this month. If you have a stats page that were not tracking, please email me at that way, your grid will be mentioned in this report every month, for additional visibility with both search engines and users.
Also, Im no longer sending out a monthly email blast reminding OpenSim grid owners to send me news and updates for this report. If you have news, please email me before the tenth of the month if you want a short item included in this monthly wrap-up. For longer news, feel free to send me press releases at any time.
OpenSim land area for March 2024. (Hypergrid Business Data.).
Our stats do not include many of the grids running on which is a distribution of OpenSim since these tend to be private grids.
OpenSim is a free open-source, virtual world platform, thats similar to Second Life and allows people with no technical skills to quickly and cheaply create virtual worlds and teleport to other virtual worlds. Those with technical skills can run OpenSim worlds on their servers for free using either DreamGrid, for those who are more technically inclined, or any other distribution, while commercial hosting starts at less than $5 a region.
A list of . Download the and find out .

Hypergrid Business newsletter is now available

Every month on the 15th right after the stats report comes out we will be sending out a newsletter with all the OpenSim news from the previous month. You can or fill out the form below.
Please leave this field empty
Get our monthly stats and all other OpenSim news delivered right to your mailbox every month.
Email Address *
We dont spam! Read our for more info.
Check your inbox or spam folder to confirm your subscription.

Top 25 grids by active users

When it comes to general-purpose social grids, especially closed grids, the rule of thumb is the busier the better. People looking to make new friends look for grids that already have the most users. Merchants looking to sell content will go to the grids with the most potential customers. Event organizers looking for the biggest audience you get the idea.
Top 25 most popular grids this month:

: 5,276 active users
: 5,271 active users
: 2,221 active users
: 2,138 active users
: 1,971 active users
: 1,342 active users
: 1,196 active users
: 1,111 active users
: 1,000 active users
: 989 active users
: 972 active users
: 879 active users
: 864 active users
: 848 active users
: 750 active users
: 678 active users
: 658 active users
: 650 active users
: 632 active users
: 618 active users
: 553 active users
: 553 active users
: 550 active users
: 518 active users
: 511 active users

Top 40 grids by land area

All region counts on this list are, whenever available, in terms of standard region equivalents. Active user counts include hypergrid visitors whenever possible.
Many school, company, or personal grids do not publish their numbers.
. . And here is a and their hypergrid addresses, sorted by popularity. This is very useful if you are creating a hyperport.
You can see all the , including polls and surveys, dating all the way back to 2009.

: 28,496 regions
: 27,145 regions
: 18,216 regions
: 11,687 regions
: 9,995 regions
: 7,896 regions
: 5,094 regions
: 3,543 regions
: 1,579 regions
: 1,464 regions
: 1,072 regions
: 952 regions
: 916 regions
: 872 regions
: 854 regions
: 816 regions
: 784 regions
: 653 regions
: 577 regions
: 515 regions
: 430 regions
: 400 regions
: 387 regions
: 378 regions
: 373 regions
: 311 regions
: 305 regions
: 298 regions
: 241 regions
: 196 regions
: 183 regions
: 173 regions
: 167 regions
: 164 regions
: 148 regions
: 144 regions
: 141 regions
: 140 regions
: 127 regions
: 126 regions

Do you know of any other grids that are open to the public but that we dont have in our database Email me at
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorlds #OpenSimStatistics #HypergridBusiness Long

New Brunswick long-term care unprepared for next generation of aging seniors
New Brunswick's seniors advocate says the province will need to rethink its long-term care offerings to respond to the needs of an increasingly diverse population.
-termCare 'Advocate

Als Handle oder Nutzerprofil bezeichnet man den Nutzernamen, der in Beitrgen angezeigt wird. Es handelt sich quasi um die "Identitt" eines Nutzers.
Bei sehr vielen Fediverse-Diensten (#mastodon, #misskey und Misskey-Forks = #forkey , #pleroma ,...) hat das Handle folgende Form: <BENUTZERNAME><INSTANZ-URL>.
Mein Handle z.B. fr meinen Mastodon-Account lautet: hvetinariburningboard.net
Bei vielen anderen Fediversediensten, wie z.B. #hubzilla , #streams , #friendica etc. unterscheidet sich das Handle (und die Bezeichnung... hier meistens als "Kanal" bezeichnet) ein wenig. Es hat die Form: <BENUTZERNAME><INSTANZ-URL>.
Das ""am Anfang wird weggelassen.
Diese Tatsache ist wichtig und kann bei Nichtbeachtung zu Problemen fhren.
Mchte man bei Hubzilla (und Verwandten) nach einem Handle suchen oder einen Kontakt hinzufgen, der von anderen Diensten stammt, dann muss man das fhrende "" weglassen!
Mchte man bei einem anderen Fediverse-Dienst (z.B. Mastodon) nach einem Hubzilla-Nutzer (Hubzilla-Kanal) suchen oder diesem folgen, muss man das "" am Anfang ergnzen!
#FediTips #FediverseTips #hubzilla #hubzillahppchen
#Long #LongPost #CWLong #CWLongPost Der Pepe (Hubzilla) That, and the typical Fediverse experience nowadays is a) Mastodon while barely or not at all knowing anything else exists and b) on a phone through a dedicated app.
The average Fediverse user doesn't start by joining Hubzilla on a desktop or laptop computer. They're fed up with Twitter and what became of it. They're told about Mastodon and the Fediverse which is implied to them to be one and the same thing.
So they grab their phones, they "install Mastodon" (the official app they've never in their lives used any online platform through an app that doesn't have the same name as the platform), and they register an account. On mastodon.social.
For at least the first three months, the Fediverse to them is Mastodon. Vanilla Mastodon with no more features than what Mastodon 3.x had. They actually think 500 characters are a lot, and they cannot imagine for the lives of them that it's possible for posts with more posts to exist in the Fediverse. How could they possibly The Fediverse is only Mastodon, after all.
Needless to say that they're deeply shocked and disturbed once they come across a post that does anything they took for absolutely impossible in the Fediverse. It's usually 500 characters, regardless of whether they come from Glitch or Misskey or Hubzilla.
At this point, they've gotten used to the Fediverse not allowing for more than 500 characters, not having text formatting, not having quotes, not having quote-tweets etc. etc. and of course being Mastodon and only Mastodon. And then this happens.
Those who are still on the official app are the poorest saps. The official Mastodon app is mercilessly hard-coded against vanilla Mastodon only with absolute and staunch disregard of the existence of anything else in the Fediverse. It totally refuses to take the existence of both Mastodon forks and non-Mastodon projects into account because that'd mean that Mastodon acknowledges the existence of Fediverse projects that have features that Mastodon a) lacks and b) flat-out refuses to introduce. So those on the official app get all long posts slammed right into their faces in the shape of unshortened walls of text.
Granted, the official Web front-end isn't that much better. It does fold long posts in. But it only folds posts in if they're ca. 2,000 characters or longer, and then it folds them in to ca. 1,500 characters.
Still, long posts can upset Mastodon users regardless of front-end. They're something that these users didn't expect. Something they don't want. Something they say doesn't belong into Mastodon and therefore into the Fediverse. Something that must be abolished.
For some even something they're willing to fight against until it's gone from the Fediverse, until the Fediverse is again what they thought it was when they were new: only vanilla Mastodon with only vanilla Mastodon's capabilities.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #500Characters Because 2010/2011 was when this federation was established. And not 2012 or 2016 or 2024.
It doesn't matter if Diaspora* has introduced an official API years later. There was no API in 2010/2011. There was no technical documentation in 2010/2011. There was no interest in connecting to anything else in 2010/2011.
But there was Mistpark/Friendika, then still developed by Mike, that had federating with everything that could possibly be federated with as one of its primary goals. No matter the odds. Even including Twitter and Facebook.
In autumn 2010, shortly after the very first public alpha of Diaspora* had come out, there were no signs of things improving, no signs of there being a stable API anytime soon, if ever. Diaspora* gave the impression of only wanting to federate with itself. So trying to wait for an appropriate server-to-server API appeared to be futile, and Mike had to start working on that federation without an API.
And besides, while Diaspora* did evolve to a certain degree, Mistpark evolved more from March, 2010 to July, 2010 than Diaspora* did from May, 2010 to now. And I'm not even talking about what came after Mistpark/Friendika/Friendica, namely the Red Matrix, Hubzilla, Osada, Zap etc. and eventually (streams).
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Diaspora #Diaspora* #Friendica I'm not talking about 2016.
Friendica, then named Friendika, introduced its federation with Diaspora* on March 19th, 2011 (see also ). This means that work on federating Friendika with Diaspora* had started as early as 2010 when the original four devs were still in charge.
If simply asking them had worked, all that hassle with reverse-engineering from source code and cracking encryption would have been unnecessary, and Friendika would have federated with Diaspora* in 2010 already.
And don't tell me that Mike Macgirvin didn't want to get into contact with the Diaspora* devs and intentionally do all the federation behind their backs. Mike has actually contributed to Diaspora*'s protocol, and unlike his attempted contributions to ActivityPub, they were even accepted AFAIK.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Diaspora #Diaspora* #Friendica

Where did you read that diaspora* never cared about federation outside of diaspora*

Did Diaspora* ever do anything to facilitate federation for Friendica or Hubzilla or (streams)
Did it ever actively try to stop them
Did it at least officially acknowledge that these three are federated with it

Where did you read that connecting to diaspora* is like to drill in a computer!

It's my description of how difficult it was to federate Friendica with Diaspora*.
Back in the day, Diaspora* had no API and no documentation on its protocol. Diaspora* was all about only federating with itself. Still, Friendica wanted to federate with it because Friendica federated with everything, full stop.
The "drilling into a computer case with a diamond drill" represents the several months it took the Friendica devs to crack Diaspora*'s undocumented encryption.
The "soldering wires onto circuit boards" represents how the Friendica devs had to reverse-engineer Diaspora* by studying its source code because there was no technical documentation whatsoever, and how Friendica could only federate with Diaspora* by latching directly onto Diaspora*'s inner workings instead of making use of any interface because there was no interface to use whatsoever.
Ask Mike Macgirvin .
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Diaspora #Diaspora* #Friendica In the long run, however, it's bad.
It'll lead to wide-spread segregation of not only single Mastodon users, but entire instances from users that regularly post over 500 characters and instances with such users.
To say that's inconvenient puts it mildly, seeing as the secondary topic of my Hubzilla channel is the Fediverse in general and educating Mastodon users about the Fediverse outside of Mastodon in particular. If these very same Mastodon users can't read my posts anymore because someone else on their instance has talked their instance admin into blocking either my channel or the entirety of hub.netzgemeinde.eu, calling it inconvenient is an understatement.
It also makes explaining that "the Metaverse" is neither Zuckerberg's invention nor dependent on blockchains, cryptocurrencies and NFTs, and that decentralised 3-D virtual worlds have been around for over a decade and a half, much more difficult. And that's the primary topic of this channel.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta phanisvara (streams) Yes, but many Mastodon users can't stand to see posts with over 500 characters. Not only do they refuse to read "long" posts, but some actually block anyone who exceeds 500 characters in a post even only once.
I'm pretty sure some ask their Mastodon instance admins to deal with such people. Have them blocked instance-wide. Have their whole Hubzilla hub blocked on that Mastodon instance.
Or they try to use Mastodon's report feature to report that Hubzilla user to the admin of that Hubzilla hub, or they have their admin try and get into contact with the admin of that Hubzilla hub, just to have that Hubzilla user sanctioned for breaking some unwritten Mastodon etiquette by posting over 500 characters in one chunk.
Of course, they fail in both cases. Hubzilla doesn't support Mastodon's report feature, and mentioning Hubzilla users, in this case the admin, in a public post won't work either. Verdict: That Hubzilla hub is unmoderated and therefore has to be blocked or even out-right Fediblocked.
On the grounds of the assumption that Hubzilla works exactly like Mastodon. Which I'm trying to debunk with this series of posts.
As at least one of my polls has revealed, there seems to be a not insignificant number of Mastodon users who demand posts with over 500 characters be banned absolutely everywhere in the Fediverse. Including in conversation between users on other projects, regardless of whether overly long posts from that conversation might leak into Mastodon or not.
And, of course, there's the Mastodon police that try to urge non-Mastodon users to limit their posts to a maximum of 500 characters, regardless of whether they're aware that the user in question is on something else than Mastodon or not. They're fully convinced that Mastodon was here first, and all the other projects are intruders in Mastodon's Fediverse and have to follow Mastodon's rules.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterCount #CharacterLimit #CharacterLimits #500Characters #Mastodon

It would be best for such a thing to exist within ActivityPub itself, yes.

It would have to exist within ActivityPub. The only alternative would be the whole Fediverse having to adopt yet another non-standard Mastodon hack that isn't documented anywhere because Mastodon didn't intend it to be adopted by other projects.
But if you don't want stuff to leak out through Hubzilla, it would also have to be included into the Zot6 protocol. And if you don't want stuff to leak out through (streams), it would have to be included into the Nomad protocol.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta

Essentially you'll need a server that hosts a virtual world, a client to consume it, and a way to transfer seamlessly between servers. The underlying protocol should be open, so other implementations can reuse that.
You go from online game to metaverse the moment anyone can author & host their own server, determine what the client experience is like, and connect it to the existing pool of servers in a decentralized way.

You've basically described . Established, free, open-source and decentralised since 2007, interconnected since 2008, today with thousands of individual worlds ("grids"), most of which are connected to the Hypergrid, and over four times the land area of Second Life.
Oh, and the OpenSim community has had "metaverse" as a regular part of their vocabulary since 2007 as well.
#Long #LongPost #CWLong #CWLongPost #OpenSim #OpenSimulator #Metaverse #VirtualWorldsAn alle meine Kontakte hier auf meinem Kanal "pepecyb8806hub.pericles.hu":
Ich habe - aus Grnden (zu lange Update-Intervalle der YunoHost App "Hubzilla") - einen weiteren Hub installiert. Der luft zwar auch auf dem YonuHost-System, aber nicht als YH-App, sondern wurde "zu Fu" aufgesetzt. Nachdem ich einige "Untiefen" umschifft habe, luft er jetzt stabil und das Log ist frei von Fehlern.
Nun ist mir meine Kanaladresse (die "8806" hinter dem pepecyb) schon geraume Zeit auf die Nerven gegangen. Die resultierte noch aus meinen Anfangszeiten mit Hubzilla. Damals hatte ich auf einem Hub den Kanal "pepecyb" (ohne 8806). Der Hub hatte so einige Probleme, so dass ich einen Klon bei einem anderen Hub anlegte. Irgendwann habe ich dann Account und Kanal auf dem ersten Hub gelscht. Nach einiger Zeit gab es dann beim zweiten Hub auch Probleme (zu Zeiten von Hubzilla 3 kam das immer mal vor). Dafr war aber der erste Hub inzwischen stabilisiert und auch schon auf einer aktuellen Version. Also legte ich einen neuen Account auf dem ersten Hub an und wollte den Kanal dorthin klonen. Nur der wollte den Kananamen nicht nehmen (weil es den ja dort schon einmal gab... und der deswegen irgendwie "gesperrt" war, obwohl gelscht) und hngte dem "pepecyb" nun das nervige "8806" an. Dieser Hub wurde aber meine Hauptinstanz fr lngere Zeit... und ich hatte mich mit dem "8806" abgefunden. Und dieses Kanalhandle schleppe ich seit dem mit mir rum. Jetzt wollte ich den Kanal natrlich auf meinen neuen Hub klonen, aber mit alternativem Kanal-Handle ("pepecyb" ohne Nummer). Das ging leider schief. Keine Ahnung weshalb. Ein Import unter dem "Nummern-Handle" funktionierte, aber die Umbenennung nicht (bei anderen Kanlen hat das reibungslos geklappt).
Deshalb habe ich nun einen frischen Kanal auf dem neuen Hub angelegt: "pepecybhub.hubzilla.hu"
Und das wird mein neuer und zuknftiger Hauptkanal. Also nicht wundern, wenn Ihr jetzt Verbindungsanfragen bekommt oder feststellt, dass Euch ein
"Der Pepe (Hubzilla) pepecybhub.hubzilla.hu"
folgt. Das bin ich und das wird mein aktiver Kanal sein. Den alten (hier) lasse ich bestehen, werde ihn aber nicht mehr "fttern".
brigens... hat jetzt auch mal einen "hbscheren" Namen, als mein "PericlesHub" (wie einfallslos) von dem hier: Whoville.
Mehr dazu:
#fediverse #hubzilla
#Long #LongPost #CWLong #CWLongPostYou can't enforce either of them Fediverse-wide.
Friendica has had "excluded + long name" () firmly hard-coded for 14 years now, almost 6 years longer than Mastodon has been around, and its descendants Hubzilla and (streams) have the same mention style hard-coded, too.
Mastodon and its forks have "included + short name" () hard-coded.
Misskey and the Forkeys have "included + short name + domain" () hard-coded.
An acquaintance of mine, himself on Mastodon, actually asked me to turn these freaky-looking long-name mentions off and switch back to Mastodon-style short-name mentions. I had to explain to him that I'm not on Mastodon, Hubzilla isn't Mastodon, Hubzilla has never been Mastodon, and on Hubzilla, mentions with long names and excluding the are hard-coded with no way to change them.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mention #Mentions #MentionTag Because the technology isn't there. And making this absolutely safe, 100% guaranteed, is impossible.
First, almost all Fediverse protocols would have to be upgraded with an extra property that can contain domains to which an object must never be sent. That is, at least ActivityPub, Zot6 and Nomad would need this extension.
And then, full support for this property must be added to dozens upon dozens upon dozens of Fediverse projects immediately, no matter how slow their development is. And all their instances must be updated ASAP.
This is even less likely to happen. Some projects simply have extremely slow development or none at all.
Chances are that a post which you absolutely don't want to end up on Threads is forwarded to someone on Meisskey. Meisskey, a Misskey fork, hasn't seen a new release in a year and any activity in its Git repository in half a year. Of course, it won't have that new property implemented.
That Meisskey user a) has at least one follower on Threads, provided that Threads is compatible with anything in the Fediverse that isn't Mastodon, and b) likes your post so much that they decide to boost it.
And you've lost.
Such a feature is only any good if it's absolutely, 100% water-tight. But it will never be absolutely, 100% water-tight.
For example, I could easily circumvent that "don't send to server XYZ" property by quote-posting your post. A feature that has been available here on Hubzilla since at least 2012. Instead of forwarding your original post with all its properties, it copies the contents of your post into a new post that formats it as a kind of quote, mentions it's your post, links to your profile, links to your original post and actually causes you to be notified about it.
But still, that copy will not have the "don't send to Threads" limitation, and everyone can boost or quote-post it to wherever they please.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta

Cox and Box

Cox and Box, also known as The Long-Lost Brothers, is a one-act comic opera with a libretto by F. C. Burnand and music by Arthur Sullivan, based on the 1847 farce Box and Cox by John Maddison Morton. It premiered in 1866 and was Sullivan's first successful comic opera. The story concerns a landlord who lets a room to two lodgers, one who works at night and one who works ...

-LostBrothers

That's what happens when people are lured to Mastodon with false promises. Such as getting a 1:1 identical Twitter clone, without Elon Musk, but otherwise identical.
Typical on-boarding tweet:

join mastodon its literally twitter w/o musk

And then they join Mastodon, actually and honestly expecting that 1:1 clone, a centralised corporate silo with a billion users and a secret-sauce algorithm that automatically throws content at you which it's certain that you might be interested in it, all before you've done anything else than load the app and register an account.
I guess thousands upon thousands of people have noped away from Mastodon again when they thought it's absolutely dead because The Algorithm didn't shovel any content into their timelines. Thousands upon thousands of other people left when they were told that they'd have to take steps themselves to populate their timelines. Too complicated, too inconvenient, too much work. Nope, I'm outta here.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Twitter #

The Long-term Impact of Infection with Novel Coronavirus ( ) study is a collaboration of researchers looking for who tested positive for -19 to understand the changes that happen after recovery from the virus.

UC San Francisco will launch the worlds first with samples donated by patients with .
The move follows research indicating that the virus can continue to linger throughout the body and may hold the key to understanding the cause of the debilitating disorder and lead to effective treatments.
By October 2023, an estimated
14% of Americans had or had had long COVID, according to the Centers for Disease Control and Prevention.
The disorder may appear as a continuation of the original COVID symptoms or manifest as new symptoms affecting any part of the body.
In serious cases multiple body systems are affected, including the , , , and .

Based on our work so far, we believe that long COVID is a - disease, said Michael , MD, principal investigator of the UCSF Long COVID Tissue Program and an infectious disease physician-scientist in the UCSF School of Medicine.

This program will allow us to comprehensively study the biological processes occurring across tissue compartments
in the blood, gut, lymph nodes, spinal fluid and bone marrow
in people living with long COVID.
This will help us better understand the underlying mechanisms of long COVID, said Peluso, who co-led recent research with Timothy , MD, a UCSF physician-scientist, that showed the virus was present in colon tissue up to 676 days following infection.

If you ask experienced users of Friendica, Hubzilla and (streams), they'd prefer doing away with poster-issued CWs altogether.
For one, they force CWs upon everyone, including people who don't need that particular CW. Besides, they leave sensitive people fully at the mercy of the posters and their willingness to write CWs.
Instead, automated, individually-generated, reader-side CWs based on keyword lists should become the new standard. On Friendica, Hubzilla and (streams), this feature is called "NSFW". It has been available since Friendica's earliest days, and Friendica is almost six years older than Mastodon.
Also, Mastodon itself has been able to generate reader-side CWs using filters since the 4.0 update last year. It just takes more awareness on the users' side that filters exist and what filters can do plus one-click or two-click CW filter creation for those who don't even know that Mastodon has filters in the first place, and that has to be implemented in all mobile apps as well.
It's actually dead-simple, and it doesn't require any W3C ActivityPub standardisation because it doesn't need a dedicated field. It uses keywords or hashtags or other strings or substrings found in the post body.
For example, you have "NSFW" in the word list of your NSFW app on Friendica/Hubzilla/(streams) (you do have it by default) or in the word list of a Mastodon filter. A post contains these four letters, "NSFW". Bam, post automatically hidden behind a CW. And Friendica, Hubzilla and (streams) even tell you that it's "NSFW" that was found and triggered the CW creation.
Of course, awareness is necessary because posters still do have to support this in their posts by adding keywords or hashtags that trigger the creation of such CWs. But that's no more difficult than writing a current Mastodon-style CW. In fact, you don't even have to jump to the CW field. And Friendica users can have sensitive stuff hidden behind automatically generated CWs even if they don't know the abstract/abstract tags.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #ContentWarning #ContentWarnings #CWMeta #ContentWarningMeta

Well, Mastodon's CW field is proprietary it abuses the subject field of ActivityPub. So, Hubzilla does not have subjects. If it had, Mastodon would mistake them for a CW.

Actually, Mastodon does use the summary field. Which Hubzilla has, but labelled "summary" and not "CW", but it works the same. It is the very field into which I've entered the CW of the start post. And you can clearly see the CW.
Don't confuse this with the subject/title field. Hubzilla has both. In Note objects/microblogging posts, Mastodon ignores and silently discards the content of the title field.
Trust me, I've been using Hubzilla for many years now.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CW #CWs #ContentWarning #ContentWarnings #CWMeta #ContentWarningMeta If there are three attributes that describe Diaspora*, it's lack-lustre, developed at a snail's pace and not interested in the outside world.
For a first alpha release, it took Diaspora* four developers, a crowd-funding campaign and significantly longer than it took Mike Macgirvin to develop Mistpark, which would later be renamed Friendika and which is known as Friendica today, all alone in only four months.
Diaspora* can't do nearly as much today as what Mistpark could do when it was first released in July, 2010, months before Diaspora*.
Diaspora* took until 2018 for a first beta release, not to mention that the entire dev team had been replaced meanwhile.
Within the same timespan plus two months, Mike developed Mistpark/Friendika/Friendica to stable releases, invented nomadic identity, forked Friendica into Friendica Red, re-wrote it entirely into Red, later known as the Red Matrix, led the Red Matrix to stable releases, redesigned it into Hubzilla, brought Hubzilla to stable releases, forked Hubzilla to Osada and forked Osada to Zap. All alone.
I'm not even sure if Diaspora* has an API now. When Friendica federated with it, it didn't. The whole Friendica-to-Diaspora* federation was 100% Friendica's work. Federating Friendica with Diaspora* was like connecting an external device to a computer by drilling a hole into the computer case with a diamond drill and soldering wires directly onto various circuit boards with only the circuit board layouts and some self-made measurements as documentation.
Diaspora* itself never cared for federation outside itself. It didn't welcome Friendica or Hubzilla or GoToSocial, it didn't take any measures against them either. It just silently ignored them and acted as if they weren't there.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Diaspora #Diaspora*phanisvara (streams)

i understand why people don't want to use a separate tool for every other thing they're doing. this gets complicated quick.

I don't complain about that as long as people choose a tool that's actually appropriate for these purposes.
But they use Mastodon for everything. They say, "I don't care how much better XYZ is at it, Mastodon can do it, and I don't want to move/I can't move/XYZ doesn't work as perfectly with my favourite Mastodon app, so I'll stick with Mastodon."
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta

-lasting

A lot of people are using the wrong tool for the job. They want a community of like-minded people, but are posting on a broadcast platform instead. That's like broadcasting a private get together with your friends on YouTube. Sure, you can do that, but there are consequences of doing so.

People do all kinds of stuff with Mastodon even though other Fediverse software is better for that. From podcasts that are MP3 files attached to Mastodon toots to groups grafted onto Mastodon. Even though there's not only Funkwhale, but even a dedicated podcast project named Castopod. And even though group discussions require conversations, and hardly anything in the Fediverse has such a lack of conversation support as Mastodon.
They don't do that because they think Mastodon is the best at it. They do it because Mastodon is all they know. They've spent their first months in the Fediverse thinking the Fediverse is only Mastodon because nobody told them about there being anything else. Either that, or the step from Twitter to Mastodon was so big that they're still recovering from it, and they don't want to learn something new again, so they use what they already know.
And if you tell them there's something better for the job, they refuse to adopt it because they "can't" move away from Mastodon for some reason.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta I'm just used to having to pick Mastodon users up at either "The Fediverse is only Mastodon" or "Yeah, well, so there's other stuff in the Fediverse as well, but it can't be so much different from Mastodon."
I keep seeing Mastodon users come up with ideas for "the Fediverse" that might work if limited to Mastodon, but cause issues in combination with other projects in doing so, that are rather unlikely to work with other typical ActivityPub-based microblogging projects, and that have no chance of being the least bit compatible with Friendica, Hubzilla and (streams) because they work so vastly differently even from Pleroma and Misskey and their forks, not to mention Mastodon. And I always feel like having to comment before a campaign to actually introduce this and try to force it upon the whole Fediverse is launched.
Easily the worst case was that issue in Mastodon's GitHub repository that suggested the introduction of "quote-tweets". Which meant that Mastodon should invent that feature from scratch. Allowing other Fediverse users to "quote-tweet" you should be opt-in. And any and all Fediverse instances that can "quote-tweet" and don't respect this opt-in should be Fediblocked. This was meant as a counter-measure against rogue Mastodon instances and potential Mastodon forks that try to circumvent the opt-in with malicious intent.
Sounds good so far, doesn't it
Well, a lot of Fediverse *blogging projects can already "quote-tweet", and some of them could even before Mastodon was made. Misskey can, Firefish can, Iceshrimp can, Sharkey can, Catodon can, all the other Forkeys can, Friendica can, Hubzilla can, (streams) can... And that's so natural to them and so much part of their culture that they don't have any opt-in, not even an opt-out, much less one that's universally understood across the Fediverse.
Mastodon would not only re-invent the wheel from scratch, it would also publish no specifications for its opt-in. The developers of the other projects wouldn't have a chance to graft compatibility with Mastodon's opt-in into their projects in time.
So the day before Mastodon introduces "quote-tweets" and the opt-in, nobody would know how this opt-in works because it isn't finalised in the code yet, and the code is the only source for how the opt-in works. One day later, when Mastodon instances roll out the new version with "quote-tweets" plus opt-in, the new rules demand they Fediblock all instances of the aforementioned projects immediately for "quote-tweeting" without respecting the opt-in.
Misskey and all its forks, as well as Friendica and its whole family, would have been cut off from Mastodon due to the ignorance of another "Fediverse = Mastodon" believer.
Or a more recent example: the Bluesky bridge debate. Not only was the Mastodon community so enraged that they basically stopped just short of murder threats, but many made clear that they don't want anything to be bridged to Mastodon's ActivityPub.
What they obviously didn't know: Hubzilla is bridged to Mastodon, too. As is (streams).
Okay, the bridge is not third-party, it's an official part of the respective project. Okay, there's one bridge per channel, operated by the channel owner, and not one bridge for everything. And yes, Hubzilla supported ActivityPub through this bridge two months before Mastodon supported ActivityPub at all.
But still, they're bridged instead of having ActivityPub as their main protocol. A ban on bridges to different protocols would ban both Hubzilla and (streams) from the Fediverse.
The only people who pointed this out in that heated debate were Hubzilla and Friendica users. But the Mastodon crowd was ready and willing to push a ban on all bridges through.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta Richtig. Und dann fangen die Leute an, einen fr verrckt zu erklren, nur weil man eine Bildbeschreibung auch dazu nutzt, das Bild und/oder Teile davon zu erklren. Weil, Bildbeschreibung ist ja nur fr Blinde und soll ja nur eine grobe visuelle Beschreibung sein.
Fr noch verrckter werde ich wahrscheinlich erklrt, wenn ich komplette, detaillierte Bildbeschreibungen und -erklrungen im Post selbst unterbringe. Und nicht im Alt-Text, wo nur eine kurze visuelle Beschreibung steht plus der Hinweis darauf, wo die detaillierte Beschreibung mit Erklrungen zu finden ist. Weil, "Bildbeschreibung" und "Alt-Text" sind ja dasselbe und meinen dasselbe.
Aber meine Posts behandeln im allgemeinen eine derart obskure Nische, da die allermeisten Menschen mit den Bildern ohne ausschweifende Erklrungen nichts anfangen knnen.
Auch in diesem Punkt knnen Bildbeschreibungen und -erklrungen hilfreich sein, wobei allerdings Erklrungen niemals im Alt-Text stehen drfen, weil nicht jeder den Alt-Text aufrufen kann.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta

The Fediverse is far more diverse than only Masto,

Not so much for . When they and many others on Mastodon write, "Mastodon and the Fediverse," what they really mean is only Mastodon.

& at least some if not possibly several of the alternatives pre-date Masto.

This.
Hubzilla, where I am, is from the year before Mastodon. When Mastodon was launched and joined the Fediverse, Hubzilla had already been there for ten months. Including the Red Matrix from which Hubzilla was renamed, it's almost four years. And Friendica can be traced back to almost six years of existence before Mastodon was made.

Some other platforms have IMO considerably less easy tools to add image #AltText, or possibly no tools at all.

Friendica, Hubzilla, (streams). All three with a common ancestor, namely Friendica itself when it was still MIT-licensed. They aren't inspired by Twitter. They're more like Facebook and even more like blogs.
Neither of the three has a nifty alt-text field like Mastodon.
If you add pictures the Mastodon way by attaching them as files, you've got no way at all to edit the alt-text. The alt-text is the file name, and that's hard-coded with no way around.
However, the usual way of adding pictures is completely and utterly different from how Mastodon does it. It is to first upload them to your own file space (all three give you file space with a file manager) and then embed them into the post like into a blog post.
But this doesn't give you an alt-text field either. It gives you raw code that you'll have to edit. With no documentation in at least Hubzilla's and (streams)' case, and with absolutely no help from the UI except for a preview button.
Friendica gives you BBcode like in a forum, but with some enhancements.
Hubzilla and probably also (streams) give you BBcode, too, but with so many enhancements that one could call it "Hubzilla-flavoured BBcode" or "Zot-flavoured BBcode".
Here on Hubzilla, you get this:

zrl=https://hub.netzgemeinde.eu/photos/jupiterrowland/image/6c9c16db-79af-41a2-9faa-5b22929fdd26zmg=800x533https://hub.netzgemeinde.eu/photo/6c9c16db-79af-41a2-9faa-5b22929fdd26-2.jpg/zmg/zrl

And you have to manually edit it into this:

zrl=https://hub.netzgemeinde.eu/photos/jupiterrowland/image/6c9c16db-79af-41a2-9faa-5b22929fdd26zmg=https://hub.netzgemeinde.eu/photo/6c9c16db-79af-41a2-9faa-5b22929fdd26-2.jpgThis is the alt-text./zmg/zrl

Heads buzzing already, everyone That was my very intention.
But this is literally the only way to add alt-text to images on Hubzilla and (streams). Unless you, as a (streams) user, are crazy enough to write the image-embedding code from scratch in Markdown or HTML. Which, truth be told, isn't any better.

So, it would be nice when Masto peeps rail against posts sans-AltText, check first from where the post originates, coz its author might be acutely aware of & sympathetic to the need for it, but be technically unable to provide it.

This won't happen.
For one, many Mastodon users still think the Fediverse is only Mastodon, so why check
Of the rest, the majority can't imagine that something that isn't Mastodon could possibly be so much different from Mastodon. So why check
Of the rest of the rest, the majority doesn't know how to check where a post came from. Remember Mastodon isn't Friendica. It doesn't tell people which project a post came from.
Oh, and besides, my experience is that the vast majority of Mastodon users refuse to read anything that goes beyond 500 characters altogether. Or anything that goes beyond what feels like 500 characters by Mastodon standards.
That's why I'm telling Mastodon users about Hubzilla in little chunks of 500 characters or fewer, even though Hubzilla doesn't have any character limit at all.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Friendica #Hubzilla #Streams #(streams) I keep explaining this again and again: This won't work for the entire Fediverse. Mastodon users would not be able to edit alt-texts in posts from

Friendica (originally DFRN instead of ActivityPub with own bridges to ActivityPub, but recently switched to ActivityPub)
Hubzilla (Zot6 instead of ActivityPub with own bridges to ActivityPub)
(streams) (Nomad instead of ActivityPub with own bridges to ActivityPub)

These three aren't Twitter-like microblogging projects. They handle more like blogs, and images are usually embedded like in blog posts and not attached as files. They also don't have dedicated alt-text fields either.
If you want to add alt-text to an image coming in from Friendica, Hubzilla or (streams), you'd have to edit the post itself. Which would be impossible.
Mastodon doesn't receive Friendica, Hubzilla or (streams) posts in their original, raw source code. But you'd have to have the original, raw source code to be able to edit these posts and add alt-text.
Even if you had it, you'd have to get your hands dirty on raw BBcode with no WYSIWYG real-time preview. If the post in question comes from (streams), chances are it isn't in BBcode, but in Markdown or HTML.
Mastodon users would have to know how to graft an alt-text into the image embedding code in a post. Something that even Friendica, Hubzilla and (streams) users often don't know at least the latter two have no documentation whatsoever for it.
Not to mention that you'd have to have the power to edit any and all post anywhere in the Fediverse. The same power that'd let you add an alt-text to a post from Hubzilla would also let you manipulate and falsify other people's Mastodon toots.
Lastly, to make matters worse, laypeople on Mastodon usually can't tell where a post came from. Okay, stuff like bold type or bullet-point lists are dead giveaways that this comment here does not come from Mastodon because Mastodon can't do bold type and bullet-point lists. But plain text plus a picture, and nobody can tell where that post came from.
So you'd wonder how come you can't edit alt-text into that Mastodon toot because you wouldn't know that it isn't a Mastodon toot, and it came from Hubzilla instead.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #Friendica #Hubzilla #Streams #(streams)phanisvara (streams)

many on the AP side of things seem to feel they are the real or only fediverse and don't spend much thought on compatibility with us, leaving our developers alone with that pressure.

The vast majority of Mastodon users as well as users of projects that have been based on ActivityPub from the start or for long enough actually think that the Fediverse is only ActivityPub. They don't even know that there's stuff in the Fediverse that has ActivityPub as an optional secondary protocol. Few know that Hubzilla and (streams) exist, even fewer know that neither of these two is based on ActivityPub.
In fact, many Mastodon users, including some who have joined during the second Twitter migration wave in November, 2022, are fully convinced that the Fediverse is only Mastodon, full stop. And that "Fediverse" and "Mastodon" mean the same.
And I think not exactly few want the Fediverse to only be vanilla Mastodon with its hard-coded 500-character limit. They aren't only against federation with Threads and a bridge to Bluesky, but they don't want all that stuff from Pixelfed to Lemmy to Misskey to Friendica to (streams) around either.
Some vulnerable groups have escaped the harassment on Twitter. Of course, they went to Mastodon and only Mastodon because that's all they knew. But now they're stuck on Mastodon. First, they didn't know that better stuff than Mastodon exists in the Fediverse. If they heard about the existence of that stuff, they didn't know and couldn't imagine that it's better or even that anything in the Fediverse could possibly have features that Mastodon doesn't.
But even now they refuse to move again. For one, there's no easy-peasy way to move an entire Mastodon account with all posts, all connections, even all settings to e.g. (streams). But they won't accept anything less. Besides, even if they did try (streams), they'd nope out quickly due to how (streams) doesn't handle anything like Mastodon. They simply don't want to get used to yet another UI/UX, and the step from Mastodon to (streams) is much bigger than from Twitter to Mastodon.
If you really want to introduce (streams)' safety features to them, you must first soft-fork (streams) into something that's indistinguishable from Mastodon on the surface, that is 100% compatible with the Mastodon API, and that Mastodon servers can be seemlessly migrated to. Then you have to migrate all major Mastodon instances, including and especially mastodon.social, to this soft fork. And then you have to adjust everyone's default settings to "perfect harassment protection, but handles exactly the same as Mastodon" because chances are these people won't even touch their settings.
If Mastodon users want perfect privacy and security, they want it on the very Mastodon instance they're on right now. And they want all these perfect privacy and security features to be on by default, but without meddling with their own use of Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta

Last updated: 2024-03-17

do not usually when i am

I have free will