Orbit eTOG Listing Service: RFC-46 Assigning Authorities and the Future
Description: General tracker issue for like should we allow this to grow beyond the bounds of hoes I know in Minneapolis or not, and if so, how to handle it
Comments:
- At least one request from someone I know only one-step out in Chicago for AA creds. I'm wary to let it spread beyond I-DM-you-to-admonish-you range, but also I think it would be funny
- I could imagine a recursive authorization system where if you have AA creds you can create a subauthority for someone else. This would also allow seeing the path, like eg "Fat Earth Orbit -> Yuni's Scratch Heads -> Chechnya"
- There are two big problems with letting it spread: (1) it's basically an in-joke database so it will stop being as funny to the orbit if there are jokes we don't know in there and (2) it would require some actual moderation tooling
- I think (1) is the biggest problem, I could imagine some split of site scheme where there is "GUY WHO <ATTENDS EVENT>" guys' site and "GUY WHO LIES ON THE IMAGINARY AXIS" type guys' site but I imagine the public-facing site quickly turns into nCatLab / pronouns.page with higher kinded types
- Resolved: use codenames. if it's really a problem make an assigning authority hierarchy
- Wait actually that's ^ for the next RFC
Home