Live data from Hacker News

VNC Viewer for Google Chrome

chrome.google.com

51–57 of 57 posts

Re: VNC Viewer for Google Chrome

#51
post #25

>This application is not supported on this computer. Installation has been disabled. Too bad, seems like it won't work with linux system.

What version of Chrome are you running? It needs version 25, which is fairly recent.

I'm using v24.0.1312.52. Will try to get v25 and give it a try.

Re: VNC Viewer for Google Chrome

#52
post #47
post #40

Earlier quoted context omitted.

Fairly recent? More like bleeding-edge. I saw the same text. I am running Mint 14 (based on Ubuntu 12.10) and my version is 24.0.1312.56.

I'm running Ubuntu 12.10 proper, and my version is 25.0.1364.152. And the update hasn't been in the last couple of days, either; there's already a Portable Chrome build of 25.0.

The update was Monday: http://googlechromereleases.blogspot.com/2013/03/stable-chan...

Re: VNC Viewer for Google Chrome

#53
post #50
post #9

Weird, looking at the manifest, I see it asks for permission for "socket": [ "tcp-connect: : " ], but when I try to use that in my own app, I get the message "socket" permissions are only allowed for packaged apps. I am quite frustrated by the confusing mix of extensions vs "legacy" apps vs "hosted" apps vs the newfangled "packaged" apps. The chrome web store is extremely confusing and the documentation is all over t…

It's not that confusing, the only confusing thing IMO is the split between hosted and packaged. I'd rather the CWS only allow packaged apps.

[deleted]

Re: VNC Viewer for Google Chrome

#54
post #9

Weird, looking at the manifest, I see it asks for permission for "socket": [ "tcp-connect: : " ], but when I try to use that in my own app, I get the message "socket" permissions are only allowed for packaged apps. I am quite frustrated by the confusing mix of extensions vs "legacy" apps vs "hosted" apps vs the newfangled "packaged" apps. The chrome web store is extremely confusing and the documentation is all over t…

Hosted app: basically an external website with more permissions, must by used online

Packaged app: Can be used offline with permissions like a native local app. Think of IPA or APK files.

Re: VNC Viewer for Google Chrome

#55
post #42

Earlier quoted context omitted.

Google captures greater profits and influence by flogging people its DRM-infested ChromeOS machines for cheap, claiming they are hyper secure. On the face of it, that may be right, but privacy and independence are lost. Victim buyers discover they can't do anything without either paying more money or being online (ie. under surveillance from the GooglePlex).

Could you please elaborate about DRM in ChromeOS?

He's referring to the HTML5 DRM, which Google, Microsoft and Netflix are supporting (I think Apple, too).

Re: VNC Viewer for Google Chrome

#56
Nice!!

And unlike Chicken of the VNC, this one actually supports the scrollwheel! (maybe there's some way to get Chicken of the VNC to support the scrollwheel but I didn't find it. I did find "Chicken", a fork of "Chicken of the VNC". It's got various connection bugs.)

No luck with copy and paste from Chrome OSX to Ubuntu 12 but maybe I'm doing it wrong

Re: VNC Viewer for Google Chrome

#57

Earlier quoted context omitted.

Oh OK, I didn't actually read those I was just posting the likely link that popped up on a search. Feel free to do your own research then. 'Developer mode' that disables consumption of things you have paid for on a machine that has virtually no storage? Sounds great. Why do you seem to support them?

I did my own research, and i don't see the issue? Yes, developer mode erases the machine for security reasons. I don't see to support them, I do support them on this (I actually am not a fan of chromeos in general), because it is still a huge step forward over almost all available newer "locked" machines available. Your solution is what exactly? It seems they've done the best pragmatic thing they can do here. It enab…

Oh, for security reasons! Whose security? Let's be honest here: the content owners. It's classic DRM: you buy the device and it works for someone else. My solution is to strive to avoid buying, supporting or discussing DRM-crippled devices except to reveal their true nature to the wider community. "Don't be evil!". Puh-lease. Anyone know what Google spends on PR? I'm sure it's either hidden or shocking.
Post reply on HN