Lewis Goddard

It's probably intertwined with the outdated base and outdated node and npm all on that platform.

I agree, this doesn't technically generate any new server workload, just different work.

That would require additional server-side logic, I think. It would certainly be possible though.

We should still be able to redirect from the hashed links to the correct page, no?

I understand that, but a javascript snippet to redirect shouldn't be difficult. It only needs to be on the homepage.

To redirect: `/#!api=gtk+-3.0/index` to `/gtk+-3.0/index` and `/#!wiki=gtk+-3.0/index` to `/gtk+-3.0/index` ``` window.addEventListener('load', function() { if ( location.hash.substr(2, 3) == 'api' || location.hash.substr(2, 4) == 'wiki' ) { redirect_to = location.hash.split('=') location...

@ZanderBrown My thought was that way whatever that first string is you just have to check for it, makes it easier to add new possibilities in case we missed any.

I don't believe moderators have the ability to enable this, it is likely rolled out by StackExchange themselves.

I can only make this happen in Firefox and Edge by letting the page load and then trying to load the page again with the hash. We don't even expose...

I believe I am now having the same problem, I don't suppose you managed to fix this? Workflow file: https://github.com/elementary/flatpak-platform/actions/runs/3382649846/workflow#L98 Similar issue: https://gitlab.gnome.org/GNOME/gnome-build-meta/-/issues/335 Relevant source ? https://github.com/flatpak/flat-manager/blob/master/flat-manager-client#L465