4,360 karma · joined October 7, 2020
I even suspect that I received sub-par service from some of them, who may have identified me as a "no-tip risk" from the first moment.
I was 8 or 9 years old when the ZX Spectrum +2 arrived home.
I'm seriously considering installing this on an old laptop and giving it to my son when he's 8 years old, together with a hard-copy of a BASIC reference and a few simple programs and games to type in.
Getting a FAT32 filesystem on day 1 is already a huge jump from my childhood experience (loading from tape).
(It's the title of his follow up work after GEB.)
https://admiralcloudberg.medium.com/reaping-the-whirlwind-in...
They're already covering the blurring, as well as detecting useful objects in imagery (traffic signs for a start).
> There are also important licensing questions. A user’s permission to send a library to OSM is not automatically the same as having a sufficiently clear right to release that factual information under terms compatible with OSM
which would imply that you could not make available your database available for download under ODbL. Yet you have made it available under that license.
Maybe that part of the article needs further editing?
Also, if the data of your tool is now available under ODbL, then the tasks related to importing it into OSM can be effectively performed by anyone, not necessarily you.
There is no implication that "having incentives" must be interpreted as "considering profit maxxing as the first and foremost goal".
Depending on which vendors you trust, they will enable AI features on your local machine later on anyway.
> Switching to Linux, BSD or another open source operating system is the only real solution to this problem.
I hope this is right, and I'd argue it is not enough. You also need trustable vendors for your web-browser and web-based apps.
In this case, this would be the song that plays over the intro credits of "Ascenseur Pour l'Echaffaud" (https://www.imdb.com/title/tt0051378/).
(Ie. Miles Davis might have several pieces of music all titled 'générique', for the various movies or shows where he contributed on soundtracks)
You don't get to shift it without raising questions about your motives.
Not sure what it is that you intend to argue.
At the other end of the spectrum ("uncompetitive") you get things like fuel-cell cars.
https://liebreich.com/the-clean-hydrogen-ladder-now-updated-...
By "that" it is understood: enforcing that the code cleans up unsafe inputs before processing them.
If there is no human doing that enforcement, the code has no chance of being secure.
> I use SI prefixes for bytes. You should too!
The prefix for 1000 is lowercase.
What internal drive moves you forward?
What sense of ownership/pride do you feel when you consider one of your works as "done"?
What would you do differently, if you were back at the starting block and had a budget of $800 to spend on writing nonfiction?
New database ⇒ use the proposed new magic PRAGMA, start with sane defaults.
Existing database ⇒ don't touch anything, keep legacy "suboptimal" defaults.
> I'm sorry, where?
Here:
quote
[...]This should be a nice middle ground which avoids breaking backwards compatibility, but lets the database engine move forwards and not be bogged down by its own history.
end quote
> Regarding busy_timeout, why is 5s specifically a better default?
According to the post we are discussing, any number greater than zero is better than the current default:
quote
The default behavior [no timeout] has lead me to writing real-world bugs, where systems would sometimes just crash. I've manually written retry loops to fix it.
end quote
Your forum links may be quite useful as a response to this comment: https://news.ycombinator.com/item?id=48928441
The way I read it, this article does not advocate at any point to change the defaults for existing databases, but rather to start with better defaults for new databases.
Also, regarding the timeout of 5 seconds, I disagree with your premise "SQLite doesn't decide, which makes perfect sense". As the article explains, SQLite decides on the value zero (ie. instant error), which is arguably an inconvenient default.
* Report any security breaches within 72 hours to a public body (country's CSIRT + ENISA).
* for "all products with digital elements [...] including those already placed on the market before 11 December 2027"
Products must be sold with a "secure by default" config, with automated security patching enabled by default (opt-out), with reporting on possible unauthorised access, with data collection minimization (tie-in to GDPR), with an SBOM, with dedicated security testing, with public disclosure of vulnerabilities, …
https://digital-strategy.ec.europa.eu/en/policies/cra-summar...
What is newsworthy here? The fact that yet one more third-party (the White House) does it too?
That might be a literal case of Chesterton's fence.