5 ms·
Except of course when for whaetever reason you won't be able to pay your DNS provider for some time, and you'll lose your identity to someone else. DNS is real
by tsimionescu 3y ago
Except of course when for whaetever reason you won't be able to pay your DNS provider for some time, and you'll lose your identity to someone else.
DNS is really not a good platform to build personal identity on.
- XorNot 3y agoConversely it is a good - or at least adequate - platform for businesses to build their identity on. But I don't know if this is being imagined as "how businesses will communicate on our platform" or it is being treated as "regular users will totally manage their own DNS".
- anderspitman 3y agoWhile there's some truth to this, it's more of an incidental problem with DNS than an intrinsic one. There's nothing preventing registrars from simplifying their UX to target average customers, including multi-year registrations and ample warning systems.
- tsimionescu 3y agoNo, it's really a fundamental problem with DNS. Owning a DNS name is, by design, a temporary deal. Ultimately the domain name system is meant to help give a user-readable name to your IP, not to establish your identity for your entire life.
- guraf 3y agoYou've left 12 comments on this thread. In all of them you're very confident about your superior understanding. And yet you seem to be really confused about the difference between DNS and a domain name registration. Curious.
- tsimionescu 3y agoCare to point out what confusion you think I'm making, instead of snidely implying I have no idea what I'm talking about?
- haakon 3y agoDomain names can also be taken from you if your adversaries are powerful enough. It happens regularly to controversial websites.
- grepfru_it 3y agoAs someone who worked in e-commerce with high value brands, this is entirely true. If you even slightly infringe on a brand name, they will throw lawyers at you and the simple threat of bankruptcy will have you handing over the domain. I’ve seen it happen too many times to count.
- notahacker 3y agoNot half as easily as social media handles though...
- rmuratov 3y agoWhat is good? Public GPG keys?
- politician 3y agoThe identity layer should be built as a blockchain. Ignore the cryptocurrency connection, focus on the distributed decentralized identity ledger.
- starttoaster 3y agoBlockchain does not by itself solve identity. You can build identity solutions atop a blockchain, sure. But “built as a blockchain” does not at all hint towards your blueprint to solving this problem.
- Karrot_Kream 3y agoThat's the same for other alternative distributed name systems like DHT based naming. For example, how should the DHT be bootstrapped, should there be any universal root zones, etc etc. GNS and IPNS are both DHT based naming systems which make different choices, much like there are various blockchain based naming systems out there. Anyway my understanding is that Bluesky uses DIDs for exactly that reason, to punt the actual naming implementation and avoid silly internet fights like this.
- SkyMarshal 3y agoYou can’t ignore the cryptocurrency layer, it’s required to fund the miners/validators who secure and run the chain. Blockchains don’t work without the cryptocurrency. And there’s already at least one blockchain purpose-built for naming - https://handshake.org/ https://handshake.org/. Worth reading their design notes on how and why it works as it does.
- tsimionescu 3y agoThe only stable life-long identity system I know of are state-assigned identities (with the court system as a last line for complex cases). Apart from that, I think per-service identities are the best that can be hoped for. If I choose to engage with Facebook, I have to trust them to some extent anyway, so trusting them with my identity on Facebook is probably good enough. If I want to establish that some Twitter identity is the same as some Instagram identity, I can do so by directly referencing them from one another. I don't think we can do much better than that without involving the state.
- devjab 3y agoI think you can come up with a range of issues as to how this will eventually fail for some people, but what is a better alternative?
- Karrot_Kream 3y agoDHT based naming systems (GNS, IPNS, Tor Onion names), Blockchain based naming systems, Web-of-Trust style naming, there's lots out there.
- didntcheck 3y agoRelevent concept: Zooko's Triangle [1]: it's hard to have a naming system which is decentralised and secure against spoofing without giving you long and random (or hashed) names, like with .onion services [1] https://en.wikipedia.org/wiki/Zooko%27s_triangle https://en.wikipedia.org/wiki/Zooko%27s_triangle
- tsimionescu 3y agoPer-service identities, as we have them right now. Alternatively, government issued and policed identities.
- eddythompson80 3y agoDNS is good enough for companies, governments, schools, organizations, military etc. Not to mention that most other identities are tied to a DNS identity of some sort. Sure it’s not ideal as something completely trust less and distribute like PGP, but it’s been 33 years and no one can come up with a decent UX for that because it’s not really possible. $8 a year is a barrier to entry, especially if you consider people in economies where that’s significant. But that’s when you tie your identity to someone else like gmail.com or yahoo.com or bsky.social. When you can afford it, you get to manage your own. it’s good enough.
- tsimionescu 3y agoYes, DNS is good enough for organizations (though I should note that governments don't rely on DNS registrars, they run their own). The crucial difference is that organizations can hire people to care about those things, or hire lawyers to ensure they can be recovered if accidentally lost. And in fact many of these organizations change domains in the longer run for various reasons. So even there, DNS is often only used as a solution to identity at one point in time, it's not meant as a permanent solution for the entire life of an organization. For individuals, the cost of losing your domain is far too high if it means losing your identity on multiple services at the same time. And, if nothing else, people eventually die, so domains will be lost by their original owner and then re-used, breaking the notion of identity again in the longer run.
- anileated 3y agoThere can be two kinds of identities: your actual legal one and ones you should be okay with losing. People keep devising more and more involved ways to maintain identities other than your legal one, but if you think about it you can still lose any of those ways (your domain name, your private key, etc.) and in the end no one should use them for anything serious.
- cout 3y agoIdentity also needs to be hard to copy (which is the main reason e.g. you would not want to use your a hash of your DNA as an identity -- it would be hard to lose but easy to copy).
- agentgumshoe 3y agoOr what if your name is John Smith? do you long for the days of being permanently known as JohnSmith21048
- deleted 3y ago[deleted]
- RestlessMind 3y agodevjab is saying how having identity based on domain names you own is better than identity based on server instances (or centralized social media providers like FB, Google etc). You haven't really refuted their point, which still stands in spite of risk of losing your domain if you don't pay in time. Btw, do you have a better proposal to mitigate the risk of failure to renew domain registration in time?
- tsimionescu 3y agoThe status right now is that you have one identity for each service you interact with. If that service decides to ban you or goes down or you get your identity stolen, you lose that identity, but keep your identity on all of the other services you use. In the worse case, if you didn't tell people about your other identities ahead of time, they may still search for you and find you somewhere else. If several services recognized your identity by virtue of having the same domain name, the fallout from losing that identity is much worse: you lose access to all these services at once, and whoever gets the domain name next will gain access to all of your followers and have a pre-built history. And if one service decides to ban you, you'll be exactly where you were if your identity was specific to that service. So, with DNS-based cross-service identities, you are at best in the same place as having service-specific identities, and at worse, much worse off. Additionally, a service which bans your account will typically not give the same name to a new user, or, even if they do, they will still separate the two identities / cleanup all previous posts. A DNS registrar will absolutely give the same domain to someone else if you stop paying for it, and any services which recognize that as your identity may not even know that a change in ownership has taken place.