skysight-inc/HackerNews huggingface dataset:
security flaws are racking up like crazy. the dom was designed for the 1990s. it will happen. but its going to be one hard transition. we all know how hard small scale migrations can be. now consider that on the scale of the internet. they need to enforce new password schemas, disable capchats , they are irritating and mak eppp leave and bots get by them anyway, and windows needs to fix their api. you can never fix a bug before someone exploits it, but you design standards that force the user to follow best practices and force tech giants to stop using oaml. vulnerabilities on large traffic sites should be jail time for the person responsible. i may just active my vpn and use tor for now on for everything, compromise my bandwidth to protect my information. btw, im sure all the cloud competition does not share data with affiliates to profit enabling black hat to exploit and use targeting techniques to launch dox attacks against individuals. im not a sec major. just my 2 bytes. also, critical 0 days need an amber alert like system that forces you to change all affected sites.
There are scenarios in which there is a difference: If some emergency happened and the hall were evacuated, everyone would be away from their phones, and they might be destroyed by whatever happens to the hall (flood, fire, etc.).

Also, a locker system introduces the possibility of disorganization: I would imagine that there will be an error where somebody else gets handed my phone instead of me. Or a malicious worker at the locker could steal it. The same reasons why I would never leave my phone in the pocket when I hand my jacket in at the cloakroom.
I pity you all.

You are forced to use it, but seemingly nobody is allowed to improve it.

