skysight-inc/HackerNews huggingface dataset:
The biggest plus that I see is that this allows to do do remote editing on a server which may otherwise be restricted from access due to security concerns. If the backend can be developed to have a lot more admin features which can be used to restrict the features which can be used, then the admin can simply leave one port open through which the front end can communciate
I would postpone learning until 2020, when it (hopefully) gets released.
I should make this into a blog post... I should start a blog...

You definitely should! This comment was great reading. You managed to condense a very complex state of affairs into an understandable explanation.
"Security is a top priority for Google. We invest a lot in making sure that our services use industry-leading security, like strong HTTPS encryption by default."

-- Says Google site that forces HTTP.
Hello HN!
We, a group of summer interns at Nordic Semiconductor, have made an Internet of Things-enabling platform based on ARM's mbed technology. We make it easy to rapidly prototype and develop Bluetooth LE enabled devices - get up and running in under 10 lines of code, written directly in the browser.

We hope to create a community around BLE devices where developers share their ideas designs with each other. Everything is open-source, of course, with lots of supporting materials, together with companion apps for both Android and iOS.
PIP support is built into puppet, not sure about other stuff but since you missed this one there's a chance u missed others too.

So basically you don't have any valid technical points against puppet other then Salt seems easier for you to use. Which is ok.
I agree with the arguments of Henry David Thoreau and of Lysander Spooner to the effect that voting is fundamentally an immoral act. To vote, above all else, is to broadcast your own acceptance of the outcome and willingness to abide by it. So from a moral perspective, I should only vote if doing so has a sufficiently strong chance of averting some even greater evil.

But setting morality aside and just assessing the expected value, I should want to vote more when the expected value is large, which is to say when I have BOTH (a) a decent chance of affecting the outcome, AND (b) some good reason to think my vote is much better informed than that of the average voter.

If - case (a) - my vote is one of millions, I have no reason to expect it to CHANGE the result.

If - case (b) - my vote isn't above average in terms of how well-informed I am and how carefully I've thought it through, I have no reason to think adding mine to the mix will IMPROVE the result, even if it DID change the outcome.

For most people and most elections most of the time, neither (a) nor (b) applies; they should not vote.

Your last paragraph suggests the use of Kant's categorical imperative, which not a great guide to action. To illustrate why: suppose our question at hand is "should I walk on the grass?" If I do, I will enjoy the feeling of grass between my toes, but if EVERYBODY walked on the grass, the grass would die and we would lose not just its usefulness and that nice feeling but also its beauty. So applying Kant says I shouldn't walk on the grass, right? But wait! There are more likely options in the world than EVERYBODY or NOBODY should walk on the grass; there's also the option that SOME people walk on the grass. If we test the rule "people SUFFICIENTLY LIKE ME should walk on the grass", that works fine when you universalize it! Then we get the prettiness for all AND the nice feelings for some and the grass survives.

So to return to voting: not everybody should vote. SOME people should vote. Which ones? People who really ENJOY doing so, and people who have reason to think it will be a close race AND are especially well-informed or otherwise have reason to think their vote helps much more than average.

I'm in neither of those categories, so I shouldn't vote.
Nice job! I got lots of questions:

1. How to deal with device features such as camera, GPS...?

2. How to have different styles of navigation like Yelp app's center button (flying out 3 other buttons)?
Docker LAMP with Remote Logging and Email Relay
It's still expensive to offer SSL when you have a CDN in front unless you go with just SNI support (which could cost a significant portion of your visitors).

