4 ms·

I’m not even suggesting people use their own did:web - for that very reason. I am saying that Bluesky could have used a did:web that uses the plc domain with e

I’m not even suggesting people use their own did:web - for that very reason. I am saying that Bluesky could have used a did:web that uses the plc domain with exactly the same effect. As is all did:plc resolution is effectively hardcoded to https://plc.directory https://plc.directory so what exactly does having its own method change (given they could decorate the docs with any additional functionality)? I don’t think did:web is the way forward either, as any domain “ownership” is temporary - including plc.directory. Even extending did:key (so the identity is actually owned by the user via a keypair) and providing a doc resolver (users could register with multiple “resolvers” including bluesky controlled ones) would at least mean an id not tied to a central authority - but they chose to use their own assigned method specific identifiers. ATProto is great. PLC sucks.

verdverm 1y ago
Some interesting points in there you have made. I run my own PLC read-only mirror and do resolution that way, the main PLC is not hardcoded and is a variable you can configure in the official packages There is also talk of supporting the did:webvh (or something like that) which addresses the domain loss iirc. > multiple “resolvers As an ATProto developer, how many authorities would I have to consult? Where would that list come from and live? More builders are welcome if you want to work on this problem. I'm working on private data and permissions for ATProto
- supermatt 1y ago
  At present you would have one - bluesky. Just as with PLC. I would hope that some form of truly distributed resolvers would become commonplace - such as those that leverage mainline DHT - and bluesky could then switch to that as well. Where do these discussions take place? I’d love to get involved somehow.
  - verdverm 1y ago
    https://discord.atprotocol.dev https://discord.atprotocol.dev is a great entrypoint fyi, the PLC is moving to an independent foundation and governance. It is unlikely to go away or change significantly in the near-term. fyi2, there are two methods already, did:plc and did:web. The most likely next addition would be did:webvh, but I'm also not involved in any of that stuff. I don't think there is much work on this front because "if it ain't broke, don't fix it". The PLC is useful, even if too "centralized" for some people's preferences
    - supermatt 1y ago
      Thanks - I will join there and see if there’s any way I can promote decentralisation as a core tenet.
      - verdverm 1y ago
        Word of caution, please don't go into a new ecosystem and start by telling them what you think needs to be changed. First understand why things are they way they are today. ATProto has attracted developers precisely because it's not a purist dominated ecosystem. The underlying ethos to everything is user choice and agency Also, show not tell, build then advocate

verdverm 1y ago

Some interesting points in there you have made. I run my own PLC read-only mirror and do resolution that way, the main PLC is not hardcoded and is a variable you can configure in the official packages There is also talk of supporting the did:webvh (or something like that) which addresses the domain loss iirc. > multiple “resolvers As an ATProto developer, how many authorities would I have to consult? Where would that list come from and live? More builders are welcome if you want to work on this problem. I'm working on private data and permissions for ATProto

supermatt 1y ago
At present you would have one - bluesky. Just as with PLC. I would hope that some form of truly distributed resolvers would become commonplace - such as those that leverage mainline DHT - and bluesky could then switch to that as well. Where do these discussions take place? I’d love to get involved somehow.
- verdverm 1y ago
  https://discord.atprotocol.dev https://discord.atprotocol.dev is a great entrypoint fyi, the PLC is moving to an independent foundation and governance. It is unlikely to go away or change significantly in the near-term. fyi2, there are two methods already, did:plc and did:web. The most likely next addition would be did:webvh, but I'm also not involved in any of that stuff. I don't think there is much work on this front because "if it ain't broke, don't fix it". The PLC is useful, even if too "centralized" for some people's preferences
  - supermatt 1y ago
    Thanks - I will join there and see if there’s any way I can promote decentralisation as a core tenet.
    - verdverm 1y ago
      Word of caution, please don't go into a new ecosystem and start by telling them what you think needs to be changed. First understand why things are they way they are today. ATProto has attracted developers precisely because it's not a purist dominated ecosystem. The underlying ethos to everything is user choice and agency Also, show not tell, build then advocate