wav-part | 7 years ago | on: The IRS Tried to Take on the Ultrawealthy – It Didn’t Go Well
wav-part's comments
wav-part | 7 years ago | on: The IRS Tried to Take on the Ultrawealthy – It Didn’t Go Well
You will always have problems when taking from the rich. 800 years ago It was barron rebellion (Magna Carta). Now its army of lawyers and gutted IRS. IMO War between taxman and rich is not entirely off table in future.
wav-part | 7 years ago | on: ICANN Calls for DNSSEC for All Domains Following Domain Hijacking Attempts
wav-part | 7 years ago | on: ICANN Calls for DNSSEC for All Domains Following Domain Hijacking Attempts
wav-part | 7 years ago | on: ICANN Calls for DNSSEC for All Domains Following Domain Hijacking Attempts
This is a fight for cert revenue: CAs vs ICANN.
wav-part | 7 years ago | on: What happens when Google says “we aren’t going to pay your fines”?
wav-part | 7 years ago | on: Abolish Billionaires
wav-part | 7 years ago | on: Google now pays more money in EU fines than it pays in taxes
wav-part | 7 years ago | on: Anti-corruption shortfalls fuelling ‘global democracy crisis’
Like democracy=good, populism=bad ?
wav-part | 7 years ago | on: Anti-corruption shortfalls fuelling ‘global democracy crisis’
wav-part | 7 years ago | on: The World Economy Just Can’t Escape Its Low-Growth, Low-Inflation Rut
wav-part | 7 years ago | on: The escape-room games industry is booming
> The cost of low-trust in a modern economy is huge.
So you dont trust anyone unless gov tells you to ?
wav-part | 7 years ago | on: The escape-room games industry is booming
wav-part | 7 years ago | on: A DNS hijacking wave is targeting companies at an almost unprecedented scale
Ultimately its about deciding who gets to own "x.y.z" string brand globally/contextlessly. World obviously need a single naming system. Either that or expect to have multiple owners to "google.com".
My suggestions are required otherwise why would someone build a global brand if ownership is not safe or guarnteed enough. Future is way more chaotic. Without crypto, a global naming system is not going to survive.
wav-part | 7 years ago | on: A DNS hijacking wave is targeting companies at an almost unprecedented scale
Lets say .com gets mismanaged. Community is infurious. firefox/chrome/etc demands that . remap .com to new more trustable entity. If . does not. firefox/chrome/etc then remap . to new more trustable entity, because .com must be as trustable as ., because .com is that important. New . give back ownership of all tlds to their previous owners. Except for .com. .com goes to the more trustable entity as intended. New .com then does again similar import of all good xxx.com.
In this whole incident, no one loses the ownership of their names except for .com and possibly . .
Now no gov can touch *.com. Though its different for cctld. Those are owned by their respective govs. Same goes for gtld. But no one gets to mess with . .com .org .net.
wav-part | 7 years ago | on: A DNS hijacking wave is targeting companies at an almost unprecedented scale
wav-part | 7 years ago | on: A DNS hijacking wave is targeting companies at an almost unprecedented scale
Again this is unavoidable in any system that need trust. Thats why I like PoW DNS.
wav-part | 7 years ago | on: A DNS hijacking wave is targeting companies at an almost unprecedented scale
DNSSEC: Google need to watch .com and dnsroot.
Which one is better ?
----
(I am ratelimited so posting here rather than reply to the child post by tptacek https://news.ycombinator.com/item?id=18889809)
Of course they can. There is literally no legal or otherwise difference between Verisign and .com. Chrome can do whatever it want, cause its Google's browser not .com's.
In case when .xxx becomes dishonest, you can just move to your own gtld or .more-trustable tld. In current system, there is no concept of ditching a CA. If a CA decided to missmap a name and you are too small, you are fked.
> it’s actually 1, or 1 AND 2
No you can have DNSSEC without CAs. I have explained that already without changing much of the tls. Basically example.com DNSSEC key become CA for example.com. example.com then would create a tls cert in the usual way. No pain.
wav-part | 7 years ago | on: A DNS hijacking wave is targeting companies at an almost unprecedented scale
However who gets to have dnsroot is just a value of a config in DNSSEC. The value itself should not be used to criticize DNSSEC cause its changeable.
wav-part | 7 years ago | on: A DNS hijacking wave is targeting companies at an almost unprecedented scale
https://www.youtube.com/watch?v=PGMQZEIXBMs