Top HN Daily Digest · Tue, Apr 14, 2026

A daily Hacker News digest with story summaries, thread context, and direct links back to the original discussion.


0. Backblaze has stopped backing up OneDrive and Dropbox folders and maybe others (rareese.com)

1035 points · 619 comments · by rrreese

Backblaze has updated its backup client to automatically exclude folders from cloud storage providers like OneDrive, Dropbox, and Google Drive, as well as `.git` directories. Users are criticizing the company for implementing these exclusions silently without direct notification or clear documentation on their website. [src]

Backblaze's decision to exclude OneDrive and Dropbox folders from its personal backup service is seen by users as a breach of its "unlimited" storage promise and a failure to act as a reliable last-resort backup [0][3][8]. While some commenters suggest the change is a technical necessity to prevent "files on demand" features from crashing laptops by forcing massive downloads [1], others argue that excluding synced folders leaves users vulnerable to data loss if a sync service accidentally overwrites or corrupts files [3][5]. Critics contend that "unlimited" marketing is inherently unsustainable and signals that financial teams are prioritizing cost-cutting over data integrity [2][9].

1. DaVinci Resolve – Photo (blackmagicdesign.com)

1082 points · 271 comments · by thebiblelover7

Blackmagic Design has introduced a dedicated Photo page to DaVinci Resolve, bringing its advanced Hollywood color grading tools, AI-powered effects, and RAW support to still photography. The update includes non-destructive editing, GPU-accelerated processing, and cloud-based collaboration for professional photographers and retouchers. [src]

Users are excited that DaVinci Resolve is bringing advanced video-centric color science and creative tools like relighting and film emulation to the stagnant photography market [0][3]. While some praise its performance on Linux via containerization [9], others report significant frustration with outdated audio APIs and codec support on the platform [2]. Early testers find the interface confusing and "tacked on" compared to Lightroom, suggesting that while the software is powerful, it currently lacks the intuitive workflow required to sway professional photographers [7].

2. A new spam policy for “back button hijacking” (developers.google.com)

862 points · 488 comments · by zdw

Google has introduced a new spam policy targeting "back button hijacking," a technique that prevents users from returning to search results by manipulating browser history. The policy aims to improve user experience by penalizing sites that trap visitors or redirect them to unwanted content. [src]

Users identify major platforms like LinkedIn, Reddit, and Microsoft as frequent offenders that manipulate browser history to trap visitors within their ecosystems [0][3][7]. While some argue that the History API is essential for modern single-page applications and bookmarking, there is a strong consensus that these features are being weaponized for "encrapification" and advertising [1][9]. Proposed solutions include restricting third-party domains from modifying history stacks and broader calls to limit how much JavaScript can override native browser behaviors [2][5][6].

3. jj – the CLI for Jujutsu (steveklabnik.github.io)

514 points · 446 comments · by tigerlily

Jujutsu (`jj`) is a distributed version control system that aims to be simpler and more powerful than Git while maintaining full Git compatibility, allowing users to adopt its advanced workflows without requiring their collaborators to switch. [src]

The primary debate surrounding `jj` centers on its "automatic commit" behavior, which some users find intuitive for tracking logical changes while others view it as a "footgun" that risks accidentally rewriting history [0][1][2]. Critics argue that the `jj edit` command leads to unintended rebases of subsequent work, though proponents suggest using `jj new` to create cheap snapshots instead of traditional Git-style staging [2][7][8]. Despite disagreements over the workflow's "backward" mental model, there is strong consensus that `jj`’s Git-compatible backend makes it a low-risk tool to trial within existing ecosystems [6][9].

4. Claude Code Routines (code.claude.com)

546 points · 313 comments · by matthieu_bl

Claude Code routines are automated, cloud-based configurations that execute tasks like code reviews and backlog maintenance via scheduled, API, or GitHub event triggers. [src]

The introduction of Claude Code Routines has sparked significant skepticism regarding vendor lock-in, with users expressing a lack of trust in Anthropic’s long-term stability and a preference for "dumb pipe" API access over integrated platforms [0][2]. Developers are particularly concerned about confusing Terms of Service regarding third-party harnesses and the potential for account termination when integrating these tools into external applications [1][4]. Additionally, many users report a perceived decline in model performance and "nerfing," questioning how autonomous routines can function effectively under increasingly restrictive usage limits [3][5][8]. While some compare these fears to early cloud adoption anxieties that never fully materialized [6], others are impressed by Anthropic's rapid feature delivery, which is quickly outpacing open-source alternatives [9].

