@silverpill does Mitra support OIDC logins?

In order to facilitate seamless login into a Mitra instance via Weird-app, Mitra needs to support logins via Rauthy (OIDC backend of Weird): https://github.com/sebadob/rauthy

The instance type we’d like to host is most likely gonna be @mitra #mitra

..specifically because it supports nomadic identity, so neither our instance nor our users are locked in stasis; Weird net can migrate to a different AP instance in the future if necessary, and instance tenants can migrate to any other instance that supports Nomadic Identity (FEP-ae97), e.g. with:

https://codeberg.org/silverpill/fep-ae97-client

It’s pretty easy to self-host; the real challenge is instance governance and moderation.

We would like to run an #activitypub instance as part of the #weirdone platform, same as the excellent #omglol by @prami

This instance will be operated as a paid extension of Weird, costing $10/yr ($20/yr after beta).

All member subscriptions will go entirely to the AP instance hosters, which should be a team of at least 2-3 sysadmins & moderators tending to the instance part-time. This is expected to be a fairly low-volume instance since all members are paid (to begin with).

#moderation

@ruben_int @johnonolan definitely! Ghost is listed in the post as one of the org structures we admire.

@fanden will do

What kind of company does Weird aspire to be?

https://blog.muni.town/weird-inc/

Must we consider ourselves a ‘possible future adversary’ of the open product and ecosystem we’re caringly shaping and seeding as founders?

Abiding by non-extractive practices means doing business on hard mode, but it’s a fun puzzle.

We believe the most realistic and sustainable way of realizing that outcome is with old-fashioned commerce:

1. Make product
2. Sell product
3. Return to step 1

#WeirdOne #indieweb #postgrowth

Here’s our roadmap for Weird going into 2025!

https://blog.muni.town/weird-2025/

We already have a proof-of-concept importer for Mastodon as a backup of your posts & connections.

#weirdweb #indieweb

@nilesh forking the official app is tricky because it’s such a fast-moving target that is unlikely to wanna merge such an addition down the road.

There are however efforts like this being discussed for unofficial clients: https://github.com/elk-zone/elk/discussions/3030

Gobo exists as a live open source example as well.

Unfortunately the middle of the venm diagram ‘atproto enthusiast/user’ and ‘ap enthusiast/user’ appears to be so small that no one has decided to pursue this yet.

https://blog.erlend.sh/prosocial-discourse

‘An ActivityPub gal and an ATProto guy enters a bar.., and they get along great, no joke.’

This is what good-faith co-creation of the Social Web looks like.

The standard for mature conversation has been set. Let this be the beginning of the end for reactionary protocol tribalism. (I’m so sick of it, make it stop make it stop make it stop.)

#fediverse #atproto #socialweb

@cwebber @zicklag lol, much appreciated! 🫶

To be clear we had no expectations of direct engagement, we just found your framing/prompts to be a fitting contextual basis from which to explain our own work.

That work does seem to align quite neatly with OCapN et.al., the docs of which we will certainly revisit more attentively in the coming weeks.

zick’s been pondering a nifty WASM-based plugins system as well..

@mttaggart cybermylowerbackhurts

@nextgraph @zicklag certainly!

Zick is currently in the process of drafting a blog post in response to Christine’s ‘Correct Fediverse’ outline in the context of Leaf.

You’re in a great position to do the same for NextGraph, with the added bonus of being innately AP compatible!

Nomadic Identity is complicated and many separate ventures are saying ‘we do this’. Such statements need to be accompanied with explanations of the flows and trade offs involved, as that makes all the difference.

@cwebber

> Decentralized identity on top of ~mutable CAS storage

Is there anything like a spec stub for that somewhere? I think we stand a good chance of checking all these boxes in #leafprotocol by @zicklag

https://mastodon.social/@zicklag/113528550574786820

@silverpill speaking of DID methods, I ran into another promising one recently: https://fedid.me/about/

@anildash “video is not available” when trying to view from Norway

From @bnewbold:

https://whtwnd.com/bnewbold.net/3kwzl7tye6u2y

A relay of the entire Bluesky network can be run for $153/month. That’s mighty impressive!

Many #ActivityPub hosters are paying this amount for member counts in the low thousands.

@mikedev @streams congrats!

#nomadicidentity over ActivityPub is a big deal; might this release be accompanied by a blog post or other such technical writeup about the implications of these new features?

Where should we be referring instance developers who’d like to implement their own version of nomadic identity?

@pfefferle could be a lot easier if all the WordPress site had to carry was the Actor ID:

Erlend Sogge Heggen (@[email protected])

https://socialhub.activitypub.rocks/t/fep-7952-roadmap-for-actor-and-object-portability/4332?u=erlend_sh 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 @[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 (…)

Writing Exchange (writing.exchange)

@bnewbold yeah I like that. Though as long as the algorithms are opt-in and composable, it’s all good really. I just don’t want any surprises in the ordering of my feed, covertly introduced by obfuscated algorithms.

Even a fairly magical sorting mechanism is fine as long as I get to explicitly flip the switch and mindfully observe its impact.

Everything works differently when the user is transparently included in the entire loop. I could happily A/B-day test my enjoyment of different configs.

@arcanicanis

> Meanwhile, in regards of Bluesky, my big concern is that users don't even control their identity.

As of today that is also the case for AP users. We must consider both standards as continuously evolving and subject to change.

> (…) they would still ultimately hold control over your identity, if they hold exclusive control of those private keys.

Maybe @bnewbold can speak to that IF of exclusive control. My understanding is they’re working towards non-exclusive control.