It's older than 1832; for example: "He who trembles at this moment is guilty. For innocence never trembles before public vigilance." Maximilien Robespierre, July 26 (8 Thermidor), 1794 (translated - the original would be in French). When it is used by surveillance advocates, they don't use the exact words.
Ah nice to know! In my defense I only searched for the English version.
That being said, Robespierre was a key participant of 'La Terreur' where tens of thousands of people where hastily judged and executed and he himself ended up executed 4 months after that speech. [1]
- the boss has agreed to the role but has reservations, seeing a few candidates solidifies them and permission to hire us withdrawn
- the team is inexperienced at hiring and don't know what they want until they've seen a few candidates
- the company is hiring a new whole team. To make hiring easier, roles that are listed are "representative roles" - the total desired skill set across all roles is accurate but the company doesn't care what the split is, they just want a team that covers it. So a candidate who is a better fit for a listed role can be passed over in favour of one that happens to be the right jigsaw piece.
- circumstances changed since permission to hire was given, and no-one remembered to update the hiring portal; because unless you're actively hiring no-one looks at it.
This last one is quite common, because there are so many applications usually that no-one wants them in their email.
GLR C++ parsers were for a short time in use on production code at Mozilla, in refactoring tools: Oink (and it's fork, pork). Not quite sure what ended that, but I don't think it was any issue with parsing.
Do each of the other filesystems have their own quirks list? That seems suboptimal. Oh, I guess it's because it's in the user space mkfs tool of each, not the kernel.
Is this a joke? I have a lot of respect for the authors of bash, but it is not up to this task.
Does anyone have recommendations for an agent sandbox that's written by someone who understands security? I can use docker, but it's too much of a faff gating access to individual files. I'm a bit surprised that Microsoft didn't do a decent one for vscode; for all their faults they do have security chops, but vscode just seems to want you to give it full access to a project.
Bash was designed decades before the current security environment, and contains many insecure-by-default mechanisms, many of which operate without you explicitly invoking them. Just for starters, in a normal language it's hard enough to operate on untrusted data, but at least you know that nothing bad is going to happen just passing $UNTRUSTED from one function to the next. In bash, because it's based on string substitution you have to enclose that variable in quotes: "$UNTRUSTED" or its contents will start being interpreted.
In short, writing security-critical code in bash,without some obvious constraint forcing this, is a sign of inexperience or not actually caring about it.
i came up with SafeExec to avoid heavy sandboxes or docker and a fast easy way to catch codex/claude from running/hallucinating destructive commands and it has been tested on mac and linux
being bash doesn't erode its ability to act as a goal keeper but looks like you are after sandbox which is overkill for the scope
The stereotype, which is sometimes true, is that people do that kind of degree because they want to understand and solve their own issues. Those who are are interested in people as such, can be more drawn to anthropology.
More true of psychiatry than neurology, though there is of course some overlap. The running joke in neurology is that neurologists are left-handed migraneurs/euses.
I was once at a small dinner talk by a well-respected headache specialist, surrounded by a dozen neurologists. He asked, "How many here have chronic headaches?" Every hand went up except mine and the drug rep's.
Interesting, but
"FunctionTrace is opensourced under the Prosperity Public License 3.0 license."
"This license allows you to use and share this software for noncommercial purposes for free and to try this software for commercial purposes for thirty days."
This is not an open source license. "Open Source" is a trademarked term meaning without restrictions of this kind; it is not a generic term meaning "source accessible".
You can also just use perf, but it does require an extra package from the python build (which uv frustratingly doesn't supply)
perf is a sampling profiler, not a function tracing profiler, so that fails the criteria I presented.
I used FunctionTrace as a example and evidence for my position that tracing Python is low overhead with proper design to bypass claims like: “You can not make it that low overhead or someone would have done it already, thus proving the negative.” I am not the author or in any way related to it, so you can bring that up with them.
But I don't think that's evidence of a botnet. Seems more likely a conventional letter writing campaign where people are invited to paste the same response. Could easily be within the police,which is dubious, but individual police officers may have the right to respond as individuals.
It doesn’t really matter whether it’s a botnet or a coordinated campaign by police officers. The fact that police is interfering with the political process is somewhere between a breakdown of the rule of law, and an attempted coup.
Voting isn’t going to fix stuff like this, that’s for sure.
Yeah, I saw this comment [0] and I'm very confused as to how one concludes there is a botnet in play, let alone by a public institution. Most likely it is an employee in the police, which is totally fine. They're not forbidden to express opinion.
In most cases the data a kalman filter is working on has some precision which is much lower than the available precision in the floating format you are using. The problem is inherently a statistical one, since the expected precision depends on the statistics of your data source.
So you would probably adopt some conservative approach in which you showed that the worst case floating point rounding error is << some quantile of error due to the data.
That's a start, but you might be able to do better than that; for example, you ought to be able to show that the floating-point rounding error is unbiased.
Incidentally here is that quote, with Ian Richardson as Robespierre: https://www.youtube.com/watch?v=bOW6OfeOW10