Sign into an existing account

Inspiration: The +NIGGER license modifier.

Because HTTP can have any custom headers, I figured why let license modifiers have all the fun, go for a protocol modifier!

Clients and servers implementing the HTTP+NIGGER protocol SHOULD include an extra HTTP header called nigger. Because most HTTP hosts don't give a fuck about uppercase and lowercase in the header key name, the case is unspecified.

The header value is also unspecified, but MAY be "NIGGER". If a client uses plain HTTP without the nigger header, the server MAY use the header value "FAGGOT". If a client sets the nigger header value to "N", the server MAY respond with nigger header value "I". Servers are encouraged to implement interesting nigger header responses depending on the client nigger header.

Example client HTTP+NIGGER request headers:
`
GET / HTTP/1.1
Host: www.voat.xyz
Nigger: NIGGER
User-Agent: curl/7.68.0
Accept: /
`

Example server HTTP+NIGGER response headers:
`
HTTP/1.1 200 OK
Date: Thu, 28 Mar 2024 00:00:00 GMT
Vary: Accept-Encoding
Transfer-Encoding: chunked
Nigger: NIGGER
Content-Type: text/html; charset=UTF-8
`

A client may also specify the HTTP+NIGGER protocol explicitly, such as HTTP/1.1+NIGGER, in which case it MUST include a nigger header. A server which receives a HTTP+NIGGER request without a nigger header SHOULD respond with HTTP+NIGGER error 444, which MAY include the text "Did Not Say Nigger".