3 ms·

Since there's a lot of discussion about the Public Suffix list, let me point out that it's not just a webform where you can add any domain. There's a whole appr

Since there's a lot of discussion about the Public Suffix list, let me point out that it's not just a webform where you can add any domain. There's a whole approval process where one very important criterion is that the domain to be added has a large enough user base. When you have a large enough user base, you generally have scammers as well. That's what happened here. It basically goes: growing user base -> growing amount of malicious content -> ability to submit domain to PSL. In that order, more or less. In terms of security, for me, there's no issue with being on the same domain as my users. My cookies are scoped to my own subdomain, and HTTPS only. For me, being blocked was the only problem, one that I can honestly admit was way bigger than I thought. Hence, the PSA. :)

lucb1e 1y ago
What sort of size would be needed to get on there? My open source project has some daily users, but not thousands. Plenty to attract malicious content, I think a lot of people are sending it to themselves though (like onto a malware analysis VM that is firewalled off and so they look for a public website to do the transfer), but even then the content will be on the site for a few hours. After >10 years of hosting this, someone seems to have fed a page into a virus scanner and now I'm getting blocks left and right with no end in sight. I'd be happy to give every user a unique subdomain instead of short links on the main domain, and then put the root on the PSL, if that's what solves this
- ericselin 1y ago
  Based on what I've seen, there's no way to get that project into the PSL. I would recommend you to have the content available at projectcontent.com if the main site is project.com, though. :)
- mh- 1y ago
  > [..] projects not serving more then (sic) thousands of users are quite likely to be declined. from PSL's GitHub repo's wiki [0]. [0]: https://github.com/publicsuffix/list/wiki/Guidelines#validation-and-non-acceptance-factors https://github.com/publicsuffix/list/wiki/Guidelines#validat...
bawolff 1y ago
> My cookies are scoped to my own subdomain If you mean with the domain option, that's not really sufficient. You need to use the Host- prefix

lucb1e 1y ago

What sort of size would be needed to get on there? My open source project has some daily users, but not thousands. Plenty to attract malicious content, I think a lot of people are sending it to themselves though (like onto a malware analysis VM that is firewalled off and so they look for a public website to do the transfer), but even then the content will be on the site for a few hours. After >10 years of hosting this, someone seems to have fed a page into a virus scanner and now I'm getting blocks left and right with no end in sight. I'd be happy to give every user a unique subdomain instead of short links on the main domain, and then put the root on the PSL, if that's what solves this

ericselin 1y ago
Based on what I've seen, there's no way to get that project into the PSL. I would recommend you to have the content available at projectcontent.com if the main site is project.com, though. :)
mh- 1y ago
> [..] projects not serving more then (sic) thousands of users are quite likely to be declined. from PSL's GitHub repo's wiki [0]. [0]: https://github.com/publicsuffix/list/wiki/Guidelines#validation-and-non-acceptance-factors https://github.com/publicsuffix/list/wiki/Guidelines#validat...

bawolff 1y ago

> My cookies are scoped to my own subdomain If you mean with the domain option, that's not really sufficient. You need to use the Host- prefix