Reply 640 of 648, by Zilch
I noticed there are AI bots on Vogons. I'm guessing those are allowed?
I noticed there are AI bots on Vogons. I'm guessing those are allowed?
Has Vogons recently changed its bookmarks policy? I have a lot of bookmarks to threads I felt were important for me that are now broken. I get a Mac classic screen with the error message "Sorry, you are not authorized to view this page". I can still find the post using search. I bookmark that page, and when I open a new browser window and go to that bookmark - same error.
leonk wrote on 2025-10-24, 16:25:Has Vogons recently changed its bookmarks policy? I have a lot of bookmarks to threads I felt were important for me that are now broken. I get a Mac classic screen with the error message "Sorry, you are not authorized to view this page". I can still find the post using search. I bookmark that page, and when I open a new browser window and go to that bookmark - same error.
I just checked some of my old bookmarks and they seem to be working fine in Firefox on Windows 10. I can make new bookmarks and open them right up as normal too.
Have you made any changes involving DNS, VPN or ad blockers?
Can you post a link to one of the threads that is doing this?
Might be worth trying a different browser too to narrow down the cause.
You're right. For some reason it works fine in Safari and Firefox, but fails in Chrome. Here's an example: PS/2 to Microsoft Serialmouse Adapter Converter / Updated First Post / Firmware Update added
I figured it out. For some reason, Vogon's web server is set to throw 403 errors when requests come in with User agent set to chrome. In particular, it doesn't like the following string (in bold). If I remove it, it works fine: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36
Other user agents work perfectly fine:
firefox: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:70.0) Gecko/20100101 Firefox/70.0
Safari: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.3 Safari/605.1.15
I believe this is a configuration issue on the server site that only admins can look into. If I change the word Chrome with anything else, it works fine.
It seems the page index for "Your posts" is broken. Can't remember when this started to happen, but I think it's fairly recent.
While the "Your posts" page itself is okay, pressing a page number (including "jump to page" option) will now go to a search page listing all my previous posts, rather than threads that I've posted in.
"Active topics" is fine, however.
LSS10999 wrote on Today, 05:18:It seems the page index for "Your posts" is broken. Can't remember when this started to happen, but I think it's fairly recent.
While the "Your posts" page itself is okay, pressing a page number (including "jump to page" option) will now go to a search page listing all my previous posts, rather than threads that I've posted in.
"Active topics" is fine, however.
Odd, I do not experience the behaviour that you describe.
Right to repair is fundamental. You own it, you're allowed to fix it.
How To Ask Questions The Smart Way
Do not ask Why !
https://www.vogonswiki.com/index.php/Serial_port
LSS10999 wrote on Today, 05:18:It seems the page index for "Your posts" is broken. Can't remember when this started to happen, but I think it's fairly recent.
While the "Your posts" page itself is okay, pressing a page number (including "jump to page" option) will now go to a search page listing all my previous posts, rather than threads that I've posted in.
"Active topics" is fine, however.
Weird. Mine isn't doing that.
I would try logging out and deleting cookies for vogons, then try it again.
weedeewee wrote on Today, 05:33:Odd, I do not experience the behaviour that you describe.
Ozzuneoj wrote on Today, 05:49:Weird. Mine isn't doing that.
I would try logging out and deleting cookies for vogons, then try it again.
I guess something's wrong with my browser setup. The system showing this behavior is using Chromium, and the user agent reads Chrome.
I just tested on a different system with Firefox (LibreWolf to be precise) and the page works fine.
EDIT: Yep. I guess it's indeed specific to my current Chromium environment. With Firefox everything's good.