Re: Alternate
8.8.8.8 ?
Stop giving away all your private information to Google for free!
199 publicly visible posts • joined 28 Sep 2009
systemd
'oh! DNS lib underscore bug bites everyone's favorite init tool, blanks Netflix
In fact it's become some a huge mess that Verisign, having successfully applied for 12 transliterations of .com and .net, have only launched two of them - .コム for Japan and .닷컴/.닷넷 for Korea - and that was over a year ago. They have abandoned launching the rest. That would make for an interesting article in itself- why would a powerhouse like Verisign not be able to handle launching the lot of them at the same time, given they're for completely different markets?
With the launch of IDN equivalent TLD's for CNO along with the newGTLD's, ICANN had an ideal opportunity to fix this problem for good. Instead they made it worse.
What should have happened: Complete banning of mixing scripts between levels. All IDN's in CNO should have been moved over to their equivalent IDN newGTLD (eg cyrillic .com's should have been grandfathered over to .ком, etc,) and the system returned to only ASCII registrations allowed in the plain old ASCII CNO TLD's.
Instead, ICANN sat on it's hands and even let mixed scripts proliferate into the ASCII new GTLD's! So now you can register chinese scripts in .xyz. How useful.
SSAC were asleep at the wheel.
But don't get me started.
Or just wait a few years and watch it on Freeview.
I'm a few seasons behind on GoT etc etc. I care not.
I stopped following F1 when it disappeared from TV3 in NZ and went to Sky where you have to pay for an entire sports channel which is 60 bloody percent rugby, just to watch ~16 F1 races each year. No thanks.
I'm not paying for bundles just to watch a few shows. Sod that.
Blame must be shared with the browser writers that sold out to the google search home page, and all the silly webmasters enslaved to google analytics (and thus giving away all their visitors information to google) - along with google tag manage, google fonts etc etc.
Oh and all the facebook/google etc "like this page" icons that are served from the data slurpers servers instead of locally.
"So if you shopped online around November last year, and you get a note from one of the 40 affected websites confessing your payment card details were stolen, you know who to blame.
Aptos, its CEO Noel Goggin, and his team."
A software company, whose "Technology Leader" is right down the bottom of the "leader list", below the "Growth Leader" and the "Strategy Leader".
Give you an idea of what his security budget level was. Surprise.
Along with lazy plug-in devs who attach unneeded CSS and JS files, leading to wordpress websites that download sometimes 100 or more .css and .js files full of unused code.
Which is why people have to go out and get a faster computer or more RAM just to get a website to function half-pie decently.
But don't get me started. The entire WordPress system is a dog's breakfast.
"Note the big clickable Google Map and the “spelling correction” suggested by Google, both prominently above the actual Streetmap result"
Bzzzzt. That's not a spelling correction SUGGESTED by Google. Google has APPLIED their spelling correction suggestion and produced results for "aspley guise street map" and the user has to click the link to get the search they asked for.
In this case, that's an important point. It's actually a "Street map" result.
I wonder if they do automatic spelling corrections on fcuk? No I thought not.
What really annoys me is that their system is transaction based. Every transaction costs the same for Paypal to process no matter what the transaction value is.
So how do they get away with charging a percentage rather than a fixed fee per transaction?
Next thing you know, motorway toll systems will be stopping your car and counting the number of people in it so they can charge per-person instead of per-car.
1. You're faking it
2. You can't spel proper and don't want the media to unprove your alternative facts.
3. To stop the guy in the row in front copying you're stuff while you're busy trying to get your tiny little hands on the naughty bits of girl beside you.
From that...
"DANE records are going to be even more non-standard, are going to be larger and browsers would have to fetch lots of them because they'll need the DNSKEY/RRSIG chain up from the root. Even if DNSSEC record lookup worked flawlessly for everyone, we probably still wouldn't implement this aspect of DANE because each extra lookup is more latency and another chance for packet loss to cause an expensive timeout and retransmit."
Since when does the browser provider get to decide whether the website operator is willing to put up with latency? Where's the democracy in that? I don't see them whining about the latency caused by websites downloading megabytes of subsequently unused javascript and CSS files.
If I chose to have my website suffer a small amount of one-time latency for the pleasure of having complete control over my CA-free TLS, (because after that it will run blazingly fast - javascript free and minimal CSS), that that should be MY CHOICE. This "we've decided that we don't like DANE so we're not going to let you use it" (by a bunch of people that have their fingers in the CA pie) is nanny state bullshit.
OK then. In the spirit of "openness and democracy" and to highlight the "important reflection of the diversity and richness of the Internet", how about you do something that's actually useful - bake DANE into Firefox.
Then we can chose to provide HTTPS without having to go anywhere near the mess that is CA.
Or explain via VultureCentral exactly what you have against DANE.