We have CDN backed HTTPS for custom sites on BitBalloon (https://www.bitballoon.com) if you're interested in a Github pages alternative that supports SSL.
MIT researchers made a material that forces water up walls
«Oh, they're screwing up before, too? Then I guess it's alright»

How is it screwing up? How are they supposed to run a search engine without prioritizing? "Here's 30000 results, we've randomly sorted them for you"?

Because only a handful of companies can issue certificates.

Fair enough.
there is something odd about this announcement. since it is no harder for a black hat publisher to switch to https than a white hat publisher, this signal will likely get noisy very quickly. i think google knows this, and its why they rarely specify ranking signals.

so, then really, they are just using their dominance in search to effect change. now, you may agree with the change (they did something similar by announcing pageload time as a signal), but it makes me a little uneasy for google to leverage their dominance in this way even if i happen to agree with the goal.
The article seems to be health focused, otherwise it could have mentioned Elephants burying fruit to get drunk when it ferments too.
1. yes, monospaced fonts reminds me ones on typewriters.
2. just press the same button that opens cabinet.
3. in public repo - no (
Wouldn't it make more sense to stop the economic blockade of this country instead?
Many "free" certificate services don't give reissued certificates for free, though, so if something like Heartbleed happens again, you might still pay a fee.
Or kangaroos and wallabies playing in the opium fields
"Having HTTPS support will only get you a very minor boost in rankings."

If your livelihood depends on getting traffic from Google - and a lot of sites do - then even a minor boost may equal a lot of money. Plus the fact that you can never know quite how much, so to be safe you must assume it's worthwhile.

The problem I have with this move is that to me it appears as Google are furthering their own political agenda. They want the web to be https, so they penalise sites that are not. It would be different if the argument was that sites on https tend to hold more quality content than non-https sites, but that doesn't seem to be the reasoning.
In my country, the cost of a SSL certificate is around 60% of my hosting costs, per year. I run a low-traffic blog with comments disabled, so users do not "interact" with the site in any way - except consume the content. I don't see any benefit from this.
This is the way I've done it. Which boils the problem down to an init call and a call per event. I dislike the code generated bindings though - is there a more... data driven alternative that's good?

I've got a simple event API where I have an event type identifier, and some basic data. Which I then need to pipe to some third party junk that listens to ETW events. To do this, I have to:

1) Manually map hundreds of event types to code generated ones, and update this mapping every time new events are added... or do a massive N:1 mapping... which is totally against the grain of the intended usage of the third party junk (although appears workable for the moment.)

2) Wrap every ETW event type with callbacks, and the init macro with a stub to allow callbacks, such that I may target the two "identically" configured endpoints... each with their own manifest and autogenerated header.

3) Wrap every ETW invoke with #ifdef s to limit them to the 1 of my 3 platforms they work on.

It's quite ugly compared to the equivalents of the other 2 platforms.
People that write content for websites are not always the same people that build those websites. In this case, the search engine team is entirely separate from the Blogspot team.
noted, will surely add some screenshots!
I love using TeamStory every day. Its great finding out all about other startups and sharing in their success. Provide feedback and get feedback back for my own startups. Share the ups and downs of being an entrepreneur...
Nothing beats up the P4 C++ Api :)

While I love perforce, their constantly changing C++ api with it's namespace wasting, bad error handling API is the worst out there...
This is a known issue and being addressed as well.

http://tools.ietf.org/html/draft-ietf-websec-key-pinning-11

http://dev.chromium.org/sts
The irony being that the breast is the least-flavourful, blandest part of the chicken, and all those years he was actually dining on the best bits without knowing?
Best GitHub repositories
I don't think it's unethical (according to whom?).

There is a problem however - children need to be educated in matters of licensing, which is why I believe starting with an open-source editor makes sense. The real power with open-source is that as a developer you've got control over it and that it never dies. We wouldn't even have this discussion if we were talking about a proprietary programming language with no open-source clone.

So there's a risk associated with picking something proprietary - those risks are sometimes worth it, Sublime Text is surely a good editor and much friendlier than Emacs and if it dies or gets too expensive, then the lock-in is not that great, but children at some point need to learn about licensing and the pros and cons of the choices they make.

But no, I don't think it's unethical.
Also smartphone. Probably my sat-receiver (for remote recording). Likely that's it.

Even in my car: I'd just use my phone (instead of something else (another and likely worse UI)). It may turn out totally different in ~10, ~20 years...

... but remember: Something comes along and the expectations are high and then we see and realize that in practice it's less spectacular / much more modest.

The iPhone and Android are great, but extending it to a smart-watch?... that's kind of a lame idea. I don't care.

Hopefully we have something less expected and more exciting by then.

So to me it's a hype word, where I shiver a bit, since I remember the .com-bubble ("Internet of Commerce" if you will) and so many other "wordings", which passed by and got replaced by the next wording (and are still not catching on).
> The only modern browsers left out appears to be Safari 7 (no WebGL)

Safari has WebGL since 5-ish but disabled by default.

To enable, Safari > Preferences > Advanced > Show Develop menu, then Develop > Enable WebGL

The presentation seems to work allright, although it suffers from some slowdowns.
One of the other legal fights they've started is to put online public domain artworks that have been scanned by museums at great expense since (at least in the US) "effort" alone is not enough to grant you copyright protection.

http://en.wikipedia.org/wiki/National_Portrait_Gallery_and_W...

