> Recently Christine Lemmer-Webber shared this on Mastodon: > >> Here is your recipe for making the "Correct Fediverse IMO (TM)": > > * Integrate ocaps, which is possible because actor model + ocaps compose > * Content addressed storage! > * Petname system UX > * Better anti-spam / anti-harassment using OCapPub ideas > * Improved privacy with E2EE ("encrypted p2p" even a better goal) > * Decentralized identity (notice the \y\, I did not say DIDs) on top of \~mutable CAS storage > > In this post I'm going to explore how Leaf stands up to these goals!

Homeownership on the web is highly analogous to the physical world. Modern homeownership is mostly a story of home-rentership, not real ownership.

Incredibly, this matches the online experience, even though the World Wide Web has an infinite amount of real-estate!

You deserve a home on the web that’s built to keep you safe; a magical place for virtual living that‘s yours for life, existing in a sociable web.

(Now stealth-releasing Weird v0.2 🥷)

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

Links:

• https://atproto.com - https://atproto.com/articles/atproto-for-distsys-engineers
• https://www.blackskyweb.xyz - https://bsky.app/profile/rudyfraser.com/post/3l6d7mmzhik2r

> For a lot of us, atproto projects are some of the biggest (most users, most publicized, most code written, etc.) projects we’ve ever done. For me, it’s also my first time working in open source (ironically, someone asked me to be more open about that) > > If you can help, pls check out open issues.

I know not everyone thinks highly of atproto around these parts, but please don’t let that get in the way of welcoming a fellow rustacean into the open source world 🦀

How open source projects can balance Makers and Takers: lessons from Drupal's contribution credit system and recommendations for WordPress and other open source communities.

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

> As a web engine, Servo primarily handles everything around scripting and layout. For embedding use cases, the Tauri community experimented with adding a new Servo backend, but Servo can also be used to build a browser. > > We have a reference browser in the form of servoshell, which has historically been used as a minimal example and as a test harness for the Web Platform Tests. Nevertheless, the Servo community has steadily worked towards making it a browser in its own right, starting with our new browser UI based on egui last year. > > This year, @wusyong, a member of Servo TSC, created the Verso project as a way to explore the features Servo needs to power a robust web browser. In this post, we’ll explain what we tried to achieve, what we found, and what’s next for building a browser using Servo as a web engine.

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

> The concept of progress is at the heart of humanity’s story. From the present, it is possible to imagine a future of abundance in which our great challenges have been addressed by the unique human ability to modify the universe toward our own ends. Many believe that we will attain this future through a combination of expanding human knowledge and advanced technologies.  > > This article explains how our current idea of progress is immature: it is developmentally incomplete. Progress, as we define it now, ignores or downplays the scale of its side effects. Our typical approach to technological innovation today harms much that is not only beautiful and inspiring, but also fundamentally necessary for the health and well-being of all life on Earth. Developing a more mature approach to our idea of progress holds the key to a viable, long-term future for humanity. > > The way we understand what progress is and how we achieve it has profound implications for our future. Ultimately, it shapes our most significant actions in the world—it affects how we make changes and solve problems, how we think about economics, and how we design technologies. Whatever is not included in our definition and measurement of progress is often harmed in its pursuit. Its side effects (or externalities) occur in a complex cascade, often distributing harms throughout both time and space. The second- and third-order effects of our actions in the world can be difficult to attribute to their original cause, and are frequently more significant than we realize.  > > As technology gets more powerful, its effects on reality become increasingly consequential. On our current trajectory, these effects will end civilization’s story long before we merge with machines, or before we have built a self-sustaining colony elsewhere in the solar system. We are not as close to a multi-planetary future as we are to the kind of damage to the biosphere that either destroys or significantly degrades civilization. If we continue to measure and optimize progress against a narrow set of metrics—metrics focused primarily on economic and military growth, which do not account for everything on which our existence depends—our progress will remain immature and humanity will continue its blind push toward a civilizational cliff edge.  > > In this article, we use the phrase “the progress narrative” to refer to the way we think and talk about progress in society. The progress narrative is the pervasive idea within our culture that technological innovation, markets, and our institutions of scientific research and education enable and promote a general improvement in human life. This article questions the accuracy, incentives, and risks of this narrative, examining the reasons that the idea has held such a central role in shaping the development of our global civilization. In doing so, it attempts to outline the progress narrative earnestly and clearly, noting that it is often driven by an honest desire to see positive change in the world. The intention is not to point the finger of blame, or to deconstruct for the sake of argument. It is to inform a way forward and outline a path ahead toward potential solutions. > > Drawing on a range of sources, the article takes an interdisciplinary approach to exploring the reality of humanity’s current trajectory. Several prevalent progress myths are reexamined, including apparent improvements in life expectancy, education, poverty, and violence. The roots of these inaccuracies are exposed by widening the aperture of our view. Even if we are living longer, many measures of the quality of life we are living are in decline. Our educational outcomes are in many ways deteriorating, even if access to education is improving. At a global level, despite the common narrative, it is not clear at all that poverty is actually reducing. And the tools of violence have increased vastly in scale of impact since the end of World War II; we now routinely create the kind of weaponry previously reserved for dystopian science fiction.  > > To convey a sense of the extent of unintended consequences that can result from a single innovation, the primary case study explores the invention of artificial fertilizers. This development enabled a significant increase in the amount of food (and therefore people) that could be produced. The externalities of this innovation have had far-reaching consequences for human health and the wider biosphere. An assessment of these side effects helps us to open our eyes a little more widely, so that we may glimpse a fraction more of the complex reality that is generally omitted from the simplified narrative of progress.  > > Our idea of progress needs to mature. If humanity is to survive and thrive into the distant future, we must transform and elevate the very idea of progress into something truly good and worthy of our shared pursuit and aspiration. As we understand more about the universe and find new ways of changing it with our technologies, we must account for the endless ripple of cause-and-effect beyond our immediate goals. We must factor both the upsides and the downsides that will continue to impact reality long after the technologists of today are gone.  > > For our idea of progress to be mature, it must take account of its side effects and plan to resolve them in advance—it must internalize its externalities. In the second part of this article, four specific methods for internalizing externalities are outlined, alongside some clear examples of what such a process might entail. > > The possibility of a mature kind of progress is both grounded and optimistic. It’s a proposal that the human capacity for both wisdom and ingenuity is far greater than we currently imagine. We are capable of holding the unknowable complexity of reality at the very center of how we take action in the world, and mitigating the consequences of the gaps in our knowledge in advance. This enables a *real *kind of progress that reduces suffering, builds a better understanding of the universe and our place within it—and increases our chances of both surviving and thriving into the distant future.

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

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.