3 replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
source | link

You are not pasting in a valid URL; although browser location bars may decode UTF-8 bytes for you, the proper way to encode those links is:

httphttps://meta.stackexchange.com/questions/203129/my-question-was-deleted-by-community%E2%99%A6
httphttps://meta.stackexchange.com/questions/99672/community-%E2%99%A6-should-discriminate-more-when-bumping-unanswered-questions
httphttps://meta.stackexchange.com/questions/238644/users-who-cant-write-good-posts-%E2%89%A0-users-who-want-to-write-good-posts

Note the %E2%99%A6 three-byte UTF-8 encoding for the diamond, or the %E2%89%A0 encoding not-equals (≠). I got these URLs simply by copying from the Chrome location bar, and they work as expected:

The URL parser is correctly not including the non-encoded diamond character in the URL, because valid URLs simply cannot include them.

You are not pasting in a valid URL; although browser location bars may decode UTF-8 bytes for you, the proper way to encode those links is:

http://meta.stackexchange.com/questions/203129/my-question-was-deleted-by-community%E2%99%A6
http://meta.stackexchange.com/questions/99672/community-%E2%99%A6-should-discriminate-more-when-bumping-unanswered-questions
http://meta.stackexchange.com/questions/238644/users-who-cant-write-good-posts-%E2%89%A0-users-who-want-to-write-good-posts

Note the %E2%99%A6 three-byte UTF-8 encoding for the diamond, or the %E2%89%A0 encoding not-equals (≠). I got these URLs simply by copying from the Chrome location bar, and they work as expected:

The URL parser is correctly not including the non-encoded diamond character in the URL, because valid URLs simply cannot include them.

You are not pasting in a valid URL; although browser location bars may decode UTF-8 bytes for you, the proper way to encode those links is:

https://meta.stackexchange.com/questions/203129/my-question-was-deleted-by-community%E2%99%A6
https://meta.stackexchange.com/questions/99672/community-%E2%99%A6-should-discriminate-more-when-bumping-unanswered-questions
https://meta.stackexchange.com/questions/238644/users-who-cant-write-good-posts-%E2%89%A0-users-who-want-to-write-good-posts

Note the %E2%99%A6 three-byte UTF-8 encoding for the diamond, or the %E2%89%A0 encoding not-equals (≠). I got these URLs simply by copying from the Chrome location bar, and they work as expected:

The URL parser is correctly not including the non-encoded diamond character in the URL, because valid URLs simply cannot include them.

2 added 299 characters in body
source | link

You are not pasting in a valid URL; although browser location bars may decode UTF-8 bytes for you, the proper way to encode those links is:

http://meta.stackexchange.com/questions/203129/my-question-was-deleted-by-community%E2%99%A6
http://meta.stackexchange.com/questions/99672/community-%E2%99%A6-should-discriminate-more-when-bumping-unanswered-questions
http://meta.stackexchange.com/questions/238644/users-who-cant-write-good-posts-%E2%89%A0-users-who-want-to-write-good-posts

http://meta.stackexchange.com/questions/99672/community-%E2%99%A6-should-discriminate-more-when-bumping-unanswered-questions

Note the %E2%99%A6 three-byte UTF-8 encoding for the diamond, or the %E2%89%A0 encoding not-equals (≠). I got these URLs simply by copying from the Chrome location bar, and they work as expected:

The URL parser is correctly not including the non-encoded diamond character in the URL, because valid URLs simply cannot include them.

You are not pasting in a valid URL; although browser location bars may decode UTF-8 bytes for you, the proper way to encode those links is:

http://meta.stackexchange.com/questions/203129/my-question-was-deleted-by-community%E2%99%A6

http://meta.stackexchange.com/questions/99672/community-%E2%99%A6-should-discriminate-more-when-bumping-unanswered-questions

Note the %E2%99%A6 three-byte UTF-8 encoding for the diamond. I got these URLs simply by copying from the Chrome location bar, and they work as expected:

The URL parser is correctly not including the non-encoded diamond character in the URL, because valid URLs simply cannot include them.

You are not pasting in a valid URL; although browser location bars may decode UTF-8 bytes for you, the proper way to encode those links is:

http://meta.stackexchange.com/questions/203129/my-question-was-deleted-by-community%E2%99%A6
http://meta.stackexchange.com/questions/99672/community-%E2%99%A6-should-discriminate-more-when-bumping-unanswered-questions
http://meta.stackexchange.com/questions/238644/users-who-cant-write-good-posts-%E2%89%A0-users-who-want-to-write-good-posts

Note the %E2%99%A6 three-byte UTF-8 encoding for the diamond, or the %E2%89%A0 encoding not-equals (≠). I got these URLs simply by copying from the Chrome location bar, and they work as expected:

The URL parser is correctly not including the non-encoded diamond character in the URL, because valid URLs simply cannot include them.

1
source | link

You are not pasting in a valid URL; although browser location bars may decode UTF-8 bytes for you, the proper way to encode those links is:

http://meta.stackexchange.com/questions/203129/my-question-was-deleted-by-community%E2%99%A6

http://meta.stackexchange.com/questions/99672/community-%E2%99%A6-should-discriminate-more-when-bumping-unanswered-questions

Note the %E2%99%A6 three-byte UTF-8 encoding for the diamond. I got these URLs simply by copying from the Chrome location bar, and they work as expected:

The URL parser is correctly not including the non-encoded diamond character in the URL, because valid URLs simply cannot include them.