social.cologne is one of the many independent Mastodon servers you can use to participate in the fediverse.
social.cologne is eine Mastodon Instanz für jede:n Kölner:in und alle, die sich mit Köln verbunden fühlen. Betrieben von https://cgnfs.de.

Administered by:

Server stats:

1.2K
active users

#identica

0 posts0 participants0 posts today
Replied in thread

@liaizon Most of my follows from 2010 are still active too!
web.archive.org/web/2009082701
web.archive.org/web/2010072401

@WikiSignpost @sal @wikimediaDE @belett @bzg @gpaumier @CristianCantoro @aklempert @eloquence @ragesoss @lyzzy @kat @notafish @metasj @hexmode etc. (and Evan and Brooke of course).

(I initially only registered @wikimediaitalia, promising I'd personally remain anti-social, but changed mind at #Wikimania 2010 and registered an account for myself too.)

Replied in thread
@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
joinfediverse.wikiFriendica - Join the Fediverse

Something I miss about the old #Identica is how weirdly well it ranked on Google. Like I could dent something like "The factory service manual doesn't mention it, but when removing the passenger-side CV axle on a 2000 #Infiniti #i30 you need to unbolt the support bearing (part 22 in the diagram) from the support bracket (part 23)" and somehow that dent would suddenly be in the top 5 results for "2000 infiniti i30 cv axle". On #Mastodon sharing such information feels like shouting into the void.

Das Fediverse hat jetzt eine Organisation!

Das Prin­zip des Fedi­ver­se ist dezen­tral. Eigent­lich kön­nen alle tun uns las­sen, was sie wol­len, solan­ge sie sich an das Acti­­vi­­ty­­Pub-Pro­­to­­koll des W3-Con­­sor­­ti­ums hält. Die Social Web Foun­da­ti­on will sich jetzt aber dar­um küm­mern, dass das Netz­werk wächst und gedeiht.

https://kaffeeringe.de/2024/09/25/das-fediverse-hat-jetzt-eine-organisation/

kaffeeringe.de · Neugründung: Das Fediverse hat jetzt eine Organisation!Das Prinzip des Fediverse ist dezentral. Eigentlich können alle tun uns lassen, was sie wollen, solange sie sich an das ActivityPub-Protokoll des W3-Consortiums hält. Die Social Web Foundation will sich jetzt aber darum kümmern, dass das Netzwerk wächst und gedeiht.

I used #Identica and #Diaspora back in the day, Tw was just way more practical, the API was almost like a protocol, you could build anything on top of it.

No service at that scale could afford losing money like Twitter. The glorious days of tw were subsidized by VCs.

As simple as that, any instance trying to replicate the current Tw will fail because that model was never real tbw.

#Cohost is a joyful blip bc how much we learned first hand instead of just theorizing about that type of sites.

#ControlYourself.Inc =
a Quebec corporation headquartered in Montreal. providing identi.ca and status.net and lead development for Laconica / StatusNet
"We make Open Network Services - sites that use Open Source software to create and distribute Open Content."


#Laconica =
Open Source Software - Twitter alternative - published 2008. Coinciding with the release of version 0.8.1 in August 2009 the Software was renamed in to "StatusNet"

#StatusNet =
Open Source Software - Twitter alternative, formerly known as "Laconica"

#status.net =
microblogging hosting service, from Control Yourself, Inc. started July 2009. technical provided by www.joyent.com
"status.net is a new microblogging service that lets anyone set up their own microblogging site, based on Laconica’s functionality. Clients can make private microblogging networks for use by a company or community, or public ones that interface with Twitter, Facebook, and other Laconica-based sites. Control Yourself is accepting applications from enterprises, marketing and publishing organizations, and Web communities to participate in their beta program for the platform they call “status-as-a-service.”


#identi.ca =
microblogging platform launched July 2, 2008 by Control Yourself, Inc. running Laconica/ Statusnet
"Users can post short messages about themselves to Identi.ca, which are then broadcast to friends in their social network using instant messages (IM), RSS feeds, and the Web."


#OStatus =
protocol - standard for federated microblogging. A suite of open protocols, including Atom, Activity Streams, WebSub, Salmon, and WebFinger.
"OStatus enables different microblogging server implementations to route status updates between their users back-and-forth, in near real-time. OStatus federation was first possible between Laconica/StatusNet installations, such as Status.net and Identi.ca"


#Pump.io =
protocol - general-purpose activity streams engine that can be used as a federated social networking protocol - successor of OStatus. Identi.ca, which was the largest StatusNet service, switched to pump.io in June 2013

#Joyent =
Cloud Computing vendor of ‘Infrastructure as a Service’

#EvanProdromou =
WebDeveloper and CEO of Control Yourself, Inc. and status.net
im.allmendenetz.deim.allmendenetz.de
Replied to Jupiter Rowland
That was all they knew. And nobody told them otherwise because nobody else knew either.

(...)

So StatusNet wasn't really part of the #FederatedSocialWeb in practice.


According to my sources the story goes a bit different here - sorry for that @Jupiter Rowland

The "Federated Social Web" was an term founded and an initiative started by Evan Prodromou, the head and CEO behind #StatusNet #Ostaus and #IdentiCa. In July 2010 he tried to get together all active groups developing code specific to federation of the web. This happen to be just around the days as @Mike Macgirvin came around the corner with #DFRN. He got even invited to this "Federated Social Web" summit but i guess the way form Australia to Portland Oregon was a bit to long, for this short-term invitation.

There where some more "Federated Social Web" meetings and one result form Evans initiative was also the "W3C Federated Social Web Incubator Group" started on 15 December 2010 and transitioned on 12 January 2012 to the "W3C Federated Social Web Community Group". This group did all the basic work for the Activitypub definitions published 2018 https://www.w3.org/TR/activitypub/

It appears that in all this meetings Mikes projects were never present. In all this "Federated Social Web" summits and follower up meeting all kinds of protocols, networks, platforms were discussed - but i read never about #Mistpark, #Friendica, #Hubzilla, #DFRN or #ZOT . But Evan and the others DEVs know about Mikes work for sure. For very sure - but they were following their own projects and ideas.

The OStatus support side was hard-coded for only this one instance because the devs believed that identi.ca was a monolithic walled garden just like Twitter.


Evan had always also some kind of businesses modes in mind and he got in August 2010 even $2.3 million. Dollars of Venture capital for the platform #status.net So the whole setting for this #FederatedSocialWeb initiative has to be seen also in this light.

And.... Guess who the chairman of the W3C Social Web Working Community Group was - Evan.

Now ... also the Free Software Foundation (FSF) was also just focused on OStatus and StatusNet. By 2009 a decision of the GNU social steering committee was made to built on top of the OStatus protocol and the StatusNet codebase a project called "GNU social". It's main goal was to deployable with a minimal hosting configuration. So GNU social got on the way and was finally around 2012/13 the successor of Laconica/StatusNet software.

Now we can understand a bit better that DFRN/ZOT/NOMAD projects were never considered later e.g. by the FSF. Today they use of coure Masto, the successor of GNU social.

Somehow the line of projects started with Mistpark got ignored by powerful institutions because advocates and proponent were missing here. In two weeks from today here in Cologne we will have a summit about the chances of free social networks, also organized by the Free Software Foundation Europe

https://fsfe.org/news/2023/news-20230712-01.en.html

One of the speaks will be @Tobias. He has been a follower of Mikes projects since the very early days in 2011 and still is running a Friendica community hub and is working for the FSFE also as system administrator. He should know also a bit about #Hubzilla and #Streams and we can hope for sure that the word about Mike projects will be finally start to be spread :-)

I will report.
im.allmendenetz.deim.allmendenetz.de