|
Notes |
|
|
(0022761)
|
|
Zalewa
|
|
2023-02-12 19:29
|
|
|
|
|
|
|
Is it a good idea to also auto-redirect URL if wadseeker detects the old URL? Incase people had the website configured manually. |
|
|
|
(0022768)
|
|
Zalewa
|
|
2023-02-13 22:24
|
|
Mucking with user choices behind the scenes and making custom exceptions for special cases is not the way I usually like to do thing. I'm considering between not doing it, doing a one-time rewrite of user config on the next update, or on parsing the URLs and aliasing this website when the sites are passed from Doomseeker's config to Wadseeker.
Let me think on that. |
|
|
|
|
Doomseeker should not become an IRC client, a HTTP web proxy, ...
It's up to the webmaster of said domain to do the HTTP redirect. If they can't, sucks to suck, take it as a lesson. |
|
|
|
|
|
A more universal solution which should work with any Doomseeker version too: Use a different DNS resolver (as long as it doesn't conflict with DNSSEC). You might even get a benefit of setting up one for DNS-based adblocking in your private network, if that's your thing. |
|
|
|
|
|
You do rise a good point, Wub, it doesnt feel like it should be doomseeker's department to handle issues like this, since doomseeker is its own project and is not strictly affiliated with TSPG to begin with. I guess its up to yall if its a good idea or not. My concerns were mostly oriented around the end user using doomseeker as the front end of all things zandronum and what would happen if the old domain was snatched up by a malicious actor. |
|
|
|
(0022774)
|
|
Zalewa
|
|
2023-02-14 22:48
|
|
Quote from Necrodoom
What would happen if the old domain was snatched up by a malicious actor
With all the ways the WADs, PK3s and DEHs can be easily and uncontrollably distributed, this has always been a problem, and snatching up a domain doesn't change anything. I think we didn't have a major exploitation by a WAD file only because nobody tried anything with the WADs, yet (or maybe they did and were successful?). doom2.exe certainly has WAD related exploits that permit arbitrary code execution (tip: don't run WADs in doom2.exe, even if it's in Dosbox). Do ports have such exploits?
Quote from Necrodoom
My concerns were mostly oriented around the end user using doomseeker as the front end of all things zandronum
Yes that's my concern too. That's also why Doomseeker offers certain features that would be considered as out-of-scope for a server browser.
But, nevertheless, the problem of a dead WAD site domain is mitigated by the fact that the primary source of WADs for all servers should be the custom URL configured by the server host. If all the hosts who previously referred to the .net domain change the URL to .com, Doomseeker will keep finding the WADs just as well as before. Because of this, and because sites go offline all the time, and also because I have a bad luck for bugging such code I opt to not add the domain translator. |
|
|
|
(0022775)
|
|
Zalewa
|
|
2023-02-15 07:18
|
|
|
I've realized that yet again we're meticulously discussing and picking apart something that should be a simple string replace. Enough. |
|