Hacker News new | past | comments | ask | show | jobs | submit | nisdec's comments login

Same here


There are way too many emotions and little facts provided in this article, it's a really hard read tbh.


Could someone please enlighten me why an installation would need 8gb of free ram?


If it's building everything (including Qt), Qt includes Webkit. I imagine that's a lot of C++ code to build.


QtWebkit and QWebEngine, which uses Blink(/CEF).

8GB RAM is rather optimistic.


author here; It's needed by `go install` to provide pre-compiled packages, which will then speedup the compilation of your applications down to 10sec. But you can also use the STUB setting, before running the setup and then use the binding with only 1gb ram as well. (the necessary c++ code will be compiled later with qtdeploy)

edit: can't comment any further currently, I will try to answer everything once I'm unblocked.


There is hope. Discord and Slack.


> There is hope. Discord and Slack.

Neither of those are FOSS, which Hello was.


Discord + Slack = Skype (+ video)


Glip offers slack + video out of the box, plus a lot of the slack pro features for free


I'm curious how it works. How does the Google car know that it's getting pulled over?


It probably doesn't. Google doesn't let their cars roam freely yet; they always have someone inside the car.


SAP?


Summary:

1. Only affects stock Android 2. Only works with password protection (PIN, pattern = OK) 3. Already patched


Yeah. It doesn't work on my Note 3. Samsung disabled copy & paste in the Emergency Call dialer.

The author clearly didn't do his research, simply assuming that the vulnerability affects all Android devices:

> But there's no telling when it'll reach Android devices made by Samsung, LG and others. Blame the Android's fractured updating system, which is slowed down by phone manufacturers and cellphone network carriers.


"Already patched" isn't really as meaningful on Android as it is on, e.g., iOS where the average user can expect to (and frequently does) update their operating system.

How many phones are still vulnerable to StageFright?


The bug appears only on stock devices which are commonly updated. OEMs provide their own lock screens which aren't vulnerable.

So in this case "patched" is pretty meaningful.


How do you know they aren't vulnerable ;)


> 1. Only affects stock Android 5.x <= 5.1.1


On paper you should be able to do the same with a HTML5 manifest file.

Don't get me wrong, it's a really neat wrapper, I'm just curious about why I should use this library instead of an already in HTML5 implemented, easy way which does pretty much the same?


By HTML5 manifest file, do you mean the Application Cache? Because that is apparently (I've never tried it) anything but an 'easy way' [0]. Whereas this script appears to wrap ServiceWorkers, which is the 'modern', recommended way to do things [1]. Also being a 'neat wrapper' with a simple API is often a good enough reason for something to exist.

[0] http://alistapart.com/article/application-cache-is-a-doucheb...

[1] https://www.youtube.com/watch?v=SdMxGNkZqnU


It's called seasickness and known for thousand of years.

You get it or you don't and there is nothing technology could do about it for a long period of time at least.

Well someone could take some medicine before playing VR, but that would be a little bit too much, wouldn't it?



Not available in my country (Spain)


I get not available in your country (Canada).


No available in my country.


Join us for AI Startup School this June 16-17 in San Francisco!

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

Search: