Misguided JavaScript API: Origin Private File System
The Origin Private File System (OPFS) is a new JavaScript API that prioritizes web developers' needs over user privacy. It allows websites to access a private file system on users' devices without stringent security checks, raising concerns about data exfiltration and excessive storage quotas. Critics argue that the OPFS poses significant risks to user control and privacy, suggesting it should not have been implemented.
- ▪The OPFS offers low-level file access that is private to the origin of the page.
- ▪Websites can potentially exploit the OPFS for side channel data exfiltration attacks.
- ▪The API allows websites to store up to approximately 60% of total disk space, which can lead to excessive data storage.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Lapcatsoftware |
| Canonical URL | https://lapcatsoftware.com/articles/2026/5/5.html |
| Publication time | Thu, 28 May 2026 22:43:58 +0000 |
| Retrieval time | 2026-05-28T22:59:38.379Z |
| Last seen | 2026-05-28T22:59:38.379Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | B69CAAeC8Io4 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Previous: The Mythical App Store Reviewer Month Articles index Jeff Johnson (My apps, PayPal.Me, Mastodon) Misguided JavaScript API: Origin Private File System May 28 2026 The web browser vendors continually add JavaScript API that prioritize the needs of web developers over web users. The interests of the two groups can conflict, for example because web developers often want to fingerprint and track web users, and I would note that Google Search advertising revenue provides a large part of the funding for all three of the major web browser engines: Chromium, Gecko/Quantum, and WebKit.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Lapcatsoftware.
Discussion
0 commentsMore from Lapcatsoftware
