I've been telling people for years that it's probably easier that they get used to the thought that everything about them is "public" in some way than waiting for the day when computers and databases are suddenly safe from hacking.
That doesn't mean that all of your neighbors know your medical history, but you have to assume that someone who wants to know those details about you will know them.
I have lost faith in people protecting any significant database from hackers.
Usually you do "rdrand % <some-number>" anyways, and in that case you will still get zeroes. True, your result might be skewed by 1/(maxint/some-number) but I guess that's not a big problem in practice
If you want uniformly-distributed random numbers, computing the remainder works only when the modulus is a power of two.
Otherwise, a slightly more complicated algorithm is necessary, where you reject a range of numbers either before computing the remainder (to make the set of possible values a multiple of the modulus) or after computing the value modulo some power of two (to reject values greater than your target).
Besides these 2 variants based on the remainder of division of integers, there are also 2 corresponding algorithms using multiplication of the input interpreted as a fraction, followed by taking the integer part of the result.
Example: to get a number between 0-2 (3 values) with a 4-bit RNG (16 values, 0-15) you can split the set 0-14 into 3 groups of 5 (doesn't matter if you use modulus or divide) but if you get 15 you need to re-roll.
I don't get what this is supposed to prove. That my browser doesn't allow websites to declare what encryption they use? I am pretty sure there's a point to all of this, but please let me (and my browser) choose which encryptions I want to trust.
Isn't the idea that the server and client should agree on a common subset? Here, the server's subset is very small, but not esoteric – so then surely it's the client that's lacking in features?
There are "sovereign" clouds like StackIT, OVH, OTC or Scaleway. What they all have in common is that they are lightyears behind hyperscalers in terms of performance, reliability and security. Needless to say, these alternatives can only serve open-source models because they are not capable of training a SOTA equivalent by themselves. The cherry on top is that you have to pay a sovereignty premium for inferior performance.
Local DeepSeek, qwen or kimi models are far better privacy-wise, faster, but much more expensive (to get a 2TB GPU RAM cluster). So everybody went with the Claude, OpenAI or CoPilot business contracts, so their secret business data leaves the EU, but will not be used to train the model. Unlike with the cloud Chinese services.
I used CLFS (Cross-Linux From Scratch) once to bootstrap Linux on my SGI Indy, and I learned quite a lot from this. That was back in 2008 or so, so way before AI and extensive online guides for almost everything. It taught me how cross compilers work, what dependencies exist in the GNU toolchain, how the SGI boots, and much more.
Too bad Cross-LFS is no longer a thing. Then again, with all these microcontrollers and ARM and RISC-V systems today, cross-compiling is no longer as magic (and tricky) as it was back then...
At least the Wolfenstein screenshot is VGA, not EGA. Yes, it looks weird with that dithering effect, but it's still VGA (too many/wrong colors for EGA, and also: Wolfenstein never was released with EGA graphics in the first place)
it would be awesome if there was an ISA bus emulation using some sort of modern protocol. You could create "modern" ISA cards using an RP2350 on every card that does the emulation, to split emulation between multiple RP2350's (one emulates a VGA card, one emulates a sound card, one emulates a network card, etc.)
Bonus points for a standardized connector that everyone could develop towards. Imagine a tiny ISA PC that you could place on your desktop, swap miniscule (ISA)-cards in and out of, and play retro games etc.
"Modern" tiny ISA would probably be LPC [0] which is a relatively simple encapsulation/serialization format for ISA that preserve full software compatibility, and can transport ISA signals over as few as 8 pins.
This thing was quite ubiquitous for inter-connecting some low-speed things within PC motherboards in the early 2000s. Although physically separate LPC cards did exits, those were rare and connector/pinout was never standardized.
it's not that bad. At 120MHz, the PSRAM still gets only around 90-100ns per word in the worst case. If you use some SRAM for caching and do bulk transfers, you can get that down quite a bit. Also you can easily overclock the PSRAM to 133MHt (10 decrease in latency) with no problem, maybe even (much?) more.
normal dynamic RAM back then was at 60-70 ns so it's really not that bad. And YT videos show that it also works fine in practice
That doesn't mean that all of your neighbors know your medical history, but you have to assume that someone who wants to know those details about you will know them.
I have lost faith in people protecting any significant database from hackers.
reply