I remember this being a big area of interest about 15 years ago, but there doesn't seem to have been much about it lately. So long as it's done in real time and just for the reader, and not an audience, I would be inclined to say that it's not infringing the reproduction right, derivative right, or most significantly, the public performance right.

You've never had to buy a license to read a book. Perhaps if you're doing other things in association with your book reading, you might need a license for that but not for just reading.

We've yet to invent a general-purpose AI. These things aren't reading books the way we do. My understanding is that they're basically compiling statistical models, and figuring out how each word or part of word relates to others. Kind of a more complicated version of playing the autocomplete game on your phone, where you input one word in a text chat and then just choose whatever the next suggested word is. The sentences you get make sense for a little while, but become run-ons and start to loop.

Analyzing a work isn't a copyright infringement. Predicate work needed to reach the point of conducting an analysis might, though. And the output of the software might as well.

That and also not wanting machines to be able to write things that sound like something she might write. Licensing isn't all that relevant, as in many cases a license would simply not be granted.

Personally I found this really eye-opening, so...

I don't think that is correct. If you are an EU citizen in Australia you are under Australian laws. However, if you are an EU citizen whose data is transferred outside the EU then the entities transferring it have to add the GDPRs standard contractual clauses to the contracts to give you the same rights as if the data was still inside the EU.

This. I recall a Flash video from back in the day that showed the relative scale of things in the universe, from the largest known cosmic structures like galaxy clusters, right down through macroscopic/human scale stuff, to the smallest known sub-atomic particles. All that was pretty well populated, with known objects present at almost every order of magnitude. However, if you continued zooming in there was then... nothing. Many, many orders of magnitude with nothing known at that scale until you arrived at the Planck length and hypothetical "fabric of the universe" type stuff.

It seems highly unlikely there's absolutely nothing there, but the kind of equipment we'd need to explore that far down into the foundations of the universe is way, way, beyond anything we might even dream of today. While this proposed collider might get us a few more orders of magnitude down from the LHC, there is still clearly a *looong* way down still to go beyond it's capabilities. You've got to start somewhere though, and that knowledge can then drive the designs for the next generation. Or maybe we could just cut to the chase and sub-contract the construction job out to the Magratheans?

This is why I trust my (cerowrt, now openwrt) wndr3800s far more than any modern PC or embedded hardware. No blobs. I sleep better. There were only two major CVEs I was ever worried about - one was kind of big, and in the FPU emulator...

I keep hoping someone will give me a simple packet capture of a single 1 minute tcp download via fq_codel shaping inbound on pfsense. I am pretty sure at this point there is something wrong here, but lack the skills and time to sort out the complaints from the reality. https://www.reddit.com/r/opnse...

I still use venerable WNDR3800s (15 years old now) as APs. (I had about 30 left over after the make-wifi-fast project ceased) They do 300Mbit, no binary blobs, have good range, stay up forever (I know of people with 3+years uptime), and are the best known fq_codel implementation across the board.

Elsewhere I kind of gave up on an all-in-one unit for gbit+ networking and went with the evenroute pro (sadly deceased, but the company was VERY good about upgrading their userbase to mainline OpenWrt) - but any x8664 mini-pc with few ethernet ports suffices nowadays.

The mt76 and mt79 wifi chips stablized a lot in the past year (and have way less "blob" to them than the qcomm gear - so they are looking like the successor to the ath9k for me.

fq_codel native on the mt76 and mt79 chips is the bomb. https://blog.cerowrt.org/post/... OpenWrt has CAKE also. I am seeing a lot of *sense fanbois complaining that fq_codel shaping inbound on BSD is seemingly buggy, and those that went from opnsense to OpenWrt, much happier with CAKE on the QoE front. I have been trying to find someone with BSD experience for ages to help figure out what is going wrong on that OS in this department.

Let's say they use bleach or some such that kills "99.99% of known germs dead", rather than just quickly rinse them or, $deity forbid, have gone directly from the cubicle/urinal to the hand dryer. That still leaves .01% to liberate and blow around. Per user.

Starting to look like a DNSSec key rotation failure, but that could also be connected to attempts to further fsck with the privacy and security of DNS within Russia as well. (I'm assuming most internal servers are already backdoored to quite some degree):

https://dnsviz.net/d/ru/ZbjruA/dnssec/
https://dnsviz.net/d/ru/ZbkVXw/dnssec/

I wish t-mobile, etc, would realize that if they fixed their bufferbloat, the complaints about speed would vanish, and they could still throttle big users to their hearts content. fq_codeled 5G in my lifetime would be nice to see.

Python is not "massively more modern" than Java. It's 4 years older.

Like I said, if a disk needs to be ejected at boot, you hold down the mouse button during boot and it should be ejected by the drive. This is even mentioned in the 128k's manual. The paperclip thing is only if nothing else works.

If the machine is already up, ejecting the disk normally should work fine as long as it isn't in use. If it is, you can close out whatever's using it or if it's already the boot disk, well, too late given that your issue was not wanting it to boot off that disk.

And yes, there were two originally hidden, but later sometimes subtle but immediately available "programmer's keys" for reset and interrupt. Given the flaky OS of the day, though, dropping into MACSbug was usually pretty pointless.

On older machines, you needed to order a small plastic clip that fit on the side and would poke the buttons hidden behind some of the vents. Eventually they were provided as small buttons on the case. Or you could just use the right sort of many-button keyboard shortcut.