The bug that has fvcked up every demon ridden software

... and has generated millions of broken links, wasting countless human hours, giving a headache even to completely healthy people. It's that simple gentlemen: THE FUCKING PARENTHESIS LINK BUG. LO AND BEHOLD
(I probably would write something like this, with the link in the end: http://bbs.progrider.org/prog/)

Look at this fucking thing. Look at it. Nobody has bothered fixing this fucking bug. Whose c*ck do I have to suck to get this thing fixed once and for all?

https://tools.ietf.org/html/rfc3986

Appendix C. Delimiting a URI in Context

URIs are often transmitted through formats that do not provide a
clear context for their interpretation. For example, there are many
occasions when a URI is included in plain text; examples include text
sent in email, USENET news, and on printed paper. In such cases, it
is important to be able to delimit the URI from the rest of the text,
and in particular from punctuation marks that might be mistaken for
part of the URI.

In practice, URIs are delimited in a variety of ways, but usually
within double-quotes "http://example.com/", angle brackets
<http://example.com/>, or just by using whitespace:

http://example.com/

These wrappers do not form part of the URI.

In some cases, extra whitespace (spaces, line-breaks, tabs, etc.) may
have to be added to break a long URI across lines. The whitespace
should be ignored when the URI is extracted.

No whitespace should be introduced after a hyphen ("-") character.
Because some typesetters and printers may (erroneously) introduce a
hyphen at the end of line when breaking it, the interpreter of a URI
containing a line break immediately after a hyphen should ignore all
whitespace around the line break and should be aware that the hyphen
may or may not actually be part of the URI.

Using <> angle brackets around each URI is especially recommended as
a delimiting style for a reference that contains embedded whitespace.

The prefix "URL:" (with or without a trailing space) was formerly
recommended as a way to help distinguish a URI from other bracketed
designators, though it is not commonly used in practice and is no
longer recommended.

For robustness, software that accepts user-typed URI should attempt
to recognize and strip both delimiters and embedded whitespace.