A blogger asks why Aaron Swartz faced prison for scraping while Meta pirated terabytes of books with no real punishment.
What the article says
- The post argues Aaron Swartz was hounded to suicide for downloading academic papers from JSTOR, facing decades in prison and huge fines.
- Meanwhile Meta reportedly torrented a massive trove of books to train its AI models and has faced barely any consequences.
- The writer sees this as proof the law protects powerful companies while crushing individuals who threaten a business model.
- Swartz wanted to share knowledge freely. Meta's scraping fuels a profitable product, which the author says explains the different treatment.
What HN is saying
- Commenters largely agree Swartz's prosecution was a vindictive overreach driven by a prosecutor's ambitions rather than real justice.
- The sharpest pushback says the headline oversimplifies things. Swartz physically broke into a wiring closet and evaded bans, which is legally different from scraping public web pages.
- Another correction, he was never really facing thirty five years. That number was the maximum on paper, not what prosecutors actually sought.
- Several people note the deeper legal distinction, distributing copies is prosecuted harshly while AI companies avoid that by only training on the data, not sharing it.
- One commenter adds grim historical context, comparing it to a British scandal where a company privately prosecuted hundreds of innocent people.
A satirical site begs people to stop pasting raw AI answers into chats, and the comments prove its own point.
What the article says
- A short satirical page argues that when someone asks you a question, they want your judgment, not a wall of copied chatbot text.
- The site says AI is fine for drafting, but you should read the answer, take the useful part, and write your own reply.
- If you genuinely have nothing to add, it suggests just saying so instead of dumping a generic response on someone.
- It offers a polite version and an angrier version to send to coworkers who paste AI replies at you.
- The page ends by noting it was written by a human on purpose, and calls itself satire.
What HN is saying
- Many commenters pointed out the irony that the site itself reads as AI generated, right down to its bullet points and forced metaphors.
- One person ran it through an AI detector and it came back fully AI written, which readers called hypocritical given the message.
- A recurring theme was that this is just the old let me google that for you problem back again, aimed at lazy questions as much as lazy answers.
- Some argued that pasting full AI context is actually more helpful than a vague human message, since it saves back and forth.
- Others said the friction of a badly worded human reply is the point, since it builds trust and skill in ways a polished AI answer never will.
AliExpress secretly plays a silent audio track to fingerprint your device, and it can hijack your Bluetooth headphones.
What the article says
- A user's Bluetooth headphones kept getting stuck connected to their PC, cutting off phone audio, only on AliExpress.
- Digging into the page found two hidden audio setups that generate a tone, analyze how it sounds, then mute it before it reaches your speakers.
- The graph still counts as active audio playback, so the browser keeps the audio hardware engaged even though you hear nothing.
- That's what was locking his multipoint headphones onto his PC. Tab muting did nothing because there was no video or audio element to mute.
- The same scripts also check dozens of other signals, like graphics card details and mouse movement, building a fuller fingerprint likely meant for fraud detection, and he shares an ad blocker rule that stops it.
What HN is saying
- Commenters report the same glitch elsewhere. Hearing aid users describe websites and apps quietly triggering Bluetooth streaming mode, dropping ambient sound.
- One person traced a similar stutter on their laptop to American Express's login page polling Bluetooth for anti bot checks.
- Others say the AliExpress phone app does this too, interrupting car audio, and some Chinese apps reportedly use these tricks to inflate active user counts.
- A Firefox developer chimes in with his own writeup on how thoroughly the fingerprinting has been studied and partly blocked.
- Bigger picture, people are frustrated that browsers grant this level of access without a visible permission prompt, and argue audio and Bluetooth access should require explicit consent like camera or microphone do.
Google quietly made it much harder to get Pixel source code, and GrapheneOS says it may break the GPL.
What the article says
- Google stopped pushing Git tags for Pixel kernel and driver code to the main Android source tree.
- Pixels no longer get their own AOSP releases, just yearly updates and monthly security patches like other phones.
- Getting the actual source now means filling out a Google Form and waiting, sometimes for weeks, for a Google Drive link.
- GrapheneOS says this used to take hours and is now a deliberately painful process.
- The change already pushed GrapheneOS into a new partnership with Motorola for its next phone.
What HN is saying
- Most commenters agree this looks like a deliberate, hostile move even if it is not technically illegal.
- The sharpest fight is over whether it actually breaks the GPL. Some say the license never promised a specific format or speed, others argue tarballs and slow manual approval no longer count as a reasonable way to share code today.
- Several people guess at motives: security through obscurity, tightening control over Android, or just avoiding the work of syncing Google's internal code to a public repo.
- A few users say this settles it for them and they are switching from Pixel to the upcoming Motorola GrapheneOS phone.
- One commenter pushes back on the framing entirely, noting Android has always been more source available than fully open source.
A running list of things plain HTML can now do without a line of JavaScript, from popups to accordions.
What the article says
- A developer built a page cataloguing browser features that used to need JavaScript and now ship as plain HTML.
- Buttons can open and close popups and dialogs on their own, including light dismiss and automatic stacking.
- Grouped collapsible sections can act like an accordion where opening one closes the others.
- Images can lazy load, and hidden text can still be found by the browser's search.
- The author warns some of these features still look inconsistent across browsers and can have real accessibility gaps.
What HN is saying
- Commenters mostly love these features but warn the newest ones are still rough or inconsistently supported.
- Several people say positioning popups near the button that opened them is still the hardest part, though CSS anchor positioning helps once it clicks.
- One thread flags that AI coding tools barely know these newer standards and default to old JavaScript patterns instead.
- A sharp disagreement breaks out over the auto closing accordion behavior, some find it slick, others call it user hostile.
- Multiple readers want native table sorting and better styling for built in dropdowns, since custom versions keep getting reinvented.