Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

I can be blamed for trying to use the "website" field in my profile for something not in the web, but currently, if I read "website" as "some personal place in the Internet" and try to set it to my gopherhole URL, gopher://, it is silently accepted but it is stored as http://gopher://, and that is the target of the link in the profile, even if it just reads gopher://….

That's also what it shows when I ask to edit the profile again, so it's not something at visualization level, but something related to parsing when changing the profile that only happens once.

So my question here is whether it is possible to remove this rewriting, so that I — and possibly others (one can dream there are some gopher users out there in SE, right?) — can list my gopherhole as the "personal space out there in the Internet", or whether this can at least be trapped so that people don't end up thinking their non-web URL has been accepted when it was, in fact, interpreted as a HTTP URL.

share|improve this question
Seriously? Are you from the past? Last count I heard was there were under 200 people on the Internet who still ran Gopher servers. Not really worth optimizing for, is it? Yes, a "website" field expects you to enter the URL to a web page. Those communicate using the http protocol. – Cody Gray Mar 20 '12 at 18:23
@CodyGray If I wanted to I could host a web site on the FTP protocol. It's a terrible idea, but the web ≠ HTTP-accessible resources; the web ⊃ HTTP-accessible resources. If that weren't the case, URLs wouldn't be what they are. – Kevin Reid Mar 20 '12 at 20:31
@KevinReid some people see web as serving HTML over HTTP(S), but really, the web is mostly about the hyperlinks and hypertext, not the protocol — you can even serve web pages over gopher. – njsg Mar 20 '12 at 21:13
@CodyGray there's no need to be harsh. It may not be worth optimizing, but I guess it would be a good idea to refuse URLs SO/SE is not willing to support, rather than generating something broken that probably isn't even a valid URL. But don't worry, in the meantime I've hacked some html+http together so I can workaround this kind of issues... – njsg Mar 20 '12 at 21:13
What you call "harsh", I call in good fun. Didn't mean for you to take it that way. The only serious part was I'm not sure this is common enough to be worth much time spent on it. – Cody Gray Mar 21 '12 at 1:58

While I gotta give you props for staying loyal to The Gopher State's offspring, it does say "website" right there next to the field.

You can drop your gopher URL into your bio text if you want, but it won't be hyperlinked (and trying to put it in an <a> tag won't help). While in theory it would be possible to whitelist these, in practice keeping the sanitizer strict solves more problems than it causes.

Light a candle in remembrance of the past, and... Set up a website ;-)

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .