3 ms·

Have you never lost a private key? I definitely lost the private key to my original PGP key. And I wouldn't say "nobody can ban you" - quite the opposite, in f

• Mediterraneo10 5y ago
  > Have you never lost a private key? I definitely lost the private key to my original PGP key. For nearly twenty years now, PGP tutorials have often explained the importance of printing out a copy of your private key in a special OCR-readable font, and putting that in a safe place. Then you won't risk losing your private key even if all the devices it was stored on perish.
• fvdessen 5y ago
  > And I wouldn't say "nobody can ban you" [...] And the obvious end state is for a setup like Mastodon It is indeed quite similar to mastodon in the sense that other instances can ban you. The difference is that in mastodon your identity is usually located on an instance, and if that instance bans you, you lose your identity. In Urbit every identity has its own instance so your personal contact list will still be able to reach you. Of course requiring everybody to run its own instance adds quite some friction for user onboarding, but that is an issue with the urbit network, not with the identity layer. You could imagine having your identity and linking it to a hosted instance, and later switch instance if the needs arise. This is what I like about the idea of having your identity as a NFT, but clearly the way urbit currently uses it does not exploit the full potential of the idea. As for losing your keys, if such a system would become widespread, most people would chose to have their keys hosted on a third party service, and only people who really care about maintaining full ownership would keep the keys to themselves.
  • geofft 5y ago
    First off, I'm talking about the case where Mastodon instances collectively ban an instance, not a user. It's pretty easy to set up your own Mastodon instance, and in turn, norms and mechanisms have arisen for coordinated banning of instances with unwanted behavior. Second, if you choose to keep your keys on a third-party service, then that third-party service can ban you.
    • samatman 5y ago
      This is a big part of the point of urbit: there is no difference between an instance and a user. If a star or galaxy wants to refuse to route to a planet, they can. A planet can then look for another star or galaxy which will route packets for them. Also, if a planet ends up on another planet's personal banlist, that's it: the identities are durable and immutable, no amount of moving around will evade the ban. The annoying user has to either buy a new planet or make a comet. It remains to be tried at scale, but urbit was carefully designed to solve some of the problems Curtis encountered with Usenet, back at the dawn of time. It might work, we'll see.
      • geofft 5y ago
        Still not following how this is different from Mastodon. Some users run their own instance (= planet), which cannot be "banned" by ordinary Mastodon means; you can only refuse to peer with it. Some users have accounts on someone else's instance, which can be banned by the admin of the instance. If you start tooting, I dunno, reactionary pro-slavery nonsense that takes asymmetrically more effort to refute than to claim, there's pressure on the instance admin to ban you, and there's a means for unpeering the instance if they refuse o if you are the instance admin. Sure, this isn't protocol-wide, and you can find your own reactionary buddies and whine about how you'd be treated more fairly under monarchism if you want, but you're cut off from large parts of the network. What's different about the outcome under Urbit? And if it is different, I don't know that a system that is carefully designed to solve the "problems" of someone who generally should be banned for good reason is what most of is want.