天空вℓσи∂ @skyblond@qoto.org

Hmmm

Some covid lung CT images from China. They called them "white lungs" because the CT image shows the affected parts in white. And according to some sources, they're pretty dangerous even if you're in a hospital with a good amount of medical resources.

Some people suggest that there are delta and other variants in China. But after a quick google search, I found this paper: Can the Omicron variant of COVID‐19 cause pneumonia in young patients without risk factors?

It suggests that even with Omicron, the one we think is a serious flu, can still cause pneumonia (which shows white in CT images?).

I mean, in my opinion, the government shouldn't take too much action, like lock down the whole country for 3 years. But at least the government should make sure the infrastructure can take it when the virus hits, such as flattening the curve. Now, after experiencing 3 years of lockdown, we can't get enough medicine and the hospital and medical services are hit hard. Even the funeral parlor is under extra load. Well done, Chinese government.

NIST还是强啊
----
This fake dog nose made chemical sensors 18x better
by Veritasium
https://www.youtube.com/watch?v=TILjzuBGkRc

还得是美利坚人才辈出（
----
Best of William Osman
https://www.youtube.com/watch?v=jAmDFBCGKAk

连个搞笑视频都容不下，老中人还是小心眼

IMO, they need to leave the compatibility and re-design things. You can't patch things forever.

I would suggest making those breaking changes and slap version 1.0.0 to it. Now they're 0.9.something. Perfect time for some breaking changes. LOL

Well, I might fail at step 1.

Parsing public keys are confusing. In the past, all keys are 256 bytes for crypto and 128 bytes for signing.

But then we have other algos, which introduce keys like 128 bytes, 512 bytes, 32 bytes, etc. How does I2P respond?

For those keys smaller than 256/128 bytes, just add paddings. Add padding after the crypto key and before the signing key.

What about those longer keys? Just chop them off. Write only the first 256 bytes of the crypto pub key and the first 128 bytes of the signing pub key. Then put the excess into a separate structure after the pub keys. Now you get something like: CryptoPubKey(part of), SigningPubKey(part of), KeyCertificate(the rest of them, act like a patch).

Is that self-contain? Not yet. That's how they handle things in RouterInfo. In some places like LeaseSet have a separate encryption and signing key, which, doesn't have any KeyCertificate. And the doc said: Key type and length are inferred from context or are specified in the Key Certificate of a Destination. Well, I do spot a Destination, but what if we have a long pub key? Where is the excess? The Destination itself has its own crypto and signing pub key. And we have part of the keys outside it. WTF

I guess that's reason why people fork it and make changes like I2P+, rather than start a new project from scratch. Those data structures are preventing people from setting up new projects. It's too hard to parse and easy to screw up.

Start writing my own I2P router.

Any suggestions?

Current plan:
1. Find a way to parse reseed file
2. Connect to those peers using NTCP2
3. Try to announce our self as hidden mode (don't accept incoming connection, aka just hang out)

The test is kind of hard. Seems like routers will ban us if we failed to give correct messages. And seems like there are some ugly patch in the architecture.

Today I noticed a new project called yggdrasil, which is a mesh routing system using IPv6 0700::0/7. Seems like it routing all IPv6 packages through this user space software. I didn't find any detailed documents, but sounds brilliant.

吧唧吧唧
----
Ice Cream Tester
https://www.youtube.com/watch?v=EYtFH2bFCfg

I was wrong (and so was everyone)
by Tom Scott
https://youtu.be/Wif1EAgEQKI
----
This video corrects a misleading statement: "Insurance Fire Brigades let uninsured buildings burn" in 18 century London. And tom hired a researcher to find out. Wow.

My throat is trying to murder me even I'm sleeping.