How about Stackexchange?

[r7l]

I've found AnonymousOverflow through Libredirect. But it seems it's limited to Stackoverflow only. Are there any plans to extend it to Stackexchange?

[httpjamesm]

Totally possible since they use the same layouts, but the issue is distinguishing between stack exchange and stack overflow threads.

Both platforms use the same URL path format, so it's a question of the best way to either guess which platform the user wants or give them a choice, which may come off as annoying to some.

[r7l]

You're right. Guessing the platform would probably be hard if not impossible. To make it even worse, they have subdomains on Stackexchange.

[r7l]

Would it possible to add some sort of configuration option if a hosted instance is for Stackexchange or Stackoverflow? So you would have instances handling Stackoverflow and others Stackexchange.

To overcome the issue with subdomains of Stackexchange, you could move them into the path string. So for example a meta.stackexchange.com question would become domain.com/meta/question/....

[httpjamesm]

That's a great idea. I'll implement it soon.

[httpjamesm]

After thinking about it a little, I actually think just creating a /exchange/:sub endpoint would be better.

[httpjamesm]

Version 1.8 has been released with StackExchange support and is deployed on the Whatever Social instance. Let me know if this fits your needs.

Example: https://code.whatever.social/exchange/apple/questions/445555/macbook-pro-2017-folder-when-booting-on-battery-boots-fine-when-connected

[r7l]

Thanks allot for your work! Somehow it does not seem work yet. I see a 404 on the link you've added and i am not able to add any Stackexchange URL into the input bar on the landing site.

[httpjamesm]

Can you send a screenshot of the 404 message? It's working on both my end and others'.

[r7l]

There isn't much to see. It's a blank white page showing only 404 page not found.

The frontpage loads fine. But when entering to the input field, it will show: Error: Invalid stack overflow URL in a orange box above the field.

Both happens on your https://code.whatever.social site.

[r7l]

Not sure if you did something but it works now. Both of it.

[privacytime101]

Hi, we deployed it on a new node yesterday, and I forgot to update it on there just now. The reason why it was working for multiple people was that they were routed to the US server (proximity-based), which was on 1.8. Thanks for reporting this.

[r7l]

Thanks allot! Great work!

On a side note: you may mention Libredirect in your README file as they've implemented your tool already. It's probably easier for most people to use that in their browsers instead of custom redirect scripts as suggested currently.

I'll head over there to inform them about this new feature and have them extend their browser extentions to automatically redirect Stackexchange as well.

[adastx]

How about superuser.com?

For example:
https://superuser.com/questions/769452/what-is-a-openpgp-gnupg-key-id
https://code.whatever.social/superuser/questions/769452/what-is-a-openpgp-gnupg-key-id

seriously why is stack exchange structured like this??

[adastx]

Hey, looking at this again now I'm wondering, why not just implement a
general solution that works across all Stack Exchange Network
sites?

Seems to me like they all use the same format. (question, description,
comments, votes, answers, chosen answer, related, ...)

An example url rewrite could look like:
{instance_url}/{site}/[meta/]{question_id}/{question_title}

So in practice:
https://exchange.adast.xyz/travel/meta/8451/january-2023-photo-competition-new

Or:
https://exchange.adast.xyz/superuser/769452/what-is-a-openpgp-gnupg-key-id

I might be wrong here, but it seems like the /question/ sub-path is kinda
redundant. Also, I'm suggesting that meta sub-domains be handled adding a
/meta/ sub-dir.