Yes, this surprised me as well. Credit card and Paypal information should give the police everything they need to identify the criminal (in a way that's much more simple and reliable than via IP address, which may be obfuscated via a VPN or similar). Why not take it, it's free?
People are already not using libraries because they'd rather rot their brains on TikTok than read a book. (Also, for information lookup, the internet and search engines exist, and have for a while now.) This has no actual causal relation.
People is a broad term. Outside of major cities (where I live) libraries serve a very essential service for parents and their children and as a free communal space for the broader community. Our libraries are always full and a large part of the health of our area.
This is quite amazing. The quality of the created palettes is surprisingly good.
For the fourth iteration (guarding against phantom blue from shadow pixels), I wonder if it may help to also take into account how close the pixels in each cluster actually cluster together in the actual photo. (None of the heuristics used here seem to be interested in the position of the pixels at all, only in their values - as-is, it seems one could sort the photo's pixels before running the program and get the same result.) Actual objects usually form connected areas, whereas at least in the fruit image, the phantom shadows are spread across the entire photo in largely disconnected chunks.
You can of course take a SQL dump that is version-independent, but if you're serious about creating backups, you want to take backups of the actual on-disk format of the WAL, because that's more efficient and also the only practical way to get point-in-time recovery. (For the efficiency, you could alternatively also take ZFS snapshots, which will work independently of the Postgres version, but those also don't give you PITR.) The WAL format is a Postgres implementation detail and therefore tools wanting to read and write it need maintenance whenever the format changes (which can happen on major version releases).
(I'm kidding, but I'm sure someone has a pie-in-the-sky geoengineering startup
about to disrupt topography using either AI, blockchain, or both.)
Well, there was that plan to use scores of nuclear bombs to alter the geography of Egypt in such a way that the Mediterranean could be drained into the Qattara Basin [1]. I think the story is somewhat well-known now, but it proves, at least, that pie-in-the-sky geoengineering startups are not a phenomenon unique to the 21st century. And given that nuclear bombs essentially were the blockchain of the 1950s, that is altogether unsurprising.
That's my approach to recreate a soft drink (ClubMate), like OP is trying to recreate Coke (etc.). Would love to also learn something about the traditional recipe
For the use cases outlined in the OP, a 36% performance gain for an optimization that complex would be considered a waste of time. OP was explicitly not talking about code that cares about the performance of its hot path that much. Most applications spend 90% of their runtime waiting for IO anyway, so optimizations of this scale don't do anything.
Adding a few borrows and annotations is not "an optimization that complex"; use Arc at first but then find those bottlenecks via profiling then fix them.
> Most applications spend 90% of their runtime waiting for IO anyway, so optimizations of this scale don't do anything.
Again, depends on what you are doing. If you are doing web servers, electron apps or microcontrollers, sure. If you are doing batch computation, games, simulation, anything number crunchy, etc: no. As soon as you are CPU or memory bandwidth bound, optimisation does matter. And if you care about battery usage you also want to go to sleep as soon as possible (so any phone apps for example).
Funnily enough, in the blog post you linked Scott Alexander also ruminates about how he never previously questioned journalistic attempts to dox Satoshi Nakamoto.
> Signal insists on using your phone number too, refusing user ids or anything that will make analysis hard.
That is no longer true, you can use user IDs now.
For the other problem, you can enable self-deleting messages in group chats, limiting the damage when a chat does become compromised. Of course, this doesn't stop any persistent threat, such as law enforcement (is that even the right term anymore?) getting access to an unlocked phone.
It doesn't mean much if it isn't the default, even then people who got it prior to that use phone numbers, you can protect yourself maybe, but not other people in the group. But it's good they're doing this now.
reply