For one of my projects my server needs a private key, and it reads this from a file descriptor on startup and then closes the fd. The fd is set up by the systemd unit, which is also configured to restrict filesystem access for the server. So the server reads a key from a file that is never visible in its mount namespace.
I don't doubt you're correct about the incentives, but one point seems amiss...
> If there's any, even the slightest, chance that buying from a business might one day reflect badly on the civil servant in the procurement office, then they won't buy from that business.
You don't think that spending £4.1 million on this garbage might reflect badly on someone?
Nope. They followed the process, they bought from an approved, respected, supplier. The site meets the specification they drew up. There will be meeting notes from a few hundred meetings to document that everyone did their job properly.
For us techies who know the tech (or even the law, in this case) this is a disaster. But for the folks in those meetings this is what they understood to be the brief.
If enough of the public gets ahold of the story so that a politician has to get up on their hind legs and issue a statement, then harsh words might be had. But otherwise, this is business as usual.
If you scroll down slightly you get a low contrast button "○
PREFER STILLNESS? READ AS PLAIN TEXT
→", which takes you to a plain text version with a rather patronising introduction that says "You chose the quiet version. No animations. No counters ticking up.
Just words. That's a valid choice."
Edit: to be just slightly nicer about it: having a plain text version is great, that's a really good thing. But the "that's a valid choice" paragraph is unnecessary and just distracts from your actual article. If I pick the plain-text version it's because I want to just get straight to the point (other people may have other reasons), and I certainly don't need your validation.
"Good instincts on choosing plain text—you're asking exactly the right questions, and it cuts to the core of what makes traditional blogging so compelling. It's not just the medium—it's direct access to the thoughts and personality of the author! Let's delve deeper into exactly why the blogging model is so powerful.
The graph I see in the article displays a single data point per year. You're not going to see seasonal variation in a graph with that resolution. Is there another graph that I missed?
It's not a false choice - "Trust" and "don't trust" are both perfectly viable options. The editor works fine in restricted mode, you just won't have all your extensions enabled.
Any naive crawler is going to run into the problem that servers can give different responses to different clients which means you can show the crawler something different to what you show real users. That turns crawling into an antagonistic problem where the crawler developers need to continually be on the lookout for new ways of servers doing malicious things that poison/mislead the index.
Otherwise you'll return junk spam results from spammers that lied to the crawler.
I've never done it so maybe it's easier than I imagine but I wouldn't be quick to assume that crawling is solved.
I don't mean to say it's trivial. I'm sure there are many hard problems such as the one you mention - though that particular one is more "cleaning the index" part which might work on top of the open common corpus.
But my impression is that it's more a question of scale and engineering time than having to invent something new.
(disclaimer: I also never worked on a internet-scale search system, maybe I'm very off the bat here as well).
Looks like I was probably wrong about this. There are a lot of "doom running on a vape" videos on YouTube - very easy to find, that's what search is for - but the best primary source I could find quickly actually has doom running separately and the vape just being used as a display.
reply