Registries have always had the ability to revoke number assignments; RPKI just makes this revocation slightly more forceful. You're going to have a bad time announcing prefixes that don't belong to you, even in the absence of RPKI.

We're all internetworking at the pleasure of IANA. Getting them out of the picture, and removing their ability to deplatform Internet participants, is a much larger task than just moving away from RPKI. We'd need to completely rethink how ASN and IP assignments are done.

Registries have tended to leave existing registration data alone in case of a situation like sanctions. They won't let you register more numbers, nor will they deregister them. If you just need the numbers, that's fine. If you also depend on the registry regularly taking data updates from you, that's a problem.

If we had to live with this rule during the "classic" Mac era, it would have disallowed HyperCard.

It has a long way to go, in the same sense that ROA had a long way to go when Cloudflare first launched this site in 2020. ASPA records are fully supported by both RIPE and ARIN these days.

RPKI isn't just ROAs anymore, and BGP hijacks can happen at other places than just the first/last hop. Why hasn't this site been updated to test ASPA-invalid prefixes in addition to ROA-invalid ones?

ReactOS did this without any need for an LLM.

No they didn't. It would be copyright washing if someone contributed to ReactOS who remembered large portions of the Windows code and wrote the ReactOS implementations based on that.

1 house is built. Alice wants to own it to live in it. Bob wants to own it to rent it to Alice. 2 people want to own the house.

> 2 people want to own the house.

and so how do you decide who gets it?

1) morally. Alice deserves it because her intention is more pure.

2) financially. Bob gets it, because he can pay more for it than alice.

Which choice above you make as a policy direction is a reflection of your world view. I'm voting for 2), but i can understand the POV of 1), even tho i disagree with it.

You are entirely missing the point. The correct answer is to build 2 houses. The problem with these policies is that they artificially restrict demand. If they didn't do that, nobody would have a problem with them.

> The correct answer is to build 2 houses

the utopian answer is to build two houses. But we don't live in utopia.

The constraints faced today is real (paper or physical). You can't wish it away, and you can't say it's "easier" to just build two houses.

So build 2 houses.

> All money is debt.

This is true for currently popular monies, but is not inherently true. Is a gold coin a debt instrument?

> Is a gold coin a debt instrument?

It is if you lend or borrow it or use it as collateral.

So no, not all gold coins are debt.

Or yes, some gold coins are debt.

Forbid the "yes", keep the "no".

The CSS :target pseudo-class is useful in situations like this. HN could do something like:

  p:target { border: 1px dashed; }

I have noticed it while running ~/bin/some_command. The ~ doesn't echo until I also type the /. It doesn't cause any misbehavior because there is no binding for ~/ but can be slightly surprising.

I find it odd that you would have commands in ~/bin but not have it be the highest priority in your PATH. I use ~/.local/bin, but would never type it because i wouldn't have bins that overlap shell commands and no other path would have priority.

Usually, it is. IIRC, this was when I was just setting up my environment on a new host, after I had populated ~/bin but before I restarted my shell to pick up PATH modifications.

The alleged author, when bringing a copyright infringement suit, will submit testimony claiming they wrote it. Parties to the suit will have a chance to present arguments and evidence. Then, the claim will be adjudicated by a judge and/or jury.