10,740 karma · joined March 11, 2011
hnchat.com:3XTKnS6ltyuLoPtjZlYF
Opinions and views expressed here are my own.
However, there is certainly a chance that Apple team didn't think the impact was that bad given all the other protections in place.
When Steve Jobs was alive, his Apple company email was leaked and published and Apple customers emailed him for features and fixes all the time and he personally responded once a while. Tim Cook did the same a couple times too. Perhaps the blog author should write in to the new CEO John Ternus or SVP of Software Engineering Craig Federighi too to see if they can fix that.
The fact that other math problems are bulk solved yet nothing from cryptography was released/published as solved could be a strong indicator that "all modern public key based cryptography" could have been at risk.
I just ran an security analysis on the repo. As is, it's not looking great (again nothing against vibe/agentic coded projects) the lack of security consideration is astonishing (not suggesting a malice). Definitely NOT production ready.
Context: about 98% of the commits are by AI bots (Antigravity, Google Jules).
That explains the bugs below.
Security bugs
1. High: the local web API lets any website use the user's files.
- paperpilot-gateway/src/server.rs:95-98 allows requests from any website, and
there's no login or authentication.
- POST /api/v1/pdf/mcp-exec (handlers.rs:233) runs any tool with any file path
on the machine.
- So while the API is running, any web page the user visits can make it
overwrite files with PDFs, create folders, and read back text from any local
PDF.
- In the desktop app the user has to switch the API on. But docker-compose.yml
opens it to the network with no authentication.
- There's also no limit on request size (usize::MAX), so one huge request can
exhaust memory.
2. High: a malicious document can run code in the desktop app.
- Search results display text from the user's own documents as raw HTML
without escaping it:
- WorkspaceSearchModal.svelte:297
- workspaceSearch.ts:84
- WorkspaceSearchModal.svelte:118
- The app has no Content Security Policy, and lets its window read any file on
disk (tauri.conf.json:28-33, scope "**").
- So a PDF or DOCX carrying an <img onerror=…> payload could read any local
file and send it out once the user searches it.
3. Medium: downloaded models and add-on packs are never verified.
- There's no checksum check on models (ai_commands.rs, ocr_commands.rs). Some
come straight from the repo's live main branch, so whatever lands there
ships to users.
- Pack downloads (pack_commands.rs:147-151) put pack_id straight into the file
path. A value containing ../ writes outside the app's data folder.
- Packs come from huggingface.co/paperpilot/packs, an account I didn't confirm
the project owns.
4. Medium/Low: the protection against fetching internal addresses can be
bypassed (paperpilot-core/src/url_fetch.rs:24-40).
- It only checks IP addresses typed directly into the URL, not what a domain
name resolves to.
- It follows redirects, so a public URL can redirect to an internal one.
- IPv6 addresses ([::1]), 0.0.0.0 and the 100.64.0.0/10 range get through.
- The impact is limited because the response must start with %PDF.
5. Low: CI supply chain.
- release.yml installs wasm-pack via curl | sh.
- GitHub Actions are pinned to version tags, not commit hashes.
- The Android build ignores the lockfile (--no-frozen-lockfile).The second video, the person who's shooting the video has his face mirrored onto the screen, anonymity is gone.
A study published in 2017 points out that almost everything known about the 50 Cent Party in the past had been wrong. Most combative posts and commentators attributed to the 50 Cent Party were instead linked to private nationalistic individuals.
So the term became a misnomer.The most iconic line was the last sentence:
a bitter lesson for interpretability: the simple thing, at absurd scale, works
This feels like the watershed moment, again if Nick is proven right, as massive as the AlexNet victory in the 2012 ImageNet Large Scale Visual Recognition Challenge, exactly as Nick pointed out.Also, I suspect what Nick hinted at, might be the discovery of earliest RSI work.
with modern agentic tools and a much closer look, the picture looks totally different.At the current market price of Apple Mac Studio Ultra, 30-core CPU + 64-core GPU w/ 256GB RAM is already reaching at around $10k. Keep in mind that computers are appreciating assets recently.
The 512GB RAM option is not even for sales yet (they said late October availability). Based on typical Apple pricing, it's likely to be around $14k apiece. So we are looking at least $28k - $30k for the setup Muse team is advertising. That's essentially the Nvidia H100 GPU w/ 96GB VRAM/HBM3 at up to 3.94 TB/second memory bandwidth, 3x+ than Mac Studio's Unified Memory speed.
Also, how did Meta get access to Apple's unreleased M5 Ultra w/512GB RAM Mac Studio? Or is that simply a marketing piece that they wrote purely on specs?
- pg_vectorsearch uses a quantized IVF index called PRISM. PRISM caps at 1968 dimensions for vectors. If your previous HNSW index has more dimensions than that, you're SOL (at least for now until they fix that).
- pg_vectorsearch requires Postgres version 18 or above. If you run PG versions below that you need to migrate your database first. Many legacy PG production environment are way dated on PG 14 or 15, migration is prohibitively high cost to just try this out.
- pg_vectorsearch shipped yesterday and it's obviously alpha. Hasn't been battle tested in production environments outside of Timescale's. Also since it's so new, it isn't on Azure's allowed-extension list or any other Hyperscale's managed PG instances' allowed extension list. It takes time to graduate from alpha and mature. So if you run managaed PG instances from hyperscaler's cloud, you're SOL (at least for now until this matures into those ecosystems) or you have to migrate to a PG 18 self-hosted.
1. they have no-cap token spend allowance internally
2. their agent swarms are amongst the largest if not the largest, again because #1 above.
3. their git repo is enormously large (100GB uncompressed git history on main, 25GB compressed).
4. their merges per day count grew an order of magnitude from May to September to 30000 times per day, they are not seeing it slowing down anytime and probably only going to accelerate.
5. all of their code agents are networked and has network access, full local pull down is not needed at all and too slow (see #3)
6. their design of the Scion is based off prior art Google’s Piper and Meta’s Sapling.
Given their own constraints and characteristics of their own. It only makes sense to build their own homegrown solution based on prior arts. But this was NOT a complete redesign from scratch - so it's an full online download only what you need type of source control system. The problem is the version control software itself but its prior tradeoffs are misaligned with their scaling needs.
PS, if anyone noticed, Anthropic starts to concealing their employee full names and replaced with only first name + last name initiate, not sure why.
PPS, the project Scion is so bad, scn is worst, it reminds people of prior SVN, which is bad by itself.
[1] https://archive.ph/FhG5L (the original either got deleted or login-walled, here is the archived version)
[2] https://hn.algolia.com/?q=always+bet+on+text
[3] https://news.ycombinator.com/item?id=26164001
[4] https://news.ycombinator.com/item?id=8451271
He posted another news from 2025 for OKI's 124 layer PCB news.
Dan, this is 2025! Not a Hacker News-worthy at the end of 2026.
Also, 124 layer PCB is ONLY 15% extra than the conventional 108 layer PCB. Incremental upgrade!
I didn't say that - Greg said it in the talk. You interpreted wrong. However, human are a few orders of magnitude slower than agents. Our context windows is definitely less than 1 million tokens (I believe, heck we don't even know how our brain works)
I do know this: having anthropomorphizing and romanticizing your dumb robots for so long like a soap opera from your founder's feed, and now staged this "humanized" robot incinerated in a melting pot EXACTLY like Terminator franchise's ending plot and EVEN hiring Arnold Schwarzenegger for a cameo, is giving me full goosebumps, NOT the right ones.
I hope Brett Adcock realize that the Terminator franchise is literally the p(doom) outcome, not just in the names only.
EPIC FAIL in your marketing stunt!
- Computer History Museum (CHM) in Mountain View, California (yes very close to Google's HQ - Google's a huge donor). Absolute the best collection of Computer Science history both from theories to software to hardware.[1]
- Museum of Radio and Technology in Huntington, West Virginia. A tiny museum completely organized by volunteers and donors (some were WW2 GIs and 3 letter agency retirees). Not famous at all in an old elementary school building. But collections were amazing. [2]
[1]: https://computerhistory.org/
[2]: https://en.wikipedia.org/wiki/Museum_of_Radio_and_Technology
Yeah, the "Several" is a massive understatement.
We would never know how since that's the part USPS redacted heavily.
I wish Anthropic/OpenAI FDE take over USPS IT altogether.
If you generate a random number even fitting the pattern and looks like a real one, the scan will fail with an error and fail to register tracking information every single step of the way that package gets scanned from dropoff at the retail postal office (this was the case) as bulk inbound pickup from USPS are only allowed for USPS verified partners.
Label creation (which generates the tracking number) is a billable action in their API. Some volume partners have pre-arranged/allocated tracking number segments assigned to the bulk volume partner/shipper (similar like how IP address v4 is assignment from IANA). And that pre-allocation tracking number range requires $$$$ contract in place. Billing that is post paid like cellphone bill.
Most retail shipping software (like shipengine, pirateship etc.) bills using the prepaid method, meaning you will have to pay for the label at the time label is generated.
Disclaimer: I used to work for a carrier that integrated a few dozens of global shipping carriers.
America.gov has 1 ERROR and FAILED TO LOAD - this is violating Federal laws. Class action suits anyone?
https://wave.webaim.org/report#/america.gov
Meanwhile the old USA.gov works and loading and no errors (some warnings are expected)
Living in the fear of p(doom) is miserable. We're all gonna die one day anyway.