HN user
https://jamesmilne.org
@shaknais@mastodon.social
No... But as we're discussing people who tried to pay nothing... Maybe they should have just bought the books in the first place. And comparing my single sentence on HN, to the hundreds of millions ingested, does suggest that maybe scale changes something.
Like most things said on social media, not being copyrightable.
The assembler you're looking for, is called YUL. [0]
You can find much of that code here [1], but unless you have a Honeywell, it isn't much help. yaYUL is a modern remake, and can assemble most of the Apollo code.
[0] https://www.ibiblio.org/apollo/Documents/agcis_13_yul.pdf
Format shifting has a DMCA carveout. It is 100% allowed. Since around 2000, the rule has permitted it for:
Literary works, including computer programs and databases, protected by access control mechanisms that fail to permit access because of malfunction, damage, or obsoleteness.
DRM being covered under other laws, and being gross, still applies. And still applies to industry giants, too. Which is why most who do this, like Google, actually buy physical copies and scan it destructively, so they don't have to deal with it.
Well, as not every book is a textbook, I'd say quite a lot of what I've read never went to any kind of knowledge in my head at all. But I reckon the author still deserves to eat.
So, continuing to profit--forever--from someone's else work, at scale, without their prior consent, is fair use?
No, that's what they got in trouble for - a lack of consent.
If the author consents, it would have been fine. If they bought the books, then it is fine. Digitisation through destruction, like most book scanning systems. As long as the original work is destroyed during the process, and you actually paid for it, then it is fair use.
If it regurgitates, then the author can sue you again. So you are incentivised to make damn sure it doesn't. That's not covered by fair use.
Its only if the original cannot be accessed anymore, and you paid to get the original. Both must be true, for fair use to hold.
Accessibility.
I, sometimes, use a circular software keyboard, that is controlled by eye tracking.
Known Issues
Exclusive fullscreen mode on Windows may cause the game to crash in certain situations, especially when using multiple monitors
Entering Exclusive fullscreen mode crashes the game on Wayland
Those, together, kinda seem like the kind of blocking bug that would usually delay a snapshot... Lets hoping it gets fixed before release lands...
Prod bugs up 260% since AI approval? Yeah, I'm gonna disagree.
BAs using AI make worse designs, management makes seniors redundant making code worse, and then QA is also laid off to make room for agentic testing. The results are not a surprise in anyway.
Our primary wordmark requires prescribed clear space and should NOT be used with the Blossom.
Ironic missing space right there...
Management think models mean juniors can do senior work. Juniors don't know the footguns. Juniors can't read the code that the system outputs. Models get overwhelmed in any decent sized codebase.
Why would you be surprised there are failures?
I bet that security will be better.
Not doxing myself, but... Company with a known name vibecoded a dashboard with Claude. Which also hardcoded a password into the client-side of the dashboard, which I caught.
I reckon security will be about the same.
Monkey. And the author. [0]
I've been playing around with SmallBASIC [0], which also comes with raylib, but also nuklear.
BASIC as a game design language does feel like some of the common game abstractions like the draw and tick loops, are really well suited to it. And offloading the math-heavy things like raycasting to C and importing does give you a nice abstraction layer.
Have fun exploring the list of things we've caught abusers actually using. [0] Or don't. Reading and keeping your soul intact aren't compatible.
I am 100% sure that some do, thanks to firsthand life. And any doing it, is enough to get people dead, even if 99% don't. And yes, CS majors can be abusers, too.
[0] https://www.esafety.gov.au/key-topics/domestic-family-violen...
Sounds like one of ADOs recent security misconfiguration vulnerability announcements. The customer is blamed, for not quite hardening everything the right way, when ADO config is... A sizeable task.
Sure, that's true.
It is also true that Copilot is currently in use developing Bitlocker and Sharepoint. So I wouldn't be confident saying it was one or the other.
This would also leave intact cookies, local/session storage, indexeddb, caches. All of which abusers do actually check, when controlling their victims.
You mention someone else's Python version. Did you note that the prototype in the video was... Python?
All the smells you pointed out, just look like a Python dev approaching bash without fully understanding it.
I wonder if the script itself was written by an LLM before obfuscation?
From the prototype shown here [0], and the way they talk about their process, I sincerely doubt it. Especially as they mention trying to make it hard for AI to handle the output.
Whilst the US has a carveout saying it has to be commercial, Australia, Quebec, and others, do not.
You do, in fact, have rights over your 'likeness'. In most jurisdictions. [0]
In the US, that would fall under Prosser's Four Torts, "appropriation of name and likeness".
The law, currently, doesn't care if you think its a new image. Likeness is protected. Similarity is enough.
Most enterprises require a 12 digit code, to meet a specific security standard. Bruteforcing that, with hardware access restricted by TPM, would take a very, very long time.
RFK's reliance on terrain theory, disproved continually since some five hundred years ago, does much to assist in citations - it is common to cite bad science as evidence where we need to improve public comprehension.
Our current research shows that people don't click. But they do scroll. So... Yes.
Infinite scrolling makes it harder to break the feedback loop, and harder to control self-interruption. It also increases the overall dopamine experienced.
Pagination, allows the user to regularly break from the cycle, and most people take advantage to do so. It allows people to notice fatigue. Which is exactly why most social media sites no longer use it.
As the 'inventor' of the infinite scroll said:
[it is] one of the first products designed to not simply help a user, but to deliberately keep them online for as long as possible - Aza Raskin
Unfortunately, that only takes care of one of the vulnerabilities that comes with basic auth.
As basic auth sends the header for every single request, it is also vulnerable to CSRF attacks.
HTTP basic auth is not secure.
That is exactly what X was designed to do. And part of why X is considered insecure today.
Decayed without breaking down, is my point. There was a failure. Which means failure is a possibility and not something to just dismiss.
If they always got the decay correct, we wouldn't have confirmed debris impact on the ground. It would be destroyed long before it reached.
https://www.smithsonianmag.com/smart-news/after-fiery-displa...
HN specifically does not. You have to click "more", leading to most people not moving beyond two or three pages, rather than infinite scrolling.