VET/USDT
What are the chances that the ActivityPub side will get full (or any) support for Pleroma and its forks, Misskey and its forks, Friendica and other things that use the Mastodon client API
Or even server applications that can speak ActivityPub, but that don't have the Mastodon client API implemented
I sincerely hope that Surf isn't built against only Mastodon so hard that it's impossible to add more than just incidental and unsupported compatibility with anything that isn't Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #ActivityPub #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse Mastodon did start out as a full-stack Web application AFAIK. It used the OStatus protocol, the same protocol as what GNU social was based on and what StatusNet was using prior to its merger with its own fork, GNU social.
However, at first, it was not positioned as a fully independent project of its own, much less a federated walled garden that allegedly only connected to itself. It was initially conceived and advertised as an alternative to GNU social proper with a different, "easier-to-use", more Twitter-like GUI being its main selling-point.
I guess it's pretty obvious that what was working underneath was not GNU social proper either. Two examples to prove this:
Neither Identi.ca nor StatusNet nor GNU social had a rigid, hard-coded character limit of 500 characters. Mastodon had it from the get-go.
Also, Identi.ca, StatusNet and GNU social had a summary field. It was part of the OpenMicroBlogging and OStatus protocols. Both Friendica and Hubzilla made use of this summary field as such. Mastodon did not have the summary field implemented because summaries were pointless if all you had was 500 characters.
Fast-forward to 2017. Mastodon had meanwhile repositioned itself on the "market" as a stand-alone microblogging platform, implying to be a "decentralised, federated walled garden" with its own exclusive technology that nothing else used, and that nothing else connected to. Something that just about every last Mastodon newbie takes Mastodon for still today.
At some point in 2017, a Mastodon user from the demo scene with some development experience submitted a pull request to Mastodon's GitHub repository which would repurpose this very same summary field as a content warning field. The pull request was accepted and merged. Ever since shortly afterwards, Mastodon users started believing that Mastodon's content warning field was invented by Eugen Rochko from scratch. And they still do.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Identi.ca #StatusNet #OStatus #Mastodon #Friendica #Hubzilla #FediverseHistory Long
Or rather, "Wait, you exist!"
And IIRC, Misskey has its own client API. Aria seems to be the shooting star mobile app for the *keys.
In this regard, Pleroma and Akkoma are the best of both worlds. Headless server, own client API, respective official frontend has its own repository, but you may install third-party frontends instead. And Mangane is actually (also) built against the *omas. "Akkomane" is a thing.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #AriaApp #Pleroma #PleromaFE #Akkoma #AkkomaFE #Mangane #Akkomane That, of course, sounds like trouble. No frontend offers you the full functionality with no problems. But still, it's obvious that Hollo is developed for a Mastodon-dominated Fediverse with a side of *key and little regard for anything else. I wouldn't be surprised if the Hollo dev, like at least three quarters of the Fediverse, had never even heard of Hubzilla.
Hubzilla is a special case in many ways. It wasn't built into a Mastodon-dominated Fediverse because it was initially created some four years before Mastodon. Also, it doesn't have replacing Twitter as any of its goals. You can use it for microblogging, yes, but then, you can use it for almost anything. Even runs on Hubzilla.
Granted, Friendica is even older. After all, Friendica's own creator started Hubzilla as a Friendica fork. But Friendica's new developers decided for Friendica to approach Mastodon in some ways. In Hubzilla's case, in stark contrast, it's an explicit design and development decision not to do that. Part of Hubzilla's philosophy is to remain independent from the rest of the Fediverse.
Hubzilla is also one of the few Fediverse projects whose ActivityPub implementation is not designed for maximum Mastodon compatibility. That's partly because Hubzilla is the only Fediverse project that had ActivityPub before Mastodon. And Mastodon's adoption of ActivityPub caused quite some head-butting between Mike Macgirvin and Eugen Rochko.
That's only some of the reasons why the Mastodon API would never work for Hubzilla, and Hubzilla will always require its own tailor-made frontends.
Beyond that, there are those many, many things neither covered by the Mastodon API nor by any Mastodon-compatible app. And I'm not just talking about CMS or groupware features like , cards, , webpages or . (That is, Hubzilla's CalDAV calendars are edited the best with external apps, but via CalDAV and not via the Mastodon API.)
It actually starts at Hubzilla's handling of identities. Your identity is not tied to your account. Your login is not your identity. . And thanks to , you can have the same channel, the same identity, on multiple server instances with different accounts and logins.
An app based on Mastodon and its API would only let you access your default channel at best. At worst, it won't let you access anything because it expects your identity and all your stuff directly on your account, and it's completely unaware of the existence of channels. This is already a feature that's essential for using Hubzilla, but that absolutely requires a UI tailor-made for Hubzilla.
Then there is the distinction between posts and comments. Hubzilla does not mimic Twitter. It's closer to Facebook and blogs.
For one, Hubzilla doesn't display content bit by bit like Mastodon does, at least not by default. It's actually an option that nobody ever uses which may be why it's no longer available on (streams). Instead, it always displays conversations as a whole, just like Facebook, just like blogs, just like forms. Post on top with a title, comments below in chronological order. Always. Even when a new comment comes in, or someone has liked or repeated a comment, when you go and look at what happened, you get the whole thread.
Speaking of which, on Hubzilla, you don't usually do as you'd do on or Mastodon and scroll through your feed/timeline until either you hit stuff that you've already read, or you want no more. Instead, Hubzilla, like everything that Mike Macgirvin has made, has a counter for unnoticed actions. If you open it, you get a list of these actions that you haven't paid attention to yet. Click one, and you're taken to the thread where it happened (and only that thread is shown to you), and everything that was unread in this thread is flagged read.
In addition, has only one editor for everything, posts, comments (which are posts), DMs. So does Mastodon. So do all Twitter/ alternatives in the Fediverse.
But Facebook doesn't. It has a separate entry area for comments. So do blogs. And so forth. And so does Hubzilla. It has , and it has right at the bottom of each thread. It's geared towards having these two separate editors. Even using Friendica, which does have the Mastodon client API implemented, with a one-editor app has to be hackish.
All this continues with text formatting. Unlike the *keys and some Mastodon forks, Hubzilla doesn't use Markdown. It uses . This goes all the way to integration of OpenWebAuth magic single sign-on and .
Generally, image handling, including alt-text. On Mastodon and its forks, you attach your images to your posts as files, and then you get one dedicated entry field for alt-text for each image.
On Hubzilla, you first go to your and use it to upload the images you want to add to your post to the WebDAV-enabled file space built into your channel. You have to pay attention to setting the permissions both for the image files and for the subfolder correctly. Then you go to your post editor (not the comment editor which doesn't officially support inserting images) and select the image you want to embed. And then . (Notice how I've linked to a Hubzilla support forum instead of the WIP help rewrite because there still is no official documentation on how to add alt-text on Hubzilla.)
Any UI elements geared towards the Mastodon way of adding images to posts are useless on Hubzilla, and nothing on a UI for Mastodon can be used to add images to posts the Hubzilla way. Again, you need a Hubzilla-specific UI for this.
By default, and I guess it's actually recommended, posts and comments are composed in raw BBcode rather than WYSIWYG. The lack of a preview button in your average Mastodon app is actually a lesser issue, although it still is an issue.
Next, posting permissions. Mastodon has "Public", "Unlisted", "Followers only" and "Private". All apps are geared towards this.
Hubzilla, in contrast, has the . It offers you to post in public, to post only to yourself, to post to one of your (think Mastodon lists on piles of coke and 'roids), or to post to any individual custom selection of connections of yours. There's no "Followers only", there's no "Unlisted", and there's stuff that's completely unthinkable from a Mastodon POV.
Oh, and if you run your Hubzilla channel on bone-stock standard default settings, you post to a privacy group named "Friends" unless you explicitly choose otherwise. But you have to be able to choose otherwise in order not to only post to that privacy group. An app made for Mastodon won't give you the UI elements to do so.
In fact, an app geared towards the Twitter-style dichotomy of followers on the one side and followed on the other side will clash with Hubzilla because of just this. Again, Hubzilla is not like Twitter. It's like Facebook. It doesn't have one-sided following connections. It only has like Facebook friends.
This means that , but with a UI made for Mastodon, is next to impossible at worst and very, very limited and much less than optimal at best.
For example, let's suppose someone wants to connect to me. On Mastodon, I'd just simply confirm their follow request if I've chosen to do so. Then I may decide whether or not I follow them back.
Here on my Hubzilla channel, a connection request takes me to the . There I choose a for the new connection that defines which permissions that contact shall have. I add the connection to one or multiple privacy groups, of which I have a lot. I adjust the affinity slider. I may also assign to that connection. I may add lines to one of the two filter lists which I have per connection. Finally, I usually hide the new connection. And then I confirm it which not only grants the permissions in the contact role to the contact, but also establishes a bidirectional connection. It's like automatically following everyone back on Mastodon.
Apart maybe from the confirmation button, not even a single one of these features is available on any of the Twitter replacements in the Fediverse, and thus, not in any of the apps geared towards these either. If I were able to use Hubzilla with a Mastodon app, I'd still have to fire up a browser or a Web app or wait until I'm back home to confirm connection requests.
All this only covers your daily operation. I haven't even talked about yet, including the which defines the basics of Hubzilla's extensive permissions system.
There's exactly one app that works with Hubzilla. It's called , it's only available on F-Droid, it hasn't been updated in over five years, and it's actually a Web app that works like a specialised browser and embeds Hubzilla's Web UI.
A fully dedicated mobile app for Hubzilla that entirely relies on a native mobile UI would be so complex even for normal operation (disregarding the CMS bits) that it'd be more complex than K-9 Mail. If you want to go all the way, including (which controls Hubzilla's optional features, and which of these are available to you can differ from hub to hub) and CMS features and such, it'd be even more complex.
The only realistic way to have different frontends for Hubzilla would be the built-in theming feature. It doesn't mean different colours and button styles. A theme on Hubzilla can be an entirely different UI, but one that you can individually choose for each one of your channels. It's like being on Akkoma and being able to switch between Akkoma-FE, Phanpy and Mangane on your account at any given time.
That is, currently, Hubzilla has only got one built-in theme. It has become , and it even as a dark mode which is every bit as configurable as the light mode. More themes are being worked on in the community right now, but I wouldn't count on them coming with all stock Hubzilla installs, much less automatically added to all existing hubs.
So if you want an alternative UI for Hubzilla, you don't install it next to your hub, just like you install Phanpy next to Hollo or GoToSocial. You install it into your hub instead.
And the best way of developing alternative UIs for Hubzilla is not as fully separate external applications that try to latch onto Hubzilla from outside. It rather is as .
Hubzilla is modular and extendable with third-party repositories.
Lastly, both desktop and mobile use can profit from it because the best way to use Hubzilla on a phone is as a Progressive Web App.
, maybe this is interesting for you as well.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla It depends. Not everything works well frontless because not everything works well with a frontend made for Mastodon.
Hubzilla, for example, has a UI that's largely stuck in 2012. Also, it doesn't have the Mastodon client API implemented. But a frontend designed for Mastodon couldn't even cover 5% of Hubzilla's features. It would not grant access to features that are actually critical for operating a Hubzilla channel such as any parts of the permissions system.
And that's actually one of the reasons why Hubzilla doesn't have the Mastodon client API implemented: The only UI that can sufficiently harness Hubzilla's power is Hubzilla's own native Web UI.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #MastodonAPI #Hubzilla
Well, depending on where in the Fediverse you are, a whole lot can be possible.
I tend to make a whole lot of use of my possibilities. Hubzilla, where I am, doesn't have any character limits, at least none worth worrying about.
Sure, depending on your contacts, it makes sense to limit your alt-texts to no more than 1,500 characters because Mastodon, Misskey and their forks chop them off at this length if they're longer. Even Hubzilla itself can no longer fully display alt-texts of over a few thousand characters because they can't be scrolled. And alt-texts of such length are very uncomfortable for screen reader users because screen readers can't navigate alt-text.
But at least for my original images, I also give long image descriptions in the posts themselves in addition to the ones in the alt-texts. And with "long", I mean not "essay", but "short story". "Excessive" if you want.
My personal limit there is 100,000 characters for the whole post. As far as I know, Mastodon rejects longer posts than that entirely, and other Fediverse server apps have even lower limits, so describing my images actually becomes increasingly pointless. But 100,000 characters of description would take me three or four days to research for and write anyway.
Still, while my image posts remain within that limit, I regularly describe and explain my original images in tens of thousands of characters each. I see it as justified, given the very obscure but potentially curiosity-inducing topic. But others may say my long descriptions are way overkill, hardly anyone even reads them because it may pretty well take one hour to do so, and literally nobody actually needs them.
That's why I'm constantly wondering if I'm going overboard with details in my descriptions. Hence the question at the end of my first comment.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
Maybe Iceshrimp is worth a look, too, for those used to Twitter. Of course, people who want to leave or have left something entirely different should be taken to something entirely different like Lemmy, Mbin or PieFed for Redditors and Friendica, Hubzilla and (streams) for Faceboook users.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Sharkey #Iceshrimp #Lemmy #Mbin #PieFed #Friendica #Hubzilla #Streams #(streams) Judging by the advice I've read so far, it's always best to describe the colour using basic colours plus attributes such as brightness, saturation and what other basic colour or colours the colour you describe is leaning towards.
For example, "light, yellowish orange", "a darker, slightly less saturated, slightly more brownish tone of orange", "various shades of slightly yellowish, medium-light-to-medium brown", "a solid, slightly pale medium blue with a minimal hint of green", "a medium-dark wood texture, slightly reddish, slightly greyish". All actually used by me in the long descriptions in (content warning: eye contact) .
If the name of the colour plays a role, use it and then describe the colour in the same way as above. Blind or visually-impaired people may not know what Prussian blue or Burgundy red looks like.
What do you say, is that appropriate, complete overkill or still insufficient
#Long #LongPost #CWLong #CWLongPost #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMetaTo my surprise, indexes instances of more Fediverse server apps than I thought.
What I've found so far, other than hundreds upon hundreds of Mastodon instances:
One could suppose that all these server applications have taken active steps to become more compatible with Mastodon, but I've got my doubts that standard support for any Mastodon API is sufficient, and that they all have gone beyond API support.
Some things that I've yet to see on the list for the first time:
Still, their not only only seem to work on Mastodon, but it seems to be only possible to add Mastodon accounts and nothing else. It says a lot that is completely empty.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Pixelfed #Firefish #Sharkey #Catodon #GoToSocial #micro.blog #Friendica #Mitra #Misskey #Iceshrimp #Iceshrimp.NET #Pleroma #Akkoma #Hubzilla #Streams #(streams) #Forte #Threadiverse #Lemmy #Mbin #PieFed #FediDevs
You don't even need Mastodon forks to stay in the Fediverse.
There's enough stuff in the Fediverse that can do the same things as Mastodon, that's fully connected to and federated with Mastodon, but that isn't Mastodon, that has never been Mastodon, that isn't affliliated with Mastodon, and that outshines Mastodon as well as its forks in many ways.
(Sent from .)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
Use typographically correct quotation marks instead.
For English alt-text, that's and .
Windows: Alt+0147 and Alt+0148.
*nix: 3rd level+B and 3rd level+N.
For Spanish alt-text, that's and .
Windows: Alt+0171 and Alt+0187.
*nix: 3rd level+X and 3rd level+Z.
Alternatively, use the character map application of your operating system. Or copy-paste them from this comment.
If that's all too inconvenient, and you absolutely must use what's on the keyboard, use what amounts to single quotes: '.
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #FediTips Loops is very far from finished. It's in a very early state, it has only got one instance, that instance is experimental, and it doesn't federate with anything else yet.
Just because has announced it, doesn't mean it's a fully-featured, rock-solid, daily-driver-material version 1.0 stable release. Welcome to the world of free and open-source software.
Also, as far as I've seen, many Pixelfed accounts seem to be set to private so you can't look at them from outside as a non-user and follow them by only clicking. You're probably asked to register an account because you have to be logged in with a Pixelfed account on that particular instance to be allowed to see these private accounts.
The only way to see what they post is by following them, by copying their ID or their account URL and pasting it into your search. And then you can see what they'll post from that point on.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Loops #Pixelfed 2008. When launched Identi.ca.
After all, Mastodon started out as an alternative frontend for GNU social. GNU social is a fork of StatusNet. StatusNet, in turn, was the software which Identi.ca used to run on until it was merged into GNU social in 2013. (Evan first launched Identi.ca, and then he open-sourced the technology under the name of Laconi.ca, later StatusNet.)
This also means that the OStatus protocol is part of Mastodon's history as well. OStatus is the protocol that GNU social was based on back in the day and probably still is, that later versions of StatusNet were based on, and that Mastodon was originally based on. It's the successor to OpenMicroBlogging, the protocol that Identi.ca was launched on, and that early StatusNet was based on. But it was gone when Mastodon was launched.
It's also fair to mention Friendica, the Facebook alternative launched by Mike Macgirvin in 2010, and Hubzilla, the "federated social content management system" which, in 2015, emerged from something that Mike himself had forked off Friendica in 2012.
Both speak a whole lot of protocols. Hubzilla used to speak OStatus, Friendica still does. And so, when the very first Mastodon test release came out in early 2016, and the very first Mastodon instance was started up, it was immediately able to connect to GNU social, Friendica and Hubzilla.
It's an important part of Mastodon's history that Mastodon has never in its history been an isolated walled garden, that Mastodon has never in its history been connected to only itself.
Speaking of Hubzilla, it should be mentioned once again, namely in 2017.
The very first Fediverse project to implement ActivityPub was Hubzilla in July. Mastodon followed in September. These two were the only Fediverse projects that adopted ActivityPub before it was declared a standard. And so, for quite a while, it was only these two that could use ActivityPub to connect to each other (while still also being able to do so via OStatus, by the way). But since both have vastly different philosophies, actual compatibility was and still is limited.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Identi.ca #StatusNet #OStatus #Mastodon #Friendica #Hubzilla #ActivityPub #FediverseHistory 2022 glaubte man noch, "das Metaverse" sei Horizons. Alias "Facebooks Metaverse", alias "Zuckerbergs Metaverse", alias "Meta Metaverse". Die virtuellen 3-D-Welten, die Mark Zuckerberg 2021 angekndigt hat, und zwar als "das Metaverse". Nur leider konnte er sich den Begriff wohl nicht exklusiv schtzen lassen.
2024 glaubt man, "das Metaverse" sei die Gesamtheit der bekannten Meta-Platforms-Produkte: Facebook, Instagram, WhatsApp, Threads. Horizons ist lngst wieder in Vergessenheit geraten. Man glaubt also, "das Metaverse" hat gar nichts mit 3-D-Welten zu tun.
Tatschlich ist "Metaverse" ein Begriff aus Neal Stephensons 1991er Cyberpunk-Roman Snow Crash: eine riesige virtuelle Welt, die vom damaligen Internet inspiriert war. Snow Crash hat brigens Philip Rosedale dazu inspiriert, Second Life zu bauen, das wiederum Ernest Cline dazu inspiriert hat, Ready Player One zu schreiben.
Aus IEEE-Kreisen gibt es tatschlich .
In Verbindung mit tatschlich existierenden virtuellen Welten wird "Metaverse" seit sptestens 2007 regulr verwendet, und zwar von der Community um , eine freie, quelloffene, serverseitige Reimplementation der Technologie von Second Life. Das kam Anfang 2007 raus, im Sommer startete das erste ffentliche Grid, , und enthlt schon den Claim, den das OSgrid heute noch verwendet: "The Open Source Metaverse".
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #VirtuelleWelten #Horizons #HorizonWorlds #OpenSim #OpenSimulator #OSgrid #Metaverse #MetaversumDer Standard ist eigentlich PascalCase: Erster Buchstabe von jedem Wort ist gro. CamelCase wre eher "camelCase", also erster Buchstabe des ersten Wortes klein, erster Buchstabe von allen anderen Wrtern gro. Aber das ist fr die, die zu faul sind, Grobuchstaben zu schreiben.
Am elegantesten sieht natrlich ein Hashtag aus mehreren Wrtern aus. Zumindest auf Hubzilla, (streams) und Forte kann man ihn mit Anfhrungszeichen generieren:
Ich wei jetzt allerdings nicht, wie gut das in Screenreadern funktioniert. Vorlesen knnen sie das definitiv, aber das Risiko besteht, da sie einen Hashtag aus mehreren Wrtern nicht als Hashtag aus mehreren Wrtern erkennen und nur das erste Wort als Teil des Hashtags erkennen.
In der Mastodon-Suche spielt das brigens keine Rolle. Beim Indizieren von Hashtags schmeit Mastodon alle Zeichen raus, die auf Mastodon in Hashtags nicht funktionieren.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #ScreenReader #A11y #Accessibility #Barrierefreiheit #FediTips No, because I'd technically make them unfollow me, too.
, where I am (and which I'm commenting from right now, so it's very much part of the Fediverse and connected to Mastodon), is much more like Facebook and not at all like Twitter. It doesn't have that distinction between followers and followed. It only has mutual connections like Facebook friends.
So if I "unfollow" someone, read, disconnect from someone, I also renounce the permission I have given them to receive my posts. I don't remove myself from their follow list, but I don't send them any content anymore. It's like rejecting a previously confirmed follow request on Mastodon.
What I do instead is filter their reposts/boosts/renotes/repeats out, using a line of filter syntax.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Boost #Boosts #Boosting #Hubzilla #Streams #(streams) #Filter #FediTips
Maybe can answer your questions.
For end users, nomadic identity is currently only available on Hubzilla and (streams), using two versions of the Nomad protocol which has been geared towards and built around nomadic identity since its very beginnings in 2011. Nomadic identity via ActivityPub is still in closed, non-public testing.
Now, let's suppose the whole Fediverse had nomadic identity at its full extent.
Moving your identity using nomadic identity would go well beyond Mastodon's account migration:
But that's only the very basics. And it's a side-effect of the real power of nomadic identity: You can have clones of your whole identity with everything that comes with it on other servers. Not dumb copies, but near-real-time, live, hot, bidirectional backups.
A fully nomadic Fediverse will see your identity as only one identity, no matter how many clones you have. That's because your clones have the same identity as your main instance.
You can use the main instance of your identity, and whatever happens there will almost immediately be sent to your clones. You can use any of your clones just as well, and whatever happens there will almost immediately be sent to your main instance and your other clones.
If the server with your main instance goes down, you still have your clones, and you can carry on. You lose nothing.
You can also make one of your clones your new main instance which will demote your previous main instance to a clone. This is useful if the server with your main instance has gone offline and will not come back. You can simply declare one of your clones your new main instance. This will change your ID because it will adopt the domain of the server with your new main instance on it, but all your contacts will be changed accordingly, even on their side.
That is, I'm not quite sure how well nomadic identity will work on stuff that isn't Hubzilla or (streams) or Forte, server applications where your identity is bound to and directly stored in your account.
It works so well on Hubzilla, (streams) and Forte because they don't do that. They don't put your identity, your connections, your content etc. directly into your account. They put it into a container which they call a . You can have as many of these channels on the same account as you want. And these channels are fairly easy to clone from server to server.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #Forte #NomadicIdentity
It isn't like the FediDevs people don't know that there is more to the Fediverse than Mastodon. They do know. At least some do. There is that did work with Mastodon and other Fediverse server apps. But it hasn't been used in nine months.
At the same time, the FediDevs website is clearly not built against any Mastodon API. If it was, then server apps that have the same API implemented would work with it. But the only non-Mastodon thing I've seen slip through is one watched Catodon instance. Catodon uses Iceshrimp's technology to mimic Mastodon, so I guess it happens to be close enough.
For the whole thing looks like built against Mastodon's inner workings without the use of any API. Why would someone build it like that Either it's cluelessness. It definitely wasn't cluelessness. At least someone had to have knowledge of a Fediverse outside of Mastodon see the Friendica group.
Or it's intentional malice. It's like someone is secretly waging war against everything in the Fediverse that is not Mastodon. That seems to be why the Friendica group was abandoned, namely in order to stop using and thus promoting something that isn't Mastodon.
And FediDevs looks like it was built the way it was built in order to make bloody sure it will always stay a Mastodon-exclusive thing by making it as incompatible with the rest of the Fediverse as possible, at least probably without as blatantly obvious means as rejecting user agents. The "Fedi" in the name is the cherry on top to a) drive the point home that the Fediverse is (or should be) only Mastodon and b) flip the bird at the non-Mastodon Fediverse.
The whole backend code seems to be built against Mastodon directly also to make it as difficult as possible to add compatibility with other Fediverse server applications because that would require the whole backend to be redesigned and rewritten from the ground up.
I'd really like the FediDevs staff to prove me wrong by actually opening their site to the non-Mastodon Fediverse.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #FediDevs
They're looking for a drop-in replacement of pre-Musk Twitter. For one, Misskey and the Forkeys are actually closer to pre-Musk Twitter in UX than Mastodon.
Besides, if you keep doing what has been done for almost three years now, railroad everyone to Mastodon without even telling them that there's more to the Fediverse than Mastodon in order to keep things simple, you'll end up with even more people who spend months or years in Mastodon-only bubbles. Who then get used to a Fediverse which allegedly is only Mastodon.
Who end up very irritated and defensive of their "Mastodon Fediverse" when an alleged "intruder" that's nothing like Mastodon shows up in their timeline.
And who try hard to force non-Mastodon users to abandon their own culture, only adopt Mastodon's culture, use whatever they're on exactly like Mastodon and stop using any features that Mastodon 3 didn't have because Mastodon's entire culture is defined by Mastodon 3's features.
Trust me, it really is that bad. I'm a Hubzilla user. I speak from personal experience.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Misskey #Forkey #Forkeys #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse I think it'll stay incomplete.
FediDevs looks to me like it was built hard against only Mastodon. Not against any Mastodon API, but directly against Mastodon's inner workings. And intentionally so. The only thing I've seen that managed to work with FediDevs in at least one case is Catodon which mimics Mastodon itself.
FediDevs used to have its own Friendica discussion group. It was last used nine months ago.
I'd be pleasantly surprised if any of this changed. But right now, it looks to me like FediDevs has explicitly positioned itself against the non-Mastodon Fediverse now.
And still, they have the audacity to call it FediDevs.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #FediDevs
Facebook may be "the Internet" for the entire Third World, but Meta need the European market. Desperately. And be it out of fear that the Facebook and Instagram killers may come out of Europe where people can no longer use "the real deal" after they were banned from the EU.
I dare say that Meta aren't a bunch of dumb jingoists who can barely grasp the idea of Europe having electricity. I'm pretty sure they know about the pile of social networks that were launched in Germany alone. I'm not even talking about Mastodon and Pleroma. I'm talking about StudiVZ/MeinVZ, Wer-kennt-wen and StayFriends, just to name the formerly biggest three. In fact, when Facebook was new, it had a hard time entering the German market because its entire potential target audience was on StudiVZ or MeinVZ and/or Wer-kennt-wen already.
So if Meta Platforms were banned from the EU market in its entirety, chances wouldn't be bad that someone whips up replacements.
And Meta know pretty well that this wouldn't even be necessary. There are already alternatives for everything the offer, even free, open-source, decentralised ones in all cases, and Meta know about at least some of them. They've known Friendica since at least 2012, for example. If Meta were forced to leave the EU, some of these alternatives would grow huge enough to have the chance to become serious competition to Meta outside the EU.
And so they're connecting Threads to the Fediverse just barely enough for the EU to shut up and leave them alone. I mean, why don't they go all-in instead if they're allegedly so eager to get their filthy hands on the Fediverse
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #MetaPlatforms #Facebook #Instagram #WhatsApp #Threads #Horizonworlds #Horizons #EU #EuropeanUnion
There were no "people who wrote the Fediverse". These was no committee who laid down the standards.
The Fediverse was invented by . In 2008. By first creating a centralised Twitter alternative silo named Identi.ca.
And then open-sourcing the underlying technology as Laconi.ca, later StatusNet (merged into GNU social in 2013).
And then laying the protocol open as OpenMicroBlogging, later superseded by OStatus.
Then, in 2010, Mike Macgirvin decided that the world needs a free, open-source, decentralised, secure alternative to Facebook that's better than Facebook. And so he made Mistpark, today .
But the features he wanted Friendica to have were impossible to achieve with any existing protocol. OStatus wasn't even that good for microblogging, much less Mike's ambitious plans. Besides, he's an experienced protocol designer. So he created a whole new protocol, DFRN, and built Friendica on top of it. Friendica did adopt OStatus as an extra protocol, though, because Friendica's goal was and still is to federate with everything and then some.
In 2011, Mike had seen many public Friendica nodes shut down with or without warning and people always losing everything and having to start over from scratch. So he decided to do something against it.
He invented . And built a new protocol around it, Zot, because there was no way DFRN could take care of this, let alone OStatus.
In 2012, he forked Friendica into Red and rewrote the whole backend against Zot, which, however, required the creation of yet another identity scheme.
For one, one login could now have multiple fully separate and independent identities on it. For example, my Hubzilla channel URL is .
Besides, one identity could now reside on multiple server instances which is what nomadic identity means.
Red was later renamed Red Matrix and, in 2015, refactored, redesigned and renamed into .
Mastodon and Pleroma started in 2016 as OStatus-based alternative UIs for GNU social. Mastodon was the first to be turned into a stand-alone project with not much interest in connecting to anything outside, all in spite of already being federated with Pleroma, GNU social, Friendica and Hubzilla via OStatus.
ActivityPub came out in 2017. No, not 2018. It was standardised in 2018. But it came out in 2017.
In July, 2017, Hubzilla was the first Fediverse project to integrate ActivityPub. Next to its own Zot, next to diaspora*, next to OStatus etc. On the one hand, Hubzilla tried to stay as close to the ActivityPub spec as possible and feasible. On the other hand, Hubzilla had to make its ActivityPub integration, which has always been an optional add-on, compatible to its own technology, to its own Zot protocol, to the way it works.
In September, Mastodon was the second Fediverse project to adopt ActivityPub. But Mastodon was more interested in doing its own thing and being as close to Twitter as it could than in sticking to a protocol spec, much less connecting to non-Mastodon stuff such as Hubzilla with which it already shared two protocols now.
Mastodon was the one that added Webfinger. ActivityPub doesn't even require Webfinger. The ActivityPub spec doesn't contain Webfinger. But Mastodon requires Webfinger. It can't live without Webfinger. So everything that wants to properly federate with Mastodon needs to implement Webfinger.
After ActivityPub had become a standard, more projects adopted it. But as lax a specification as ActivityPub is, it allowed for a lot of liberties.
Some devs looked at how Mastodon had integrated ActivityPub, decided it was rubbish and did it their own way.
Some devs looked at how Mastodon had integrated ActivityPub, decided they couldn't do it the same way because what they did was too different from Mastodon and did it their own way.
Some devs didn't look at what anyone else did and did it their own way.
Probably none of them looked at how Hubzilla had integrated ActivityPub because none of them even knew that Hubzilla existed. Except for those who were maintaining Friendica now. And Friendica had to make it compatible with DFRN and with the way it had been working since 2010.
Fast-forward to 2023. Mike's current piece of work was which contains an intentionally nameless fork of a fork of three forks of a fork (of a fork) of Hubzilla, slimmed down from Hubzilla, but modernised and technologically even more advanced.
It was then that , creator and maintainer of , got into contact with him because he wanted to add nomadic identity to Mitra. Something that's built on ActivityPub and only supports ActivityPub. A first. No-one had ever done nomadic identity with nothing but ActivityPub before.
So the two started working on how to implement nomadic identity using only ActivityPub. Mike had a vision of a Fediverse with nomadic identity all over and Fediverse identities cloned beyond server application borders. Like, a (streams) channel cloned to Mitra, Mastodon, PeerTube and Mobilizon, all with the same identity.
This, however, required another, brand-new way of identifying Fediverse actors. And so was created.
We're probably in the middle of xkcd 927 now.
Mike set up an experimental branch of (streams) to develop and test nomadic identity via ActivityPub, also since (streams) already had nomadic identity anyway.
Around summer, the "nomadic" branch (for nomadic identity via ActivityPub) seemed reliable enough to merge it into "dev". And in July, "dev" was merged into "release", complete with nomadic-identity-via-ActivityPub code.
It was shortly after that merge that I created my two (streams) channels. The channel URL of my channel for Fediverse memes is . But its DID, which all channels created on accounts registered after that merge got, is . And that's only two IDs of the same channel. There are also others for (streams)' native Nomad protocol, Hubzilla's Zot6 protocol, ActivityPub, OAuth, OAuth2 and probably also OpenWebAuth magic single sign-on, another one of Mike's creations. Not to mention that (streams) channels, like Hubzilla channels and Friendica accounts, can also optionally be group actors.
In fact, this blew up into (streams) users' faces because (streams) confused the various IDs to such degrees that it wouldn't federate at all anymore. It took Mike a whole lot of work to iron this out again, so much that he officially retired from Fediverse development on August 31st.
And in the middle of this, he even created yet another fork, Forte, which is (streams) minus Nomad, minus Zot6, based on and supporting only ActivityPub. My guess is still that one of the reasons to create Forte at that point was to get rid of the Nomad and Zot6 IDs to sort the ID mess out.
Even if nomadic identity via ActivityPub should ever become stable and start spreading, I don't expect DIDs to become the one norm in the Fediverse. Not with all those barely or unmaintained projects and those devs who refuse to acknowledge that devs of other projects do great stuff, too.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #OStatus #DFRN #Zot #ActivityPub #Nomad #Laconi.ca #Identi.ca #StatusNet #GNUsocial #Friendica #Hubzilla #Mastodon #Pleroma #Streams #(streams) #Forte #FEPef61
Das ist schon mal positiv. Es gibt Leute, die sich so an ein reines Mastodon-Fediverse gewhnt haben, da sie alles, was anders ist, als strende Eindringlinge empfinden und wieder weg haben wollen.
Na ja, auf eine Art schon. Was nicht Mastodon ist, ist ja auch nicht Mastodon mit einer anderen Oberflche. Das kann schon ziemlich anders sein.
Zunchst mal sind so Features wie Textformatierung, Zitate oder Drkos/Drukos und sehr viel hhere oder gar keine Zeichenlimits auerhalb von Mastodon gang und gbe. So manch jemand, der bis dahin das Fediverse als reines Vanilla-Mastodon-Netzwerk ansah, kriegt ja einen Riesenschreck, wenn das erste Mal ein Beitrag mit deutlich ber 500 Zeichen auftaucht. Oder mit einem Zitat. Oder mit einer Stichpunkteliste. Oder mit Kursivschrift, aber es ist keine Unicode-Trickserei.
Schon im Microblogging-Bereich gibt's einiges, das ziemlich anders ist als Mastodon. ist ja auf einer der letzten verbliebenen Instanzen von Calckey. Das ist ein Fork des japanischen Misskey, der eigentlich letztes Jahr durch Firefish ersetzt wurde. Misskey hat schon 3000 Zeichen, die wie auf Mastodon hartgecodet sind. Bei den diversen Forkeys (Calckey/Firefish, Sharkey, CherryPick, Iceshrimp, Catodon usw. usf.) liegen die Limits mindestens auf dem Niveau, wenn nicht hher, sind aber durch den Admin konfigurierbar.
Interessanterweise sind Misskey und die Forkeys (wobei Iceshrimp allmhlich kein Fork mehr ist) in der Handhabung trotzdem, und obwohl sie auch noch Features wie Textformatierung mittels einer erweiterten Variante von Markdown und eine sehr konfigurierbare Oberflche haben, dichter an Pr-Musk-Twitter, als es Mastodon ist. Eine Mehrspaltenansicht la TweetDeck haben Mastodon und die *keys, aber vor allem bei denjenigen Forkeys, die gegenber Misskey noch Extrafeatures haben, kannst du damit mehr anstellen.
Die richtig groen Keulen sind dann die von Mike Macgirvin ber gute 14 Jahre auf den Weg gebrachten (mehr oder weniger) Facebook-Alternativen. Friendica existiert schon seit 2010 und hatte von Anfang an schon eine sagenhafte Feature-Palette. Whrend Mastodon versucht, Twitter nachzuffen, hat Friendica nie versucht, Facebook nachzuffen, sondern eher, besser als Facebook zu sein.
So gibt's da beispielsweise auch alles, was man zum Bloggen bruchte. Zeichenlimits gibt's nicht, gab's nie. Dafr gibt's die volle Palette an Textformatierung per erweitertem BBcode. Es gibt einen eingebauten Filespace, wo man z. B. Bilder hochladen und dann beliebig viele davon in Posts einbetten kann, also mit Text darber und Text darunter, statt wie auf Mastodon nur vier davon als Dateien anhngen zu knnen.
Man kann Friendica-Konten auch als moderierte Diskussionsgruppen verwenden, hnlich wie Gruppen auf Facebook. Die Erfahrung hat gezeigt, da Friendica-Gruppen mit groen Teilen des Fediverse kompatibel sind bis hin zu Mastodon, nur da es besonders fr Mastodon-Nutzer nicht ganz straight-forward ist, einen Thread zu starten.
Friendicas eigentliches Killerfeature war aber immer, da es stets versucht hat, sich mit allen mglichen Sachen zu verbinden. Es sollte so eine Art Kommunikationszentrale sein. Friendica kann sich mit diaspora* verbinden, es kann sich ber OStatus mit den Sachen verbinden, die es noch haben, man kann zu WordPress und kompatiblen Blogs crossposten, man kann RSS- und Atom-Feeds abonnieren, und man kann auch per E-Mail oder XMPP kommunizieren.
Man kann auch ein Tumblr- oder Bluesky-Konto ins Friendica-Konto einbinden und sich dann damit bidirektional verbinden, ganz ohne Bridge. Theoretisch ginge das sogar mit , wenn der Node-Betreiber ein Multimillionr wre, der sich die API-Lizenz leisten kann. Und ab 2012 ging es kurzzeitig sogar mit Facebook, bis Facebook das unterbunden hat.
ber Friendica gbe es noch einiges mehr zu erzhlen, was da geht. So manch einer sieht es als das Schweizer Taschenmesser des Fediverse.
Aber wenn Friendica das Schweizermesser ist, dann ist Hubzilla das Leatherman. Hubzilla ist nmlich noch heftiger. Es wird bezeichnet als "dezentrales soziales Content Management System" und vereinigt entsprechend viele Funktionalitten unter einem Dach.
Hubzilla fing ja 2012 an als ein Friendica-Fork namens Red, dann Red Matrix, und war zunchst einmal nicht viel mehr als Friendica mit , und einem ziemlich mchtigen und detaillierten Berechtigungssystem. 2015 wurde es dann in Hubzilla umbenannt und entsprechend featuremig zur eierlegenden Wollmilchsau aufgebohrt.
Man knnte Hubzilla jetzt fr alles Mgliche und Unmgliche nehmen. Beispielsweise habe ich auf diesem Kanal und . Und ist selbst Teil eines Hubzilla-Kanals.
Der Pepe (Hubzilla) hat Hubzilla sehr gut und sehr detailreich in seiner erklrt.
Danach folgte von 2018 bis 2021 eine ganze Reihe von Forks, bei denen Zusatzfeatures und Verbindungsmglichkeiten wieder abgespeckt wurden, die aber allmhlich technisch und in der Handhabung immer weiter aufgefrischt und modernisiert wurden.
Im Oktober 2021 kam dann etwas, was eine ganze Zeitlang als stabil angesehen wurde, was aber auch ziemlich ungewhnlich ist. Es hat nmlich offiziell, mit voller Absicht und aus guten Grnden keinen Namen, keine Markenidentitt, (fast) keine Nodeinfo, und es wurde ebenso mit voller Absicht in die Public Domain gestellt, whrend Mike sonst alles unter die MIT-Lizenz gestellt hat.
Das Code-Repository brauchte aber zwingend einen Namen. Mike hat es Streams genannt, und so wird auch die Anwendung nicht ganz offiziell (streams) genannt, inklusive der Klammern.
Krzlich hat Mike die Readme-Datei aktualisiert, .
Okay, seit Osada und Zap von 2018 hat die Familie keine Artikel mehr, keine Karten, keine Wikis, keine Webpages, der Kalender ist vereinfacht worden usw. Das ganze Zeug gab es ja eh schon auf Hubzilla, und Mike wollte wieder zurck zu reinem Social Networking.
Dafr hat er aber die Handhabung vereinfacht, verschlankt und der Realitt angepat, vor allem auch der Realitt eines Fediverse, das mehr und mehr von ActivityPub dominiert wurde. Deswegen hat (streams) eine bessere ActivityPub-Integration als Hubzilla. Auf beiden ist ActivityPub optional, aber auf (streams) ist es in den Kern eingegossen, und (streams) kann es sich im Gegensatz zu Hubzilla erlauben, ActivityPub standardmig in neuen Kanlen zu aktivieren.
Ganz besonders die Berechtigungssteuerung ist vereinfacht und entschlackt und ermglicht eine direktere Kontrolle darber, welcher Kontakt was darf. Gleichzeitig ist (streams) aber auch sicherer, weil es nicht mehr mglich ist, den ganzen Kanal auf ffentlich zu schalten.
(streams) wird heute noch von Mike mehr oder weniger weiterentwickelt. Aber mit Forte hat er seit August noch ein weiteres Eisen im Feuer. Forte ist im Prinzip (streams), aber es untersttzt nur noch ActivityPub. Das heit auch, da auf Forte nomadische Identitt rein ber ActivityPub abgewickelt wird und nicht mehr ber ein eigens dafr entwickeltes Protokoll. Deswegen ist Forte noch nicht ffentlich, ebenso wie brigens die Entwicklerversion des Microblogging-Projekts Mitra, in der auch nomadische Identitt eingebaut wird.
Aller Komplexitt zum Trotze kann man, wenn man will, alle vier natrlich auch zum Microbloggen nehmen.
Darber hinaus gibt's im Fediverse noch in andere Richtungen spezialisierte Sachen, die also nichts mit Microblogging oder Social Networking zu tun haben.
Mit Lemmy, dem dahinsiechenden /kbin, Mbin, PieFed und dem in Entwicklung befindlichen Sublinks gibt es etwa eine ganze Anzahl an Alternativen zu Reddit oder auch Hacker News.
Mit WriteFreely und Plume gibt's zwei spezialisierte Blogginganwendungen im Stil von Medium. Plume ist von den Features her eigentlich besser, wird aber im Moment nicht weiterentwickelt. Auerdem sind inzwischen viele WordPress-Blogs ans Fediverse angebunden.
PeerTube prsentiert sich als Alternative zu YouTube mit einer Prise Peer-to-Peer zwischen den Instanzen, inklusive Livestreaming. Rein auf Livestreaming la Twitch spezialisiert ist Owncast. Ganz neu ist Loops als TikTok-Ersatz vom Macher unter anderem von Pixelfed und der FediDB, das fderiert aber noch nicht.
Im Audiobereich gibt's Funkwhale, wo man im Prinzip alles hochladen kann, aber nur lizenzmig freie Sachen ffentlich machen sollte, das noch recht junge Bandwagon als Bandcamp-Alternative und Castopod speziell fr Podcasts wie z. B. das auch von gefeaturete .
Es gibt noch einiges mehr, z. B. Mobilizon fr kooperative Eventplanung, BookWyrm als GoodReads-Ersatz oder, auch noch recht neu, Flohmarkt, das ziemlich genau das ist, wonach es sich anhrt.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Misskey #Forkey #Forkeys #Calckey #Firefish #Sharkey #CherryPick #Iceshrimp #Catodon #Friendica #Hubzilla #Streams #(streams) #Forte #Lemmy #/kbin #Mbin #PieFed #Sublinks #WriteFreely #Plume #WordPress #PeerTube #Owncast #Loops #Funkwhale #Bandwagon #Castopod #Mobilizon #BookWyrm #Flohmarkt #FediTips FediDevs als Ganzes scheint komplett hart gegen Mastodon, nur Mastodon und nichts als Mastodon gebaut zu sein. Oder was auch immer gengend proprietren Mastodon-Kram eingebaut und sich an Mastodon angepat hat, um kompatibel zu sein.
Beispiel 1: Guckt euch mal unter den die Liste der getrackten Instanzen an. Wieviele Nicht-Mastodon-Instanzen sind da, auer einer einzigen Catodon-Instanz (Catodon soll eine Art Mastodon mit einem Rest Iceshrimp-Backend darunter werden, soweit ich das verstanden habe.)
FEDIDevs impliziert doch, fr Entwickler aus dem ganzen Fediverse zu sein. Es schliet aber fast alles aus, was nicht Mastodon ist, und somit auch die Entwickler vieler Serveranwendungen, die nicht Mastodon sind. Die knnen gar nicht teilnehmen, weil das Backend von FediDevs vermutlich nicht mal gegen eine Mastodon-API gebaut ist, sondern direkt gegen Mastodon-Code.
Beispiel 2: ein Starterpack namens "".
Der ist komplett leer. Da ist genau berhaupt nichts drin.
Warum Weil es ganz augenscheinlich technisch vollkommen unmglich ist, irgendwas da einzutragen, was nicht auf Mastodon ist.
Wer auch immer hinter dem Bau von FediDevs steckt, scheint entweder anzunehmen, da das Fediverse nur aus Mastodon besteht. Oder es war einfacher, FediDevs nur gegen Mastodon zu bauen, stattdas eine Promille das eine Prozent die zwei Prozent die knapp 30 Prozent an Fediverse-Nutzern zu bercksichtigen, die nicht auf Mastodon sind.
Ganz offenkundig wei bei FediDevs eine Hand nicht, was die andere tut. Auf der einen Seite gibt's ein Webportal, das nur mit Mastodon funktioniert. Auf der anderen Seite gibt's mit eine Friendica-Gruppe aus denselben Kreisen, wobei die seit einem Dreivierteljahr nicht mehr genutzt wird.
Das, oder dahinter steckt der Vorsatz, das Fediverse (wieder) zu nur Mastodon zu machen, indem alles Mgliche und Unmgliche, was an "Fediverse"-Diensten und -Zusatzfeatures entwickelt und beworben wird, mit voller Absicht gleichzeitig "Fedi" im Namen hat und nur gegen Mastodon gebaut wird.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon #FediDevs
Nicht nur knnte ich ohne groe Schwierigkeiten mit meiner kompletten Identitt und allem, was dazugehrt, umziehen. Sondern ich kann sie auch ber mehrere Serverinstanzen klonen. So liegt sie nicht in einer, sondern aktuell in zwei Hnden. Geht eine Instanz mal offline, oder ist sie gestrt, habe ich einen identischen Klon meines Kanals woanders, und zwar mit allem Content, mit allen Kontakten, mit allen Dateien, mit allen Einstellungen, mit allem Drum und Dran.
Und im brigen kann sich im Fediverse jeder aussuchen,
Wer die technischen Fhigkeiten und Mglichkeiten hat, kann ersteres sogar umschiffen, indem er seine eigene Privatinstanz von was auch immer betreibt, vielleicht gar auf einer Maschine im eigenen Eigentum in den eigenen vier Wnden.
Aber generell habe ich schon genug Erfahrung mit dezentralen Systemen (XMPP, Matrix, OpenSimulator, das Fediverse auch schon seit Anfang der 2010er), da ich sagen kann: So etwas wird sich nie 100% wie ein zentralistisches, kommerzielles Silo anfhlen und auch nie so funktionieren. Und wem das nicht pat, der ist da eben falsch.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #NomadischeIdentitt
Dafr mte Mastodon erst nomadische Identitt einfhren. Dann ginge das ziemlich problemlos. Hubzilla hat das seit Anbeginn, seit 2012. Aber rein ber ActivityPub ist das noch extrem experimentell.
Hufig gestellte Forderung. Aber technisch unrealistisch.
Nehmen wir mal an, ich setze meine eigene (streams)-Instanz auf. Alles konfiguriert, alles startklar. Ich gebe
In diesem Sekundenbruchteil mten alle zigtausend Fediverse-Instanzen sofort von der Existenz meiner (streams)-Instanz wissen. Instantan. Auf der Stelle. (Du hast "wirklich *alle* Server" geschrieben. Also ohne jegliche Ausnahme.)
Das wre nur auf drei Arten und Weisen vorstellbar.
Erstens: Alle zigtausend Fediverse-Instanzen wissen vorher, da ich vorhabe, diese (streams)-Instanz aufzusetzen. Vorstellbar, aber vollkommen unrealistisch.
Zweitens: Meine (streams)-Instanz kennt alle, aber auch wirklich absolut ausnahmslos alle anderen Fediverse-Instanzen, die zu dem Augenblick existieren, wo der Webserver anspringt. Und zwar ohne dezentrale Hilfsmittel.
Das heit: Der Quellcode im streams-Repository enthlt eine nanosekundenaktuelle Liste aller Fediverse-Instanzen. Die Liste wird beim Klonen des Quellcode auf den Webserver mit runtergeladen. Beim ersten Start macht die (streams)-Instanz als allerallererstes einen
So eine Liste mu dann im Quellcode von absolut ausnahmslos jeder Fediverse-Serveranwendung eingebaut sein. Auch wenn jemand gerade erst mit einer ganz neuen Fediverse-Serveranwendung anfngt, mu da sofort diese Liste in vollem Umfang rein.
Und natrlich mu sie aktuell gehalten werden. Das heit, jede startende neue Instanz mu sich selbst in die Listen in den Quellcodes aller Anwendungen eintragen.
Meine (streams)-Instanz mte also alle Fediverse-Serveranwendungen kennen, die es berhaupt gibt. Auch wenn ein Fediverse-Entwickler erst eine halbe Sekunde vorher den allerersten git commit einer ganz neuen Fediverse-Serveranwendung gemacht hat.
Das heit auerdem: Meine (streams)-Instanz mte unmittelbar nach dem Start die Quellcodes von weit ber 100 Fediverse-Serveranwendungen
Jetzt kommt's: Die nderungen mssen ja auch noch gemerget werden. Dafr mte mein (streams)-Instanz sich auf hunderten Git-Repositories volle Maintainer-Rechte verschaffen und die eigenen Commits mergen. Und zwar auch, ja, gerade in Produktivcode.
Ich sage ja nicht, da das potentiell unsicher ist.
Auerdem mu das schnell gehen. Hunderte Repositories klonen, ndern, committen, reinhacken und mergen, alles innerhalb eines Nichtsigstels einer Sekunde, damit die experimentelle Iceshrimp.NET-lnstanz, die jemand eine Zehntelsekunde spter startet, auch von meiner eigenen (streams)-Instanz wei und ihre eigene Instanz meiner (streams)-Instanz mitteilen kann.
Noch einmal: Du hast "wirklich *alle* Server" gesagt. Das heit, eine neue Iceshrimp.NET-Instanz mu zwingend und sofort eine neue (streams)-Instanz kennen, die eine Zehntelsekunde frher gestartet ist.
Ach ja, das ganze Theater ist auch vollumfnglich ntig, wann immer
Jeder Entwickler wird mir besttigen, da das nicht nur komplett unrealistisch ist, sondern absolut haarstrubend. Alleine schon, weil 99,9% der Commits in den meisten Repositories von Fediverse-Instanzen kommen werden und alle Commits, die hndisch von Entwicklern kommen, darunter ersaufen. Und weil kein Entwickler seine eigenen Sachen so schnell rebasen kann, wie neue Commits mit nderungen an der Instanzenliste reinkommen.
Okay, also bleibt als dritte und einzige noch mgliche Lsung eine zentral verwaltete Liste auf einem zentralen Webserver.
Dieser Server mu verpflichtend in alle Fediverse-Serveranwendungen eingebaut sein. Auch die, die eigentlich gar nicht mehr gewartet werden, aber noch laufende Instanzen haben (Calckey, Plume usw.).
Damit wrde sich das ganze Fediverse bis in den allerhinterletzten Winkel absolut und total abhngig von zentraler Infrastruktur machen.
Warum das schlecht ist Stell dir mal vor, diese Liste geht offline aus irgendeinem Grunde. Oder irgendeiner, z. B. Elon Musk oder Jeff Bezos oder Mark Zuckerberg, kauft den Webserver mit der Liste drauf. Der htte dann die totale Kontrolle ber das Fediverse.
Willst du das
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #git
Or even server applications that can speak ActivityPub, but that don't have the Mastodon client API implemented
I sincerely hope that Surf isn't built against only Mastodon so hard that it's impossible to add more than just incidental and unsupported compatibility with anything that isn't Mastodon.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #ActivityPub #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse Mastodon did start out as a full-stack Web application AFAIK. It used the OStatus protocol, the same protocol as what GNU social was based on and what StatusNet was using prior to its merger with its own fork, GNU social.
However, at first, it was not positioned as a fully independent project of its own, much less a federated walled garden that allegedly only connected to itself. It was initially conceived and advertised as an alternative to GNU social proper with a different, "easier-to-use", more Twitter-like GUI being its main selling-point.
I guess it's pretty obvious that what was working underneath was not GNU social proper either. Two examples to prove this:
Neither Identi.ca nor StatusNet nor GNU social had a rigid, hard-coded character limit of 500 characters. Mastodon had it from the get-go.
Also, Identi.ca, StatusNet and GNU social had a summary field. It was part of the OpenMicroBlogging and OStatus protocols. Both Friendica and Hubzilla made use of this summary field as such. Mastodon did not have the summary field implemented because summaries were pointless if all you had was 500 characters.
Fast-forward to 2017. Mastodon had meanwhile repositioned itself on the "market" as a stand-alone microblogging platform, implying to be a "decentralised, federated walled garden" with its own exclusive technology that nothing else used, and that nothing else connected to. Something that just about every last Mastodon newbie takes Mastodon for still today.
At some point in 2017, a Mastodon user from the demo scene with some development experience submitted a pull request to Mastodon's GitHub repository which would repurpose this very same summary field as a content warning field. The pull request was accepted and merged. Ever since shortly afterwards, Mastodon users started believing that Mastodon's content warning field was invented by Eugen Rochko from scratch. And they still do.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Identi.ca #StatusNet #OStatus #Mastodon #Friendica #Hubzilla #FediverseHistory Long
VET/USDT
Entry price : - 0.05450 - 0.05300
Target 1: 0.055
Target 2: 0.057
Target 3: 0.060
Stop loss : 0.051
Leverage: 10x
Allocate only 1-3% of our deposit for each trade
BTC/USDT:
ENTRY:-104000 -103000
LEVERAGE: ( 10x-20x )
1 105000
2 106000
STOP-LOSS: 102600
This is also why I find the western Misskey forks' desire to pander to mobile users by trying to function with existing Mastodon Clients so counterproductive - the Mastodon Clients often just don't care. They really only are for Mastodon and everything else is "good luck have fun".
Or rather, "Wait, you exist!"
And IIRC, Misskey has its own client API. Aria seems to be the shooting star mobile app for the *keys.
Frontless servers to me are a bad idea, as things stand - despite the appeal in speeding up initial development.
In this regard, Pleroma and Akkoma are the best of both worlds. Headless server, own client API, respective official frontend has its own repository, but you may install third-party frontends instead. And Mangane is actually (also) built against the *omas. "Akkomane" is a thing.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Misskey #Forkey #Forkeys #AriaApp #Pleroma #PleromaFE #Akkoma #AkkomaFE #Mangane #Akkomane That, of course, sounds like trouble. No frontend offers you the full functionality with no problems. But still, it's obvious that Hollo is developed for a Mastodon-dominated Fediverse with a side of *key and little regard for anything else. I wouldn't be surprised if the Hollo dev, like at least three quarters of the Fediverse, had never even heard of Hubzilla.
Hubzilla is a special case in many ways. It wasn't built into a Mastodon-dominated Fediverse because it was initially created some four years before Mastodon. Also, it doesn't have replacing Twitter as any of its goals. You can use it for microblogging, yes, but then, you can use it for almost anything. Even runs on Hubzilla.
Granted, Friendica is even older. After all, Friendica's own creator started Hubzilla as a Friendica fork. But Friendica's new developers decided for Friendica to approach Mastodon in some ways. In Hubzilla's case, in stark contrast, it's an explicit design and development decision not to do that. Part of Hubzilla's philosophy is to remain independent from the rest of the Fediverse.
Hubzilla is also one of the few Fediverse projects whose ActivityPub implementation is not designed for maximum Mastodon compatibility. That's partly because Hubzilla is the only Fediverse project that had ActivityPub before Mastodon. And Mastodon's adoption of ActivityPub caused quite some head-butting between Mike Macgirvin and Eugen Rochko.
That's only some of the reasons why the Mastodon API would never work for Hubzilla, and Hubzilla will always require its own tailor-made frontends.
Beyond that, there are those many, many things neither covered by the Mastodon API nor by any Mastodon-compatible app. And I'm not just talking about CMS or groupware features like , cards, , webpages or . (That is, Hubzilla's CalDAV calendars are edited the best with external apps, but via CalDAV and not via the Mastodon API.)
It actually starts at Hubzilla's handling of identities. Your identity is not tied to your account. Your login is not your identity. . And thanks to , you can have the same channel, the same identity, on multiple server instances with different accounts and logins.
An app based on Mastodon and its API would only let you access your default channel at best. At worst, it won't let you access anything because it expects your identity and all your stuff directly on your account, and it's completely unaware of the existence of channels. This is already a feature that's essential for using Hubzilla, but that absolutely requires a UI tailor-made for Hubzilla.
Then there is the distinction between posts and comments. Hubzilla does not mimic Twitter. It's closer to Facebook and blogs.
For one, Hubzilla doesn't display content bit by bit like Mastodon does, at least not by default. It's actually an option that nobody ever uses which may be why it's no longer available on (streams). Instead, it always displays conversations as a whole, just like Facebook, just like blogs, just like forms. Post on top with a title, comments below in chronological order. Always. Even when a new comment comes in, or someone has liked or repeated a comment, when you go and look at what happened, you get the whole thread.
Speaking of which, on Hubzilla, you don't usually do as you'd do on or Mastodon and scroll through your feed/timeline until either you hit stuff that you've already read, or you want no more. Instead, Hubzilla, like everything that Mike Macgirvin has made, has a counter for unnoticed actions. If you open it, you get a list of these actions that you haven't paid attention to yet. Click one, and you're taken to the thread where it happened (and only that thread is shown to you), and everything that was unread in this thread is flagged read.
In addition, has only one editor for everything, posts, comments (which are posts), DMs. So does Mastodon. So do all Twitter/ alternatives in the Fediverse.
But Facebook doesn't. It has a separate entry area for comments. So do blogs. And so forth. And so does Hubzilla. It has , and it has right at the bottom of each thread. It's geared towards having these two separate editors. Even using Friendica, which does have the Mastodon client API implemented, with a one-editor app has to be hackish.
All this continues with text formatting. Unlike the *keys and some Mastodon forks, Hubzilla doesn't use Markdown. It uses . This goes all the way to integration of OpenWebAuth magic single sign-on and .
Generally, image handling, including alt-text. On Mastodon and its forks, you attach your images to your posts as files, and then you get one dedicated entry field for alt-text for each image.
On Hubzilla, you first go to your and use it to upload the images you want to add to your post to the WebDAV-enabled file space built into your channel. You have to pay attention to setting the permissions both for the image files and for the subfolder correctly. Then you go to your post editor (not the comment editor which doesn't officially support inserting images) and select the image you want to embed. And then . (Notice how I've linked to a Hubzilla support forum instead of the WIP help rewrite because there still is no official documentation on how to add alt-text on Hubzilla.)
Any UI elements geared towards the Mastodon way of adding images to posts are useless on Hubzilla, and nothing on a UI for Mastodon can be used to add images to posts the Hubzilla way. Again, you need a Hubzilla-specific UI for this.
By default, and I guess it's actually recommended, posts and comments are composed in raw BBcode rather than WYSIWYG. The lack of a preview button in your average Mastodon app is actually a lesser issue, although it still is an issue.
Next, posting permissions. Mastodon has "Public", "Unlisted", "Followers only" and "Private". All apps are geared towards this.
Hubzilla, in contrast, has the . It offers you to post in public, to post only to yourself, to post to one of your (think Mastodon lists on piles of coke and 'roids), or to post to any individual custom selection of connections of yours. There's no "Followers only", there's no "Unlisted", and there's stuff that's completely unthinkable from a Mastodon POV.
Oh, and if you run your Hubzilla channel on bone-stock standard default settings, you post to a privacy group named "Friends" unless you explicitly choose otherwise. But you have to be able to choose otherwise in order not to only post to that privacy group. An app made for Mastodon won't give you the UI elements to do so.
In fact, an app geared towards the Twitter-style dichotomy of followers on the one side and followed on the other side will clash with Hubzilla because of just this. Again, Hubzilla is not like Twitter. It's like Facebook. It doesn't have one-sided following connections. It only has like Facebook friends.
This means that , but with a UI made for Mastodon, is next to impossible at worst and very, very limited and much less than optimal at best.
For example, let's suppose someone wants to connect to me. On Mastodon, I'd just simply confirm their follow request if I've chosen to do so. Then I may decide whether or not I follow them back.
Here on my Hubzilla channel, a connection request takes me to the . There I choose a for the new connection that defines which permissions that contact shall have. I add the connection to one or multiple privacy groups, of which I have a lot. I adjust the affinity slider. I may also assign to that connection. I may add lines to one of the two filter lists which I have per connection. Finally, I usually hide the new connection. And then I confirm it which not only grants the permissions in the contact role to the contact, but also establishes a bidirectional connection. It's like automatically following everyone back on Mastodon.
Apart maybe from the confirmation button, not even a single one of these features is available on any of the Twitter replacements in the Fediverse, and thus, not in any of the apps geared towards these either. If I were able to use Hubzilla with a Mastodon app, I'd still have to fire up a browser or a Web app or wait until I'm back home to confirm connection requests.
All this only covers your daily operation. I haven't even talked about yet, including the which defines the basics of Hubzilla's extensive permissions system.
There's exactly one app that works with Hubzilla. It's called , it's only available on F-Droid, it hasn't been updated in over five years, and it's actually a Web app that works like a specialised browser and embeds Hubzilla's Web UI.
A fully dedicated mobile app for Hubzilla that entirely relies on a native mobile UI would be so complex even for normal operation (disregarding the CMS bits) that it'd be more complex than K-9 Mail. If you want to go all the way, including (which controls Hubzilla's optional features, and which of these are available to you can differ from hub to hub) and CMS features and such, it'd be even more complex.
The only realistic way to have different frontends for Hubzilla would be the built-in theming feature. It doesn't mean different colours and button styles. A theme on Hubzilla can be an entirely different UI, but one that you can individually choose for each one of your channels. It's like being on Akkoma and being able to switch between Akkoma-FE, Phanpy and Mangane on your account at any given time.
That is, currently, Hubzilla has only got one built-in theme. It has become , and it even as a dark mode which is every bit as configurable as the light mode. More themes are being worked on in the community right now, but I wouldn't count on them coming with all stock Hubzilla installs, much less automatically added to all existing hubs.
So if you want an alternative UI for Hubzilla, you don't install it next to your hub, just like you install Phanpy next to Hollo or GoToSocial. You install it into your hub instead.
And the best way of developing alternative UIs for Hubzilla is not as fully separate external applications that try to latch onto Hubzilla from outside. It rather is as .
Hubzilla is modular and extendable with third-party repositories.
Lastly, both desktop and mobile use can profit from it because the best way to use Hubzilla on a phone is as a Progressive Web App.
, maybe this is interesting for you as well.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla It depends. Not everything works well frontless because not everything works well with a frontend made for Mastodon.
Hubzilla, for example, has a UI that's largely stuck in 2012. Also, it doesn't have the Mastodon client API implemented. But a frontend designed for Mastodon couldn't even cover 5% of Hubzilla's features. It would not grant access to features that are actually critical for operating a Hubzilla channel such as any parts of the permissions system.
And that's actually one of the reasons why Hubzilla doesn't have the Mastodon client API implemented: The only UI that can sufficiently harness Hubzilla's power is Hubzilla's own native Web UI.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #MastodonAPI #Hubzilla
so that those who need alt-text have as much information as possible.
Well, depending on where in the Fediverse you are, a whole lot can be possible.
I tend to make a whole lot of use of my possibilities. Hubzilla, where I am, doesn't have any character limits, at least none worth worrying about.
Sure, depending on your contacts, it makes sense to limit your alt-texts to no more than 1,500 characters because Mastodon, Misskey and their forks chop them off at this length if they're longer. Even Hubzilla itself can no longer fully display alt-texts of over a few thousand characters because they can't be scrolled. And alt-texts of such length are very uncomfortable for screen reader users because screen readers can't navigate alt-text.
But at least for my original images, I also give long image descriptions in the posts themselves in addition to the ones in the alt-texts. And with "long", I mean not "essay", but "short story". "Excessive" if you want.
My personal limit there is 100,000 characters for the whole post. As far as I know, Mastodon rejects longer posts than that entirely, and other Fediverse server apps have even lower limits, so describing my images actually becomes increasingly pointless. But 100,000 characters of description would take me three or four days to research for and write anyway.
Still, while my image posts remain within that limit, I regularly describe and explain my original images in tens of thousands of characters each. I see it as justified, given the very obscure but potentially curiosity-inducing topic. But others may say my long descriptions are way overkill, hardly anyone even reads them because it may pretty well take one hour to do so, and literally nobody actually needs them.
That's why I'm constantly wondering if I'm going overboard with details in my descriptions. Hence the question at the end of my first comment.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta
XRP/USDT
Entry price : - 2.48 - 2.43
Target 1: 2.55
Target 2: 2.62
Target 3: 2.70
Stop loss : 2.39
Leverage: 10x
Allocate only 1-3% of our deposit for each trade
Truth be told, as cool as Sharkey is with its load of features, its devs have a track record of bad decisions. Cuddling up with Mastodon and bringing Sharkey closer to it isn't even the worst one. Ask ().Maybe Iceshrimp is worth a look, too, for those used to Twitter. Of course, people who want to leave or have left something entirely different should be taken to something entirely different like Lemmy, Mbin or PieFed for Redditors and Friendica, Hubzilla and (streams) for Faceboook users.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Sharkey #Iceshrimp #Lemmy #Mbin #PieFed #Friendica #Hubzilla #Streams #(streams) Judging by the advice I've read so far, it's always best to describe the colour using basic colours plus attributes such as brightness, saturation and what other basic colour or colours the colour you describe is leaning towards.
For example, "light, yellowish orange", "a darker, slightly less saturated, slightly more brownish tone of orange", "various shades of slightly yellowish, medium-light-to-medium brown", "a solid, slightly pale medium blue with a minimal hint of green", "a medium-dark wood texture, slightly reddish, slightly greyish". All actually used by me in the long descriptions in (content warning: eye contact) .
If the name of the colour plays a role, use it and then describe the colour in the same way as above. Blind or visually-impaired people may not know what Prussian blue or Burgundy red looks like.
What do you say, is that appropriate, complete overkill or still insufficient
#Long #LongPost #CWLong #CWLongPost #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMetaTo my surprise, indexes instances of more Fediverse server apps than I thought.
What I've found so far, other than hundreds upon hundreds of Mastodon instances:
- three Pixelfed instances
- one instance each of Firefish, Sharkey and Catodon, indicating that it's compatible with at least the Forkeys
- two GoToSocial instances
- micro.blog
- Symfony Station's Payload newsletter which seems to be running their own proprietary code
- three Friendica nodes (!)
- the main development instance of Mitra (I'm not sure if that's the one used for testing nomadic identity via ActivityPub)
One could suppose that all these server applications have taken active steps to become more compatible with Mastodon, but I've got my doubts that standard support for any Mastodon API is sufficient, and that they all have gone beyond API support.
Some things that I've yet to see on the list for the first time:
- Misskey itself
- Iceshrimp, both JavaScript Iceshrimp and Iceshrimp.NET
- Pleroma and any of its forks
- any of Friendica's nomadic descendants (Hubzilla, (streams) and that one well-hidden Forte instance)
- anything from the Threadiverse (Lemmy, Mbin, PieFed...)
Still, their not only only seem to work on Mastodon, but it seems to be only possible to add Mastodon accounts and nothing else. It says a lot that is completely empty.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Pixelfed #Firefish #Sharkey #Catodon #GoToSocial #micro.blog #Friendica #Mitra #Misskey #Iceshrimp #Iceshrimp.NET #Pleroma #Akkoma #Hubzilla #Streams #(streams) #Forte #Threadiverse #Lemmy #Mbin #PieFed #FediDevs
we would just move on and let the forks pick up where he'd left off.
You don't even need Mastodon forks to stay in the Fediverse.
There's enough stuff in the Fediverse that can do the same things as Mastodon, that's fully connected to and federated with Mastodon, but that isn't Mastodon, that has never been Mastodon, that isn't affliliated with Mastodon, and that outshines Mastodon as well as its forks in many ways.
(Sent from .)
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
BB/USDT
Leverage: 20-75x
Entry Targets:
0.5220
0.5000
Take-Profit Target :
1)0.540
2)0.550
3)0.580
4)0.620
Stop-Loss 0.480
Here's some good advice: Don't use the quotation marks on your keyboard in alt-text! They may be mistaken for control characters. I've seen alt-text being cut off at the first quotation mark, for example. Or they may be rendered incorrectly otherwise.Use typographically correct quotation marks instead.
For English alt-text, that's and .
Windows: Alt+0147 and Alt+0148.
*nix: 3rd level+B and 3rd level+N.
For Spanish alt-text, that's and .
Windows: Alt+0171 and Alt+0187.
*nix: 3rd level+X and 3rd level+Z.
Alternatively, use the character map application of your operating system. Or copy-paste them from this comment.
If that's all too inconvenient, and you absolutely must use what's on the keyboard, use what amounts to single quotes: '.
#Long #LongPost #CWLong #CWLongPost #AltText #AltTextMeta #CWAltTextMeta #FediTips Loops is very far from finished. It's in a very early state, it has only got one instance, that instance is experimental, and it doesn't federate with anything else yet.
Just because has announced it, doesn't mean it's a fully-featured, rock-solid, daily-driver-material version 1.0 stable release. Welcome to the world of free and open-source software.
Also, as far as I've seen, many Pixelfed accounts seem to be set to private so you can't look at them from outside as a non-user and follow them by only clicking. You're probably asked to register an account because you have to be logged in with a Pixelfed account on that particular instance to be allowed to see these private accounts.
The only way to see what they post is by following them, by copying their ID or their account URL and pasting it into your search. And then you can see what they'll post from that point on.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Loops #Pixelfed 2008. When launched Identi.ca.
After all, Mastodon started out as an alternative frontend for GNU social. GNU social is a fork of StatusNet. StatusNet, in turn, was the software which Identi.ca used to run on until it was merged into GNU social in 2013. (Evan first launched Identi.ca, and then he open-sourced the technology under the name of Laconi.ca, later StatusNet.)
This also means that the OStatus protocol is part of Mastodon's history as well. OStatus is the protocol that GNU social was based on back in the day and probably still is, that later versions of StatusNet were based on, and that Mastodon was originally based on. It's the successor to OpenMicroBlogging, the protocol that Identi.ca was launched on, and that early StatusNet was based on. But it was gone when Mastodon was launched.
It's also fair to mention Friendica, the Facebook alternative launched by Mike Macgirvin in 2010, and Hubzilla, the "federated social content management system" which, in 2015, emerged from something that Mike himself had forked off Friendica in 2012.
Both speak a whole lot of protocols. Hubzilla used to speak OStatus, Friendica still does. And so, when the very first Mastodon test release came out in early 2016, and the very first Mastodon instance was started up, it was immediately able to connect to GNU social, Friendica and Hubzilla.
It's an important part of Mastodon's history that Mastodon has never in its history been an isolated walled garden, that Mastodon has never in its history been connected to only itself.
Speaking of Hubzilla, it should be mentioned once again, namely in 2017.
The very first Fediverse project to implement ActivityPub was Hubzilla in July. Mastodon followed in September. These two were the only Fediverse projects that adopted ActivityPub before it was declared a standard. And so, for quite a while, it was only these two that could use ActivityPub to connect to each other (while still also being able to do so via OStatus, by the way). But since both have vastly different philosophies, actual compatibility was and still is limited.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Identi.ca #StatusNet #OStatus #Mastodon #Friendica #Hubzilla #ActivityPub #FediverseHistory 2022 glaubte man noch, "das Metaverse" sei Horizons. Alias "Facebooks Metaverse", alias "Zuckerbergs Metaverse", alias "Meta Metaverse". Die virtuellen 3-D-Welten, die Mark Zuckerberg 2021 angekndigt hat, und zwar als "das Metaverse". Nur leider konnte er sich den Begriff wohl nicht exklusiv schtzen lassen.
2024 glaubt man, "das Metaverse" sei die Gesamtheit der bekannten Meta-Platforms-Produkte: Facebook, Instagram, WhatsApp, Threads. Horizons ist lngst wieder in Vergessenheit geraten. Man glaubt also, "das Metaverse" hat gar nichts mit 3-D-Welten zu tun.
Tatschlich ist "Metaverse" ein Begriff aus Neal Stephensons 1991er Cyberpunk-Roman Snow Crash: eine riesige virtuelle Welt, die vom damaligen Internet inspiriert war. Snow Crash hat brigens Philip Rosedale dazu inspiriert, Second Life zu bauen, das wiederum Ernest Cline dazu inspiriert hat, Ready Player One zu schreiben.
Aus IEEE-Kreisen gibt es tatschlich .
In Verbindung mit tatschlich existierenden virtuellen Welten wird "Metaverse" seit sptestens 2007 regulr verwendet, und zwar von der Community um , eine freie, quelloffene, serverseitige Reimplementation der Technologie von Second Life. Das kam Anfang 2007 raus, im Sommer startete das erste ffentliche Grid, , und enthlt schon den Claim, den das OSgrid heute noch verwendet: "The Open Source Metaverse".
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #VirtuelleWelten #Horizons #HorizonWorlds #OpenSim #OpenSimulator #OSgrid #Metaverse #MetaversumDer Standard ist eigentlich PascalCase: Erster Buchstabe von jedem Wort ist gro. CamelCase wre eher "camelCase", also erster Buchstabe des ersten Wortes klein, erster Buchstabe von allen anderen Wrtern gro. Aber das ist fr die, die zu faul sind, Grobuchstaben zu schreiben.
Am elegantesten sieht natrlich ein Hashtag aus mehreren Wrtern aus. Zumindest auf Hubzilla, (streams) und Forte kann man ihn mit Anfhrungszeichen generieren:
#"The Prodigy". In der Darstellung verschwinden dann die Anfhrungszeichen, und man sieht einen durchgngig linkenden Hashtag mit mehreren Wrtern. Eventuell geht das auch auf Friendica.Ich wei jetzt allerdings nicht, wie gut das in Screenreadern funktioniert. Vorlesen knnen sie das definitiv, aber das Risiko besteht, da sie einen Hashtag aus mehreren Wrtern nicht als Hashtag aus mehreren Wrtern erkennen und nur das erste Wort als Teil des Hashtags erkennen.
In der Mastodon-Suche spielt das brigens keine Rolle. Beim Indizieren von Hashtags schmeit Mastodon alle Zeichen raus, die auf Mastodon in Hashtags nicht funktionieren.
#TheProdigy, #The-Prodigy und #"The Prodigy" (das dann ja zu #The Prodigy wird) sind im Suchindex von Mastodon alle gleichermaen #TheProdigy.#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #ScreenReader #A11y #Accessibility #Barrierefreiheit #FediTips No, because I'd technically make them unfollow me, too.
, where I am (and which I'm commenting from right now, so it's very much part of the Fediverse and connected to Mastodon), is much more like Facebook and not at all like Twitter. It doesn't have that distinction between followers and followed. It only has mutual connections like Facebook friends.
So if I "unfollow" someone, read, disconnect from someone, I also renounce the permission I have given them to receive my posts. I don't remove myself from their follow list, but I don't send them any content anymore. It's like rejecting a previously confirmed follow request on Mastodon.
What I do instead is filter their reposts/boosts/renotes/repeats out, using a line of filter syntax.
verb == Announce into the blacklist for that particular contact (I've got per-connection filters), and there's silence. Over on , I even have a dedicated switch for that per contact.#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Boost #Boosts #Boosting #Hubzilla #Streams #(streams) #Filter #FediTips
I feel interested. I tried reading more about nomadic identity, but still couldnt really figure things out, and I didnt use Nomad-based platforms before. Techdoc is too technical to understand. Could you explain what nomadic identity would look like in practice
Maybe can answer your questions.
What possibilities would AP user have and how would it compare to existing solutions, like Mastodon's account migration
For end users, nomadic identity is currently only available on Hubzilla and (streams), using two versions of the Nomad protocol which has been geared towards and built around nomadic identity since its very beginnings in 2011. Nomadic identity via ActivityPub is still in closed, non-public testing.
Now, let's suppose the whole Fediverse had nomadic identity at its full extent.
Moving your identity using nomadic identity would go well beyond Mastodon's account migration:
- You could take all your toots and boosts with you. They won't be new copies, they will be the originals. Within threads, each one of your toot stays in place. It will only be re-attributed to your new identity. Whoever you've ever mentioned will not be notified about being mentioned again because you toots won't be re-uploaded.
- You could take your entire timelines with you.
- You could take all your followers and followed with you. On the other sides, your following entries of your followed and your followed entries of your followers would all automagically be changed from your old ID to your new ID without them having to do anything.
- You could take all your settings with you.
- You could take all your filters with you.
- You could take all your mutes and blocks with you.
- Your old account will be deleted without leaving a trace. But that's okay because you don't leave any dead links behind, because everything will be re-attributed to your new ID instead of recreated or copied and then deleted.
But that's only the very basics. And it's a side-effect of the real power of nomadic identity: You can have clones of your whole identity with everything that comes with it on other servers. Not dumb copies, but near-real-time, live, hot, bidirectional backups.
A fully nomadic Fediverse will see your identity as only one identity, no matter how many clones you have. That's because your clones have the same identity as your main instance.
You can use the main instance of your identity, and whatever happens there will almost immediately be sent to your clones. You can use any of your clones just as well, and whatever happens there will almost immediately be sent to your main instance and your other clones.
If the server with your main instance goes down, you still have your clones, and you can carry on. You lose nothing.
You can also make one of your clones your new main instance which will demote your previous main instance to a clone. This is useful if the server with your main instance has gone offline and will not come back. You can simply declare one of your clones your new main instance. This will change your ID because it will adopt the domain of the server with your new main instance on it, but all your contacts will be changed accordingly, even on their side.
That is, I'm not quite sure how well nomadic identity will work on stuff that isn't Hubzilla or (streams) or Forte, server applications where your identity is bound to and directly stored in your account.
It works so well on Hubzilla, (streams) and Forte because they don't do that. They don't put your identity, your connections, your content etc. directly into your account. They put it into a container which they call a . You can have as many of these channels on the same account as you want. And these channels are fairly easy to clone from server to server.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #Forte #NomadicIdentity
The Long Drive
It's funny. It is a drive that I have done plenty of times. Tomorrow I will do the usual twelve hour drive from Switzerland to around Alicante, and I will do so with minimal stops.
In essence the drive is easy. I take the motorway from Nyon all the way to Ondara, with a small segment on open roads around Grenoble. It's long, but easy.
There is a difficulty that I face. I always do this drive alone. Whilst it gives me the freedom to drive at my speed, stop when I want to and more, it also reminds me that I am still solitary. I always feel a little fragile before a trip, especially one like this.
If I was going to Barcelona it would be an easy eight hour drive, but to go towards Ondara is a twelve hour drive. That's twelve hours of podcasts, audio books and more. With a good audio book the drive is easy.
Some people would stop along the way, and I have considered it. I don't know where I would stop. If I stopped I could break the journey in two, but would that increase fatigue over two days
In reality this drive is a fun challenge. It's liberating to drive for twelve hours, and to listen to an audio book from cover to cover. it's fun to travel through three countries in a car like this. From the road to Grenoble in the dark to the sunrise near Valence to getting to see the Motorway after Marseille, to the wind and more as I head to the Spanish border, and then the congestion around Barcelona, before the quieter roads toward Valencia and beyond. The road is familiar, and it has memories.
It would be nice to do this trip as a person in a relationship, rather than solo. I was reading The Midnight Library and this is one of those situations. When I travel my subconscious feels the presence of the book of regrets, so rather than excitement I feel regret until I start to drive, and then I feel the adrenaline of the open road. It's the waiting for a trip that plays with us.
Yesterday I spoke to someone who said doing this trip solo would be boring. That's why podcasts and audio books are good.
I considered taking the bike but that adds a layer of complexity. This time is different. I have my climbing stuff with me. If an occasion to climb comes up then I can take that opportunity to do something a little different.
I think the problem is that I have too much time to think before a trip. If I had no time to think about the journey I'd be excited, and impatient. I should be excited and impatient. I will read most of Nexus, in theory. I finished Sapiens while eating lunch today.
Tomorrow I drive a familiar road that is one thousand two hundred kilometres long. In the US such a distance is ordinary. In Europe it's less ordinary.
#contemplation #drive #endurance #long #reading
AVA/USDT
Leverage: 20-75x
Entry Targets:
2.32
2.28
Take-Profit Target :
1)2.45
2)2.55
3)2.70
4)3.20
Stop-Loss: 2.00
TURBO/USDT
Leverage: 20-75x
Entry Targets:
0.01107
0.01000
Take-Profit Target :
1)0.01200
2)0.01300
3)0.01500
4)0.01800
Stop-Loss: 0.009400
MOODENG/USDT
Leverage: 20-75x
Entry Targets:
0.358
0.330
Take-Profit Target :
1)0.370
2)0.390
3)0.420
4)0.450
Stop-Loss: 0.300
MOODENG/USDT
Dolphins In Depth: Was signing Odell Beckham a mistake for Miami
XRP/USDT
Entry price : - 2.45 - 2.35
(SCALP)
Target 1: 2.50
Target 2: 2.60
Target 3: 2.70
(SWING TRADE)
Target 1: 2.75
Target 2: 3.20
Stop loss : 2.25
Leverage: 5x
Allocate only 1-3% of our deposit for each trade
Attention-Worthy Links for December 13th, 2024
-term -rays
Until the people behind FediDevs honestly try to fix it by adding compatibility with the rest of the Fediverse, I'll consider this an act of intentional discrimination against everything that isn't Mastodon and keeping the non-Mastodon server apps and their users out of everything they do.It isn't like the FediDevs people don't know that there is more to the Fediverse than Mastodon. They do know. At least some do. There is that did work with Mastodon and other Fediverse server apps. But it hasn't been used in nine months.
At the same time, the FediDevs website is clearly not built against any Mastodon API. If it was, then server apps that have the same API implemented would work with it. But the only non-Mastodon thing I've seen slip through is one watched Catodon instance. Catodon uses Iceshrimp's technology to mimic Mastodon, so I guess it happens to be close enough.
For the whole thing looks like built against Mastodon's inner workings without the use of any API. Why would someone build it like that Either it's cluelessness. It definitely wasn't cluelessness. At least someone had to have knowledge of a Fediverse outside of Mastodon see the Friendica group.
Or it's intentional malice. It's like someone is secretly waging war against everything in the Fediverse that is not Mastodon. That seems to be why the Friendica group was abandoned, namely in order to stop using and thus promoting something that isn't Mastodon.
And FediDevs looks like it was built the way it was built in order to make bloody sure it will always stay a Mastodon-exclusive thing by making it as incompatible with the rest of the Fediverse as possible, at least probably without as blatantly obvious means as rejecting user agents. The "Fedi" in the name is the cherry on top to a) drive the point home that the Fediverse is (or should be) only Mastodon and b) flip the bird at the non-Mastodon Fediverse.
The whole backend code seems to be built against Mastodon directly also to make it as difficult as possible to add compatibility with other Fediverse server applications because that would require the whole backend to be redesigned and rewritten from the ground up.
I'd really like the FediDevs staff to prove me wrong by actually opening their site to the non-Mastodon Fediverse.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #FediDevs
/USDT
ZONE: 28.80 - 28.22
LEVERAGE: Isolated 20x
Targets:
1) 29.02
2) 29.38
3) 29.66
4) 29.95
5) 30.24
6) 30.53
STOPLOSS: 27.48
it's not what most former Bluesky users would be looking for, exactly.
They're looking for a drop-in replacement of pre-Musk Twitter. For one, Misskey and the Forkeys are actually closer to pre-Musk Twitter in UX than Mastodon.
Besides, if you keep doing what has been done for almost three years now, railroad everyone to Mastodon without even telling them that there's more to the Fediverse than Mastodon in order to keep things simple, you'll end up with even more people who spend months or years in Mastodon-only bubbles. Who then get used to a Fediverse which allegedly is only Mastodon.
Who end up very irritated and defensive of their "Mastodon Fediverse" when an alleged "intruder" that's nothing like Mastodon shows up in their timeline.
And who try hard to force non-Mastodon users to abandon their own culture, only adopt Mastodon's culture, use whatever they're on exactly like Mastodon and stop using any features that Mastodon 3 didn't have because Mastodon's entire culture is defined by Mastodon 3's features.
Trust me, it really is that bad. I'm a Hubzilla user. I speak from personal experience.
CC:
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Misskey #Forkey #Forkeys #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse I think it'll stay incomplete.
FediDevs looks to me like it was built hard against only Mastodon. Not against any Mastodon API, but directly against Mastodon's inner workings. And intentionally so. The only thing I've seen that managed to work with FediDevs in at least one case is Catodon which mimics Mastodon itself.
FediDevs used to have its own Friendica discussion group. It was last used nine months ago.
I'd be pleasantly surprised if any of this changed. But right now, it looks to me like FediDevs has explicitly positioned itself against the non-Mastodon Fediverse now.
And still, they have the audacity to call it FediDevs.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #FediDevs
Audrey Hepburn with long hair!!
It definitely is. Whether Meta like it or not.Facebook may be "the Internet" for the entire Third World, but Meta need the European market. Desperately. And be it out of fear that the Facebook and Instagram killers may come out of Europe where people can no longer use "the real deal" after they were banned from the EU.
I dare say that Meta aren't a bunch of dumb jingoists who can barely grasp the idea of Europe having electricity. I'm pretty sure they know about the pile of social networks that were launched in Germany alone. I'm not even talking about Mastodon and Pleroma. I'm talking about StudiVZ/MeinVZ, Wer-kennt-wen and StayFriends, just to name the formerly biggest three. In fact, when Facebook was new, it had a hard time entering the German market because its entire potential target audience was on StudiVZ or MeinVZ and/or Wer-kennt-wen already.
So if Meta Platforms were banned from the EU market in its entirety, chances wouldn't be bad that someone whips up replacements.
And Meta know pretty well that this wouldn't even be necessary. There are already alternatives for everything the offer, even free, open-source, decentralised ones in all cases, and Meta know about at least some of them. They've known Friendica since at least 2012, for example. If Meta were forced to leave the EU, some of these alternatives would grow huge enough to have the chance to become serious competition to Meta outside the EU.
And so they're connecting Threads to the Fediverse just barely enough for the EU to shut up and leave them alone. I mean, why don't they go all-in instead if they're allegedly so eager to get their filthy hands on the Fediverse
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #MetaPlatforms #Facebook #Instagram #WhatsApp #Threads #Horizonworlds #Horizons #EU #EuropeanUnion
The people who wrote the Fediverse
There were no "people who wrote the Fediverse". These was no committee who laid down the standards.
The Fediverse was invented by . In 2008. By first creating a centralised Twitter alternative silo named Identi.ca.
And then open-sourcing the underlying technology as Laconi.ca, later StatusNet (merged into GNU social in 2013).
And then laying the protocol open as OpenMicroBlogging, later superseded by OStatus.
Then, in 2010, Mike Macgirvin decided that the world needs a free, open-source, decentralised, secure alternative to Facebook that's better than Facebook. And so he made Mistpark, today .
But the features he wanted Friendica to have were impossible to achieve with any existing protocol. OStatus wasn't even that good for microblogging, much less Mike's ambitious plans. Besides, he's an experienced protocol designer. So he created a whole new protocol, DFRN, and built Friendica on top of it. Friendica did adopt OStatus as an extra protocol, though, because Friendica's goal was and still is to federate with everything and then some.
In 2011, Mike had seen many public Friendica nodes shut down with or without warning and people always losing everything and having to start over from scratch. So he decided to do something against it.
He invented . And built a new protocol around it, Zot, because there was no way DFRN could take care of this, let alone OStatus.
In 2012, he forked Friendica into Red and rewrote the whole backend against Zot, which, however, required the creation of yet another identity scheme.
For one, one login could now have multiple fully separate and independent identities on it. For example, my Hubzilla channel URL is .
Besides, one identity could now reside on multiple server instances which is what nomadic identity means.
Red was later renamed Red Matrix and, in 2015, refactored, redesigned and renamed into .
Mastodon and Pleroma started in 2016 as OStatus-based alternative UIs for GNU social. Mastodon was the first to be turned into a stand-alone project with not much interest in connecting to anything outside, all in spite of already being federated with Pleroma, GNU social, Friendica and Hubzilla via OStatus.
ActivityPub came out in 2017. No, not 2018. It was standardised in 2018. But it came out in 2017.
In July, 2017, Hubzilla was the first Fediverse project to integrate ActivityPub. Next to its own Zot, next to diaspora*, next to OStatus etc. On the one hand, Hubzilla tried to stay as close to the ActivityPub spec as possible and feasible. On the other hand, Hubzilla had to make its ActivityPub integration, which has always been an optional add-on, compatible to its own technology, to its own Zot protocol, to the way it works.
In September, Mastodon was the second Fediverse project to adopt ActivityPub. But Mastodon was more interested in doing its own thing and being as close to Twitter as it could than in sticking to a protocol spec, much less connecting to non-Mastodon stuff such as Hubzilla with which it already shared two protocols now.
Mastodon was the one that added Webfinger. ActivityPub doesn't even require Webfinger. The ActivityPub spec doesn't contain Webfinger. But Mastodon requires Webfinger. It can't live without Webfinger. So everything that wants to properly federate with Mastodon needs to implement Webfinger.
After ActivityPub had become a standard, more projects adopted it. But as lax a specification as ActivityPub is, it allowed for a lot of liberties.
Some devs looked at how Mastodon had integrated ActivityPub, decided it was rubbish and did it their own way.
Some devs looked at how Mastodon had integrated ActivityPub, decided they couldn't do it the same way because what they did was too different from Mastodon and did it their own way.
Some devs didn't look at what anyone else did and did it their own way.
Probably none of them looked at how Hubzilla had integrated ActivityPub because none of them even knew that Hubzilla existed. Except for those who were maintaining Friendica now. And Friendica had to make it compatible with DFRN and with the way it had been working since 2010.
Fast-forward to 2023. Mike's current piece of work was which contains an intentionally nameless fork of a fork of three forks of a fork (of a fork) of Hubzilla, slimmed down from Hubzilla, but modernised and technologically even more advanced.
It was then that , creator and maintainer of , got into contact with him because he wanted to add nomadic identity to Mitra. Something that's built on ActivityPub and only supports ActivityPub. A first. No-one had ever done nomadic identity with nothing but ActivityPub before.
So the two started working on how to implement nomadic identity using only ActivityPub. Mike had a vision of a Fediverse with nomadic identity all over and Fediverse identities cloned beyond server application borders. Like, a (streams) channel cloned to Mitra, Mastodon, PeerTube and Mobilizon, all with the same identity.
This, however, required another, brand-new way of identifying Fediverse actors. And so was created.
We're probably in the middle of xkcd 927 now.
Mike set up an experimental branch of (streams) to develop and test nomadic identity via ActivityPub, also since (streams) already had nomadic identity anyway.
Around summer, the "nomadic" branch (for nomadic identity via ActivityPub) seemed reliable enough to merge it into "dev". And in July, "dev" was merged into "release", complete with nomadic-identity-via-ActivityPub code.
It was shortly after that merge that I created my two (streams) channels. The channel URL of my channel for Fediverse memes is . But its DID, which all channels created on accounts registered after that merge got, is . And that's only two IDs of the same channel. There are also others for (streams)' native Nomad protocol, Hubzilla's Zot6 protocol, ActivityPub, OAuth, OAuth2 and probably also OpenWebAuth magic single sign-on, another one of Mike's creations. Not to mention that (streams) channels, like Hubzilla channels and Friendica accounts, can also optionally be group actors.
In fact, this blew up into (streams) users' faces because (streams) confused the various IDs to such degrees that it wouldn't federate at all anymore. It took Mike a whole lot of work to iron this out again, so much that he officially retired from Fediverse development on August 31st.
And in the middle of this, he even created yet another fork, Forte, which is (streams) minus Nomad, minus Zot6, based on and supporting only ActivityPub. My guess is still that one of the reasons to create Forte at that point was to get rid of the Nomad and Zot6 IDs to sort the ID mess out.
Even if nomadic identity via ActivityPub should ever become stable and start spreading, I don't expect DIDs to become the one norm in the Fediverse. Not with all those barely or unmaintained projects and those devs who refuse to acknowledge that devs of other projects do great stuff, too.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #OStatus #DFRN #Zot #ActivityPub #Nomad #Laconi.ca #Identi.ca #StatusNet #GNUsocial #Friendica #Hubzilla #Mastodon #Pleroma #Streams #(streams) #Forte #FEPef61
Ich mags, dass das alles existiert.
Das ist schon mal positiv. Es gibt Leute, die sich so an ein reines Mastodon-Fediverse gewhnt haben, da sie alles, was anders ist, als strende Eindringlinge empfinden und wieder weg haben wollen.
Ich hab nur gar nicht so viel Sehnsucht nach Ersatzdiensten fr Facebook, Insta, Wasweissich. Entgeht mir da was
Na ja, auf eine Art schon. Was nicht Mastodon ist, ist ja auch nicht Mastodon mit einer anderen Oberflche. Das kann schon ziemlich anders sein.
Zunchst mal sind so Features wie Textformatierung, Zitate oder Drkos/Drukos und sehr viel hhere oder gar keine Zeichenlimits auerhalb von Mastodon gang und gbe. So manch jemand, der bis dahin das Fediverse als reines Vanilla-Mastodon-Netzwerk ansah, kriegt ja einen Riesenschreck, wenn das erste Mal ein Beitrag mit deutlich ber 500 Zeichen auftaucht. Oder mit einem Zitat. Oder mit einer Stichpunkteliste. Oder mit Kursivschrift, aber es ist keine Unicode-Trickserei.
Schon im Microblogging-Bereich gibt's einiges, das ziemlich anders ist als Mastodon. ist ja auf einer der letzten verbliebenen Instanzen von Calckey. Das ist ein Fork des japanischen Misskey, der eigentlich letztes Jahr durch Firefish ersetzt wurde. Misskey hat schon 3000 Zeichen, die wie auf Mastodon hartgecodet sind. Bei den diversen Forkeys (Calckey/Firefish, Sharkey, CherryPick, Iceshrimp, Catodon usw. usf.) liegen die Limits mindestens auf dem Niveau, wenn nicht hher, sind aber durch den Admin konfigurierbar.
Interessanterweise sind Misskey und die Forkeys (wobei Iceshrimp allmhlich kein Fork mehr ist) in der Handhabung trotzdem, und obwohl sie auch noch Features wie Textformatierung mittels einer erweiterten Variante von Markdown und eine sehr konfigurierbare Oberflche haben, dichter an Pr-Musk-Twitter, als es Mastodon ist. Eine Mehrspaltenansicht la TweetDeck haben Mastodon und die *keys, aber vor allem bei denjenigen Forkeys, die gegenber Misskey noch Extrafeatures haben, kannst du damit mehr anstellen.
Die richtig groen Keulen sind dann die von Mike Macgirvin ber gute 14 Jahre auf den Weg gebrachten (mehr oder weniger) Facebook-Alternativen. Friendica existiert schon seit 2010 und hatte von Anfang an schon eine sagenhafte Feature-Palette. Whrend Mastodon versucht, Twitter nachzuffen, hat Friendica nie versucht, Facebook nachzuffen, sondern eher, besser als Facebook zu sein.
So gibt's da beispielsweise auch alles, was man zum Bloggen bruchte. Zeichenlimits gibt's nicht, gab's nie. Dafr gibt's die volle Palette an Textformatierung per erweitertem BBcode. Es gibt einen eingebauten Filespace, wo man z. B. Bilder hochladen und dann beliebig viele davon in Posts einbetten kann, also mit Text darber und Text darunter, statt wie auf Mastodon nur vier davon als Dateien anhngen zu knnen.
Man kann Friendica-Konten auch als moderierte Diskussionsgruppen verwenden, hnlich wie Gruppen auf Facebook. Die Erfahrung hat gezeigt, da Friendica-Gruppen mit groen Teilen des Fediverse kompatibel sind bis hin zu Mastodon, nur da es besonders fr Mastodon-Nutzer nicht ganz straight-forward ist, einen Thread zu starten.
Friendicas eigentliches Killerfeature war aber immer, da es stets versucht hat, sich mit allen mglichen Sachen zu verbinden. Es sollte so eine Art Kommunikationszentrale sein. Friendica kann sich mit diaspora* verbinden, es kann sich ber OStatus mit den Sachen verbinden, die es noch haben, man kann zu WordPress und kompatiblen Blogs crossposten, man kann RSS- und Atom-Feeds abonnieren, und man kann auch per E-Mail oder XMPP kommunizieren.
Man kann auch ein Tumblr- oder Bluesky-Konto ins Friendica-Konto einbinden und sich dann damit bidirektional verbinden, ganz ohne Bridge. Theoretisch ginge das sogar mit , wenn der Node-Betreiber ein Multimillionr wre, der sich die API-Lizenz leisten kann. Und ab 2012 ging es kurzzeitig sogar mit Facebook, bis Facebook das unterbunden hat.
ber Friendica gbe es noch einiges mehr zu erzhlen, was da geht. So manch einer sieht es als das Schweizer Taschenmesser des Fediverse.
Aber wenn Friendica das Schweizermesser ist, dann ist Hubzilla das Leatherman. Hubzilla ist nmlich noch heftiger. Es wird bezeichnet als "dezentrales soziales Content Management System" und vereinigt entsprechend viele Funktionalitten unter einem Dach.
Hubzilla fing ja 2012 an als ein Friendica-Fork namens Red, dann Red Matrix, und war zunchst einmal nicht viel mehr als Friendica mit , und einem ziemlich mchtigen und detaillierten Berechtigungssystem. 2015 wurde es dann in Hubzilla umbenannt und entsprechend featuremig zur eierlegenden Wollmilchsau aufgebohrt.
Man knnte Hubzilla jetzt fr alles Mgliche und Unmgliche nehmen. Beispielsweise habe ich auf diesem Kanal und . Und ist selbst Teil eines Hubzilla-Kanals.
Der Pepe (Hubzilla) hat Hubzilla sehr gut und sehr detailreich in seiner erklrt.
Danach folgte von 2018 bis 2021 eine ganze Reihe von Forks, bei denen Zusatzfeatures und Verbindungsmglichkeiten wieder abgespeckt wurden, die aber allmhlich technisch und in der Handhabung immer weiter aufgefrischt und modernisiert wurden.
Im Oktober 2021 kam dann etwas, was eine ganze Zeitlang als stabil angesehen wurde, was aber auch ziemlich ungewhnlich ist. Es hat nmlich offiziell, mit voller Absicht und aus guten Grnden keinen Namen, keine Markenidentitt, (fast) keine Nodeinfo, und es wurde ebenso mit voller Absicht in die Public Domain gestellt, whrend Mike sonst alles unter die MIT-Lizenz gestellt hat.
Das Code-Repository brauchte aber zwingend einen Namen. Mike hat es Streams genannt, und so wird auch die Anwendung nicht ganz offiziell (streams) genannt, inklusive der Klammern.
Krzlich hat Mike die Readme-Datei aktualisiert, .
Okay, seit Osada und Zap von 2018 hat die Familie keine Artikel mehr, keine Karten, keine Wikis, keine Webpages, der Kalender ist vereinfacht worden usw. Das ganze Zeug gab es ja eh schon auf Hubzilla, und Mike wollte wieder zurck zu reinem Social Networking.
Dafr hat er aber die Handhabung vereinfacht, verschlankt und der Realitt angepat, vor allem auch der Realitt eines Fediverse, das mehr und mehr von ActivityPub dominiert wurde. Deswegen hat (streams) eine bessere ActivityPub-Integration als Hubzilla. Auf beiden ist ActivityPub optional, aber auf (streams) ist es in den Kern eingegossen, und (streams) kann es sich im Gegensatz zu Hubzilla erlauben, ActivityPub standardmig in neuen Kanlen zu aktivieren.
Ganz besonders die Berechtigungssteuerung ist vereinfacht und entschlackt und ermglicht eine direktere Kontrolle darber, welcher Kontakt was darf. Gleichzeitig ist (streams) aber auch sicherer, weil es nicht mehr mglich ist, den ganzen Kanal auf ffentlich zu schalten.
(streams) wird heute noch von Mike mehr oder weniger weiterentwickelt. Aber mit Forte hat er seit August noch ein weiteres Eisen im Feuer. Forte ist im Prinzip (streams), aber es untersttzt nur noch ActivityPub. Das heit auch, da auf Forte nomadische Identitt rein ber ActivityPub abgewickelt wird und nicht mehr ber ein eigens dafr entwickeltes Protokoll. Deswegen ist Forte noch nicht ffentlich, ebenso wie brigens die Entwicklerversion des Microblogging-Projekts Mitra, in der auch nomadische Identitt eingebaut wird.
Aller Komplexitt zum Trotze kann man, wenn man will, alle vier natrlich auch zum Microbloggen nehmen.
Darber hinaus gibt's im Fediverse noch in andere Richtungen spezialisierte Sachen, die also nichts mit Microblogging oder Social Networking zu tun haben.
Mit Lemmy, dem dahinsiechenden /kbin, Mbin, PieFed und dem in Entwicklung befindlichen Sublinks gibt es etwa eine ganze Anzahl an Alternativen zu Reddit oder auch Hacker News.
Mit WriteFreely und Plume gibt's zwei spezialisierte Blogginganwendungen im Stil von Medium. Plume ist von den Features her eigentlich besser, wird aber im Moment nicht weiterentwickelt. Auerdem sind inzwischen viele WordPress-Blogs ans Fediverse angebunden.
PeerTube prsentiert sich als Alternative zu YouTube mit einer Prise Peer-to-Peer zwischen den Instanzen, inklusive Livestreaming. Rein auf Livestreaming la Twitch spezialisiert ist Owncast. Ganz neu ist Loops als TikTok-Ersatz vom Macher unter anderem von Pixelfed und der FediDB, das fderiert aber noch nicht.
Im Audiobereich gibt's Funkwhale, wo man im Prinzip alles hochladen kann, aber nur lizenzmig freie Sachen ffentlich machen sollte, das noch recht junge Bandwagon als Bandcamp-Alternative und Castopod speziell fr Podcasts wie z. B. das auch von gefeaturete .
Es gibt noch einiges mehr, z. B. Mobilizon fr kooperative Eventplanung, BookWyrm als GoodReads-Ersatz oder, auch noch recht neu, Flohmarkt, das ziemlich genau das ist, wonach es sich anhrt.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Misskey #Forkey #Forkeys #Calckey #Firefish #Sharkey #CherryPick #Iceshrimp #Catodon #Friendica #Hubzilla #Streams #(streams) #Forte #Lemmy #/kbin #Mbin #PieFed #Sublinks #WriteFreely #Plume #WordPress #PeerTube #Owncast #Loops #Funkwhale #Bandwagon #Castopod #Mobilizon #BookWyrm #Flohmarkt #FediTips FediDevs als Ganzes scheint komplett hart gegen Mastodon, nur Mastodon und nichts als Mastodon gebaut zu sein. Oder was auch immer gengend proprietren Mastodon-Kram eingebaut und sich an Mastodon angepat hat, um kompatibel zu sein.
Beispiel 1: Guckt euch mal unter den die Liste der getrackten Instanzen an. Wieviele Nicht-Mastodon-Instanzen sind da, auer einer einzigen Catodon-Instanz (Catodon soll eine Art Mastodon mit einem Rest Iceshrimp-Backend darunter werden, soweit ich das verstanden habe.)
FEDIDevs impliziert doch, fr Entwickler aus dem ganzen Fediverse zu sein. Es schliet aber fast alles aus, was nicht Mastodon ist, und somit auch die Entwickler vieler Serveranwendungen, die nicht Mastodon sind. Die knnen gar nicht teilnehmen, weil das Backend von FediDevs vermutlich nicht mal gegen eine Mastodon-API gebaut ist, sondern direkt gegen Mastodon-Code.
Beispiel 2: ein Starterpack namens "".
Der ist komplett leer. Da ist genau berhaupt nichts drin.
Warum Weil es ganz augenscheinlich technisch vollkommen unmglich ist, irgendwas da einzutragen, was nicht auf Mastodon ist.
Wer auch immer hinter dem Bau von FediDevs steckt, scheint entweder anzunehmen, da das Fediverse nur aus Mastodon besteht. Oder es war einfacher, FediDevs nur gegen Mastodon zu bauen, statt
Ganz offenkundig wei bei FediDevs eine Hand nicht, was die andere tut. Auf der einen Seite gibt's ein Webportal, das nur mit Mastodon funktioniert. Auf der anderen Seite gibt's mit eine Friendica-Gruppe aus denselben Kreisen, wobei die seit einem Dreivierteljahr nicht mehr genutzt wird.
Das, oder dahinter steckt der Vorsatz, das Fediverse (wieder) zu nur Mastodon zu machen, indem alles Mgliche und Unmgliche, was an "Fediverse"-Diensten und -Zusatzfeatures entwickelt und beworben wird, mit voller Absicht gleichzeitig "Fedi" im Namen hat und nur gegen Mastodon gebaut wird.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #NichtNurMastodon #FediDevs
Internazionale by Internazionale
Breve guida alla lunga guerra in Siria
Con la caduta di Assad si conclude larco delle rivolte della primavera araba che hanno ridisegnato la regione. Leggi
Translated:
Short Guide to the Long War in Syria
With the fall of Assad, the arc of the Arab Spring uprisings that have redrawn the region concludes.
Nicht nur knnte ich ohne groe Schwierigkeiten mit meiner kompletten Identitt und allem, was dazugehrt, umziehen. Sondern ich kann sie auch ber mehrere Serverinstanzen klonen. So liegt sie nicht in einer, sondern aktuell in zwei Hnden. Geht eine Instanz mal offline, oder ist sie gestrt, habe ich einen identischen Klon meines Kanals woanders, und zwar mit allem Content, mit allen Kontakten, mit allen Dateien, mit allen Einstellungen, mit allem Drum und Dran.
Und im brigen kann sich im Fediverse jeder aussuchen,
- in wessen Hand er seine Daten gibt, denn nicht alles im Fediverse ist in derselben Hand
- was er da an Features hat, denn nicht alles im Fediverse ist Mastodon
Wer die technischen Fhigkeiten und Mglichkeiten hat, kann ersteres sogar umschiffen, indem er seine eigene Privatinstanz von was auch immer betreibt, vielleicht gar auf einer Maschine im eigenen Eigentum in den eigenen vier Wnden.
Aber generell habe ich schon genug Erfahrung mit dezentralen Systemen (XMPP, Matrix, OpenSimulator, das Fediverse auch schon seit Anfang der 2010er), da ich sagen kann: So etwas wird sich nie 100% wie ein zentralistisches, kommerzielles Silo anfhlen und auch nie so funktionieren. Und wem das nicht pat, der ist da eben falsch.
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #NomadischeIdentitt
Ich glaube, dass man schon mal viel gewinnen wrde, wenn man *mit* seinen Beitrgen auf Servern umziehen kann (nimmt Bedenken, sich vielleicht den "falschen" Server auszusuchen)
Dafr mte Mastodon erst nomadische Identitt einfhren. Dann ginge das ziemlich problemlos. Hubzilla hat das seit Anbeginn, seit 2012. Aber rein ber ActivityPub ist das noch extrem experimentell.
und wenn *alle* Server untereinander bekannt wren und die Suche nach Hashtags & Co eben ber wirklich *alle* Server (minus den Geblockten) gehen wrde und nicht nur denen, die irgendwann mal irgendwie Bekanntschaft geschlossen haben.
Hufig gestellte Forderung. Aber technisch unrealistisch.
Nehmen wir mal an, ich setze meine eigene (streams)-Instanz auf. Alles konfiguriert, alles startklar. Ich gebe
#systemctl start httpd ein, und der Webserver erwacht zum allerersten Mal.In diesem Sekundenbruchteil mten alle zigtausend Fediverse-Instanzen sofort von der Existenz meiner (streams)-Instanz wissen. Instantan. Auf der Stelle. (Du hast "wirklich *alle* Server" geschrieben. Also ohne jegliche Ausnahme.)
Das wre nur auf drei Arten und Weisen vorstellbar.
Erstens: Alle zigtausend Fediverse-Instanzen wissen vorher, da ich vorhabe, diese (streams)-Instanz aufzusetzen. Vorstellbar, aber vollkommen unrealistisch.
Zweitens: Meine (streams)-Instanz kennt alle, aber auch wirklich absolut ausnahmslos alle anderen Fediverse-Instanzen, die zu dem Augenblick existieren, wo der Webserver anspringt. Und zwar ohne dezentrale Hilfsmittel.
Das heit: Der Quellcode im streams-Repository enthlt eine nanosekundenaktuelle Liste aller Fediverse-Instanzen. Die Liste wird beim Klonen des Quellcode auf den Webserver mit runtergeladen. Beim ersten Start macht die (streams)-Instanz als allerallererstes einen
git pull, holt sich die nanosekundenaktuelle Liste aller Fediverse-Instanzen und meldet seine Existenz sofort an alle Instanzen auf der Liste.So eine Liste mu dann im Quellcode von absolut ausnahmslos jeder Fediverse-Serveranwendung eingebaut sein. Auch wenn jemand gerade erst mit einer ganz neuen Fediverse-Serveranwendung anfngt, mu da sofort diese Liste in vollem Umfang rein.
Und natrlich mu sie aktuell gehalten werden. Das heit, jede startende neue Instanz mu sich selbst in die Listen in den Quellcodes aller Anwendungen eintragen.
Meine (streams)-Instanz mte also alle Fediverse-Serveranwendungen kennen, die es berhaupt gibt. Auch wenn ein Fediverse-Entwickler erst eine halbe Sekunde vorher den allerersten git commit einer ganz neuen Fediverse-Serveranwendung gemacht hat.
Das heit auerdem: Meine (streams)-Instanz mte unmittelbar nach dem Start die Quellcodes von weit ber 100 Fediverse-Serveranwendungen
git clonen, also herunterladen. Und zwar jeweils alle Branches und alle Forks. Dann die eigene Adresse eintragen, auch wieder in alle Branches. Dann mte sie die nderungen an allen ber 100 Fediverse-Anwendungen als Pull Request git committen. Und jeweils wieder alle Branches und alle Forks. Auch die, die lange nicht maintaint worden sind. Man wei ja nie.Jetzt kommt's: Die nderungen mssen ja auch noch gemerget werden. Dafr mte mein (streams)-Instanz sich auf hunderten Git-Repositories volle Maintainer-Rechte verschaffen und die eigenen Commits mergen. Und zwar auch, ja, gerade in Produktivcode.
Ich sage ja nicht, da das potentiell unsicher ist.
Auerdem mu das schnell gehen. Hunderte Repositories klonen, ndern, committen, reinhacken und mergen, alles innerhalb eines Nichtsigstels einer Sekunde, damit die experimentelle Iceshrimp.NET-lnstanz, die jemand eine Zehntelsekunde spter startet, auch von meiner eigenen (streams)-Instanz wei und ihre eigene Instanz meiner (streams)-Instanz mitteilen kann.
Noch einmal: Du hast "wirklich *alle* Server" gesagt. Das heit, eine neue Iceshrimp.NET-Instanz mu zwingend und sofort eine neue (streams)-Instanz kennen, die eine Zehntelsekunde frher gestartet ist.
Ach ja, das ganze Theater ist auch vollumfnglich ntig, wann immer
- eine Instanz heruntergefahren wird
- eine Instanz sich umbenennt
- ein Hubzilla-Hub oder eine (streams)-Instanz ActivityPub deaktiviert oder wieder aktiviert, denn was interessiert eine Mastodon-Instanz ein Hubzilla-Hub, mit dem sie eh nicht interagieren kann
Jeder Entwickler wird mir besttigen, da das nicht nur komplett unrealistisch ist, sondern absolut haarstrubend. Alleine schon, weil 99,9% der Commits in den meisten Repositories von Fediverse-Instanzen kommen werden und alle Commits, die hndisch von Entwicklern kommen, darunter ersaufen. Und weil kein Entwickler seine eigenen Sachen so schnell rebasen kann, wie neue Commits mit nderungen an der Instanzenliste reinkommen.
Okay, also bleibt als dritte und einzige noch mgliche Lsung eine zentral verwaltete Liste auf einem zentralen Webserver.
Dieser Server mu verpflichtend in alle Fediverse-Serveranwendungen eingebaut sein. Auch die, die eigentlich gar nicht mehr gewartet werden, aber noch laufende Instanzen haben (Calckey, Plume usw.).
Damit wrde sich das ganze Fediverse bis in den allerhinterletzten Winkel absolut und total abhngig von zentraler Infrastruktur machen.
Warum das schlecht ist Stell dir mal vor, diese Liste geht offline aus irgendeinem Grunde. Oder irgendeiner, z. B. Elon Musk oder Jeff Bezos oder Mark Zuckerberg, kauft den Webserver mit der Liste drauf. Der htte dann die totale Kontrolle ber das Fediverse.
Willst du das
#Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #git
Last updated: 2024-12-18
All text and images © eLoc8.is-fabulous.com