Revisions to data.stackexchange.com site URLs contain spaces

replaced http://data.stackexchange.com/ with https://data.stackexchange.com/

Source Link

edited Jan 18, 2021 at 12:14

Swapping the spaces out for _'s
Using the SE sub-site's sub-domain name instead (i.e., httphttps://data.stackexchange.com/diy/queries) instead
Removing the spaces, like httphttps://data.stackexchange.com/theoreticalcomputerscience/queries and all but one :s of the meta http://data.stackexchange.com sections

Swapping the spaces out for _'s
Using the SE sub-site's sub-domain name instead (i.e., http://data.stackexchange.com/diy/queries) instead
Removing the spaces, like http://data.stackexchange.com/theoreticalcomputerscience/queries and all but one :s of the meta http://data.stackexchange.com sections

Perhaps having the metas indented under their respective sites. They might be easier to find, if nothing else.
Not sure why http://data.stackexchange.com/mathematica%20meta/queries has a space, while other metas don't
Not sure why http://data.stackexchange.com/christianity%20stack%20exchange/queries or http://data.stackexchange.com/christianity%20meta%20stack%20exchange/queries has Stack Exchange suffixed to it

Swapping the spaces out for _'s
Using the SE sub-site's sub-domain name instead (i.e., https://data.stackexchange.com/diy/queries) instead
Removing the spaces, like https://data.stackexchange.com/theoreticalcomputerscience/queries and all but one :s of the meta http://data.stackexchange.com sections

Perhaps having the metas indented under their respective sites. They might be easier to find, if nothing else.
Not sure why https://data.stackexchange.com/mathematica%20meta/queries has a space, while other metas don't
Not sure why https://data.stackexchange.com/christianity%20stack%20exchange/queries or https://data.stackexchange.com/christianity%20meta%20stack%20exchange/queries has Stack Exchange suffixed to it

replaced http://stackoverflow.com/ with https://stackoverflow.com/

Source Link

edited May 23, 2017 at 12:36

In order to get these to display unescaped, without an unsightly (i.m.o.) %20 (or similar) in them, it seems the only option is to use the [1] and [1]: structure the [1] and [1]: structure (Like in Search comments, from other commentors; on question/answers you authored, or have commented on), which I feel creates unnecessary overhead for more people than a change to the URLs that SE control, that could be made:

In order to get these to display unescaped, without an unsightly (i.m.o.) %20 (or similar) in them, it seems the only option is to use the [1] and [1]: structure (Like in Search comments, from other commentors; on question/answers you authored, or have commented on), which I feel creates unnecessary overhead for more people than a change to the URLs that SE control, that could be made:

replaced http://meta.unix.stackexchange.com/ with https://unix.meta.stackexchange.com/

Source Link

edited Mar 16, 2017 at 15:45

In order to get these to display unescaped, without an unsightly (i.m.o.) %20 (or similar) in them, it seems the only option is to use the [1] and [1]: structure (Like in http://meta.unix.stackexchange.com/questions/1403/search-comments-from-other-commentors-on-question-answers-you-authored-or-hav Search comments, from other commentors; on question/answers you authored, or have commented on), which I feel creates unnecessary overhead for more people than a change to the URLs that SE control, that could be made:

In order to get these to display unescaped, without an unsightly (i.m.o.) %20 (or similar) in them, it seems the only option is to use the [1] and [1]: structure (Like in http://meta.unix.stackexchange.com/questions/1403/search-comments-from-other-commentors-on-question-answers-you-authored-or-hav), which I feel creates unnecessary overhead for more people than a change to the URLs that SE control, that could be made:

In order to get these to display unescaped, without an unsightly (i.m.o.) %20 (or similar) in them, it seems the only option is to use the [1] and [1]: structure (Like in Search comments, from other commentors; on question/answers you authored, or have commented on), which I feel creates unnecessary overhead for more people than a change to the URLs that SE control, that could be made: