[jeshin]

if there's one thing I hate, it's websites "supporting" tor by redirecting from a specific article to the main page of their (in this case non-functional) onion URL.

twitter did this too a while back, they made a big show of how they're supporting tor now, and now whenever i click a link to a tweet via tor, it redirects me to their frontpage.

thanks, can you stop supporting tor now please, so I can use the site with tor again?

[Syonyk]

You know, I don't think I tested specific pages when I put the Tor meta support in. That's a fairly recent addition I was messing around with.

It's a '<meta http-equiv="onion-location"' tag, and it points to the base URL even on the blog pages. I'll get that fixed to point to the actual page of interest (should be easy enough in Jekyll to just re-render things). It's handled client side in your browser, so you should be able to tell the browser to ignore that.l

But as far as I can tell, the Onion address is up and operating.

[jeshin]

Yes, unfortunately this is often the case. people who don't really use or test the site in tor put in some half-baked support and it just ends up making things worse. But my grievances aside (and please don't take this personally, it's just an issue that I've encountered one too many times, so it gets on my nerves), thank you for fixing it, and indeed it looks like the onion URL is now online, it wasn't working for me earlier.

[Syonyk]

I very much appreciate it - as I said, it was something I'd missed in my dorking around with Tor. No idea why it was down earlier, unless it was just loaded - I haven't changed anything on the server related to Tor in a while.

It seems any time a post of mine makes the HN rounds, I get some other weird corner case of my site pointed out, and it does improve things over time! Jekyll makes it easy to just re-render the site with changes like this too.

[Syonyk]

I think it's fixed now. The meta onion-location line is now pointing to the specific page, not the base website, and Whonix does the redirect to the proper page now.

I'd missed that in testing - I went to the root domain, and it redirected properly and let me browse to pages, but I never went directly to a post, on a browser that wasn't already aware of the redirect. Thank you so much for pointing that out!