erlend_sh

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_[email protected] and @[email protected]

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_[email protected]:

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

I’m personally very excited about this because Rauthy provides a robust foundation of OIDC-based identity for the fedi-connected platform we’re building with Weird netizens.

The addition of “social logins” such as GitHub means indie platforms like Weird can let people easily sign in with the mainstream identity provider they’ve already got, but once they’ve signed up they’ll have the option of using our open source identity provider for other services going forward, thus reducing their dependency on the Big Corp.

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.

To free ourselves of our current predicament, we must simultaneously de-centralize and re-centralize identity.

• Decentralize ownership.
• Recentralize agency.

By de-centralizing the ownership of identity away from platform monopolies and back to individuals, we can re-centralize the agency of personhood.

The central authority of ones digital identity must first and foremost be the individual themself. That's how we regain our digital sovereignty.

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

Like any other major network incumbent, Discord cannot simply be side-stepped altogether; appropriate off-ramps are required.

#Matrix bridging enables an incremental, non-disruptive transition from the old to the new.

We invite anyone interested in the development of #CommuneApp to join our newly opened space: https://matrix.to/#/#home:commune.sh

The first half of our product rollout starts next month, as we begin publicly testing our uniquely community-oriented Matrix client.

Microblog link: https://writing.exchange/@erlend/112141665369480242

This article shows the overview of the development process of the Fish Folly game using Fyrox Game Engine.

Rauthy is an OpenID Connect (OIDC) Provider and Single Sign-On solution written in Rust.

Cyber is an embeddable language for fast, efficient, and concurrent scripting, ideal for rapid iteration in games and app development. Made with Zig.

At a glance:

• Easy to learn.
• Dynamic and static types.
• Concurrency with fibers.
• Memory safe.
• FFI and Embeddable.
• Fast VM and JIT.
• Cross platform.