That then introduces ease of use problems. You won’t be able to log in to another device without copying your key over from an already logged in device for example.
Web browsers don’t usually allow access to local files made outside the browser, so even logging in between browsers would require having your key on hand.
Not to mention if you lose the file containing your key (hard drive craps out, etc), you’ll lose access to your account entirely. So users would be forced to backup their keys.
Not issues that would make the product unusable, but enough of a hindrence that 90% of users would just go find something else (like threads) to use instead.
For identity verification, you can just do a simple key signing, just like how Nostr does it.
Each user will generate a public-private key pair on their own device and has all their posts (and edit/delete requests) signed using their key.
If someone wants to delete or edit their post, the site can just verify that the request is signed with the same key.
There’s still issue of who’s going to store the user’s follows, etc. but I think we can find a way to workaround it.
That then introduces ease of use problems. You won’t be able to log in to another device without copying your key over from an already logged in device for example.
Web browsers don’t usually allow access to local files made outside the browser, so even logging in between browsers would require having your key on hand.
Not to mention if you lose the file containing your key (hard drive craps out, etc), you’ll lose access to your account entirely. So users would be forced to backup their keys.
Not issues that would make the product unusable, but enough of a hindrence that 90% of users would just go find something else (like threads) to use instead.