Hacker Newsnew | past | comments | ask | show | jobs | submit | more lambda's commentslogin

Did anyone else get a Google internal link for "Chrome DevTools" that gives you an internal Google login page?

https://devsite.googleplex.com/chrome-developer-tools/docs/r...

I clicked on that link and got a page that says "moma: inside google. Single Sign On" and asks for a Google login, password, and OTP. It also appears to display a random image; I wonder if that random image is used as part of the authentication process, perhaps as an authenticator that this is a valid Google login page (perhaps something you can verify with your OTP device).


Doh! On it.. In the meantime, this is the link you want: https://developers.google.com/chrome-developer-tools/docs/re...


That seems busted. I'll see if I can get someone to fix it.


I've recently seen more and more ads on pages in Chrome. Just a few days ago, I got fed up and switched to Firefox (with Ad Block Plus installed), and boy am I glad that I did. There are a few places where I feel it's a little slower, and it occasionally frustrates me with links that are close together as it doesn't have the zoom that Chrome does when you hit a link that's sufficiently close to another link as to be ambiguous. But the lack of ads more than makes up for those shortcomings. I've come to realize that I just cannot live without ad blocking any more.

And yes, I do realize that advertising pays for many of the services that I use. It's just that the advertising arms race always makes it more and more intrusive until it's unbearable; I just cannot put up with them. Those services that I value and which offer a subscription plan instead of ads I subscribe to (like LWN). Sadly there's not a lot of content that you can actually choose to pay for rather than receiving via ads, so I just use an ad blocker and move on.


While I was reading this post, the page automatically reloaded to something that said "oops, this page can't be found", and then a few seconds later loaded back to the original. This is while I was simply reading the text, not interacting with the page at all.

Somehow, through the magic of JavaScript and Websockets, they managed break passively reading static content.


It's not static and it's not readable HTML when accessed without JavaScript. If I understand, that's the feature of the framework that is being praised.


I don't think that's completely fair. Meteor to me, is more cased for building realtime applications. Should a blog be a realtime application? Probably not, can it? Sure.

Not only that but, but the page compensated.

It's also kind of neat, that the author has indeed written a realtime blog. For fun: they could magically fix typos while you're reading.


Perhaps I should write a quick event to highlight words as they get fixed in realtime :)


Or users could legitmataly highlight typos and they could get fixed in real time.


Great idea!


I had to accept cookies from the site before it would even show me anything but a blank page.


sorry that was a deploy to fix the "oops, this page can't be found" that was flashing before the page loads. When we deploy Meteor, it hot fixes the client (i.e. restarts the app in your browser)


My skepticism here is due to the use of an "app in my browser" to display a static blog post.

A blog post is fairly simple static content. My browser is an app that does fine at displaying it. By making the page an app that dynamically updates upon server changes, you actually substantially damaged my experience, as I was interrupted in the middle of reading the page.

I'm not opposed to apps which dynamically update data in real time from the server, when that's appropriate. A static blog post does not appear to be such a case.

The irony here is that this was on an article titled "Why Meteor will kill Ruby on Rails", an overstated claim describing how a framework build around updates from the ground up is so much stronger than one based on delivering static content. The actual behavior of the page seemed to speak more loudly than the content.


To be fair, this is something that you can easily change if you prefer to take the site down while deploying. Hot code pushes are a feature.

It's difficult to implement the same functionality with Rails, where the default is to be down while deploying.


It takes maybe a day working with your Capistrano script to implement zero downtime deploys in Rails if you're running Unicorn, Puma, or Passenger Enterprise...


A day we didn't spend for Meteor, for sure. Tradeoffs.


As far as I can tell (given that they haven't actually released anything yet, I can't verify), they will release the source under a BSD style license, which grants you copyright rights to modify and use the source as you like. A BSD style license grants you no patent rights, however. They will furthermore release a binary blob that grants you patent rights, but only if you use that specific binary blob obtained from them and don't redistribute it.

That's as open as you can get with a patent-encumbered codec. I'm not sure what else they could do.


  Mozilla has been resisting Googles libre codecs even 
  though they come with full source code and a patent 
  pledge. Google has already even paid to eliminate 
  potential threat from the evil MPEG LA. It is as 
  free(libre) as you can get in this space.
Source? As far as I can tell Firefox implements WebM for <video> and VP8 for WebRTC. In what way is Firefox resisting Google's libre codecs?


Sometimes, DNS will break for me (someone's DNS server will get hit by a DDOS, say), and I'll add the appropriate records to my /etc/hosts to work around it. I may not notice that I've done this until several years later when it stops working because their IP address changed.


Sure, and you are allowed to have GPSes in your field of view.

http://www.dmv.ca.gov/pubs/vctop/d12/vc27602.htm

But the Glass is more than a GPS. It lets you read texts and emails. Reading texts and emails while you're driving will necessarily be more distracting than not doing so. And that's what's not allowed.

The law is written such that it's only allowed to be able to offer both an approved function as well as an entertainment/business function if there's an interlock that prevents anything but the approved functions from being used while the vehicle is in motion.


So if a driver uses his cell phone as his GPS he's breaking the law? If so, that sounds like a law that needs to be revisited anyway.


> The law is written such that it's only allowed to be able to offer both an approved function as well as an entertainment/business function if there's an interlock that prevents anything but the approved functions from being used while the vehicle is in motion.

Should be easy enough to arrange. Also, implement a time readout for "current GPS Nav session" so the officer can verify there was no funny business going on.


  A person shall not drive a motor vehicle if a television 
  receiver, a video monitor, or a television or video screen, 
  or any other similar means of visually displaying a 
  television broadcast or video signal that produces 
  entertainment or business applications
It doesn't have to be only an entertainment device. If it can produce entertainment or business applications, it's not allowed.

http://www.dmv.ca.gov/pubs/vctop/d12/vc27602.htm

There are exceptions for devices that have interlocks that allow them to act only as a GPS, map, vehicle information system, or or rear-view camera display while the vehicle is in motion. The Glass doesn't meet these criteria as it has no such interlock.


Basically, the way JavaScript security currently works, browsers trust all code sent from the server you are communicating with to manipulate everything coming from or going to that server.

You could talk about ways to independently sign and verify some crypto primitive or crypto library and be confident that it was being used to encrypt your communications appropriately. But this wouldn't help at all. There's nothing stopping the person controlling the server (or MITMing your connection to it) from adding additional code that scrapes the text input boxes, or captures keystrokes, or simply follows the appropriate variables down to the ones which contain your text before its sent off, and then sending that back to the server in an XMLHTTPRequest, via a websocket, via loading an appropriate image, or even hiding it quite well among the timing of when requests are made to the server.

The fundamental problem is that the code comes from the same person providing you the connection, and it is updated every time you use the page, so it offers no additional security above just trusting them directly.

If you want good crypto and good security, you want stable client side software from a trusted source, and a different source routing your traffic, so that both of them would have to be compromised to compromise your data.

Now, there may be one small advantage in client-side crypto. That's if due to problems with TLS (in particular, the version and protocols supported by your browser), there are TLS weaknesses that can be exploited, like a MITM attacker forcibly downgrading your crypto to a weak algorithm that allows them to eavesdrop but not forge content. In this case, stronger crypto implemented in JavaScript could be used to keep your data confidential. But this is a very narrow corner case, that's probably better handled by fixing browsers so they aren't prone to protocol downgrading attacks.


Wow, my thoughts exactly. I thought "huh, kind of neat concept, but seems a bit impractical, don't think anyone will actually be able to manufacture the hardware efficiently."

Now, it's still vaporware, but Motorola's backing is a big step towards something that could actually happen.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: