Although I do wish that profiles and comment history could be preserved from one server to another. That’s basically the last piece of the puzzle that would give the user a completely a completely free experience.
Something like an independent third party data bank that saves profile data? So your user data would be publicly accessible - any server can access it to populate your profile on that server - but nobody can update or delete it but you?
Shit, have we found an actual use case for blockchain?
I’m as anti crypto rugpull nft bullshit web 3.0 is gonna be uuuuge bro i swear bro where are you going bro as much as the next person buuuuut…cryptocurrency is a godsend in shithole countries such as mine where the local currency is a joke and and possession of any non local currency is illegal
Nah, There’s other ways to store data while preserving confidentiality, integrity and availability that isn’t on the blockchain. Besides A public ledger connected to a specific profile could make it easier for the profile to be doxxed/fingerprinted.
Spitballing here but a service using simple key-pairs might be a better way to do this.
• Users generate a key pair client-side.
• Public key is stored on the server, acting as the user’s identity.
• To update their profile, users sign the request with their private key. (Data is signed/verified client side before submission)
• The server verifies the signature using the stored public key before edits can be made.
Because data signature/verification are done client side theoretically you don’t need a ledger, your client can enforce profile state. (Maybe an HMAC is sent with the verified data and there reverted periodically by the client)
Just public key cryptography. All your actual posts and comment history are already shared. What is missing is a way to authenticate yourself to anyone but your home server. If the protocol included every profile having a public key, you could then use that to authenticate to any server. And managing that private key is no more complicated than managing your private key in a block chain context.
Non public info like subscriptions is a bit more complicated, because there is an actual policy question of who you share it with. You would either need to make it publicly available, keep a copy yourself, or have your home instance give it to you/the other server at the time you want to migrate.
Something like an independent third party data bank that saves profile data? So your user data would be publicly accessible - any server can access it to populate your profile on that server - but nobody can update or delete it but you?
Shit, have we found an actual use case for blockchain?
Nope, that could still be done with a regular database. Blockchain has no practical use case.
I’m as anti crypto rugpull nft bullshit web 3.0 is gonna be uuuuge bro i swear bro where are you going bro as much as the next person buuuuut…cryptocurrency is a godsend in shithole countries such as mine where the local currency is a joke and and possession of any non local currency is illegal
deleted by creator
Nah, There’s other ways to store data while preserving confidentiality, integrity and availability that isn’t on the blockchain. Besides A public ledger connected to a specific profile could make it easier for the profile to be doxxed/fingerprinted.
Spitballing here but a service using simple key-pairs might be a better way to do this.
• Users generate a key pair client-side.
• Public key is stored on the server, acting as the user’s identity.
• To update their profile, users sign the request with their private key. (Data is signed/verified client side before submission)
• The server verifies the signature using the stored public key before edits can be made.
Because data signature/verification are done client side theoretically you don’t need a ledger, your client can enforce profile state. (Maybe an HMAC is sent with the verified data and there reverted periodically by the client)
You guys are re-inventing self sovereign IDs
Just public key cryptography. All your actual posts and comment history are already shared. What is missing is a way to authenticate yourself to anyone but your home server. If the protocol included every profile having a public key, you could then use that to authenticate to any server. And managing that private key is no more complicated than managing your private key in a block chain context.
Non public info like subscriptions is a bit more complicated, because there is an actual policy question of who you share it with. You would either need to make it publicly available, keep a copy yourself, or have your home instance give it to you/the other server at the time you want to migrate.