HN user

greyface-

7,030 karma

Look at all the order around you,

Posts234
Comments1,014
View on HN
www.post-gazette.com 10d ago

The cowboys of crypto: Wyoming ropes a $1 stablecoin

greyface-
5pts1
www.wilmerhale.com 13d ago

The 4th Amendment Moves to the Cloud: Chatrie and the Future of Digital Privacy

greyface-
3pts0
www.justice.gov 15d ago

Las Vegas Business Owner Sentenced to 15 Years for Tax Fraud Scheme (2009)

greyface-
1pts0
papersplease.org 16d ago

When you fly, you fly with ICE

greyface-
2pts0
www.bloomberg.com 20d ago

Egg Libor Was Also Manipulated

greyface-
6pts0
geohot.github.io 1mo ago

You don't understand, prices can't go down

greyface-
8pts3
www.helionenergy.com 1mo ago

Helion obtains regulatory approval to operate fusion power plant in Washington

greyface-
2pts1
mason.gmu.edu 1mo ago

Personal Email Salons (1997)

greyface-
1pts0
osaka.law.miami.edu 1mo ago

Untraceable Digital Cash, Information Markets, and BlackNet (1997)

greyface-
43pts1
oldhome.schmorp.de 2mo ago

Bournegol??? (2014)

greyface-
36pts9
www.cryptnet.net 2mo ago

The Keysigning Party HOWTO (2008)

greyface-
1pts1
www.fcc.gov 2mo ago

FCC Seeks Comment on Enhanced Know-Your-Customer Requirements

greyface-
4pts1
www.bitsaboutmoney.com 2mo ago

Notes on a non-profit indicted for bank fraud

greyface-
42pts8
www.wired.com 3mo ago

Behind the Scenes of the Demise of Muxtape (2008)

greyface-
2pts0
www.icann.org 3mo ago

Financial Information for ICANN

greyface-
1pts0
murmurationstwo.substack.com 3mo ago

Bitcoin developers are mostly not concerned about quantum risk

greyface-
2pts0
support.mozilla.org 3mo ago

How do I turn on the Do Not Track feature?

greyface-
2pts0
www.kuow.org 3mo ago

Washington passes new AI laws to crack down on misinformation, protect minors

greyface-
2pts0
papersplease.org 4mo ago

Your rights when an airport checkpoint is staffed by ICE agents

greyface-
20pts2
archive.blogs.harvard.edu 4mo ago

"Surveillance Camera Man" Provokes Questions About Recording in Public (2013)

greyface-
5pts0
fred.stlouisfed.org 4mo ago

Share of Labour Compensation in GDP for United States (1950-2023)

greyface-
3pts0
apenwarr.ca 4mo ago

Every layer of review makes you 10x slower

greyface-
577pts315
casey.github.io 4mo ago

The BIP

greyface-
1pts0
geohot.github.io 4mo ago

Polynomial Time Factoring Algorithm

greyface-
4pts0
confusedofcalcutta.com 4mo ago

Is there a Gresham's Law for information? (2006)

greyface-
2pts0
www.wikimediastatus.net 4mo ago

Wikipedia was in read-only mode following mass admin account compromise

greyface-
1049pts384
en.wikipedia.org 5mo ago

Yates v. United States (2015)

greyface-
2pts0
datatracker.ietf.org 5mo ago

IP Address Space for Outer Space

greyface-
4pts0
en.wikipedia.org 5mo ago

FISA of 1978 Amendments Act of 2008

greyface-
1pts0
papersplease.org 7mo ago

Has the TSA added immigration enforcement to "Secure Flight"?

greyface-
3pts0
OpenAI Presence 6 hours ago

Instead of throwing an LLM on top of it, just give me direct access to the levers that the agent is allowed to pull on my behalf. A sufficiently motivated attacker will be able to sweet talk the agent around whatever natural language "guardrails" were put in place, anyway.

