Reference for the admission?

And it’s made by a Bitwarden developer.

They highlighted it was a bug and said it would be fixed very soon after it was flagged. It was addressed in a matter of days. You can build the server with the /p:DefineConstants=“OSS” flag still and you can build the clients with the bitwarden_license folder deleted again (now they’ve fixed it).

I don’t understand why you’re throwing FUD about this. Building without the Bitwarden Licensed code has been possible for years and those components under that license have been enterprise focused (such as SSO). The client is still GPL and the server is still AGPL.

This has been the way for years.

Cool. They got that sorted nice and quickly.

Edit:

I don’t get why people think they’re suddenly doing stuff under a different license to subvert the open nature of the project. They’ve been totally transparent on what isn’t part of the GPL/AGPL licensed code for years.

SSO, the password health service, organisation auth requests, member access report blah blah have been enterprise features under the Bitwarden License for ages and they architected the projects in a clear and transparent way to build without those features since they added them.

Sleep

It sounds like you’re interested in epistemology. Take a dive into this Wikipedia article and give at least the parts on Justified True Beliefs a read.

Best answer here. Wikis have a much more complex syntax and templating if you’re trying to do visually appealing content whereas Obsidian with Canvas, Graph, and many of the plugins is so much easier to get up to speed with and add in crazy cool functionality.

They offer hosting for $8 or $10 per month.

You can also just use GitHub and do it all for free.

The car thing really blew my mind. My hotel was 400m from the office but 1.6km by car. Colleagues were waiting for a taxi while I walked. I had to cut over a couple of car parks and a bit of grass (zero sidewalks) and was there in a few minutes while they turned up 15min later since they were waiting for a taxi.

The worst part, they all jumped in cars to go 300m down the road for lunch. Yeah, I walked. With looking for a parking space then walking from the space to the restaurant, they got there after me.

I adore Americans; they’ve been nothing except kind and generous to me in every part of the country I’ve visited but damn, the money they’re wasting alone just starting their engines and the wear and tear on the vehicles blows my fucking mind. Build some sidewalks, guys!

None of which are intelligence, and all of which are catered towards predicting the next token.

All the models have a total reliance on data and structure for inference and prediction. They appear intelligent but they are not.

deleted by creator

Mean, median, or mode?

I’m not insisting anything; stating C is not a memory-safe language isn’t a subjective opinion.

Note I’m not even a Rust fan; I still prefer C because it’s what I know. But the kernel isn’t written by a bunch of Lewis Hamiltons; so many patches are from one-time contributors and the kernel continues to get inundated with memory safety bugs that no amount of infrastructure, testing, code review, etc is catching. Linux is written by monkeys with a few Hamiltons doing their best to review everything before merging.

Linus has talked about this repeatedly over the past few years at numerous conferences and there’s a reason he’s integrating Rust drivers and subsystems (and not asking them to fork as you are suggesting) to stop the kernel stagnating and to begin to address the issues like one-off patches that aren’t maintained by their original author and to start squashing the volume of memory corruption bugs that are causing 2/3rds of the kernel’s vulnerabilities.

No idea what you’re being downvoted. Just take a look at all the critical CVSS scored vulnerabilities in the Linux kernel over the past decade. They’re all overwhelmingly due to pitfalls of the C language - they’re rarely architectural issues but instead because some extra fluff wasn’t added to double check the size of an int or a struct etc resulting in memory corruption. Use after frees, out of bounds reads, etc.

These are pretty much wiped out entirely by Rust and caught at compile time (or at runtime with a panic).

The cognitive load of writing safe C, and the volume of extra code it requires, is the problem of C.

You can write safe C, if you know what you’re doing (but as shown by the volume of vulns, even the world’s best C programmers still make slip ups).

Rust forces safe® code without any of the cognitive load of C and without having to go out of your way to learn it and religiously implement it.

deleted by creator

Conway’s Law applies in this respect; the mess in governance of Nix has produced a product that reflects that mess. Nix started a beautiful movement but like many first movers, they rarely reap long-term rewards.

You’re right which is why our freezer is out in the garage rather than in the house.

Another thing you can do is buy an ice vest - a vest with waterproof pockets for ice packs. They usually come with a load of extra ice packs so you can freeze and cycle through them. They’re great if you have to go outdoors for something.

AC is expensive but the freezer is already on so I’ve been rather creative with its use haha.

Doggo also enjoys a rubber bone thing that I fill with water and freeze so he can chew and stay cool. Also love freezing ice cubes full of berries and stuff too.

If you have a freezer and a fan, freeze a bunch of water bottles and then put them right behind your fan blades for a cheap AC-like chilly breeze. If you have enough bottles, you can cycle through them and refreeze as they thaw out.

deleted by creator

He’s been here the whole time!