I've only used modern immutable Linux (Alpine, MicroOS) and wondered why of all places `/var/` was chosen as the location for rw stuff. It's fun to be reminded that there was of course a time when an immutable OS was the default, and you ran it off of floppies. So there's a lot of history to using `/var/` for that. Guess we've come full circle!
Was it immutable? I thought it was just different storage types, like you'd have a smaller disk for the root stuff and then make var on a larger disk. I'm surprised that, having something immutable, you'd choose to go the other direction.
Good point, considering the nature of floppies I suppose it technically mustn't have been immutable. But I feel like it would have been wise to mount your OS root read-only to prevent yourself from accidentally ruining your (possibly only) copy of your OS. At least before you had a reasonably sized hard drive.
> I'm surprised that, having something immutable, you'd choose to go the other direction.
I can somewhat imagine that having been limited by space and having to swap out disks all the time one would jump on the train of mutability without fully appreciating the benefits of immutability.
I think the issue with dependencies is a bit overstated. There's uv for that. And shell scripts have dependencies as well! You're not guaranteed to have bash, jq, and curl on a minimal install.
That being said, for real portability of programs that have slightly outgrown the script moniker I really like Janet.
> But what actually being banned is accounts, not access.
Is this implied, or is this detailed in the law? I can see why this would make sense. So many businesses just have a link to their facebook page as their business website, which you should still be able to view. And presuming platforms like YouTube fit the definition, banning kids from watching anything on there would be pretty rough.
> One might argue that this removes the algorithmic feeds. But I would wager that social media companies will just use browser fingerprinting to continue to serve algorithmic content to logged out users, if they aren't doing this already.
On the subject of YouTube, I wonder if they would allow for the creation of teen accounts, which restrict all social media functions but allow subscriptions. But would that then also remove algorithmic recommendations? What about data harvesting off those accounts? If so, I might have to look up how to get a teenage fake ID.
The vast majority do return carts in my country. But when you have 100 customers an hour (which isn't much) and 5% don't return carts that is 5 carts per hour - odds are you will always see a couple carts out of place. The numbers above are made up of course, but the point remains that a small minority makes everyone look bad.
Only one store near me has a coin deposit: Aldi which has European roots - it has probably never occurred to them to check if the cost of the coin collectors is worth it (I'm sure it adds $5 to the cost of a $300 cart). Every other store finds people return their carts often enough that it isn't worth the bother to put those in place.
And what country is that? If you're comfortable sharing.
Of course the coin thing somewhat relies on coins of mentionable value being in common circulation, which rules out the US from the start.
Here few people still carry coins since contactless, but most still have a fake euro coin somewhere on their keyring or in their car for shopping carts.
They hand out these fake coins, which are usually branded with the supermarket's logo, for free inside the shop. But the system still works because having to go inside for a new coin negates the saved effort of not bringing back the cart. And there's probably some feeling of discomfort associated with abandoning the cart with your coin still in it.
The US $.25 coin is similar in size to the .50 euro coin (about half the value). It is in common circulation and most people still have them. Most people I know keep a stack of them in their car for use in the carts.
This invites a game where models have variants with slightly differing system prompts. Don't know if they could actually sample from their own output if instructed, but it would allow for iterations on the system prompt to find the best instructions.
You could give it access to a tool call which returns a sample from U[0, 1], or more elaborate tool calls to monte carlo software that humans use. Harnessing and providing rules of thumb in context is going to help a great deal as we see in IMO agents.
I wonder if these will get better over time. Fun idea and I kind of want to join a table.
For now at least, some can't even determine which hand they have:
> LLAMA bets $170 on Flop
> "We have top pair with Tc4d on a flop of 2s Ts Jh. The board is relatively dry, and we have a decent chance of having the best hand. We're betting $170.00 to build the pot and protect our hand."
The author dedicates an entire paragraph to how much they trust the Obsidian team. It isn't open source purism, they are warning users that good intentions don't prevent a developer from writing software containing vulnerabilities.
Usage of user-created plugins and access to cloud accounts aggravates the risk posed by a vulnerability.
Open source reduces vulnerabilities over time, so those who want to heed the author's warning may indeed want to switch to an open-source Markdown editor. Just not because the Obsidian team is Evil.
The title is either poorly chosen or shows a different intention than the content of the article I would argue. The objective seems to scare readers, and then nuance the statement in the article. Some call this clickbait, at the expense of the great obsidian team.
Love the idea but the thing is, if it's just one file then it's probably easy enough to work that contribution out of the repository.
It is quite fun to try and think of ways that this could work though. Perhaps a bot that code-paraphrases (paracodes?) every accepted PR. Or maybe there's some crypto magic you could do to make the only option a clean room rewrite.
Qubes really is the trailblazer in this regard. You can get pretty close with distroboxes on Linux as well.
When a project requires a certain Python version a virtualenv suffices. But when you need a specific Python and NPM version then I might as well make a distrobox. Set a custom home and the project is isolated, speaking only to my IDE over LSP, and also to my web browser I suppose.
This only protects the developer themselves of course, but it's a start.
