erlend_sh

Some folks have gotten themselves together as something they’re calling the Social Web Foundation, and I’ll cut to the chase: this is an attempt by ActivityPub partisans to rebrand the confusing “fediverse” terminology, and in the process, regardless of intent, shit on everything else that’s been the social web going back twenty-five years.

Hey 👋 if you don't know us already, we're building Frontpage; an AT Procol based federated link aggregator. We shipped an initial MVP in closed beta recently and have since been thinking about the road to general availability.

This post is an RFC (Request for Comments) targeted at technically minded folks who are interested in seeing the progression of atproto for non-Bluesky/microblogging use cases. All that's to say the language that follows assumes some knowledge about how Bluesky and atproto work! I've tried to include links to explain what all of the jargon means though, so hopefully it's not entirely nonsense for folks a little less familiar!

When you post on Frontpage, we propose that a mirror post will also be created in your Bluesky account. When you comment on Frontpage, we propose that a mirror reply will be created in your Bluesky account.

Conversely, when you reply to one of these mirrored posts in Bluesky - we will show it as a reply in Frontpage.

Additionally, Bluesky likes will be translated to Frontpage votes and vice versa.

Back in June I wrote about an exciting confluence of digital auth tech:

(1) The commodification of #OIDC infrastructure, (2) the emergence of #FedCM, (3) and the compatibility of both with #indieauth .

In short, it is now easier than ever to log into web applications using your own website as an identity provider. Or at least, it would be, if your favorite web apps supported these agency-enhancing technologies.

https://blog.erlend.sh/indie-social-sign-in-could-go-mainstream

#opensource #indieweb #identity

https://writing.exchange/@erlend/113091679196090320

Speaker: Martin Kleppmann, University of Cambridge, Inc & Switch

We have come a long way since my colleagues and I published the local-first essay five years ago. In this talk I'll review where the local-first idea came from, where we are now, and what I hope the local-first community can work towards in the future.

I think this is the most important (WIP) Fediverse Enhancement Proposal of this year for the #ActivityPub protocol:

FEP-7952: Roadmap for Actor and Object Portability — by @by_caballero@mastodon.social and @dmitri@social.coop

It ties a lot of elementary building blocks for #nomadicidentity neatly together, most succinctly summed up by one particularly magic feature:

Bring-your-own Actor ID! 🪪💫

Actor profiles can now be hosted separately from the instance (including as a static JSON object on a personal website), which in turn enables service providers to offer their users a “BYO (Bring Your Own) domain name” feature.

That’s really all I ever needed from the notion of a ‘single-user instance’. All I want to manage on my own is my identity; I don’t want to take on the full burden of managing a whole AP server.

In this paradigm, someone’s tiny personal website could also be their Actor-ID Provider, and nothing more. That ID could in turn be used to as a (reasonably nomadic) account on any FEP-7952 compatible instance.

From @by_caballero@mastodon.social:

the idea is to detach the Actor object (which could be operated by a microserver that consumes almost zero resources, and basically just operates a big redirect table like a link-shortener) from the Service Provider, to be a little more like email (in the use case where you point a domain that you own and configure at protonmail or mailgun or some other provider) or SMS service (in that regulation enables you to keep your number when you switch phone co’s).

We will prototype the micro-Actor in the coming months, but we have no idea how long it would take for implementations like WordPress or forks of Mastodon/Misskey/Pleroma to offer support for this kind of externalized/self-managed Actor. We are hoping existing servers will find it interesting to offer a “service-provider mode” for the nomadic/domain-owning user class, for many reasons. In the meantime, we might also prototype a Fedify-powered server that only allows external Actors to create accounts.

Mastodon: https://writing.exchange/@erlend/112684879834557152

Social bookmarking is a novel use case for ActivityPub and I’m super excited about it. I heckin’ love links and lists! I wanna use them for everything.

Things like Bookwyrm are cool, but it’s not what I want. I just wanna link the thing. Books, films, podcasts, articles, songs.., they’re all just resource recommendations which can be encapsulated by links.

In the glory days of web 1.0, social websites would prominently link out to their digital neighbors via lists known as webrings; magical doorways to an expansive hinterland of digital villages.

Let's envision what a truly federated chat like Matrix could do to improve the cross-connectivity of chat channels. Most of these features are already possible, they just haven't been implemented yet in a community-oriented client experience.

I suspect the fedi-collective has more negotiating power in this moment than it realizes. We may as well make some asks, see how Meta responds, and they in turn will see how the public, the media and the regulators respond to them in this bold new era of pervasive Big Tech skepticism.

Money can mitigate the risk of Threads:

'coopting the fediverse': $200k for Test Suite. 'overburdening moderators': $200k for moderation. 'locking in users': $200k for Nomadic Identity

A bit of internet reparations.

https://writing.exchange/@erlend/112163747418805861

With the now accepted RSA signatures for DPoP tokens, the ephemeral, dynamic clients and the basic serving of webid documents for each user, Rauthy should now fully support. Solid OIDC. This feature just needs some more real world testing with already existing applications though.

EVENT_MATRIX_ERROR_NO_PANIC This new config variable solves a possible chicken and egg problem, if you use a self-hosted Matrix server and Rauthy as its OIDC provider at the same time. If both services are offline, for instance because of a server reboot, you would not be able to start them.

One of the best features of Lemmy is that it supports a combination of image and text. I wish including the source link of a comic would be a standard practice on the fediverse, just like alt-text already is.

Source links are great for:

• Properly crediting and driving traffic to artists
• Checking authenticity
• Preventing image degradation for re-shares

p.s. I was thinking of posting this as a meta-post in /c/comicstrips but I only saw guidelines for how to post comics there.

There’s a major convergence of OAuth/OIDC support across fediverse applications, Matrix is going all-in on it as its root default, and other social web protocols are tagging along as well.

Like the separation of church and state, it seems prudent to keep the management of our digital identities separate from our social network servers.

Domain-based OIDC accounts, especially when self-hosted, serve the function of a minimum-viable ‘nomadic identity’.

With the emergence of Rauthy, being a self-hosted OIDC provider is suddenly viable. All that’s missing is web sign-in (IndieAuth lite) as single sign-on for the masses.

Mastodon post: https://writing.exchange/@erlend/111376285042429865