Toilet paper is barbaric and uncivilized. We can and absolutely should discontinue it everywhere. If you got poop on your arm, you wouldn't smear it off with dry paper. You'd wash with soap and warm water. Bidet all the way.
Real question: don’t you need TP even when using a bidet? Bidets seem to make it easier to clean via wiping, but doesn’t seem to clean enough by itself.
I'd advice for the excellent pulsesms app, which will let you sync you sms from your phone to your desktop.
You can read and write messages from the comfy keyboard of your Windows/MacOS/Linux laptop, even if your phone is at the other side of the world, as long as both are connected to internet.
As someone who forgets his phone regularly at home, it's great.
Assuming there is only one big filter, which I think is unlikely.
Any mega black swan event is a filter in its own since it's disturbing the system you are adapted to. The worse event is one that disturbs the system you are dependant on.
Climat change is terrible, but it could be worse. We depend on oxygen. Gravity. What else await for us ?
If you define a great filter as something that statistically prevents the preponderance of life in the galaxy, then "any mega black swan even" is just noise. With small likelihood, it will wipe out a civilization, (definition of black swan). But for it to be a great filter per definition, it has to somewhat reliably affect all potentially universe-spanning intelligence. All I'm saying is that most likely, once an intelligent tribe of creates arises, it's likely to go on to dominate the planet, and likely to go on to reach technological readiness to go to space (assuming it can get access to energy easily, which may be another small filter).
So, you're not wrong, all dangers events could be humanity's end, I'm just saying something more general -- that civilization-limiting events are probably clustered before the civilization arises.
It may very well be after it ,still due to “black swan” type events. With technology continuing to progress, there may be a point where a small group of dedicated people can construct enough nuclear warheads for a nuclear winter, or engineer the perfect deadly virus with a large incubation period. And/or if we develops AGI, that a single malicious group controlling an AGI can end all life on earth. Technology will continue to advance, and it is easier to destroy than to create.
My dirty dozen-ish: tautline hitch, bowline, square knot, figure eight + variants, fisherman's knot, N half hitches, sheet bend, Zeppelin bend, trucker hitch, Alpine butterfly, hangman knot, and a variant on the shoe knot that doesn't come loose. Can't remember the name but in sure you can find many variants with a search.
Square knot most people already know. Tautline and bowline are the two worth memorizing being able to do soaking wet in the dark.
Personally I rate the figure-8 over the bowline. I think it's a much more versatile family (and much easier to tie and inspect with high confidence soaking wet in the dark).
Good point! I think I mentally chucked it with the square knot under "knots that should already be in most people's inventory" but you are right, that is definitely worth learning, since there are so many useful variants.
So like, 4 essential knots:
Figure 8, square knot, bowline, hitch. The map, filter, fold, and reduce of knots, if you will. Most everything else can be composed from those.
Not the parent comment, but you'll get a long way with a figure-8 (both on a working end and on a bight), a clove hitch, and an alpine butterfly. I'm sure others have a couple more favorites.
(this is omitting a few "foundation" knots like the overhand)
Learn a munter hitch, it's extremely versatile and can do everything from securing something, to belaying or rappeling off it (with a locking carabiner). It is an extremely important knot for setting up rescue systems as it can hold a load under tension, yet can be undone and slack added to the system while under complete control.
I like the feature, but if it requires somebody to creates an account, it's a hard sell.
If they got a signal account, which is more likely than a bitwarden account, I'll ask them to use that. If they don't, then something like 0bin.net will likely be easier to use (no account necessary, just copy/paste).
Now, bitwarden allows you to send any type of file, which is better than 0bin, being very limited in size, and to text and pictures. But you need a pro account for this.
So I'm not sure how it's better than the competition. Although I'm posting this comment so that someone on HN can show be I'm missing something.
While that is true, it is unclear is the Send feature is available on the self hosted,
Further most of the time people are using the opensource fork / rust rewrite of BitWarden (bitwarden-rs)which may not have all the features of the official bit warden
Just checked, should be available on the self-hosted version as well. [0] And the author of bitwarden_rs seems to be planning to tackle it over the weekend!
I don’t get why most people trust this unofficial clone. It’s neither audited for security issues (unlike official bitwarden) nor is it developed by bitwarden.
This is why good ORM like SQLAlchemy actually are split in 2 parts: the declarative layer, and the core layer.
The declarative layer gives you the handy ORM syntax for simple operations.
The core layer is lower level, and allows to composes all possible SQL operations you can dream, but from the comfort of your programming language, including typing, completion, and so on.
Does something like that exist for Go ? I don't know the golang ecosystem very well.
I couldn't find exactly an only Core example that you are looking for in the examples folder [0] so here is a more complicated tutorial query [1] and here's how I use Core in my project [2] (mostly short select statements so not really a comprehensive demonstration of SQLAlchemy Core's capabilities).
> My dream is to write actual SQL in the middle of my code, as a valid syntax and first-class construct. As I said, that's not really a realistic goal.
Sure, it is. See how regexes in some languages are first class datatypes, so you can have a regex literal in your code (with backreferences too, I believe).
There is no good reason that SQL statements can't also be a datatype, with SQL literals in the code like the way regexes do. I'm imagining something like this:
The stmt above is not a string, hence is part of the AST and can be checked at compile time. The execution might be a problem (returned columns have to be checked too).