Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
shdjhdfh
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
3 ms
·
1.
▲
by
shdjhdfh
9mo ago
This was killed in the recent budget bill: https://www.cnbc.com/2025/11/13/congress-thc-hemp-ban.html
2.
▲
by
shdjhdfh
11mo ago
The highest bitrate UHD Blu-ray supports is 144mbit/s: https://en.wikipedia.org/wiki/Ultra_HD_Blu-ray . A one gigabit NIC is not even close to the biggest compromise on this system.
3.
▲
by
shdjhdfh
1y ago
You should assume it will not work unless you test it regularly. That's a big part of why having active/active multi-region is attractive, even though it's much more complex.
4.
▲
by
shdjhdfh
1y ago
My guess is that skywhopper is correct. We're only able to see the tail end of the attack, but the repo was likely compromised in some way.
5.
▲
by
shdjhdfh
1y ago
Another thing to note, the AI angle on this is nonsensical. The commit could have just as easily done many other negative things to the system without AI as a layer of indirection.
6.
▲
by
shdjhdfh
1y ago
Your article breathlessly blames AWS for being reckless while having no real facts about the compromise. The whole thing reads like click bait.
7.
▲
by
shdjhdfh
1y ago
Ah, I think it might have been this, which was reverted and seems to have been pushed directly to master: https://github.com/aws/aws-toolkit-vscode/commit/678851bbe97...
8.
▲
by
shdjhdfh
1y ago
The prompt 404 quotes in the article doesn't appear to exist anywhere in the git history for the repo they point to. It seems unlikely that Amazon would rewrite git history to hide this. Maybe the change was in a repo pulled in as a
9.
▲
by
shdjhdfh
4y ago
It is encrypted at rest: https://github.blog/changelog/2019-05-23-git-data-encryption...