5. Spain to expand internet blocks to tennis, golf, movies broadcasting times (bandaancha.eu)

407 points · 415 comments · by akyuu

We couldn't summarize this story. [src]

The debate centers on whether Spain’s aggressive internet blocking is a response to a "service problem" or a "pricing problem." Some argue that piracy persists because official services are fragmented, laden with ads, and difficult to cancel [0][2], while others contend that many users pirate simply to get "free stuff" as a game or cultural habit, even when they can afford to pay [1][3]. Critics suggest these blocks are an "absurd" overreach by a bureaucratic state that undermines privacy and should be regulated at the EU level [4][6][7]. Ultimately, some believe pirate sites will always offer a superior user experience because they lack the legal and financial constraints of official channels [8].

6. I wrote to Flock's privacy contact to opt out of their domestic spying program (honeypot.net)

569 points · 230 comments · by speckx

Flock Safety denied a California resident's CCPA request to delete personal and vehicle data, claiming that as a service provider, it cannot fulfill requests directly because its customers own and control the collected information. [src]

The primary debate centers on whether Flock Safety acts as a mere service provider, similar to a cloud storage vendor, or as a data broker responsible for the information its cameras collect [1][3][9]. Flock claims that customers own the data, but critics argue the company maintains "unfettered access" to a massive surveillance network to drive its multi-billion dollar valuation while shifting legal liability to local agencies [0][8]. There is significant disagreement over whether license plate captures in public constitute "personal information" under the CCPA and whether the company's ownership of the hardware makes them legally responsible for deletion requests [4][5][6][7].

7. Rare concert recordings are landing on the Internet Archive (techcrunch.com)

596 points · 170 comments · by jrm-veris

The Internet Archive is digitizing music superfan Aadam Jacobs’ collection of over 10,000 rare concert cassette tapes recorded since the 1980s, featuring previously unreleased performances from artists like Nirvana, Phish, and Sonic Youth. [src]

The preservation of rare concert recordings on the Internet Archive highlights the historical value of bootlegging, with recordists sharing anecdotes of bands embracing high-quality fan recordings as valuable additions to their digital legacy [0][7]. While some users lament the loss of physical music shops where such "gems" were once easily accessible, others argue that copyright laws should be reformed to move music into the public domain after 30 years [2][3]. There is a strong consensus that artists benefit from these archives, leading to suggestions that musicians should officially record and sell live sets directly to attendees [1][2].

8. Stop Flock (stopflock.com)

544 points · 128 comments · by cdrnsf

Stop Flock is a campaign raising awareness about Flock Safety’s AI-powered surveillance network, which uses "vehicle fingerprints" to track movement patterns and associations across a nationwide database accessible to police without a warrant, sparking significant Fourth Amendment and privacy concerns. [src]

The discussion highlights a tension between public safety and the dangers of mass surveillance, with some arguing that institutional leaders face immense pressure to eliminate camera blind spots to track criminals [0]. Critics contend that the current business model of data brokering creates "toxic waste" that threatens privacy, suggesting that data should be treated as a legal extension of the home requiring warrants and mandatory notifications [1][2]. While some argue there is no expectation of privacy in public spaces [3], others emphasize the need to close legal loopholes that allow the government to "launder" information through third parties to bypass Fourth Amendment protections [5][9].

9. Tell HN: Fiverr left customer files public and searchable

509 points · 103 comments · by morpheuskafka

Fiverr is reportedly exposing sensitive customer documents and PII in public Google search results due to the use of unsecured Cloudinary URLs for private messaging and work products. [src]

Fiverr has faced criticism for leaving sensitive customer files—including tax forms, API tokens, admin credentials, and internal reports—publicly searchable and accessible [3][4][5][7]. While Fiverr claims they are working on a resolution and disputed the timeline of initial reports, users argue the leak is so severe that the company should immediately block all static asset access regardless of business impact [1][3][8]. The incident sparked a debate over professional standards: some argue for mandatory software engineering certifications to prevent such incompetence, while others contend that licensing would be an ineffective "hassle" that cannot solve fundamental carelessness [0][2][6][9].