GP was asking for a guarantee against emitting false decidable statements. We agree that this is impossible. You can slap layers upon layers of heuristics on top, yes, but you will not eliminate all hallucinations because Church and Turing proved it fundamentally impossible nearly a century ago.

It's still very early. RIPE and ARIN have only supported publishing them for a few months. ARIN made very little noise about it during the rollout, and many networks are probably still unaware. Give it a couple years, and I expect we'll see fairly good adoption among those already publishing ROAs. There will still be the never-RPKI holdouts, however.

HE publishes their full ASPA table here, if you're interested in digging in: https://routing.he.net/?cmd=display_aspa_table

RPKI addresses both.

Route Origin Authorizations (ROAs) enforce which ASes are allowed to originate a prefix. ROAs address origin hijacks, and have been around for longer.

Autonomous System Provider Authorizations (ASPAs) enforce which ASes are allowed to be adjacent to each other in an AS_PATH. ASPAs address path hijacks, and were introduced more recently. It used to be that you had to self-host (as in the article) in order to publish ASPAs, but RIRs are now starting to support them on their hosted RPKI offerings. I'm surprised the article didn't mention this as a reason to run your own RPKI.

If the first hop publishes a ROA, and all subsequent hops publish an ASPA, then the full path can be validated.

Remote Attestation 14 days ago

The path to compromise that you describe exists, of course. But it's not the only way. For example, a zero-day in SGX combined with privileged access to AWS infrastructure could compromise Signal's SGX setup without any knowledge or collusion by Signal or Intel. As you note, it is not unreasonable for a project of Signal's stature to expect to face adversaries with such capabilities.

Remote Attestation 14 days ago

running the expected payload

SGX does not cryptographically guarantee this. It cryptographically guarantees that the processor contains a legitimate provisioning key signed by Intel. Intel pinky promises that its processor will then only use this provisioning key in certain ways. This promise is essentially unauditable, and previous SGX bugs have shown that Intel isn't really in a position to make it anyway.

There are infinity dollars in the Federal Reserve. Pay-for requirements are a concern troll bludgeon used against only politically disfavored spending. Taxation (on the federal level) does not pay for services, but merely counteracts the inflationary effect of their provision in an indirect way. It's indirect enough that those who disregard it are not politically punished.

gives over most or all of the dash over to another company

The dash isn't the manufacturer's property. It's the car owner's.

Much of the cost here comes from compliance with the ICANN gTLD program structure, not from running the underlying technical infrastructure (which is not limited to DNS - you also need EPP/RDAP/etc). See https://www.icann.org/en/registry-agreements for (hundred+ page) documents outlining registry responsibilities. Registries can outsource some of this to an ICANN-accredited "registry service provider", but should expect to pay upwards of hundreds of thousands of dollars yearly for the privilege.

https://hccf.onmy.cloud/wp-content/uploads/2026/06/dot-self....

Everyone entitled to a subdomain at no cost

How are you going to pay for the (substantial) cost of running a TLD without registration fee revenue? Is this a loss leader for other services? Are you operating on a 100% donation model?

No parking, squatting, or reselling

How do you plan to tell the difference between a parked/squatted domain and one in legitimate use but offering no public-facing services?

a valuable dataset

It's CC-BY-SA/GFDL, and the underlying copyright belongs to the editors that wrote it. There is no commercial value in reselling access, and WMF does not have the right to relicense it.

Financially, they're not equivalent. If you buy your bread on credit, you get an interest-free loan, and benefit from the time value of the money that you otherwise would have paid immediately. As you correctly point out, this value comes from those fleeced by the arrangement. If my comment attributed any moral valence to the two options, that was unintentional.

straightforwardly regressive

Fiscally? Sure. In terms of liberty? Absolutely not. We are talking about public access to law, which is foundational to a free society.

Federal courts are not strictly limited by tax revenue in the same way that state courts are, and I am more sympathetic to this line of argument on the state level. Finding replacement revenue is a legitimate concern, but a secondary one due to the federal government's deficit spending privilege.