![[nanachi] TOTAL EMPLOYMENT - S03E07 [1080p].mkv](https://mk.magicka.org/files/c7153a78-b5ab-46c5-9223-1d9c1d1dbf6d.png "[nanachi] TOTAL EMPLOYMENT - S03E07 [1080p].mkv")
indians have consequences
0 Boosts
0 Likes
Blurry Moon
@sun@shitposter.world
·
activity timestamp
yesterday
@jaff this is the most indian thing I have read in a couple years. "we spent years irresponsibly building up a pile of shit, now here's some money to quick-fix it, we are now going to blame you if you can't quick-fix our pile of shit."
@sun@shitposter.world dw his nephew who got hired via nepotism is on the job, it'll be fiiiine
@jaff I thought the exact same thing.
@sun@shitposter.world @jaff@mk.magicka.org or south african considering this is what elon musk tried to do with the government
@sun@shitposter.world @jaff@mk.magicka.org I see. still. I have to admit I am getting a bit tired of this limitation when ATProto and nostr both already have this solved
@sun@shitposter.world @jaff@mk.magicka.org current account migration on AP is pretty limited, you basically just notify your followers that you moved and their instance may or may not autofollow. You don't bring your post history and it's a completely new account so you still lose your old identity
@sun @anemone @jaff @rees I mean in a lot of ways moving accounts with posts is something most people don't really care about, so it is very down the priority list. I've seen only e-celebs complain about it so far. You technically can also import all your posts from a backup on another server, but then all the object links that other instances have to the old posts are invalid anyway.
The Mitra implementation uses DIDs instead of domains I think, anyways paging @silverpill 😊
The Mitra implementation uses DIDs instead of domains I think, anyways paging @silverpill 😊
@phnt @anemone @silverpill @jaff @rees it works its just obviously bolt-on until every server just natively supports keys
@sun @anemone @silverpill @jaff @rees
>it works its just obviously bolt-on until every server just natively supports keys
Yeah, never happening.
>it works its just obviously bolt-on until every server just natively supports keys
Yeah, never happening.
@sun @anemone @silverpill @jaff @rees I mean there still are fedi servers that don't understand the concept of editing ones post without a delete & redraft. Almost every extension on this network is never going to achieve near complete adoption.
@phnt@fluffytail.org @anemone@ebiverse.social @sun@shitposter.world @silverpill@mitra.social @rees@pleroma.ree.social what if we had a "minimum protocol compliance specification" that includes things users actually ask for not things eugen feels like adding
@jaff @anemone @sun @silverpill @rees I think that is what silverpill is essentially working on with ap-next.
@phnt @anemone @silverpill @jaff @sun creating new specs/protocols is pointless if it doesn't enable anything new
@rees @anemone @phnt @jaff @sun
It's not a new protocol. ap-next currently has two goals:
1. Documenting how ActivityPub really works vs what one could find in the specs: https://codeberg.org/ap-next/ap-next/src/branch/main/guide.md
2. Extending ActivityPub protocol (the "real" one) to support new features such as cryptographic identities: https://codeberg.org/ap-next/ap-next/src/branch/main/nomadpub.md
@silverpill@mitra.social @phnt@fluffytail.org @anemone@ebiverse.social @sun@shitposter.world @rees@pleroma.ree.social after skimming a few of the specs I feel like nomadic identity as defined there has too many moving parts and something simpler like "this web finger user also has this client public key, here it is signed by domain key, and here in the user profile the client key is attesting it is currently owned by the domain key, here is just the signature figure it out" (with a spec on how to figure it out) would get more servers implementing this feature. Having multiple key slots complicates everything and any kind of history can be derived over time by observation. I am not sure there needs to be a standardized interface for nomadic identity migration verification at first.
is there a "minimum compliance specification" for ap nomadic?
