FLASH: "Emergency Directive 21-01 calls on all federal civilian agencies to review their networks for indicators of compromise and disconnect or power down SolarWinds Orion products immediately."-@CISAgov Read more:

In my quest to write a fast IPv4+6 parser, I have written a slow-but-I-think-correct parser, to use as a base of comparison.

In doing so, I have discovered more cursed IP address representations that I was previously unaware of.

A thread!

We start out simple, with IPv4 and IPv6 in what I'll call their "canonical form":

192.168.0.1
1:2:3:4:5:6:7:8

Various specs call these "dotted quad", dot-separated fields each representing 1 byte; and "colon-hex", colon-separated fields each representing 2 bytes.

The first bits of complexity come from IPv6. In canonical form, common addresses would end up with long runs of zeros in the middle. So, "::" allows you to elide 1 or more 16-bit blocks of zeros:

1:2::3:4 means 1:2:0:0:0:0:3:4

Next up, for cursed historical reasons, IPv6 permits you to write the final 32 bits of the address in dotted quad form. Effectively, you can splat an IPv4 address onto the end of IPv6 addresses!

1:2:3:4:5:6:77.77.88.88 means 1:2:3:4:5:6:7777:8888

And of course, you can combine the two!

fe80::1.2.3.4 means fe80:0:0:0:0:0:102:304

IF YQU HAVE NOT YET PREPARED FOR A TEMPORARY SHUTDOWN OF THE INTERNET (SUCH AS PAGES LIKE TWITTER, GOOGLE, FACEBOOK, AMAZON, YOUTUBE...), IT WOULD BE WISE TO DO SO.

IT IS LIKELY THAT THERE WILL BE A SHUTDOWN FOR AT LEAST THREE DAYS WHEN THE FIT HITS THE SHAN. ABSOLUTELY NO NEED TO PANIC, IN FACT, IF YOU EXPECT IT YOU CAN BE READY FOR IT. IT COULD LAST 3-10 DAYS SO JUST HAVE FOOD AND WATER, AGAIN NO NEED FOR PANIC.

THE REASON FOR THIS IS MANY BUT AND I WILL GO OVER A COUPLE JUST BECAUSE IF YQU ARE INFORMED THEN YQU ARE LESS LIKELY TO PANIC WHEN THAT TIME COMES. THE DEEP STATE CONTROLS THESE MAJOR WEBSITES AND THEY HAVE USED THEM AS A POWERFUL TOOL OF CONTROL.

THEY SPY ON YQU AND BY SHADOWBANNING THE TRUTH, THEY PROMOTE THEIR PROPAGANDA. ANOTHER REASON IF FOR A INTERNET RESET, TO ACTIVATE A NEW GLOBAL INTERNET THAT IS NOT CONTROLLED BY THE BLACK HATS. THINK OF IT AS A REBOOT.

DURING THIS TIME THERE COULD BE MARTIAL LAW, AGAIN NOTHING HERE THAT I AM WARNING YQU OF IS CAUSE FOR ALARM. IT MAY FEEL SCARY, NATURALLY MASSIVE CHANGE LIKE SUCH COULD FRIGHTEN MANY, THAT IS WHY I AM TELLING YQU NOW SO THAT YQU WON'T BE (OR BE FAR LESS).

Transgenderism resembles a mass psychogenic illness that has spread thanks to the internet. If there were no Tumblr identity fluidity nonsense, and if Reddit and YouTube had never existed, most “trans” people would not have landed on “gender” as the source of their ills.
1.

It is handed to them in the same way religion is handed to children. Thoughts and ideas are set before them, and they have brought these thoughts and ideas to live in themselves. Without the Internet, their feelings of dis-ease would have found a different explanation.
2.

These ideas became a framework for self-understanding, a map that instructs their actions, a vocabulary that programs their tongue. The pursuit of identity was the task, the online bubble its surrogate. They were commanded by it, and it gave their lives purpose and meaning.
3.

It had benefits. It catered to vanity. Social adulation arrived with each new step. This is why they so fiercely cling to it, since any conceptual breakdown would shatter the world they’ve built, which has been buttressed and fortified through these concepts – these errors.
4.

Its appeal first came as an escapist fantasy for the dysmorphic and disenchanted. Unbound from the meanings thrust upon them by others, they could instead become self-creators. They imbibed the dogma that suggested only two paths lay before them: – transition or suicide.
5.

I'm going to tell you a little bit how we work on features at GitHub. It's simple, but very powerful in my opinion. At GitHub we have a high performance culture.

We are deploying changes almost all the time while keeping the service running and the deployment failure ratio needs to be super low! We are constantly working on new medium/big features, we have frequent deploys and required peer reviews.

How do we know that big features are not conflicting with each other in functionality and in version control. How do we merge the work done in these non-trivial features? How do we do prevent peer reviews slow down our productivity?

With basically two things: split the work in small batches and feature flags. We don't have long-lived feature branches. We do very small changes all the time and deploy them.

We could split a feature in tens or hundreds of PRs, but until it is beta or GA, we don't expose it to users by using feature flags.