Comment on FEP-7952: Roadmap for Actor and Object Portability
muntedcrocodile@lemm.ee 4 months ago
From my understanding of this it means client side signing of actions would be supported?
It seems that accounts (actor objects) can now just be a static file hosted anywhere which lowers the bar for entry of self hosting. Id love to see something about supporting .onion addresses when looking up this file would allow self hosted anonymous identity while not requiring support for a whole instance as a hidden service.
by_caballero@mastodon.social 4 months ago
@muntedcrocodile @erlend_sh Technically, in the current draft, it can't actually be a *static* file, you still need nginx/caddy/etc to redirect the permanent "indirect urls" (`https://myownserver.xyz/bumble?service=storage?object=123`) to the current/mutable "direct urls" (`https://serviceprovider.com/user/bumblefudge/AP/posts/123`).
by_caballero@mastodon.social 4 months ago
@muntedcrocodile @erlend_sh As for .onion addresses for the Actor object/microservice, that's a bigger ask of implementers, and even if it were implemented, I'm sure more legally-cautious servers would want to disable that feature... but i'm sure someone would make `http://anonserver.xyz/` once people start using this, and i'm sure they would accept payment in Monero and ZCash 😉
But hey, it's an interesting backlog ticket to consider, I appreciate the suggestion!