I too use it daily as my employer is a google apps customer. Which is why I am so frustrated and really need to vent about how featureless it is, and especially about how its improvement trajectory is so flat.
I think that throwing people into the deep end is the only way to get them to do it right in this case. Defaulting to graphemes is too often the wrong answer, as well (e.g. you don't want that in a parser).

Really, this is not dissimilar to "what do you mean, there are more letters than A to Z?" issue that plagued software written in US back before Unicode became dominant. The way we (my perspective on this is as a native speaker of a language with a non-Latin alphabet) have eventually solved it is by basically forcing Unicode onto those people. It broke their simple and convenient picture of the world, and replaced it with something much more complicated. But it was necessary.

My position is that letting programmers get away with a simplistic view of text processing (by allowing defaults that "mostly" work) is what creates those issues. So adjusting the abstractions such that they expose more of the underlying complexity is a good thing. People SHOULD believe that doing text processing the right way is hard, because it is.
This introduction neglects to mention that Makefile rules are primarily rules to derive files (usually from other files). Make will not re-run a rule when the target (file) generated by the rule is already up to date.

From this perspective, a well structured Makefile can be thought of as a pipeline/graph of functions, that derive values (files) from previously known values (files).

Expressing a build process in this kind of way makes it possible to support incremental / distributed build in a fairly natural / obvious way.

It is less obvious how to support incremental / distributed builds for the more general kind of imperative build script that does a bunch of side effects (e.g. the style of build script you'd get using something like ant).
Beyond your cable modem – How not to do DOCSIS networks [32c3] [video]
Ask HN: Certifications for people who contribute to open source?
I guess a lot of the people coming to HN contribute to open source software. The quality and standards of popular open source libraries are generally higher than what we see in proprietary software. However, the benefits of contributing to open source are mostly intangible. I wonder if there could be certifications for people who contribute to open source in a substantial way. Could this be an alternative to a university qualification? Or does it already exist in one form or another?
I find your lack of underwear disturbing.
If you were applying the penal systems to kids, all kids would end up in jail, they spend their time fighting each others and telling each others nasty things.
That same thought came to me when I read the article, but from a different angle: I have a work phone and a private phone, so I could just give up the work phone and see if that's enough for them.
Do so many people who go on this site not know how to make makefiles? Also why is it for hipsters? Or is the article for hipsters? Why does the author call his own published notes factually inaccurate? Why is it hacky to use a makefile? Is this all a big ruse?
That is what other non C derived languages use while and repeat for.
"Put your cybernetic implants in this pouch. Resistance is futile."
It is possible to legally own a lot of stuff but still be cool if you lose most of it.
So something like http://comroads.com ?
Minimalism sounds admiral, but how do you stop it limiting your life?

For example someone invites you on a hike but you can't fit decent hiking boots in your two suitcases. Or someone invites you to a semi-formal dinner but you can't fit a proper evening jacket in there.

You can't even hire boots as they need to broken in.
Addendum: Identity is a first-class concept when it comes to decentralised HTTP/2.

What we're looking at is Users in a shared channel applying functions to a synchronised tree, when it comes to edits. That's exciting to reason about.

Forget replicating frames, p2p live broadcasts and storing references to edits of hyperdocuments in a DHT for just a second though.

When it comes to identity we'll keep it simple and use the SHA1 of an ip, port and public key. This prevents people generating the node ID that corresponds to google.com at will, in principle.

As a user of the software implementing this protocol you can be identified as network_name/node_id/uuid4, where your contacts can alias that address with a username or you can transmit the nickname you want to be seen as alongside an avatar image.

The idea is to then facilitate a server/browser contacts API. You're a peer node. You're willing to transact with other people who're caching hypermedia either indefinitely or for a minute or so for a live broadcast. What needs exporting is the API for contacts list operations (JavaScript class and thoroughly documented stream RPCs) so developers and entrenched entities can implement chat, webrtc teleconferencing etc on top of this simply by introducing the functioning hypermedia into the DHT for retrieval. It shouldn't matter whether the original host serves the resource.

For example G+, Twitter, Facebook and Skype et al. could introduce their own particular index.html and client.js which execute a single-page app for utilising their silo'd contacts data/news feeds etc. Permitting them granular access to your decentralised contacts list.

I'm willing to discuss this via luke.brooks42 [at] gmail.com if anyone would like to support the development of this project.
I'd use separate libraries rather than monolithic frameworks. By the time you finished there'd be good chance the framework will be abandoned or have a huge backwards-incompatible update or two. With separate libraries you can swap those bits out, or otherwise it's manageable for you to take ownership of them by yourself.
There are more types of contracts than written contracts. Even handshake deals can be considered contracts (though you'd need evidence that the agreement happened as well as evidence that all of the other conditions for enforceable contracts apply). Paper contracts exist so that there is a very clear statement of intent, but that's just one kind of contract.
Write make files, or write CMake files.
These are welfare aspects, not socialist aspects. Socialism is public ownership of the means of production. When you tax on the high end of the income scale, and distribute those taxes as welfare, healthcare etc on the lower end, that's not socialism - it's welfare with capitalist economy as an engine (actually producing the income that you redistribute). The factories and the service providers are still privately owned.

So Australia, Sweden etc are not socialist in any meaningful way. Venezuela, OTOH, was actually going that way, with an ongoing large-scale nationalization of private businesses:

http://www.reuters.com/article/us-venezuela-election-nationa...
Its lock.
Sending her to jail, depending on how it plays out, may disqualify her from student financial aid, government jobs, pretty much any job with an element of trust involved, housing, foreign travel. To keep her alive, you burn many bridges that could have led to a life worth living. More likely than death, jail is what will eventually happen on its own if you fail to help her, and then she will carry that stigma forever (on top of being an addict).
Fixing autoconf/automake issues (particularly when autotools is upgraded) is one of the least fun things to do.

Make is fine. Automake is horrific.
I'm not convinced that state machines will operate at the byte level. First of all, not all tokenizers are written using state machines. Even if that is the mathematical language we use to talk about parsers, it's still relatively common to make hand-written parsers. Secondly, if you take a Unicode-specified language and convert it to a state machine that operates on UTF-8, you can easily end up with an explosion in the number of possible states. Remember, this trick doesn't really change the size of the transition table, it just spreads it out among more states. On the other hand, you can get a lot more mileage out of using equivalency classes, as long as you're using something sensible like code points to begin with.

If you're curious, here's the V8 tokenizer header file:

https://github.com/v8/v8/blob/master/src/parsing/scanner.h

You can see that it works on an underlying UTF-16 code unit stream which is then composed into code points before tokenization. This extra step with UTF-16 is a quirk of JavaScript.

If you think that V8 shouldn't be processing by code point, feel free to explain that to them.
It's a surprisingly high percentage... Here's an article about it, apparently the choice to have a child or not apparently plays pretty heavily into how you feel about it. I think it's cruel to judge people for regretting having a child, they already deal with the guilt of that as well as raising the child. There are all sorts of feels and viewpoints towards the world so I think as long as the parent still does their best it's best to respect their feelings rather than judge them as a bad person for having them.

http://www.theatlantic.com/health/archive/2012/09/not-wantin...
For the target audience (total Make beginners) poring through autogenerated makefiles might not be such good advice. It's functionally equivalent to telling people to learn Bash by studying a `configure` script, or learning JavaScript by studying EmScripten output.

If you're decent with Make and want to learn advanced tricks, then by all means go right ahead, but 95% of Make users will never need to delve into such details.
Wait... on-call time is not paid in the US?
QW had to send a lot less data. All the physical simulation ran on the server, so each client would send their inputs and the server would send back the world state. Current games' world state is a lot bigger than before with dynamic physical objects and skinned meshes with thousands of polygons, whose movement is dictated by a blend of physics, inverse kinematics and skeletal animation. Computer power has scaled farther than bandwidth and latency.
I dunno. Maybe it's a reaction to the myriad build tools developed for Javascript recently. Could they have been done with makefiles instead?
I wish I could adopt this with all the files that litter my google drive, dopbox, and desktop :-/
it is ironic that The DAO will then rely on something which they were trying to supplant.
Make is a great tool for automating simple things, but if you use a programming language you should probably use native automation tools for common tasks. If you have any non-trivial logic or want to enable code-reuse make doesn't seem like the right choice either.
Welcome, most reliable karma generator on HN.
As much as I like the idea of living with only a few possessions, it strikes me as a constant struggle: where do you put the 50 pack of envelopes you had to buy to send one letter? Are scissors for opening packaging included in his possessions? Nail trimmers? Toiletries? A formal pair of shoes? Do you have to hire all this stuff when you need it, or just keep in a drawer out of sight? And this is what I didn't get about the KonMari method either: a formal suit doesn't "bring me joy" any more than a sink plunger, but both are necessary. How are minimalists able to get away without this cloud of objects following them?
I suppose so. But there are always many tools for everything. And everyone can select his favorite.
But isn't that how businesses and boards work anyway? A supermajority will gladly screw over anyone else on the board. Just look at "Silicon Valley", the whole plot is about how boards can screw over the founders.
> You need to create a makefile to tell make what to do.

Nope. You can say "make hello" and have make automatically use its default rules - which can be configured - to e.g. compile hello.c into a hello executable. I use this frequently.
I'm going to guess it's due to repeated inaccurate characterizations of those countries' drug laws (or purported lack thereof).

When there's a thing that "everybody knows", but that thing is wrong, it's hard not to continue to correct it every time you see it misreported.

Again, this is my guess, I'm not rayiner.
Internet of Things, Machine Learning and Robotics Are Priorities for Dev in 2016
You _can_ use the GNU Autotools on Windows, though you need a shell installed (and a vaguely sane POSIX environment). CMake does a good job targeting a bunch of environments, including Windows.
The problem is if you want support (even commercial help) you'll need to follow some kind of prevailing trend. If I've got a system with grunt or gulp and I need help, I can probably find a local web developer. I'm not so sure if I can find someone who's an expert in Makefiles at the moment.
If you have on two pairs of trousers at once, one becomes underwear.
For anyone who's curious: you can use a ".PHONY" target to force targets to be rebuilt (i.e. that they don't correspond to real files). All dependencies of the .PHONY pseudo-target will be rebuilt unconditionally when encountered. Typically, "all", "clean", "install", etc. will all be phony targets as the goal isn't to literally make a file called "all".

The syntax is simple:

.PHONY: all clean install

marks "all", "clean" and "install" as phony. Even if the file "all" happens to exist, "make all" will still trigger the build.
Haven't used SQLite in a while, but this is how I did it.

You should enable WAL (pragma journal_mode=wal) I believe you need to do this on every connection.

Now, whenever you are accessing the data do it within transactions (https://www.sqlite.org/lang_transaction.html) generally SQLite will acquire proper locks when needed (it will minimize amount of locked time by deferring locks until they are needed, but you can use immediate or exclusive modifiers. If you for example put exclusive modifier only one program will be able to read/write at the time, you generally will want to use defer (default) behavior since it still provides the safety but multiple applications still can access the database at the same time)

Also note that locking might not work if you keep the database on network file system.
Travel Consulting – Airline Negotiations – Travel Team Consulting
Travel Consulting tips on how to make airline negotiations in such a way that you grow your agency's profits like never before. For more info visit:-
http://travelteamconsulting.com/airline-negotiations/
> I still frequently take off for the weekend without my phone, just because.

Same here, but this has a different quality. When you go offline for a weekend, it's your own choice. Putting your phone into a Yondr pouch is someone else's choice.

Within the "smartphone is part of my body" metaphor, it's similar to voluntarily going on a diet vs. being forced into one by someone else.
they probably borrow from neighbors...?

i definitely run into this problem. i need that _one_ envelope. do i really want to buy 50 to shove the rest into a drawer?
Upvote for that comment.

The stuff I've seen in some people's multithreaded code just makes me want to cry.
The only percentage that I can find in that article that lists 'unwanted' is 10, and the study is anything but scientific.

For most people birth control is about when they will have their children, not whether or not they want children. Having kids is - in mosts parts of the world - still the norm and not having kids the exception. Maybe that will change over time, it is now socially acceptable not to want children whereas say 200 years ago that meant that you were either destined to become part of some religious organization as a monk, nun or in the clergy.
When I read Dragon's Egg a few years ago, I realized that it had been the basis of my favorite ST:VOY episode:

https://en.wikipedia.org/wiki/Blink_of_an_Eye_(Star_Trek:_Vo...
Make's default implicit rule set is very useful for C, C++, Fortran, Pascal, and basically nothing else.

Out of curiousity: how do you configure the implicit ruleset? I wasn't able to find documentation on that (the closest I found was https://ftp.gnu.org/old-gnu/Manuals/make-3.79.1/html_chapter..., which explicitly documents the Make implicit rules but says nothing about changing/augmenting them).
This reminds me of the Ambric am2045 with 336 cores from 2007. They put 40 of these into an X-Ray machine for a total of 13,000 cores.

https://en.wikipedia.org/wiki/Ambric

http://www.embeddedinsights.com/epd/Diagrams/nethra-am2045.j...
Regarding your first paragraph, almost every hazard you mention is a consequence of prohibition, not an innate hazard of opiates themselves.

Illegal drugs get adulterated due to black market actors looking to pad their margins. Needles get shared because they're not legal to buy OTC. Poor injection technique and inappropriate routes of administration occur (in part) due to the desire to hide drug use. Those two items would probably be lessened if addicts had the same access to education that diabetics do.

And wildly varying purity is not something you find in drugs bought from a pharmacy, but is found from sellers operating in the shadows.

Cigarettes and alcohol do not suffer from these things, because they're legal and regulated.
You already found at least one. Also try anyone with a degree in computer science. I'd wager it's in most first year courses; it was in 3 of mine. Also you could consult anyone who spends a lot of time working on/programming for Linux and/or in C/C++.

And it's really easy, and there's tons of literature on it on the internet. And it has a manpage.
> I'll prove

Badly worded, sorry: I was inviting OVH to go to a court and check if Canonical has any right asking them a license.

I confirm that I'll move to another distro if OVH charges me more because of this.
For their talk of physics, missing an easy to measure results table seems very lacking when making a claim like this. Link bait?
So how do you program such a beast? What progress is being made on that front?

Cache coherency seems really hard to give up on, and even CPU-GPU cache coherency is becoming the expected norm, with even ARM delivering it.
It's probably not so much a minifier than an obfuscator.
I hate this. Every programming language that bolts on its own build environment. Make is language agnostic and that's a huge benefit, it means you have to learn about just one build tool and its peculiarities and that will allow you to build many different projects in different languages.

All these languages with their half-baked build tools that won't accept that they may have to play nice with other languages and their build tools are not helping.

Of course it is great when you write a language to also throw in a build tool, but in the end if the build tool re-implements 30% or so of make in a broken way I don't see the point.

Make does have its limitations, but most ordinary projects get nowhere close to reaching those.
If the storage is 100% reliable, why do they checksum the metadata?
The single biggest piece of advice I can give for Make is to make sure your text editor uses real tabs in Makefiles. My personal preference for everything is spaces (mostly a habit learned from Python's PEP 8), but Make doesn't honour spaces for indentation - only tabs.

Despite being an obvious usability hole, this has never been fixed. Exacerbating the issue is the poor error message given upon encountering a space-indented line in Make:

Makefile:2: *** missing separator. Stop.

Make is ubiquitous and fairly easy to use, but it's warts like this that remind you that it is fundamentally a build system from the far past.
> To explain the difference between your experience (outages taking you out) and "Google.com"

My comment was somewhat terse (to remain as brief as possible) so perhaps it wasn't clear. My logic was "Google.com is supremely reliable, which is a supremely difficult task, so Google must have really good engineering chops, so their products must be really well engineered." In other words, I was saying that I had in my head an image of Google being filled with great engineers building generally well engineered products. I wasn't commenting on reliability of service, which we haven't had any issues with that I can presently recall (we're only in us-central1-c).

> [Edit: And please reach out to support! Don't be silently unhappy, have someone call us up, even if it's just to strangle a PM about how difficult it is to use.]

Google provides no way to contact support without paying them for a support contract. It makes no sense for us to pay Google for the privilege of debugging their service/software. And I've crawled my way to support through sales before. For all my effort, and an inability to use the platform for a week, I was left with "Sorry, here's an issue tracker". The same kind of issue tracker that's filled with stagnant issues that are months or a year old.

The same argument could naively be made about AWS, which also charges for the privilege of reporting issues to them. But in all the years that I've used AWS I've only once needed to contact them with a problem. It was a billing issue, which they fixed, and then comp'd us with free service for the trouble. With Google Cloud we would need to diagnose, debug, document, and report an issue roughly every day of development.
This an API, jQuery autocomplete is a Javascript library. Typeflow is inteded for big amounts of strings to autocomplete. It lets you push a list of strings to the typeflow API and exposes an endpoint for querying it via an HTTP API. You can easily make it working with Twitter Typeahead or jQuery autocomplete leaving the computation of the suggestion to the API.
People have been underwater kicking since the 80s. They changed the rules to limit the distance one could kick underwater. Is this an old story?

Also, interesting to note that in the olympic / NCAA 50 yard and 50 meter freestyle, a drag race, usually people are not kicking to 15m. So perhaps underwater is only faster with effeciency in mind. With a short race like the 50 free it's possibly still not the fastest. It's similar to how fly is as fast as free swimming at short distances. It's the inefficiency that makes fly end up slower over a 50/100 vs freestyle.