dwt

You know, protecting against Powerloss was the major feature of filesystems in a time gone by…

I like git, most used version control system around these days. The way in which commits are hashed is very much a blockchain.

I also like public timestamp services, which are also often implemented as a blockchain

Well, if you do it this way, you can’t least be sure that you wasted any the during the creation process. And you are free to use as much as you want.

If you want to work on your tolerance, a few months of abstinence will do wonders there. If you can stomach that.

you know, I would recommend decarbing your herbs in a vaporizer. That way you get high the first time. Then keep and collect the leftovers and when you have enough for a tea spoon, sprinkle it on anything you like. Not much taste left, slightly crunchy.

Super easy to make and nothing going to waste. Works every time.

On python, because of the Gil, multi processing should always be preferred if possible.

Surprised pikachu face….

If you do want to try, just start a docker container and try inside there. That should negate all risk

Couldn’t get single quotes to type on my phone, but best to always use them for problems like that, to completely get rid of shell interference.

rm ./—rf\ \*

Am I missing something?

It’s easy to set the path to include the venv in the Dockerfile, that way you never have to activate, either in the run line, nor if you exec into it. Also this makes all your custom entry points super easy to use. Bonus, it’s super easy to use uv to get super fast image builds like that. See this example https://gist.github.com/dwt/6c38a3462487c0a6f71d93a4127d6c73

Did you catch that a Microsoft employee found the xz exploit?

I really like some Mammal Hands http://mammalhands.com/