This is awesome. I've used a number of apps where the PWA is better than their native counterpart. I want more people to use this technology.

It sounds like an Internet equivalent of a Nielsen box?

What does AMP have to do with anything? The fine article is about flagging potential URL homograph attacks. It's a reasonable thing for a browser to do, since those attacks are incredibly hard to spot.

I don't know why Wired clickbaited the headline like this.

They've been running wild with "KILLING THE URL" for some time now. Put it right next to "Google murdering ad blockers" and "Google decapitating hangouts classic".

Is there any unbiased article out there going over the proposals?

WIRED published a (relatively positive!) article last fall entitled "Google Wants to Kill the URL": https://www.wired.com/story/google-wants-to-kill-the-url/ I'm interpreting the title as a reference to that.

And the relevance is that AMP shows its own fake-URL bar, and Google could choose to "kill the URL" by trusting https://www.google.com/amp/ with not-URL overrides. (But, they could do that presently and trust themselves with URL overrides.)

The reasonable thing would be to display the real domain, and the punycode one, in the same bar. Then you can at least detect some homograph attacks. Or possible use a monospace font for the URL bar. So that 0 with a dash and O are actually visible at first glance.

Please distinguish between fonts-for-data and monospace-fonts. E.g. http://input.fontbureau.com/info/#writing has a sample of a not-actually-monospace font with IMHO awesome legibility in the mentioned "matter-of-fact" category of typefaces.

0 with a dash and O without are not at all bound to monospaced fonts.

FYI, I left console editors due to their inability to handle my preferred Input Sans Narrow Light 14pt (16pt on my 110 dpi screen), just so you can understand the pain of monospace.

Of course, but selecting a monospace font is already in built in all operating systems, so this could be a quick and dirty fix.

Oh man, if this could get things like Signal Desktop off of Electron, I would be so happy...

Electron apps are pretty miserable in general.

Is Google Chat really an Electron app? If it is, then I wonder why it cannot do OTA update or why it has to open a browser for login (instead of opening the page in the Electron shell).

Long story short: It's either a really badly written Electron app or no Electron app (well, still obviously not written for 2018).

The issues mentioned are not related to Electron or technology in any way. This is just complete apathy to the users. I am not even surprised, between all the google communication apps, not even sure which one this blog post is about.

The cement tiles around Building 17 at Microsoft are actually like a physical graveyard. So many dead products! The 90's CD-ROM multimedia era generated a lot of dead-end franchises.

I could see this seriously effing with software jobs. Even if a company intends to keep their noses squeaky clean, every developer hired becomes an additional risk. Companies will try to control more of the process from the top down (and that works out great LOL) and they'll try to do more with less. Or GTFO of the country.

Some services use ultrasonic pairing, like (IIRC) Google Play Movies on Roku.

Too bad Edge doesn't support Safe Browsing mode. IIRC the API is publicly available too; MS doesn't want to swallow its pride and implement a client for it.

Stability is ALWAYS ALWAYS ALWAYS priority #1 in an operating system!

Unless it is a development phone, then it is fun to play with new, partially supported features.

It all depends on the context of your statement.