This seems to me to be exactly the kind of thing Wikipedia should be doing, though similarly there are some people outraged that the poor museums don't get to exploit a monopoly on the cultural works they control.

Just sparking debate about exactly what copyright is for is a good thing in my opinion, and helpful in fulfilling their mission:

"The mission of the Wikimedia Foundation is to empower and engage people around the world to collect and develop educational content under a free license or in the public domain, and to disseminate it effectively and globally."

With emphasis:

"The mission of the Wikimedia Foundation is to empower ... people ... to collect ... content ... in the public domain, and to disseminate it."

If you don't believe in that mission then donating to Wikipedia is probably not a recommended action.
Apologies, I haven't made myself clear with that idiotic of a snarky remark :) What I meant is that their actions in the past shouldn't be an excuse to their actions today.

The principles behind PageRank are based on unbiased reputation, and provide for a good ranking system (spammers aside). Whatever's thrown on top needs to be carefully considered not to enforce biases towards any group in particular.
It's Bejeweled for nerds, essentially.
1- Invite students that you think might be interested
2- Explain the idea of your club as stated here
3- After members sign up to your club, real work begins
4- Every 2 weeks you'd have each one of the club go up and suggest an idea and people would vote for it
5- Ideas with most votes then would state what kind of specialized people they need and create their group
6- two weeks later they finish their project and do the something again
7- Eventually people would start recognizing others who work well with them and when that happens they would form their own groups after they finish school and you would have helped create a business
Now, that was just because I'm stupid. Fixed, thanks!
If you disagree with PHK, you have to refute the details in his notes, not just wave them away. That they can be made to work does not mean there is not a problem.
I stared at it for 5 minutes, before realizing the fish's probably sleeping.
Whilst I am of the opinion that the original photo is not copyrighted because it was taken by a Monkey.

I would have to question what is the actual photo being distributed? Is it the original work or was it a version that had been edited before being posted online? Can you take a public domain item, alter it and it then become a copyright? If I used it in a logo, does that logo become public domain?

Personally I wish the photographer would use the work to promote himself rather than fighting for royalties.
I see the benefits but I have to agree. This is a very real barrier to entry, and not just financially. Making SSL a global standard is just one more thing new web developers have to appreciate.
Blackhat keynote: Cybersecurity as Realpolitik
The company is still responsible for that, it doesn't mattter why.

Do you think that consumer cares if the lack of PCI compliance caused them to have their CC information stolen and used because someone internally thought someone else was responsible for PCI compliance?

If you choose to store CC information it's your responsibility to make sure you're PCI compliant, if you employ people, it's your responsibility to make sure they get paid.
> People that write content for websites are not always the same people that build those websites.

Wow Seriously? You don't say.

Seems the irony escaped you: announcement was made on a Google site that forces (i.e redirects from HTTPS) you to read it over HTTP.

If you read closely enough it refers to all of Google, not just "the search engine team" or (Google - Blogspot).
Mind numbingly simple and fast parallel processing in Ruby
No, he doesn't lose copyright, he simply never gets it in the first place since he doesn't meet the criteria set down by law.

In the US you can't get a copyright on a database at all. I doubt you could get it in the EU for a database created by a random accident either.
Ofcom: six-year-olds understand digital technology better than adults
The OP was referring to the webmasters, not the search engine end users, as the ones being 'dictated'* to by Google.

Unlike end users, webmasters themselves switching to Bing or DDG in their personal capacity would have little influence on their visitor's (end users) behavior.

* 'firmly encouraged' is perhaps more appropriate ;)
I would have counted wordpress as a counter example: they offer both, but on different sites (wordpress.com vs wordpress.org).
... after the first visit...
Exactly. Almost all of the problems people raise with this way of working are valid problems and can be solved with appropriate tools. Something that can't be solved with tools is for me to have no idea when someone says they want to meet at a particular time whether they're talking my time, their time or some other time.
Look at it this way:

1. Most software today is I/O bound, which is when programmers don't (and shouldn't care) about shared memory parallelism.

2. Most popular programming languages today are based on classic imperative programming going back Fortran and co.

3. These classic languages suggest using loops.

4. Loops are inherently not parallelizable. Only in a specific case where there is no carried on dependency, a loop becomes parallelizable.

5. These languages have basically infested everything we do, including compute / memory bandwidth bound problems that should now be treated in parallel. (Even bandwidth goes down with sequential execution, for example on Intel sockets usually by a factor of 2).

