Sign into an existing account

Inspiration: The [+NIGGER license modifier](https://plusnigger.org/).

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".

It is like an infestation in every way. Rabbits are also rodents and have rodent behaviour, always tunneling around and under buildings.

If the floor starts speaking yid, it is time to gas the vermin out. Either that or just start filling it in, although admittedly these rabbi holes will need one massive volume of building material better used elsewhere.

Santa goes *down* the chimney!

The purpose of asking is to consider and capture the essence of what makes a forbidden word, and if possible, design the most offensive word in the world.

Nigger is great, which we can see every time the jew media is forced to refer to it and has to say "n-word". Niggers call niggers niggers all the time though, so it cannot be *that* bad. I want something which even a uppity nigger would not dare speak.

Fuck and cunt can be heard at many businesses so those no longer meet the standard.

We don't need deep field stuff with over 9000 galaxies in one image when we aren't even interstellar yet, let alone intergalactic.

Most nebulae look much the same, and none are of any use.

Space fully deserves its fake and/or gay status until we can get an actual generation ship flying to an actual habitable exoplanet. Identifying them is difficult because the orbit has to pass by its star for back-lighting, which says to me that all of its time should go into locating new candidate exoplanets, with priority access when such a passage occurs.

With a definitive destination, I am 100% sure that an actual voyage is possible (the first step is never submitting to pessimism). I would go, even if my purpose was just to produce and educate the next generation during the flight, because it feels natural to have the forefront of humanity in mind.

Standard ASCII is one byte per character, ending at 0x7F, which gives just about enough space for control bytes, spaces, punctuation and uppercase/lowercase Latin.

Extended ASCII uses the upper half to include some accented letters, and there have been attempts to use dreaded "code pages" for switching alphabet entirely, but Unicode is the proper international solution... in return for accepting that the character encoding is no longer one byte each, and moreover may be variable width.

UTF-8 is proudly variable-width, matching ASCII in most documents while using only those upper half byte values to encode non-ASCII, a robust system which reduces impact when an unaware program reads it as ASCII. The variable width is an issue for a few types of program such as word processors, though most operations (copying, sorting, searching) need not care.

Then some butthurt happened in the early 1990s, and someone just *had* to insist on fixed byte width, and out popped UTF-16. Two bytes per character, costing a load of extra storage for most files, and absolutely no plan for what happens when we reach 0xFFFF. Java, C# and JavaScript all signed up to it for their fixed width string storage.

The Unicode character space started getting flooded with every alphabet in existence with all the durka durkas and the ching chang chongs, and symbols for mathematics, music and such. It looks to me that they got up to 0xD000 before admitting that it is going to run dry.

The solution? Reserve 0xD800 to 0xDFFF... for using pairs of characters in that range to represent 0x10000 and above. So, a variable width encoding.

This is indeed literally as retarded as having to use a gas-powered generator to recharge an electric car.

Even worse, the UTF-8 system could store Unicode up to 0x7FFFFFFF, but that UTF-16 extension only takes it up to 0x10FFFF, and now Unicode itself specifies 0x10FFFF as the limit just to appease UTF-16.

UTF-16 has fucked everything up for zero benefit in return. Even C++ has an entire wide-string type and string library suite for it which is widely known as a massive trap to avoid and put UTF-8 bytes inside normal strings instead. Windows purports to use wide-strings for files, but it is broken.

Python (a.k.a. programming for niggers) 2 tried to "help" with Unicode in the same way that cats "help" ensure that everything is knocked successfully onto the floor. Python 3 sort of behaves itself, while in the background it insists that if a single string character would be multi-byte in UTF-8 then the entire fucking string gets converted to a fixed width encoding big enough for that. Actually that is really a different manifestation of insistence on fixed width rather than UTF-16 specifically, but that type of thinking is still the problem.

UTF-16 must be destroyed.

Infogalactic has UTF-8 at accounting for 85% of websites in 2015, and Wikipedia claims 98% presently. The latter whores itself out and has no criticism of UTF-8 at all, and the former only really covers the obvious points about some operations being mildly less convenient with variable-width encoding and sometimes using 3 bytes instead of 2 for an asian glyph. Everyone recommends it as a standard, even Microsoft.

I have no direct problem supporting UTF-8 and running tests against UTF-8 input and those icon characters it has, but its dominance has me very suspicious. If it has the blessing of that much of the world, that must include communists and degenerates. This almost never happens unless it's a format lock-in to secure future compliance of the developer, or incur royalties if a piece of a program happens to be able to encode it (MP3 is that way).

I don't doubt its usefulness, I just get concerned at the lack of anyone presenting any real contrary position at all. Is my suspicion unfounded, or does UTF-8 have some deep rabbit-hole beneath the surface?

Messed up like a retarded sheep? Control-Z your low IQ monkey blunder for the low price of one "I am sorry, I was wrong and you were right".

No idea how it would be done, nor whether it would be a good idea to contradict an otherwise Darwinian outcome, though at least it would be impossible to get without admitting fault. Hopefully the shame would be too much to endure for the ones who need to be culled most.

All of my contact with Python is to fix broken stuff, where most of the time the fix is to start over with a better platform. Every time I end up having to use it, I find new failures in its design which are even more mentally retarded than the time before.

Reliance on white space is colossally retarded and it imposes the need for a `pass` keyword. Anyone who thinks it is possible to force programmers into writing legible code that way is a colossal retard.

Like most pretentious garbage it changes many classic reserved words, just enough that the number of complainers does not rise above half the users. `throw` is `raise`, `catch` is `except`, `null` is `None`, `true` is `True`, `false` is `False`. So much for keeping to a lowercase style when you can use capitals just because those are constants rather than keywords.

Inconsistently, it retains `==`, `!=` and `^` but changes `&&` to `and`, `||` to `or` and `!` to `not`.

Despite being popular for data processing, it cannot thread. It has something *called* threads, but this is only useful for I/O, because its "global interpreter lock" fundamentally can only run one line at any time. The autistically screeched response is to run extra processes, but its attempt at shared memory is also total ass. All the data popularity comes from being a front end to NumPy, which is written in C.

Lambdas? Only if the result can be written in one expression, no statements allowed.

Class constructor? Some nigger decided to name that `__init__`.

Anonymous object? It was supposed to work but doesn't, but you can `import types` and use `types.SimpleNamespace` instead, that works. Unless you want methods with statements in, then you need to use `def` and pass in all scope variables.

No pre-increment or post-increment. `+=` works, but you can't use it within a comparison test, because fuck you.

No `switch`, get used to `elif` nigger.

No do-while, make a flag or copy the fucking loop code.

No labels for `continue` and `break`, no numeric argument option, not even a fall-back `goto`. Guido himself said that this type of code is too complicated, by which he means he is too retarded to understand it, so fuck off and make a load of complicated flags and tests instead.

It doesn't even have the `===` operator like other languages with dynamic types, you have to test the types yourself... using `__class__` like a nigger.

No `static` keyword, but you can make a static method if you put `@staticmethod` on the line before. Genius.

You can have the ternary operator, but you have to put the test condition in the middle instead of at the front. Also `if` and `else` are reused for doing that, just in case you missed having a horizontal scroll bar.

That much is only what I have learned while otherwise trying to avoid Python.

Fuck

Especially if you are able to record it and post the video online. The only way that this would be infeasible is through differential enforcement of some rule against it versus the entry rules being breached. If all the wall money instead funded a bounty pot, the problem would be solved long ago.

Is there even any such rule? The most I can imagine is that taking a few snipes technically is a form of exporting munitions,

See https://files.catbox.moe/gxrxmq.JPG for reference.

The blue arrow was 99%+ fine*, gambling on the very likely chance that nobody has a client with a blue menu background, but this isn't the case for white, black, and some greys.

As with good meme image text, it needs something like a sharp outline, drop shadow, or just a (rounded?) square block behind it.

*Even then, the blue arrow fails in the case of placing a website link on a blue PC desktop or blue mobile home screen. Favicons generally just need contrast to be sure.

Years on, I keep seeing new screen captures with this still happening. It's still always a jew, and it can still be used as basis to call the jew a jew with 100% success rate. I know as well as any here that the jews can not and will not stop jewing, but have they really not made any genuinely new effort to shape-shift?

Surely they must know that White people don't address each other that way, on account of having actual distinguishing properties and identities beyond lineage. That being the case, are they actually addressing non-White people with a signal that it's okay to lambast White people about the topic in question? I imagine that does work due to lower non-White IQ. No wonder they cannot tolerate intelligent non-jews, nor the anathema that is having their shape-shift pass declined by being called a jew.