6

On July 21, the swe subdomain was added for Software Engineering, making swe.stackexchange.com a redirect to softwareengineering.stackexchange.com. Now that there is a shorter URL, this should be the URL that appears when using the share button on posts.

Doc Brown points out that one use case for this is when including links to other questions or answers in text length-constrained fields, such as comments on the SE network. Comments are limited to 600 characters, so eliminating 16 characters from the URL automatically would give commenters extra space.

6
  • Not seeing much being done about this. Is there a form to fill out or a street to protest on?
    – candied_orange
    Oct 4, 2022 at 20:07
  • @candied_orange The status-review tag should put it in a queue for review. Tomorrow, I'll ping someone on the CM team to see what the deal is if they don't respond before then.
    – Thomas Owens Mod
    Oct 4, 2022 at 20:24
  • Thank goodness. This is not protest friendly weather.
    – candied_orange
    Oct 4, 2022 at 20:53
  • @Thomas, is this still under review? Or do we have some action (or inaction!) on its way?
    – Toby Speight
    Dec 1, 2022 at 9:36
  • 1
    @TobySpeight I will follow up. The status-review tag should put it up for review, so I'd have expected at least a comment from staff by now.
    – Thomas Owens Mod
    Dec 1, 2022 at 10:24
  • 3
    Since the functionality isn't broken, this rates relatively low in the priority scale, and is in our backlog. Updated the status tag to reflect that.
    – JNat StaffMod
    Dec 5, 2022 at 12:59

2 Answers 2

Reset to default
5

While we're at it can we do the same for meta share links? Likely first need to get its certificate worked out so that

https://meta.swe.stackexchange.com/a/9397#comment28925_9397

will work as well as

http://meta.swe.stackexchange.com/a/9397#comment28925_9397

does. Maybe also get it to stop striping out the comment info.

3
  • If the redirect is losing fragment identifiers, that's not something the server can fix - those are entirely client-side.
    – Toby Speight
    Dec 1, 2022 at 9:37
  • @TobySpeight doesn't the client-side code I run come from the server? Or are you trying to say it's a bug in my browsers code?
    – candied_orange
    Dec 1, 2022 at 22:21
  • I assumed that the redirection is a HTTP 301 response (Moved Permanently), rather than some client-side script, so that it will work for everyone, rather than just those willing to enable scripts. That shouldn't cause loss of the fragment identifier, if your browser is behaving. If my assumption is wrong, I'll sit corrected....
    – Toby Speight
    Dec 2, 2022 at 7:33
3

Thus I vote to make the code monkey1 change this once to save the multitude from changing it every time.

You must log in to answer this question.

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