> You've provided the current rewritten thinking and the guidelines, but I don't see the "next thinking" content that I should be rewriting. Could you provide the next thinking that needs to be rewritten?

These sentences are completely unrelated to the actual conservation

The kernel is not just open source, it's a very fast-moving codebase. That's how we win all wars against AI-authored exploits. While the LLM trains on our internal APIs, we change the APIs — by hand. When the agent finally submits its pull request, it gets lost in unfamiliar header files and falls into a state of complete non-compilability. That is the point. That is our strategy.

1 - https://en.wikipedia.org/wiki/Demobbed_(2000_film)

Primarily to use in conjunction with OpenVPN. Like secretive or /usr/lib/ssh-keychain.dylib[2], but not just for SSH.

1 - https://github.com/ne-bknn/nailed

2 - https://news.ycombinator.com/item?id=46025721

...a smooth sea never made a skilled sailor

1) allocations via memguard bypass gc entirely

2) they are encrypted at all times when not unsealed

3) pages are mprotected to prevent leakage via swap

4) and so on...

Not as ergonomic as OP's proposal, of course.

[1] https://github.com/awnumar/memguard

T_co = TypeVar("T_co", covariant=True)

class Indexable(Protocol[T_co]): def __getitem__(self, i: int) -> T_co: ...

def f(x: Indexable[str]) -> None: print(x[0])

I am failing to format it proprely here, but you get the idea.

2) I never said receiving email is a SPoF

3) Please explain in detail what do I do in order to keep receiving emails using "me@johndoe.com" after johndoe.com gets undelegated. I do not know of a way and would very much like to know. If there is no way.. It is a SPoF.

edit: formatting

I'm not saying email self hosting should not be done, I just say a bit of planning should be done.

DNS seems like the most annoying part, it is SPoF by design. The problem can be mitigated, but seems like cannot be solved. For example, owning multiple domain names in multiple jurisdictions. And round-robin them. You cannot eliminate SPoF for any one specific service you want to login using email. But you won't lose access to everything at once.

Edit: P.s. At the same time, owning your domain for mail seems to be one of the most impactful things to do to reduce digital serfdom. Banned at *mail? Just switch those MX records and go on.