3 ms·

I tried it. The url I got looked like guid.domain.net. At first I was thinking that the guid part must be unique for every user, but then the domain.net part is

I tried it. The url I got looked like guid.domain.net. At first I was thinking that the guid part must be unique for every user, but then the domain.net part is still susceptible to being seized. So… without being able to compare the url I got with other people, I’m left wondering how this actually works.

deleted 4y ago
[deleted]
BHSPitMonkey 4y ago
FTA: "The domain names in question are subdomains of newly registered TLDs that rely on different domain name registries." There are multiple TLDs/SLDs involved (and the pool will likely grow over time)
dkjaudyeqooe 4y ago
> domain.net part is still susceptible to being seized Yes it is, but how do you discover the domains? There could be just a few hundred users per domain. Then you have to expend substantial effort to seize each domain. Meanwhile any affected user just moves to their second domain. Even if the authorities got much better at taking down domains the only issue would be increasing the number of extra domains per user. I can't see how the authorities can beat this.
- stevenhuang 4y ago
  I had to use https://singlelogin.me/ https://singlelogin.me/ for it to generate the special domain, so can't the central https://singlelogin.me/ https://singlelogin.me/ domain be seized at some point?
  - esposm03 4y ago
    From the article: > If users can’t access the universal login page, Z-Library says they can log in through TOR or I2P and get their personal clearnet domains there.
  - bogwog 4y ago
    Yeah but that’s only used for creating the unique domain, and it wouldn’t affect user domains. So if that one goes down, they’ll just have throw the registration page up on a new domain.
webmaven 4y ago
> I tried it. The url I got looked like guid.domain.net. At first I was thinking that the guid part must be unique for every user, but then the domain.net part is still susceptible to being seized. The GUID seems to be unique per-user, but also per ccTLD (mine are GUID.DOMAIN.cz and OTHERGUID.DOMAIN.ph). I would guess that the pool of registered DOMAIN.ccTLD will grow faster than they can be blocked or seized, that new user per-domain GUIDs can be issued on demand onto different registered domains, and that there is an unused reserve of registered domains ready for deployment.

deleted 4y ago

[deleted]

BHSPitMonkey 4y ago

FTA: "The domain names in question are subdomains of newly registered TLDs that rely on different domain name registries." There are multiple TLDs/SLDs involved (and the pool will likely grow over time)

dkjaudyeqooe 4y ago

> domain.net part is still susceptible to being seized Yes it is, but how do you discover the domains? There could be just a few hundred users per domain. Then you have to expend substantial effort to seize each domain. Meanwhile any affected user just moves to their second domain. Even if the authorities got much better at taking down domains the only issue would be increasing the number of extra domains per user. I can't see how the authorities can beat this.

stevenhuang 4y ago
I had to use https://singlelogin.me/ https://singlelogin.me/ for it to generate the special domain, so can't the central https://singlelogin.me/ https://singlelogin.me/ domain be seized at some point?
- esposm03 4y ago
  From the article: > If users can’t access the universal login page, Z-Library says they can log in through TOR or I2P and get their personal clearnet domains there.
- bogwog 4y ago
  Yeah but that’s only used for creating the unique domain, and it wouldn’t affect user domains. So if that one goes down, they’ll just have throw the registration page up on a new domain.

webmaven 4y ago

> I tried it. The url I got looked like guid.domain.net. At first I was thinking that the guid part must be unique for every user, but then the domain.net part is still susceptible to being seized. The GUID seems to be unique per-user, but also per ccTLD (mine are GUID.DOMAIN.cz and OTHERGUID.DOMAIN.ph). I would guess that the pool of registered DOMAIN.ccTLD will grow faster than they can be blocked or seized, that new user per-domain GUIDs can be issued on demand onto different registered domains, and that there is an unused reserve of registered domains ready for deployment.