5 ms·

So when I visit my did:plc at https://plc.directory/did:plc:i3gjwozl32eq3j3ejyw44hh4 https://plc.directory/did:plc:i3gjwozl32eq3j3ejyw44hh4 It has a reference t

So when I visit my did:plc at https://plc.directory/did:plc:i3gjwozl32eq3j3ejyw44hh4 https://plc.directory/did:plc:i3gjwozl32eq3j3ejyw44hh4 It has a reference to alsoKnownAs: ["at://evbogue.com"]. And that is _not_ my did:web. That is a reference to the dns txt record that I used to verify my account and lose the subdomain evbogue.bsky.app that I had before. If I was to upload a document like yours at https://retr0.id/.well-known/did.json https://retr0.id/.well-known/did.json How do I configure Bluesky's social application to reference my did document at https://evbogue.com/.well-known/did.json https://evbogue.com/.well-known/did.json (which doesn't exist yet) and have that be how people find my posts on Bluesky? Even if my selfhosted did document points to "https://shimeji.us-east.host.bsky.network https://shimeji.us-east.host.bsky.network" as my PDS? Could I use this to host my stuff at many PDSes? Sorry if I seemed confused. I listened the whole podcast and didn't realize alsoKnownAs is different than did:web.

Retr0id 2y ago
at://evbogue.com is your handle, you don't have a did:web because you have a did:plc instead. Your DID string is the immutable root of your account's identity, it cannot be changed (the DID document it references can be updated, though) - but you can create a new account that uses a did:web instead. There aren't really any instructions on doing so (afaik) but you can do it pretty easily when you self-host a PDS. (It's no longer possible to create new accounts with a did:web on Bluesky PBC's hosted PDSes, mine is old and "grandfathered" in)
- evbogue 2y ago
  This helps, I am less confused now. What happens if I set my handle on my selfhosted PDS as "alsoKnownAs: [evbogue.com]" and leave my handle at Bluesky PBC's PDS as "alsoKnownAs: [evbogue.com]".
  - Retr0id 2y ago
    Then the handle on the not-self-hosted-account will be invalidated (potentially after some cache expiry)
- xeonmc 2y ago
  > It's no longer possible to create new accounts with a did:web on Bluesky PBC's hosted PDSes If that's the case, what is the (very well hidden) "choose your account provider" button on Bluesky's registration page ("You are creating an account on [[Bluesky Social]]") used for? Self-hosted PDS? If so, if it's possible to spin up a temporary PDS with TryCloudflare for the initial set up and keep the did.json hosted on static site instead?
  - Retr0id 2y ago
    > Self-hosted PDS? Yes, or some other commercial PDS hosting service. > If so, if it's possible to spin up a temporary PDS with TryCloudflare for the initial set up and keep the did.json hosted on static site instead? Not sure why you'd want to do that, but it sounds possible.
    - xeonmc 2y ago
      What I’m thinking of is to use the _redirect file as a manual DDNS with cloudflare pages as a stable url that points to an ephemeral TryCloudflare address of a temp PDS running on my laptop. Does the validation scheme follow through HTTPS redirects?
      - evbogue 2y ago
        This is an interesting idea that is worth exploring more. I wonder if when your PDS was online if you had some kind of local sync for messages from the people you follow? You wouldn't follow many people, so you could quickly build a local Appview that organizes the posts into a chronological feed. Then you could browse your messages later without an Internet connection.

Retr0id 2y ago

at://evbogue.com is your handle, you don't have a did:web because you have a did:plc instead. Your DID string is the immutable root of your account's identity, it cannot be changed (the DID document it references can be updated, though) - but you can create a new account that uses a did:web instead. There aren't really any instructions on doing so (afaik) but you can do it pretty easily when you self-host a PDS. (It's no longer possible to create new accounts with a did:web on Bluesky PBC's hosted PDSes, mine is old and "grandfathered" in)

evbogue 2y ago
This helps, I am less confused now. What happens if I set my handle on my selfhosted PDS as "alsoKnownAs: [evbogue.com]" and leave my handle at Bluesky PBC's PDS as "alsoKnownAs: [evbogue.com]".
- Retr0id 2y ago
  Then the handle on the not-self-hosted-account will be invalidated (potentially after some cache expiry)
xeonmc 2y ago
> It's no longer possible to create new accounts with a did:web on Bluesky PBC's hosted PDSes If that's the case, what is the (very well hidden) "choose your account provider" button on Bluesky's registration page ("You are creating an account on [[Bluesky Social]]") used for? Self-hosted PDS? If so, if it's possible to spin up a temporary PDS with TryCloudflare for the initial set up and keep the did.json hosted on static site instead?
- Retr0id 2y ago
  > Self-hosted PDS? Yes, or some other commercial PDS hosting service. > If so, if it's possible to spin up a temporary PDS with TryCloudflare for the initial set up and keep the did.json hosted on static site instead? Not sure why you'd want to do that, but it sounds possible.
  - xeonmc 2y ago
    What I’m thinking of is to use the _redirect file as a manual DDNS with cloudflare pages as a stable url that points to an ephemeral TryCloudflare address of a temp PDS running on my laptop. Does the validation scheme follow through HTTPS redirects?
    - evbogue 2y ago
      This is an interesting idea that is worth exploring more. I wonder if when your PDS was online if you had some kind of local sync for messages from the people you follow? You wouldn't follow many people, so you could quickly build a local Appview that organizes the posts into a chronological feed. Then you could browse your messages later without an Internet connection.