ICANN's position is that their policy is triggered by changes to ISO-3166. The code SU has not been removed from ISO-3166-2; instead it is "exceptionally reserved" (as is the code UK).
If the standards committee takes the same approach with IO, then it's possible that gives ICANN a route not to apply this policy. However, if IO is deleted completely, then my reading is the policy would apply.
I use a .io domain for some of my email. I’m starting to think I should divest and change my email everywhere instead of continuing to add more places to it. And worry about monitoring for a potential future shutdown.
Luckily, since I used a custom address for each place I used it (so I could track and block spam easily), I kept a spreadsheet of every site I used it with. 55 sites so far and I haven’t had to block anything for being sold, so it hasn’t really been that useful so far.
I have it setup in Proton where anything sent my domain goes to my inbox. So I write it down to keep track, just for my own knowledge of what I used (but it’s not technically needed). The nice thing is I don’t have to set anything up before I start to use it. I can just type sitename@mydomain.io and it shows up in my inbox, which has made it very low maintenance. I tried to setup aliases in the past and it became more work than I wanted.
The idea was if I got spam, I’d know who not to trust in the future, and could easily send anything to that address to spam/trash.
I use a password manager as well, and have all the accounts tagged in there as well. The spreadsheet was basically a backup, and for if I gave an email address out that wasn’t actually tied to an account I’d have a password for.
.su still exists, so there's precedent for keeping a "legacy" ccTLD of a non-existing entity.
ICANN's position is that their policy is triggered by changes to ISO-3166. The code SU has not been removed from ISO-3166-2; instead it is "exceptionally reserved" (as is the code UK).
If the standards committee takes the same approach with IO, then it's possible that gives ICANN a route not to apply this policy. However, if IO is deleted completely, then my reading is the policy would apply.
I use a .io domain for some of my email. I’m starting to think I should divest and change my email everywhere instead of continuing to add more places to it. And worry about monitoring for a potential future shutdown.
Luckily, since I used a custom address for each place I used it (so I could track and block spam easily), I kept a spreadsheet of every site I used it with. 55 sites so far and I haven’t had to block anything for being sold, so it hasn’t really been that useful so far.
Same here.
Luckily, tho, I use alias from my mail provider, so I don't have to write them down.
Also, a password manager, so it won't be too much work changing my E-Mail Domain Name.
But it's still unfortunate. It's just a ccTLD what does it matter, let us keep it.
I have it setup in Proton where anything sent my domain goes to my inbox. So I write it down to keep track, just for my own knowledge of what I used (but it’s not technically needed). The nice thing is I don’t have to set anything up before I start to use it. I can just type sitename@mydomain.io and it shows up in my inbox, which has made it very low maintenance. I tried to setup aliases in the past and it became more work than I wanted.
The idea was if I got spam, I’d know who not to trust in the future, and could easily send anything to that address to spam/trash.
I use a password manager as well, and have all the accounts tagged in there as well. The spreadsheet was basically a backup, and for if I gave an email address out that wasn’t actually tied to an account I’d have a password for.