6. Since therefore most parallel things get written in loops, this becomes a hard problem. What the compiler vendors are doing is usually flinging [directives](http://www.openacc.org/) [at us](http://openmp.org/wp/).

7. Directives work well until they don't and you have no idea why, because it's usually a black box for most programmers (who can't read assembly like code).

8. What we should get is a way of saying: Here is some scalar code. I'd like this code to be applied in parallel over domains X, Y, Z etc. Be aware of symbols alpha and beta that are dependant in X, Y, Z as well as gamma that is dependant in X only.

10. This should be available at language level, so programmers start thinking in these terms. Only then do we have a reliable way of making use of data parallelism.

11. CUDA and OpenCL are actually pretty close to this, but slightly too low level and generally thought as being hard to program in (which I don't agree, but that's the image).

Disclaimer: I've been involved in this problem space since some time and [this](https://github.com/muellermichel/Hybrid-Fortran) is what has come out of it. It's HPC targeted, but at some point I'd like to make this whole parallel computing thing more generally approachable.
I do not envy the googlers who have to keep stuff like that up to date.
heartbleed was much much worse than unencrypted logins.
For me , Qooxdoo (qooxdoo.org) making QT almost obselete.
Qooxdoo + CEF (nodewebkit, atom-shell) making QT un-necessary.
I wonder why qooxdoo is very less known around here.
I mean, I understand their argument against it, but I think this is one of those cases where the pros definitely out-weigh the cons, this is great.
The original comment was about "rewriting history".

History is written by winners, who change over time and have been known to rewrite history. Digital formats require constant transformation from legacy formats to modern formats (per http://fileformat.info). This has an economic cost and only a subset of content is prioritized for forward migration, depending on which parties wield economic power at that time.

A book on acid-free paper that has a reasonable print run will be stored in geographical locations worldwide and will preserve information for decades if not hundreds of years, without requiring battery power, OS upgrades or file format migration.

History is also about economics. Digital storage economics is increasingly driven by cloud vendor bulk manufacture of custom servers and data centers, e.g. OpenCompute. Centralized copies can be rewritten. If local communities start building their own https://archive.org/web/petabox.php to record local/global digital history in archival file formats, maybe digital can record long-term history, EMPs not withstanding.
> No longer does "6pm" mean "close to sunset" for most people. You have to keep a sunset/sunrise calculator with you at all times just so you can remember what time to set that alarm in order to be at the local office on time.

My one-time-to-rule-them-all does in fact include a sunset/sunrise calculator, which it draws onto the face based on geolocation. http://kybernetikos.github.io/UIT
Full-screen stacked navigation tutorial
Drive Time – how does traffic influence travel time?
Another advantage to we masters with money … why?

SSL does not come cheap. Certificates have become cheap but you need your own IP, i.e., shared hosting is a problem and hosting becomes more expensive. Certificate sellers, hosters etc. on the other hand are certainly happy about these new business opportunities – although we all know that SSL is inherently broken.

OK, probably still better than nothing! :)
Πως να κάνετε BackUp και Restore – SEO | WEB DESIGN
A bit of a misleading title.

Comparing linux containers to native performance wouldn't be terribly interesting; there is little reason to believe there is any nontrivial overhead from using cgroups, chroot, etc.

Instead, this is comparing different Docker configurations to native performance (to Virtual Machines as well). The insights one can get is the amount of I/O overhead that is introduced by using local NAT as well as AUFS. (turns out NAT and AUFS overhead are quite significant.)

Finally, figure 17 is a bit interesting. It implies that there is some inherent overhead (before NAT/AUFS) of 2% from the container; it'd be interesting to find out what the source of that is.

/aside: putting percentage loss and absolute numbers on the same graph (figure 16) is incredibly confusing.
X-Ray Vision for Robots: Seeing Through Walls with Only WiFi
Help your customers and increase effectivity with a Community forum
> timezones, because they are irregular, and not equal 24 divisions of earth, do not reflect actual "phase of the sun" at place X. With a constant universal time, we could use equal divisions to find out the difference, which would be even more accurate than knowing 2am Bangalore is X am at some other place

The time system I came up with uses geolocation to orient the clock so local solar midday is always at the top of the clock (12 o'clock on a normal clock) and local solar midnight is always at the bottom of the clock (6 o'clock on a normal clock).

http://kybernetikos.github.io/UIT
It's debatable if your phone number is any of their business, but sending IMIE and MSISDN numbers without using SSL is just stupid.
Beautifully put. I do think "learn to code" is society's attempt to bottle up the magic of the tech boom. Maybe in the 60s it was "learn polymer chemistry".