Now it covers all aspects of ownership, including ownership transfer, and provides a comprehensive authentication and authorization framework for ActivityPub implementers.
Announcing FedIAM 0.1.0 - Sign in with a Fediverse account!
Suppose you want to allow people to log in to your web site. How will they identify themselves? With a username and password? We've all got far too many of those already, and they're not even particularly secure. Perhaps with a Google or Facebook account? That's a lot easier, but do we really want to allow these companies even further into our lives?
FedIAM is a research project which aims to offer an alternative: using Fediverse and IndieWeb protocols, visitors can log in using any one of thousands of small, independent networks run by ordinary people - or even using a provider that they host themselves, independently of any outside influence.
Announcing FedIAM 0.1.0 - Sign in with a Fediverse account!
Suppose you want to allow people to log in to your web site. How will they identify themselves? With a username and password? We've all got far too many of those already, and they're not even particularly secure. Perhaps with a Google or Facebook account? That's a lot easier, but do we really want to allow these companies even further into our lives?
@FediverseSymbol I generally like the idea for a unicode symbol for the Fediverse, though I'd not replace the pentagram with it, but use both, depending on the use case.
What I definitely don't like is this top down approach. "Hey, here is a new symbol for the Fediverse. Spread it!". Shouldn't this be a democratic process?
@FediverseSymbol I feel like the colors in the default logo are important. For me it represent different instances with different purposes. Mastodon isn't just a cluster of servers talking to each other, it's the people using it - which is represented by colors nicely right now.
I've made the decision to officially suspend development of lotide.
As I see it, the project doesn't have a future. By now, there are several implementations of forum federation that are much more feature-complete (if a bit strange), and it no longer makes sense to stubbornly implement something that is almost but not sufficiently compatible. But most importantly, working on lotide is no longer something I enjoy.
That's not to say that it will never be revived should the situation change, and the code is available as always.
Until whenever, vpzom
The End of lotide
I've made the decision to officially suspend development of lotide.
As I see it, the project doesn't have a future. By now, there are several implementations of forum federation that are much more feature-complete (if a bit strange), and it no longer makes sense to stubbornly implement something that is almost but not sufficiently compatible. But most importantly, working on lotide is no longer something I enjoy.
Updating this old post:
>emoji reacts fully supported :eimithumbsup:
>frontend basically everything I could want from a fedi frontend (and it's not bloated to heck)
>no emoji autocomplete yet but :cirnoshrug:
>replies work well (reply notifs don't appear consistently in husky for whatever reason but I'll make a git issue for that)
>better docs for federation but I still find following relays with a throwaway bloats the db very quickly (there's probably a better solution I missed, I may be retarded)
>quote posts fully supported
>enough markdown, greentext support built in (death to indented quotes from > in markdown) (headings would be nice tho)
>still kinda wish there was a web UI for administrative stuff but we got mitractl + confs a non-schizoid can comprehend (looking at you pleromer) so :cirnoshrug:
>can replace static assets now ala pleroma, all that's left is figuring out how2change.css without rebuilding frontend
>on the subject of static assets I wonder if there could be an option to ignore file extension when replacing as I can't figure out how to APNG on GIMP and would like to make animated webp related the background for the instance frontpage and the filename must be identical down to the png extension
>would be nice to have bookmarks like pleromer
>docs for setting up XMR donations spotty and confusing, have dead links
Tl;dr: Mitra is at the point I could comfortably run it for my main instance, and I would recommend people run it over Pleromer or its forks. It runs better, it's not a pain in the arse to set up and maintain, DB doesn't eat up 500 quintillion terabytes of data for a single user instance (unless you do something retarded), updates are frequent and add features that are actually needed. It's pretty swell.
Updating this old post:
>emoji reacts fully supported :eimithumbsup:
>frontend basically everything I could want from a fedi frontend (and it's not bloated to heck)
>no emoji autocomplete yet but :cirnoshrug:
>replies work well (reply notifs don't appear consistently in husky for whatever reason but I'll make a git issue for that)
>better docs for federation but I still find following relays with a throwaway bloats the db very quickly (there's probably a better solution I missed, I may be retarded)
>on the subject of static assets I wonder if there could be an option to ignore file extension when replacing
That could be done by overriding CSS
One way to do that is to add CSS variables to a file with an agreed upon name like theme.css located in web_client_theme_dir. Frontend will try to load this stylesheet and if it is present it will replace default values
Mitra 3.2.0 finally adds UI elements for emoji reactions. This is a significant change and if you don't like it, let me know. I can add a setting that hides reactions.
We need to get to identities that aren't tethered to particular instances. Various approaches have been discussed, all more or less valid IMHO, we just need to get them implemented.
We have had one working implementation for 13 years now. In the Fediverse. In stuff that's federated with Mastodon.
@Mike Macgirvin 🖥️, creator of Friendica (2010), creator of Hubzilla (2015), creator and maintainer of the streams repository (2021) and, most recently, creator and maintainer of Forte (all four are being actively maintained, part of the Fediverse and federated with Mastodon), invented the concept of nomadic identity in 2011.
The same year, he implemented it in his own Zot protocol. Zot came to use first in 2012 in a Friendica fork named Red, later the Red Matrix, which became Hubzilla in 2015. Hubzilla still uses the latest stable version of the Zot protocol that's still called Zot. Everything that Mike did since 2012, with the exception of the first Osada from 2018, featured nomadic identity, including (streams) which is based on an "offspring" of Zot called Nomad.
I'm writing to you from a Hubzilla channel that simultaneously resides on two server instances. Not in the shape of a dumb copy, but in the shape of a real-time, bidirectional, live, hot backup.
It's basically what Bluesky has claimed to be a revolutionary new and never-done-before feature in the AT protocol, only that a) it's even more advanced, b) it's older than Bluesky, c) it has been proven to actually work in daily use, and d) it is in daily use.
Right now, Mike is working on implementing nomadic identity using only ActivityPub, specifically FEP-ef61. Even this has advanced beyond theoretical. (streams) has it implemented already. All channels created on accounts that were registered on versions 24.07.20 and newer are made compatible with nomadic ActivityPub. I have two such channels, although neither has a clone yet.
In fact, it could be that at least Forte, which is in a very early stage right now, will have Nomad and maybe even support for Zot6 removed and go nomadic using only ActivityPub. Mike said he wants to sunset Nomad and Zot6 once nomadic identity via ActivityPub is ready for prime time.
We need to get to identities that aren't tethered to particular instances. Various approaches have been discussed, all more or less valid IMHO, we just need to get them implemented.
We have had one working implementation for 13 years now. In the Fediverse. In stuff that's federated with Mastodon.
The cat is out of the bag. Mike Macgirvin's family of Fediverse server applications has a new member: Forte which he has forked off his own streams repository some three weeks ago.
The first announcement came in a comment on a post about Friendica with which everything had begun, just three days ago. The same day, the up-until-then still unannounced Forte repository was discovered. Unlike what's in the streams repository, Forte seems to have a name again, and Mike refers to it as a "project".
(streams), as its predecessor is colloquially being referred to, is already one of the most advanced and innovative server applications in the Fediverse. It has the most elaborate set of permission controls as of yet, even surpassing Hubzilla, the younger one of its surviving ancestors. Also, Mike uses it to develop the implementation of nomadic identity, his own invention from as early as 2011, purely via ActivityPub, including FEP-ef61. So (streams) itself is already a pioneering work, and its development is far from done.
And now we have Forte which promises to be even more advanced. There are no specs yet, much less any public instances. And even if it's the latest fork in 14 years of Fediverse development, I guess it's far from being ready for prime time. But seriously, it's a (streams) fork.
The cat is out of the bag. Mike Macgirvin's family of Fediverse server applications has a new member: Forte which he has forked off his own streams repository
I've changed the Authorization section of FEP-c7d3 (Ownership). Now activity and its object/target can have different owners as long as they have the same origin.
For example, this allows admins and moderators to Delete objects and Remove objects from collections hosted on their server.
Same origin principle equally applies to FEP-ef61 portable objects where naming authority of URI is not a DNS name but a DID.
I'm collecting various ideas on improving ActivityPub developer experience. Currently they are in a FEP format, though that might change: FEP-d85d: ActivityPub for developers.
The goal of this document is to provide information that is useful for beginners but can't be found in the ActivityPub spec, simplify the protocol while improving interoperability, and address common misconceptions. It was partially inspired by ActivityPub Minimal Core by @steve
This is a milestone worth celebrating! :fediverse:
In development as we speak, @forgejo can now federate comments (and tons of other stuff) from issues in repos!!!
@liaizon It's not just comments! Pretty much all public user activity federates. Creating a repo? Yup. Tagging? Yup. Branching? Yes. Cutting a release? Sure! Opening an issue? Aye. A PR? Of course. Merging a PR? Mhm. Closing an issue? Yep. And so on...
Do note: this is like the user RSS feeds, except over AP. While federated activities can be replied to, and can be viewed on the Forgejo UI, they are completely detached, and live in their own little world.
(Eventually, I want to make it possible to log into a Forgejo account from any Fedi client. But we're not there yet.)
@liaizon It's not just comments! Pretty much all public user activity federates. Creating a repo? Yup. Tagging? Yup. Branching? Yes. Cutting a release? Sure! Opening an issue? Aye. A PR? Of course. Merging a PR? Mhm. Closing an issue? Yep. And so on...
Do note: this is like the user RSS feeds, except over AP. While federated activities can be replied to, and can be viewed on the Forgejo UI, they are completely detached, and live in their own little world.
@gabriel have just FINALLY uploaded a torrent with the svgs for both :butterfedy1: fediverse and :peertube:PeerTube and a bunch of sizes pre-exported into png for both.
is up on the i2p torrent tracker.... (NOTE: link will not work unless you have the parallel internet installed with a browser configured to use it. i2p bounces ur web traffic around the world for better anoymity)
i thank dsfgs, nestort and @smallcircles for their past effort of 3 years and celebrate mitra server (@silverpill@nimda) on the page, i also :bun_hd:
@gabriel have just FINALLY uploaded a torrent with the svgs for both :butterfedy1: fediverse and :peertube:PeerTube and a bunch of sizes pre-exported into png for both.
is up on the i2p torrent tracker.... (NOTE: link will not work unless you have the parallel internet installed with a browser configured to use it. i2p bounces ur web traffic around the world for better anoymity)
The developer of Streams contributed a lot to this FEP, based on the NomadicIdentity features it's shared with Hubzilla for years(1). So it's already been implemented in Streams.
I'm curious to see it added to other ActivityPubs apps so I can test an app-to-app migration.
The developer of Streams contributed a lot to this FEP, based on the NomadicIdentity features it's shared with Hubzilla for years(1). So it's already been implemented in Streams.
Gregory's Server
