-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove www. from domain names (at least in viewer) #532
Comments
Can't you use the search box, though? |
Nevermind, saw the context in #archiveteam-bs. The problem with this is that www. is sometimes different from "normal". It's not common, but I've seen it before, although I can't remember what website it was (some type of forum). Non-www was a home page with a link to both the English one, and the www one (I don't remember what language the www one was, but it wasn't English). Something like that, at least. But, if you are just suggesting that www.fanfiction.net should also be under F in addition to W, I think that would be OK. Maybe a maintainer can say whether this is doable. :-) |
Working protocol/subdomain difference examples (as of 2022-12-10 20:38:17 UTC):
Minor page difference example (working as of 2022-12-10 20:38:17 UTC):
I know there are other instances of this—some returning vastly different pages or redirecting to other domains—but no further examples come to mind at the moment. I will update this message when I come across more (if I remember to do so, that is, haha). To add further insult to injury, I have come across instances of prefixes such as
I, too, agree with this implementation. |
When browsing for an archived website here: https://archive.fart.website/archivebot/viewer/domains/ -- I didn't expect "fanfiction.net" to be under "www.fanfiction.net".
www
is the equivalent of "the" in a title -- it shouldn't be used in an index as it's not really part of the website's canonical name. Is it possible this might be implemented in the viewer only, with no other code changes required? Or whichever solution is best.The text was updated successfully, but these errors were encountered: