The only dishonesty here is you pretending to not see the actual harm from the huge uptick in indiscriminate badly behaved scraping bots that LLMs have empowered even the dullest wanna-be grifter to deploy.
I really like this idea, but I’m not clear how the logistics work out. It’s “free” but 1.5 - 3 months in NYC is not cheap and would mean carrying double rent for that period of time on top of living expenses. Is there financial assistance or are participants expected to cover all of their own costs? If so doesn’t that make this only accessible to those quite well off already? That is, those who can afford to take off 1.5-3 months while covering the cost of living in one of the most expensive cities in the world. I see there’s a remote option but the in-person aspect of this really feels key to the experience.
Really not trying to be a spoil sport because the idea is incredible and worthwhile but I couldn’t find the answers looking at your website.
My understanding is that if I want to host AT Proto infra for my community and want to give people <usename>.<domain> account, I can either host a did:web for them which ties their account permanently to that domain, or they have to register with the centralized PLC to actually have all the benefits of a migratable DID, while tying themselves to a central authority. Ergo, did:web does not provide the same UX as did:plc and there’s currently no way (that I know of) to provide such UX to users without requiring them to register did:plc accounts
Dan my concern is explicitly that did:web is not the same experience for users as a did:plc.
If I host AT Proto infra for my community and want to give people <usename>.<domain> accounts, I can either host a did:web for them which ties their account permanently to that domain, or they have to register with the centralized PLC to actually have all the benefits of a migratable DID. did:web does not provide the same UX as did:plc
From the post I was responding to:
> Second, even if you're on a PDS, you're still reliant on the Public Ledger of Credentials (PLC) to host your Distributed ID (DID) document. The PLC is run by Bluesky, although they've taken steps to make it easy to notice if they were to do something fucky with the PLC. But let's say we don't like that. There is a solution: you can host your DID document on a normal web server. Problem solved?
>
> Well, if you were setting up an account for the first time, then yes, the problem is actually solved, you're 100% independent of Bluesky. But if you made the mistake of registering an account normally, you have a did:plc identity. And one core principle of ATProto is that identity names never ever ever change. So if you go and make a did:web identity, it's like having a second account, there is no way to tie your old did:plc identity into it. In fact, I'm pretty sure you can't even redirect one did:web identity to another (say if you need to switch domain names)