iiinova — where your digital self keeps evolving

Replies

Ducky 🦆 @ducky.ws · 16/02/2026

1) Using a pre-existing domain Pointing your domain at cname.didweb.cloud, claiming it, pointing it at a PDS, and letting the app create the did:web on said PDS. In the spirit of did:web, if you wish to move somewhere else, a DID Doc exporting and PDS migration will also be available. 3/9

190

Ducky 🦆 @ducky.ws · 16/02/2026

2) Using a pre-existing did:web Logging into didweb.cloud with the already-existing did:web, then migrating the DID Doc over to the app. Same as 1, DID Doc exporting and PDS migration will too be available. 4/9

160

Ducky 🦆 @ducky.ws · 16/02/2026

3) Using a hosted domain What I know as the "fuck it, we make our own did:plc", this will create a did:web:*.didweb.cloud account. Of course, this relies entirely on us keeping the service alive: if it dies, all accounts die with it. Only recommended for fleeting alts and test accounts. 5/9

160