home.social

#ostatus — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ostatus, aggregated by home.social.

  1. Das #Fediverse ist (zumindest an ein paar Stellen) in der Mitte der Gesellschaft angekommen. Das ist stark und sicher mehr als mensch hoffen konnte als @evan damals 2008 #identica und #StatusNet gegründet und geschrieben hat.
    Andererseits: Es ist auch eine Entwicklung von jetzt 17 Jahren, die zeigt, wie lange solche Projekte auch "im digitalen Zeitalter" brauchen. #ostatus #activitypub

    en.wikipedia.org/wiki/Identi.ca

  2. Das #Fediverse ist (zumindest an ein paar Stellen) in der Mitte der Gesellschaft angekommen. Das ist stark und sicher mehr als mensch hoffen konnte als @evan damals 2008 #identica und #StatusNet gegründet und geschrieben hat.
    Andererseits: Es ist auch eine Entwicklung von jetzt 17 Jahren, die zeigt, wie lange solche Projekte auch "im digitalen Zeitalter" brauchen. #ostatus #activitypub

    en.wikipedia.org/wiki/Identi.ca

  3. Das #Fediverse ist (zumindest an ein paar Stellen) in der Mitte der Gesellschaft angekommen. Das ist stark und sicher mehr als mensch hoffen konnte als @evan damals 2008 #identica und #StatusNet gegründet und geschrieben hat.
    Andererseits: Es ist auch eine Entwicklung von jetzt 17 Jahren, die zeigt, wie lange solche Projekte auch "im digitalen Zeitalter" brauchen. #ostatus #activitypub

    en.wikipedia.org/wiki/Identi.ca

  4. Das #Fediverse ist (zumindest an ein paar Stellen) in der Mitte der Gesellschaft angekommen. Das ist stark und sicher mehr als mensch hoffen konnte als @evan damals 2008 #identica und #StatusNet gegründet und geschrieben hat.
    Andererseits: Es ist auch eine Entwicklung von jetzt 17 Jahren, die zeigt, wie lange solche Projekte auch "im digitalen Zeitalter" brauchen. #ostatus #activitypub

    en.wikipedia.org/wiki/Identi.ca

  5. Das #Fediverse ist (zumindest an ein paar Stellen) in der Mitte der Gesellschaft angekommen. Das ist stark und sicher mehr als mensch hoffen konnte als @evan damals 2008 #identica und #StatusNet gegründet und geschrieben hat.
    Andererseits: Es ist auch eine Entwicklung von jetzt 17 Jahren, die zeigt, wie lange solche Projekte auch "im digitalen Zeitalter" brauchen. #ostatus #activitypub

    en.wikipedia.org/wiki/Identi.ca

  6. Fediverse-Protokolle

    Um sich miteinander austauschen zu können, müssen sich Instanzen im #Fediverse untereinander verstehen können. Dazu dient ein standardisiertes #Kommunikationsprotokoll für den Austausch von Daten zwischen Computern bzw. Prozessen (hier also den einzelnen Instanzen bzw. Servern), die in einem Rechnernetz (hier im Allgemeinen das #Internet) miteinander verbunden sind (verteiltes bzw. föderiertes System).

    Anno 2024 kommt hierzu gern und häufig das #Protokoll #ActivityPub zum Einsatz.

    Allerdings war das in der Anfangszeit des Fediversums noch nicht so. Die #OpenMicroBlogging-Spezifikation wurde im Jahr 2008 veröffentlicht und dann ab 2010 als #OStatus weitergeführt. Auch ActivityPub hieß zunächst einmal #ActivityPump. Im Januar 2018 gab das #W3C (World Wide Web Consortium) den ActivityPub-Standard frei und empfiehlt ihn seither für dezentrales Teilen von Inhalten.

    Historisch wäre auch noch #Diaspora zu erwähnen. Die Fediverse-Plattform #Friendica spricht übrigens mehrere Protokolle.

    Bleiben wir bei ActivityPub: Das Protokoll spezifiziert sowohl Server-zu-Server- als auch Client-zu-Server-Kommunikation. Hierbei ist zu beachten, daß sich die Instanzen im #Fediverse via Server-zu-Server-Kommunikation unterhalten. Mit einem Client oder einer App auf ein Konto auf einer #Instanz zuzugreifen, wäre ein Anwendungsfall für die Client-zu-Server-Kommunikation. Hier setzt aber zum Beispiel die #Fediverse-Plattform #Mastodon auf eine eigene Implementierung, die #Mastodon-#Client-#API, die zum Teil auch von anderen Plattformen zumindest teilweise unterstützt wird.

    Da es sich bei ActivityPub um einen offenen Standard handelt, kann jeder Mensch oder jede Organisation eigene #Software implementieren, um am #Fediverse teilzunehmen. Die Instanz mastodonium.de läuft etwa auf #Mammuthus, einer eigenen Implementation des Autors dieser Zeilen.

    Zum weiteren Schmökern sei auf folgende #Wikipedia-Artikel hingewiesen:
    https://de.wikipedia.org/wiki/OStatus
    https://de.wikipedia.org/wiki/ActivityPub
    https://de.wikipedia.org/wiki/Netzwerkprotokoll
    https://de.wikipedia.org/wiki/World_Wide_Web_Consortium
    https://de.wikipedia.org/wiki/Diaspora_(Software)

  7. @cy
    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 @Evan Prodromou. 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 Friendica.

    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 nomadic identity. 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 https://hub.netzgemeinde.eu/channel/jupiter_rowland.

    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 Hubzilla.

    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 the streams repository 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 @silverpill, creator and maintainer of Mitra, 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 FEP-ef61 "Portable Objects" 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 https://streams.elsmussols.net/channel/fedimemes_on_streams. But its DID, which all channels created on accounts registered after that merge got, is https://streams.elsmussols.net/.well-known/apgateway/did:⁠key:z6Mkf2dhUa65zBYCNVqs3AHyt8uPixauZ7bPzEJn15LJANsd/actor. 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 #FEP_ef61
  8. That's right folks! Stripey Sums it up below.

    #Fediverse is often misconstrued as that network in the #DeSoc space powered by #ActivityPub exclusively - NOPE!

    In fact, even mastobruhs would be wise to note that Eugen's original creation was an #OStatus networked product until quite recently in Fediverse evolution years.

    Still, there's a lot of otherwise respected tech personalities that continue to insist and spread disinformation to the contrary. Shame on them - someone, everyone, needs to edjumacate those individuals spreading FUD and confusion to the next generation of n00bs arriving in this free and thriving world of privacy respecting, horizontally scaling, #FOSS based social communication systems.

    Apparently, what I've quoted below was part of a larger, longer conversation, yet I'm confident that just what #Stripey points out below in correcting someone else's erroneous assumptions more than correctly describes Fediverse and puts an end to any misunderstanding for all sentient #Fedizens 🤘🤠🤘

    #tallship
    @strypey

    .

    RE: https://mastodon.nzoss.nz/users/strypey/statuses/113015290565128857

  9. @fediverseobserver

    #snac2, #PeerTube, #WordPress #Misskey, #Akkoma; it's especially refreshing to see a #snac instance in the list.

    And only a single mastopub box in the list, lolz.

    People are starting to learn that there's no such thing as a mastodon network, and further that there's waaaay mo better #Fediverse platforms to meet whatever their needs and desires are in #DeSoc - many of those Fediverse severs in fact bridging the #protocol_divide by supporting not just #ActivityPub in the Fediverse, but also #OStatus (yes, still), #AT_Protocol, #Nomad, #Zot, #nostr, #Diaspora, and other emerging Fediverse protocols under current development!

    w00t 🤘🤠🤘

    #tallship #FOSS #privacy 🔏

    .

    RE: https://fediverse.one/objects/fdc30534-1166-c797-1d9c-12e934354315

  10. @jupiter_rowland @danie10 @thenexusofprivacy @mikedev

    Okay first I should state that I've never actually said that masto isn't a solid and capable platform. It is, but at a severe cost - the design of masto, notwithstanding the insistence on maintaining a historically lackluster feature set when compared with almost any other Fediverse software, is such that it really isn't built for #DeSoc - it really strives to be some sort of unachievable ideal for the monolithic silo model.

    No one but me seems to site this nowadays, but masto doesn't even really shine with respect to cost in terms of system resources and stability until you approach the 20,000 user account mark. What? Why would you do that? Back when these stats were being bandied about, Pleroma was showcasing its new #Gopher protocol (browsing) support, and reminding people that it felt perfectly at home on an #rPi. No such claim was ever made for masto, lolz. That doesn't mean that the other platforms aren't just as capable of scaling vertically... but... why? Who's going to foot the bill? Who's going to manage all of those un-vetted people creating accounts on your machines? Why would someone bother with that in the first place?

    Community? Nope - there's no sense of community on masto servers, and I'll get to that later. Because you want to create your own private Idaho? Probably. mastodon.social is one of, if not the, largest deprecated monolithic silos existing in the Fediverse today. Why? What possible benefit could be derived by driving a million people into a single funnel under the auspices of telling them that they're escaping that very same model? It's ludicrous.

    No matter what happens in the short term, Eugen is assured of his parachute and comfortable retirement fund, except for the part where he forgot to have his new significant other sign a pre-nup - that might dash his net worth later, but that's another consideration entirely. I hope his marriage is actually a long and fruitful one that lasts forever, he's not a bad guy, he's just been courted and corrupted by the "Ooh shiney" phenomenon of financial entrapments that come with relative success in the media and pop culture.

    The reason masto needs to be hard forked (several times, IMO) is not to create a better masto that will lend itself to DeSoc, #smolweb, and self-hosting on people's home networks, but rather, to further dilute the trademark, and especially the brand, effectively killing it if possible, supplanting it with Fediverse instead. People like to bounce around that term inclusivity, well, this accomplishes that.

    Forks of masto aren't going to create a better masto. No way. Sure, some improvements on this one, other features on that one, but dilution of the brand until it is only as significant as any other deserving Fediverse platform is and should be the ultimate goal. It's not well suited, architecturally for horizontal scaling anyway, unless you don't mind throwing all those system resources at it that could better serve you elsewhere with something like #GoToSocial or one of the #Misskey and #Pleroma family fork members.

    True leaders in the Fediverse will initially be those platforms that have planned ahead and accommodate other DeSoc protocols, arguably Fediverse protocols, at this time, #Diaspora, #OStatus, #Nomad, #Zot, and even others that some #Fedizens turn their noses up at, like #nostr and #Bluesky's #ATP. #ActivityPub is NOT the end-all, be-all for the future. It is the golden calf of today, and just as others that have come before, it will morph and evolve or be obviated by others that will be plugged into the platforms currently running it - #Friendica, #Hubzilla, and Streams are prime examples of this, and Friendica especially, considering it's the only extant original member of the Fediverse for all intents and purposes. One could say that Friendica is the #Slackware of the Fediverse, lolz.

    With respect to Friendica in particular, but also Hubzilla and others that have arrived at this obvious conclusion, ActivityPub is merely the major vehicle by which it communicates with other decentralized social communications systems on the Internet. I don't think it has ever lost sight of that, like another of its contemporaries, #GNU_Social did.

    Hemming large masses of people onto a single (and at this time appearing to be) and open walled garden has the immediate effect of control over large swaths of population - you can say this, but not that. You can think this, but not that. You can be this, but not that. You can believe this, but not that - under penalty of excommunication.

    In reality, we don't have strong friendships with our neighbors - that's why we have fences. We wave to them and say hi, call the cops when they're on vacation and see someone suspicious lurking about their property. That's about the extent of being a neighbor. We invite our friends and coworkers over for BBQ's and to swim in our pools, not so much our neighbors.

    The current masto social architecture is the antithesis of that, and so is it's physical architecture - put all the lobsters in the same pot of boiling water. Turn on and off their ability to speak all at once. Force them en masse to endure advertising blitzes (Oh, mark my word that's coming) decided upon by the server admin. It's like Baba O'Reilly by The Who - "Meet the new boss, Same as the old boss".

    That's not the promise of Fediverse. it's the antonym.

    masto also hinders innovation, attempting to define, dictate even, what should and should not be available - Nomadic identity is but one emerging facet of what is fracturing the masto monopolistic initiative - and that's a good thing, because with the help of FEPs, already, others are adopting various cooperative models for this as well, but discussing that now, and here, at this time, is more of a tangent so I'll get back to the point.

    Jupiter:
    > That's why people still fork Mastodon to add features that are available just about everywhere else.

    Indeed it is, and why it has managed to enjoy a reasonable level of notoriety. There's also the wholly undeserved notion of community that actually, in direct opposition to, masto has continually sought to break and in a very big way, break.

    There are certainly platforms (mostly forumware) that curate a sense of community, but those days are largely past. Whether it was #gplus, #Myspace, #Faceplant, #InstaSPAM, or #Twitter; because just as it is in real life, #COMMUNITY is that which you define for yourself through your connections - your follows and those who choose to follow your account. The biggest failures in the Fediverse that I've personally observed are those that seek to localize, geographically or by shared interest, a monolithic ivory tower of sameness and similarity amongst people.

    I felt so awful for one guy who, so enthusiastically upon discovering the Fediverse, started registering domain names corresponding to several states, thinking that he would be successful in launching a geographically oriented family of masto based servers tending to the shared interests of people by offering them a place to congregate. He quickly discovered the fatal flaw in his model, but was stuck with hefty data center bills to maintain all these masto servers that were largely uninhabited.

    Trying to get rid of your masto subscribers when you figure out that you need to egress from it is not an easy task without disenfranchising your user base. I know, because a few years back, not long after @Gled archived his #mastodo fork and urged everyone to adopt Pleroma instead, I face the daunting task of trying to convince my user base to migrate elsewhere - it took more than a year to accomplish!

    Danie:
    > thing is though there are also many existing alternatives to Mastodon already on the Fediverse, so why fork it?

    In a nutshell, because it serves to, at the very least, dilute the masto brand, and more likely kill it. It has served its purpose and now that it has been exposed as a vehicle antithetical to #DeSoc, it's time to deprecate it.

    My introduction to the #Fediverse occurred when I stumbled upon an earlier incarnation of #Friendica, started looking at #Red_Matrix, and discovered that the monolithic model, if not having been shown the door, had at least been handed its hat.

    The problem at that time, was the effect of Prettiness, and of course, UX. Friendica wasn't too bad in that latter sense, when compared to that of Faceplant, but it sure didn't even come close to being as pretty as Faceplant - or even Myspace, which had only recently fallen into the abyss. That's changed A LOT, even in just the past year, with respect to Friendica and Hubzilla - they're much more intuitive for a layperson parachuting to the ground after jumping from the cesspit over at Faceplant.

    I think that more than anything, not being pretty enough for the subjugated chattel coming from Twitter and Faceplant, was the most difficult thing for onboarders to embrace. Mike placed all of his focus on functionality and forward thinking vision with respect to what these and later efforts could provide the masses, but the "prettification" was left to others who didn't step up for the challenge for many years. I'm all for features six-ways to Sunday, but I also feel that many things need to be hidden from the landing page a new user sees upon account creation - the very basics they expect should be there, akin to those available in the deprecated monolithic space; users expect this, but they don't yet know they not only want, but really need all of these other feature sets too, yet some things should left, IMO, to be discovered later by the user.

    And in my conversations years ago with Mike, I gleaned as much from him [paraphrased, of course]: "Here's this really bitchen gift for the masses, it does all this kewl stuff, now I leave it up to others to make it pretty" (and with a sense of coherency that these former subjugated chattel can initially get their heads around). Putting all that stuff right in their face was awe inspiring, but foreboding at the same time for many.

    Well, finally, people are making it pretty :) And they're also moving much of the overwhelming busy-ness elsewhere in the UI. As a result, there's been an explosion of adoption - not even primarily from former masto folks either.

    I'd like to touch on the notion of community one more time in closing. It might be convenient for n00bie onboarders to glean a bit about how a particular platform functions, but just like in your own neighborhood where you live, you make friends elsewhere mostly - at work, at functions of the hobbies you engage in, with friends you meet at the grocery store or libraries, and the beaches or on hiking or 4x4 weekend excursions. It's the same way in the Fediverse, you make your friends through connections here and there through people you discover along the way, and 99% of them ARE NOT on your particular server instance.

    They don't need to be either, because this is the Fediverse :)

    #tallship #FOSS

    .

  11. This is my first #Mastodon-powered fediverse server. _^

    That means, aleph.land is one of the first and oldest Mastodon-based #Fediverse instance. _~

    I occasionally log in here to keep it alive because this is historical and memorable for me. During this time, and before Mastodon was released, I was running my own Fediverse instance powered by #Hubzilla.

    Back then, the protocol of the fediverse was #OpenMicroBlogging then #OStatus; #AcitivtyPub came years later.

    Today, we have another federated protocol: #ATproto which is powering The #ATmosphere network (#Bluesky is just one instance).

    (PS. Max chars in Aleph.Land is 1024; and using the #GlitchSoc fork since it came out.)

    You can check out my first ever post using Mastodon here: aleph.land/@yahananxie/28062

    @youronlyone

    #MyFediverseJourney #SocialWeb #OpenSocialWeb #FederatedWeb #FederatedSocialWeb

  12. @snarfed.org

    Ryan,

    How refreshing!

    Another bridging mechanism to extend the reach and interoperability with other Fediverse protocols in the #DeSoc space is most welcome, and from the limited analysis I've been able to perform so far this is a novel approach to what some point in the future will find other Fediverse platforms incorporating in their network stacks.

    So far, we've got seamless nostr interoperability to add to the other fine protocols such as Diaspora, ZOT, Nomad, OStatus, ActivityPub, and others in the mix. You might also wish to take a look at the repo for Minds to see how they've made seamless integration between the ActivityPub and nostr portions of the #Fediverse as well, and oh, pay no mind to the infantile and disparaging remarks that some small minded folks in this thread have exhibited - they are free to *defederate themselves from the Fediverse at any time.

    We've been following withe some enthusiasm your project in the Fediverse-City community and it would be a pleasure to have you participate there. Your insight into the open and public aspects of Fediverse traffic in the #DeSoc world is a testament to the innovation and evolution that is possible in obviating the proprietary, privacy disrespecting, deprecated monolothic silo networks that have sowed so much acrimony and subjugation over the very people whom they seek to quantify as their business products.

    You're performing a great service here, feel free to block any miscreants in this thread who don't understand the definition of public.

    Also, might I suggest that instead of offering a `#nobridge keyword index, you think about offering a solution as a FEP here?:
    https://codeberg.org/fediverse/fep/

    There are a lot of Fediverse platform developers I'm sure that you'll find welcoming, encouraging, and willing to offer assistance in formulating solutions to silence the adolescent juvenile mindsets that have been berating you in this thread for your selfless commitment to the well being of us all.

    In the future, the Fediverse that we perceive and interact within will become its own heterogeneous superset of networking protocols to facilitate effortless communications between individual parties regardless of which portions of the Fediverse and their associated protocols implemented. Just like #OStatus has been largely supplanted by ActivityPub, and #ZOT has been superseded by #Nomad, the ActivityPub portion of the Fediverse will also eventually be deprecated and replaced by other stacks that will emerge from the ether of creativity. In the meantime, we'll be bridging between the various protocol stacks, and Bridgy-fed is one of those tools that serves to make that a reality :)

    Thank you again, for your selfless contribution to #DeSoc and the Fediverse. it's a fantastic achievement that will serve to benefit many in both the #ATP and #ActivityPub portions of the Fediverse!

    #tallship #bridgy #FOSS #Fediverse #DeSoc #innovation

    ⛵️

    .

  13. Thank you for the optimistic PoV on the entrance of others to the #DeSoc of the Fediverse. It is an optimism that I share - especially with Matthias' announcement just an hour ago that his team behind the development of the #WordPress ActivityPub plugin has just released version 2.0.0 - considering the enormous footprint of WordPress installations across the entire Internet belonging to both common, everyday individuals and companies alike, of every shape and size, this is HUGE news.

    It instantly, overnight, positions common folks and businesses to leap into the freedoms afforded them by the existing, privacy respecting, #FOSS based Fediverse that hitherto was... well, a bit of a leap for them psychologically. But now they have a familiar platform with which to begin a journey through the minefields of the deprecated, privacy mining, monolithic silos; its proprietors programming their masses of #subjugated_chattel into livestock holding pens, where they are weighed, measured, packaged, placed into inventory, and sold.

    That does raise the issue of an error in your assertions however. You mentioned, "instances in Meta's fediverses and on Bluesky".

    The truth however, the reality, is that each are merely a single instance - One big monolithic silo, as described above, with the same incentives of monetization through privacy mining techniques that have made them the dreadnoughts that they are; at least in the case of #Meta (Threads).

    Bluesky is of that vertically scaling market as well, but much smaller than the #Faceplant and #InstaSPAM engines operated by Meta, and now their new spearhead into the DeSoc space occupied by ActivityPub and other decentralized or federated protocol based, horizontally scaling instances.

    #Bluesky hasn't actually shown their hand yet to the general public, but already, they've disenfranchised (fired) much of their talent; some, actually principal architects of their monolith who were frustrated and disillusioned with the direction Jay has been taking the company - moving further and further away from the disowned public community they spawned, organized, and abandoned following the initial trials and tests of the open source preview version of what became #ATP protocol (ATX).

    Even Jack has moved on and embraced yet another horizontally scaling protocol in the DeSoc space, #nostr, and it's already bridged and interoperating flawlessly with the ActivityPub powered portion of the Fediverse, which in turn interoperates with instances running other protocols such as #Nomad, #OStatus, #Streams, #Diaspora, and #ZOT... all of them part of the Fediverse.

    Many of the extant #ActivityPub powered instances in the Fediverse merely need to install these capabilities with a couple of clicks to enable this interoperability, while others bridge the divide through infrastructure developed and deployed over the past year or so.

    What will be Meta's use case here for their business product?

    That's the main question I think folks need to address - not punish the good people on the so-called evil side of the divide, the hitherto subjugated chattel that populate Marks so-called Metaverse or whatever he thinks he can compel people to adopt and endure. The point is, childish, domain level blocking by juvenile minds operating ActivityPub powered #Fediverse server instances only serves to paint themselves (and the users who have to date trusted those admins with being told what they can and cannot see and do) into a corner where they effectively cancel themselves, and find that their users have migrated to other spaces... maybe WordPress, where they truly control their own destiny in the DeSoc space and can now fully participate and engage with others - but on their own terms, not someone else's.

    And that, I believe, is what the whole thing has always been about, going back as far as #AngelFire and #GeoCities :)

    I do agree with you that we should indeed embrace these common, everyday individuals who, through their programmed ignorance, are mostly clueless as to exactly what the Fediverse is, and more importantly, has always promised for them. This is an opportunity, like Steve Austin, (the Six Million Dollar Man): "We can rebuild them, we have the technology, we can make them better, stronger, faster..."

    One more thing I should correct you on, the Fediverse is an internetwork of networks, on the Internet - there are no fediverses, Fediverse is itself a plurality, but your intent wasn't lost on me.

    Great article, I enjoyed the read and most of all, your optimistically tempered intent. Thanks for sharing and I hope to see much more from you in the future!

    #tallship

    .

  14. @rabble @Fediverse Report Only halfway through it due to lack of time, but in that half, the only pre-#Mastodon, pre-#ActivityPub hint was a very brief mention of the #OStatus protocol and #StatusNet. And it doesn't sound like the other half would actually deal with anything between identi.ca and Mastodon.

    Then again, #Bluesky tries to convince us that the concept of #NomadicIdentity is their original pioneering creation, so naturally, they'd never admit that it was actually invented along with the #Zot protocol in 2011 and has been in use since the creation of the #RedMatrix in 2012 from which eventually #Hubzilla emerged.

    And the representatives of ActivityPub and #Nostr would never admit either that there are protocols and projects that are more powerful than theirs while also being older and having been in active use for longer.

    Interestingly, not even #Diaspora was mentioned.

    So basically, this isn't about the origins of the concept of open social media platforms and their largely unknown history prior to Mastodon. It's about the history of three specific platforms.

    Or should I continue listening, and what I think is missing is yet to come?
  15. CW: What'll happen when Threads introduces ActivityPub? And will it even do so in the first place? A rant
    @Fediverse News

    The hottest topic in the #Fediverse right now has to be #Threads, formerly known as #P92 or #Barcelona, the alleged #Twitter killer by #Meta, and what'll happen when it federates with the rest of the Fediverse. So without further ado, here are my thoughts about this.

    So why did Meta announce Threads to include #ActivityPub?

    Well, it certainly wasn't because they needed a ready-to-use federation protocol. Threads itself will remain a centralised, proprietary, corporate silo with exactly one instance. I mean, when #Tumblr announced to include ActivityPub, this didn't come with the announcement that everyone will be able to run their own Tumblr instance, remember? It just meant that their silo will be able to connect to Mastodon & Co. and quit being a walled garden.

    It's more likely that Threads was planned to get ActivityPub support because at least the EU is going to force online services to become interoperable in some ways. And some big corporations are growing cautious of the expected "or else!" So if Meta wants to offer Threads in the EU, Threads will have to be able to connect to something not owned by Meta. So they've decided to include ActivityPub because a) it's ready-to-use, b) it's free-to-use, c) it already has lots of projects and instances and users to connect to, d) it's something Meta has heard of, and e) it isn't Dorsey's #ATproto.

    I mean, they could also have played it safe and included #OStatus just to have something they'd theoretically be able to connect to without running into nearly as many renitent netizens opposed to Meta. It'd still pass the #DigitalServicesAct. But they probably don't even know that OStatus exists.

    That said, I currently wouldn't be so certain that Threads will actually add ActivityPub. It has never been Threads' unique selling-point. That'd rather be Twitter-like microblogging without Elon Musk or Jack Dorsey at the helm plus one-click registration for Instagram users. Marc Zuckerberg has never wanted to have his own Mastodon. He has always wanted to have his own Twitter. And now that the real deal is on its deathbed, he finally can.

    If ActivityPub integration was actually only planned as appeasement towards the EU, it has become completely unnecessary when Threads blew a raspberry and flipped two birds at the #GDPR with its iOS app that phones all your most private data home to Threads and Instagram and Facebook to be sold to the highest bidder. Because of that, Meta is banned from offering Threads in the EU altogether. Why appease to the EU when you're banned there anyway?

    So there wouldn't be any reason to be surprised if ActivityPub never came to Threads. After all, #Bluesky has talked big about decentralisation and federation and even the "invention" of #NomadicIdentity (which was actually invented in 2011 and first implemented in 2012 on Red Matrix, known as #Hubzilla today). Bluesky was announced long before Threads. Bluesky was launched long before Threads. And just like Threads, it has yet to deliver. As of now, it's just another centralised, monolithic silo, and third-party developments are the only reason why it isn't entirely a walled garden.

    I guess even Jack Dorsey had to realise that it's complete non-sense to create a technological platform for decentralised social networking that's only compatible to itself, save for connectors developed by third parties without his consent. I guess he must have realised just how big and wide-spread the ActivityPub-based Fediverse is and how rapidly it's growing. Decentralising Bluesky now would be like introducing a replacement for e-mail that's completely incompatible with e-mail itself.

    In fact, I think that Dorsey had launched the Bluesky project and placed high bets on it before he even knew that the Fediverse existed. And when he found out about the Fediverse, there was no way back anymore. Not without being punished by his investors.

    Marc Zuckerberg, on the other hand, knew about the Fediverse when he greenlit Project 92, now known as Threads, for one of its earliest announced features was interoperability with the Fediverse via ActivityPub. That's another difference: He didn't want to compete with the Fediverse, he wanted to connect to it. Whether he actually will, now that one of the main perks of doing so has vanished due to Meta being Meta and the EU reacting accordingly, remains to be seen.

    But even if ActivityPub came to Threads, that wouldn't mean that Zuck embraces the Fediverse. He won't. Even if they all used ActivityPub, the Fediverse as we know it now would be direct competition for Threads.

    Threads won't tell its users about Mastodon, Akkoma, The Project Still Known As CalcKey, Pixelfed, Lemmy etc. That'd be like Microsoft officially acknowledging that Linux-based operating systems are nice, too, if installed stand-alone instead of Windows. That'd be like Apple officially publishing a list of the top five greatest Android phones with Samsung on #1.

    Threads won't tell its users how to migrate to another Fediverse instance. That'd be like Microsoft officially publishing a tutorial on how to wipe your hard drive and replace the Windows on your computer with Ubuntu.

    And Threads won't add migration functionality to elsewhere in the Fediverse either. That'd be like Microsoft installing an exporter for personal data on everyone's Windows machines on the next patch day that makes it easier for you to keep your data when replacing Windows with GNU/Linux on your machine.

    For a while after ActivityPub has been activated, practically nobody on Threads would make use of it, especially not to connect with users in the rest of the Fediverse. They simply won't know that this rest of the Fediverse exists, much less who exists there. If any connections will be established, they'll be in-bound.

    Even these first connections won't come to pass by someone discovering a cool Threads account in their Mastodon timeline. Instead, someone will stumble upon Threads accounts either because they're on Threads themselves or because the addresses of these Threads accounts are published somewhere on the Web, e.g. someone adding their Threads ID to their blog or their website. They'd end up connecting by copy-pasting that someone's Threads ID into their search field.

    After these first connections have been established, it will still take very very long for the Threads users to discover that there's a Fediverse beyond Threads. No, really.

    For comparison: Many of you came into the Fediverse through mastodon.social. And I dare say that a great deal of those of you did not know anything about decentralisation and instances and all that stuff at that point and instead believed that they had joined another centralised walled garden like Twitter. Someone has told me a while ago that some people who came in through mastodon.social took three months to even notice that Mastodon is decentralised, that many of the toots in their timelines come from someplace else than mastodon.social.

    It takes new Mastodon users even longer to discover that there's a Fediverse beyond Mastodon. From my experience, that's often three to six months. There are three major ways for Mastodon users to find that out.

    One, you stumble upon a post that mentions Fediverse projects that aren't Mastodon, and that mentions that they're Fediverse projects and connected to Mastodon.

    Two, you post something that implies or out-right claims that the Fediverse is only Mastodon, and someone comes and tells you otherwise in the comments.

    Three, you discover weird-looking posts in your timeline that can't possibly come from Mastodon with way over 500 characters, strange-looking mentions, strange-looking hashtags etc. If you inquire whoever wrote that post about it, they'll tell you they aren't on Mastodon, but on an instance of another project which is nonetheless connected to Mastodon.

    It'll be very similar on Threads, but on a much greater scale with a much bigger timeframe. I guess many Threads users may spend years without even encountering a post from outside. Most will spend many months. And I'm not talking about actually noticing that the post in question did not originate on Threads.

    Unless Threads will actually slam account IDs with non-Threads domains on them into its users' faces, I think one element that Threads users will notice will be hashtags which Threads doesn't have, but which I don't expect Threads to strip out entirely like Mastodon strips out any and all text formatting. Thread user: "Hey dumbass, this ain't Twitter, Threads doesn't have hashtags!" External user: "But Mastodon has them. I'm on Mastodon and not on Threads." Thread user: "What's Mastodon, and WTF are you doing on my timeline then?!" External user: "[Fediverse explanation noises]" And even this will only lead to one more Threads user knowing about the rest of the Fediverse. Out of hundreds of millions.

    The difference between mastodon.social and Threads is that new arrivals on mastodon.social are left uninformed about what Mastodon is and how it works to make on-boarding easier than if they were educated about decentralisation and instances and other Fediverse projects and then left to choose the project and the instance themselves. Threads users, on the other hand, are left believing that, beyond being a centralised silo, Threads is a walled garden with no connections to the outside world whatsoever. To be fair, it is one right now and will remain one for the foreseeable future. mastodon.social doesn't try to pretend to be a walled garden. And Mastodon itself only does so a little by hardly, if ever, acknowledging the rest of the Fediverse.

    If Threads users should actually set out to discover the rest of the Fediverse and make connections to there, the impression they get from the Fediverse won't be too positive. That's because two out of three Fediverse instances will be inaccessible to them due to having blocked Threads altogether. From the point-of-view of a Threads user who has always put full trust and faith into all Facebook/Meta products and never used anything decentralised before, believing that even e-mail is a Microsoft or Google or Yahoo! product, the Fediverse will appear as nothing but a bunch of entitled arseholes.

    It certainly won't help that the [Fediverse explanation noises] won't include, "This is all just hackish amateur stuff rather than professional corporate software development, and we're lightyears from your features, but it does its job." Instead, users from other Fediverse projects will mention ("brag about") the features that these other Fediverse projects have that Threads lacks. Hashtags, for example. Let me show you them.

    It gets even worse if someone on Threads happens upon someone on something else than Mastodon. In comparison with Akkoma, Threads pales more. In comparison with what's-still-but-not-for-much-longer-called-CalcKey, it pales even more. And now imagine what'd happen if someone on Threads met someone on Hubzilla. Or /kbin. "Whaddaya mean, you're talkin' to me from a Reddit clone?! How's that even possible?"

    Okay, so those Fediverse people aren't just entitled, they're also snooty braggarts who claim that their stuff that was developed with a budget of zero is allegedly better than Threads that was developed with a several-billion-dollar budget.

    Let's just say that even if the Threads users discovered the Fediverse beyond Threads by-and-by, they wouldn't be too keen on connecting to what's left of it that they can actually connect to. The biggest chances will be if it'll be possible on Threads to share Follow Friday posts from Mastodon in such a way that it isn't too obvious that they come from Mastodon. Since Mastodon mentions don't include domains, they might pretty well pass for mentioning Threads users, and the Threads community will believe that Follow Friday was invented on Threads. Also, out-right celebrities on George Takei's level of fame if they reside on instances that don't block Threads. But otherwise, no chance.
  16. Eugen can be the #BDFL of Mastodon if he wants to.

    But the article really doesn't explain that the #Fediverse is bigger than Mastodon, that Mastodon is only one client among dozens. If there is to be any BDFL over the #Fediverse it would be @evan and I don't think he wants the job.

    The #Fediverse started in 2008 with Evan's Laconi.ca and #OStatus. Mastodon has been around for less than half the lifespan of the #Fediverse.

    #BDFL= #BenevolentDictatorForLife

    @tarkowski @Gargron @nilaypatel

  17. #Rappler, please correct this: Users of #Mastodon have created a “Fediverse”…

    Please also correct: “Mastodon's fediverse”. The fediverse is not Mastodon's, Mastodon is simply one part of the #Fediverse network.

    A little #history.

    * 2008: #identica, powered by #OStatus protocol, came online. The first publicly launched federated platform, or software, as well as service.

    * 2010: #Friendica (called #Mistpark during development, and #Friendika when it) launched publicly.

    (aside) * 2010(?): diaspora launched (diaspora protocol). Their network is called “The Fediverse” (or maybe later? I can't remember this part)

    * Sometime between 2010 and 2012, the term #Fediverse was first coined to replace the brand-based terminology #identiverse (based on identica).

    * 2014: The W3C started the #ActivityPub protocol working group.

    * 2016: Mastodon launched, supporting only the #OStatus protocol.

    * 2017 July: #Hubzilla officially added support for the ActivityPub protocol.

    * 2017 September: Mastodon officially added support for the ActivityPub protocol

    * 2018 January: ActivityPub officially reached “W3C Recommendation” (a.k.a. launched, stable, final, recommended standard)

    The Fediverse has existed since 2008. Eight years before the “Mastodon” platform/software launched. It was not even the first to implement the ActivityPub protocol.

    Other than those mentioned, everything is cool.

    rappler.com/technology/feature

    EDIT: added extra info, re: #diaspora and #TheFediverse.

  18. » :fediverse: Bridgy Fed turns your web site into its own #fediverse account, visible in #Mastodon and beyond. You can post, reply, like, repost, follow […] by posting on your site with #microformats2 and sending #webmentions. Bridgy Fed translates those posts to protocols like #ActivityPub and #OStatus, and sends interactions back to your site as webmentions.«

    »[It] takes some technical know-how to set up« — true, but still: Wow 😮 & nice 👍

    fed.brid.gy/docs

    /via @pfefferle

    #IndieWeb

  19. Que es ​:fediverse:​ y cual es su 'magia', información necesaria, posibilidades que brinda, enlaces de consulta, servidores para hacer una cuenta... #feditips

    Al
    #fediverso se le llama así por su estructura, "#Fedi" por ser descentralizado (#descentralizacion) con la idea de formar parte de una misma red (una #federacion, #abierta porque de ahi viene #federar, que se puede hacer o no, eliges con quien hacerlo) y "#Diverso" porque la red se conforma de diferentes redes, cada red funciona mediante servidores con software (implementaciones de software / mismas #plataformas o #diferentes, etc.#diversidad) que se puede conectar con otros servidores con software que usan (hablan) el mismo protocolo, hay servidores que tienen implementaciones de software que hablan diferentes #protocolos, es decir, forman parte de diferentes redes (la red se puede definir por dos o más tipos, principalmente es por su protocolo o por la implementación de software que usa los servidores, un ejemplo de un tipo es la red de #activitypub o la red de #ostatus y un ejemplo de otro tipo es la red de #mastodon o la red de #friendica).

    Así que al pertenecer a la
    #red del #fediverse puedes escoger a que #redes del #fediverso pertenecer, por medio del #protocolo y el #software que usarás (o elijas usar) según también en el #servidor (#instancia , #nodo) en el que escojas registrar una #cuenta (administrado por alguien, #publico o tuyo propio). También tienes la posibilidad de preferir entre las #opciones que hay, como ver el espacio donde interactuarás, por medio de que #plataforma decidas usar, también por la #interfaz (#interfaces) que te guste más y la #app (#apps y por el sistema operativo #web #apk #pwa #linux #gnulinux #ios #windows) que te venga mejor. Mucha #libertad de uso, por eso al Fediverso se le suele llamar la red de redes, ya que es una analogía a #internet pero para la comunicación social.

    ¿Quieres registrarte una cuenta o saber más? En estos enlaces puedes encontrar
    #servidores #instancias #nodos (todos los días hay nuevos, que se mantienen y otros que desaparecen, así que hay muchos le veas por donde le veas), #protocolos, #software (implementaciones de software, plataformas,etc.) del Fediverso, información, etc.:
    https://fediverse.observer/list
    https://fedidb.org/network
    https://joinfediverse.wiki/
    https://fediverse.party/en/miscellaneous/
    https://the-federation.info/
    https://nodes.fediverse.party/
    https://www.fediverse.to/
    https://fedi.ninja/mastodon
    https://fediverse.space/
    https://en.wikipedia.org/wiki/Fediverse
    https://en.wikipedia.org/wiki/Comparison_of_software_and_protocols_for_distributed_social_networking

    Vídeo de ¿qué es el
    #fedi verso?, explicativo con subtitulos:
    https://framatube.org/videos/watch/4294a720-f263-4ea4-9392-cf9cea4d5277

  20. i am making a #fediverse #hungergames kinda thingy (that one site brainsteele.net/hungerhames). why? idk i had the idea and i'm like "yeah let's do it"

    anyways who wants to participate? tell me in the replies! only the first 24 people get to be in so be quick if you wanna participate. share this!

    #activitypub #mastodon #misskey #pleroma #hubzilla #friendica #fedi #mastodonsocial #mstdnsocial #blobcat #koyuspace #masto #nixnetsocial #koyu #absturztau #smoothbrain #users #user #gnusocial #kibou #microblogpub #ostatus #socialhome #socialnetwork #microblogging

    also #pixelfed probably

  21. ♲ @[email protected]:

    The Fediverse - A decision-making aid


    There are four different protocols the #ActivitiPub, #Diaspora and #OStatus and there is also the #DFRN protocol which is as good as dead.

    Mastodon is the number 1 network with over 4.000.000 users followed by Diaspora with over 600.000 members. On place 3 comes #Pleroma with over 30.000 members followed by #Hubzilla on place 4 with over 10.000 members and on place 5 comes #Friendica with almost 4.000 members.

    According to this calculation it would be clear that #Mastodon is the clear winner but here the idea of the #Federation (Association) takes hold. Let's see who can communicate with whom and what the result is, start with the winner.

    Mastodon can communicate with Pleroma, Hubzilla and Friendica so that results in 4.044.00 users.

    Diaspora can communicate with Hubzilla and Friendica, resulting in a total of 614,000 users.

    Pleroma can communicate with Mastodon, Hubzilla and Friendica and has a comparable reach to Mastodon of 4,044,000 members.

    Hubzilla can communicate with Friendica and Pleroma, resulting in a reach of 44,000 members.

    Friendica can communicate with Mastodon, Diaspora, Pleroma, and Hubzilla, resulting in a reach of 4,644,000 people.

    Friendica is the clear winner in terms of reach. Now everyone just has to find out for themselves which platform suits them best.