skysight-inc/HackerNews huggingface dataset:
I used to think the same, and in the past it was possible (more or
less) to use just one messenger for everything, but I've changed my
mind on this.

- Siloing helps to separate communities. In particular, it reduces the
probability of accidentally sharing content with the wrong
crowd. I'm happy that people can't even see who's in my contact
list. On twitter people use automated blacklists to block people
based on whom they follow etc.

- One size does not fit all. Insta is ideal for sharing photos, but
not good for sharing code. BitBucket / Github on the other hand ...

Agreeing with CPLX, I'd say
the UX of modern phones makes is really easy to switch between apps,
to route content between apps if required (rarely in my experience)
and has enough similarity (e.g. shared keyboard, same cut/copy/paste
mechanism) so that using all of them is pretty seamless and requires
little in the way 're-wiring' one's muscle memory when changing apps.

I'm also an emacs user, but there is too much visual stuff going on in my communication these days that I can no longer route it through emacs. Moreover, I do most of my communication through the phone these days.
This is precisely the case. I doubt cost has all that much to do with it. Times have changed, and whereas in the past having folks over might include outdoor activities, it rarely does now. There are more entertaining things to do inside the house. And you have privacy. Most lawn care is just work, with equipment that costs money. And in the states, at least, if you don't do the work, you'll get fined. The city might even send someone out to do the work for you and charge you for it. Or you might have to deal with the housing association, which regulates what you can indeed to to your yard (sometimes they are fairly strict). If the area permits, you might be able to landscape your way out of most lawncare, but alas, that itself costs a decent amount of money.

The most redeeming aspect of the lawn is that it gives space between your neighbor and yourself. With some luck of location and money, you can make it fairly private - you know, just the sort of area to sit outside in the shade with your laptop and listen to the birds at the birdfeeder.
Acquired Podcast 15: ExactTarget CEO Scott Dorsey on $2.5B Sale to Salesforce
Yes, that seems to be a good combo, using the same.

Both AVG and Avast have really annoying upselling techniques, even when you already bought the product there are always addons they are trying to promote. Some popups and notifications are as annoying as the ones Microsoft use to push Windows 10 updates.
It seems like "won handily" would be more appropriate. I searched within the linked book and the only result for "handedly" or "handily" was one occurrence of "single-handedly".

Surprisingly, when you Google "won handedly" (used Incognito) the tenth result is that book.

Within Google books, the query "won handedly" returns 26 results; the first being the linked book as well as another The Michelin Men: Driving an Empire.

I would assume that phrase is used in the books, but if not the text possibly an image from one of the ads?
Maybe Eric Shmidt is a lower risk customer because he's opinion on "don't be evil" is that is a bad idea? :)
Average Israeli salary rises
That could cut both ways -

The sponsors whose content articles get blown up might get pissed with Google and take their ad spend elsewhere...
7 (I)’s of the Software Industry
Are you saying that most SSDs lose data they claimed was saved to stable storage in the event of power loss? That's crazy. Filesystems are greatly complicated by the need to be resistant to power loss.

What is the point of all that complication if the block device is just going to throw away those guarantees? If we're giving up on power loss safety I can make a super fast filesystem by making fsync a no-op and keeping everything in ram until I feel like writing it.
Open Source Hardware?
Or sometimes require you to have lawns at all (instead of other options that don't require the water).
An interview with Sean Parent
Lenovo Considers Price Hikes, Other Measures to Tackle Brexit
I've tried the Vive and it is very cool, but I do wonder how much physical space will be an issue for its take-up in the UK. We've got a decent size house by UK standards (4 double bedrooms and 3 reception rooms), but, with two kids, I really can't think of anywhere that we could sensibly put one.
You mean... like gzip?
> There's no Facebook Phone either

Well, not any more, but they tried.

https://en.wikipedia.org/wiki/HTC_First
It, or rather its OS, should be. But just like desktop OSes, I feel it doesn't enforce enough interoperability beteween applications and uniformity of UX.
His comment sums up exactly my thoughts wrt literate programming. It sounds like a nice idea, but in practice it falls far short.

The worst program I've ever had to maintain was written in funnelweb. It was a large, complicated program, so the funnelweb-generated documentation was tens of thousands of pages long. Nobody was ever going to read that. Trying to find out what you needed to modify to fix a bug was impossible from that document. Most developers I know looked at the woven C code (after all, that's where the line numbers in the stack trace pointed to), and worked from there.
If the system is correlating consonants in surname or prime number of '4' digits in a telephone number with increased risk, well, then in practice that simply means that you have a bad system with a serious overfitting problem - i.e., not a problem with your data but a problem with your learning process that's obtained "superstition" by treating random noise as important signal.

However, if you do some reason analysis, then this is useful and gives a lot of interesting information.

Names will be correlated with socioeconomic status and ethnicity, and also with education level [of your parents], income, etc.

Addresses obviously are strong indicators especially if you combine them with data about that location or even particular building if that's available.

Even phone numbers can carry a lot of true information e.g. location, or for countries that handed out new ranges for mobile phones, it would be correlated with how long you've had your phone number/how often you change them, which is a proxy for stability.

I'd bet that you could even build a somewhat predictive model of credit risk based on character-by-character analysis of email adresses - even excluding domain names, the fact if someone chose fluffybunny420 or jonathan.cumbersnatch carries some signal; not very much, but if you don't have better data then it will serve as a vague proxy for age, lifestyle and frivolousness (and in case of domain names, possibly employer) which all are important influencers of risk.
If others in this thread are correct and the explanation will be a sort of sensitivity analysis (meaning that the factors relevant for the decision have to be communicated) that will amount to discrimination. It doesn't matter if some employee judges customers by their skin colour or if someone build a convenient algorithm to do it for them.

I think name-based decisions are pretty obviously racist. I'm wondering about the less correlated variables such as addresses.
Your argument was cogent and reasonable until you used the term "SJW". It's a useless term, meaning different things to different people.

The point you seem to be arguing could also be applied to the funding of string theory, and is one that I agree with. You won't find people like Lee Smolin saying that the disparity in research funding in these areas is due to "SJWs", rather they would point to the short term vision of those who provide the funding (amongst other factors).
Apollo 11 Guidance Computer source code
There's code paths in the driver for artificial vignetting - likely added as a means for reducing risk for motion sickness in fast moving scenes. If those paths are activated erroneously (there's quite a few bugs transitioning between game and menus)
yeah, but also the opposite direction client -> server. client will send compressed data to server use LZFSE. Kind of nice extension to HTTP protocol, which only supports compression from server to client.
Exactly.

And the phone number and/or the IMEI is the technological identifier that ties all our identities together.
In a voluntary market such as the internet force is not part of the equation. I the consumer choose not the suuport aggressive anti-ad-block measures. I further am taking part in advocacy of removing aggressive anti-ad-block measures, or links to, sites I frequent. If someone posted links to trash you did not support you would of course not be forced to click it, but if you find a medium you enjoy frequently full of trash it would certainly be an annoyance.
Wouldn't be any surprise if Tim Peake turns out to be Britain's first and last official astronaut.
Great question!
There is more to it than you can see in the animation.
Because this is a quantum mechanical problem, it's not enough to take into account a single given field configuration at a given point in time, but we have to work with all possible field configurations at the same time.
Because the number of configurations grows exponentially with the complexity of the system, we have to invest enormous amounts of memory and computing power into simulating it.

Feynman actually wrote this pretty amazing paper on the topic of simulating quantum mechanical systems with computers: http://link.springer.com/article/10.1007/BF02650179.
You should have a look, it's quite readable!

(If the paywall is a problem for you, you should be able to find the paper elsewhere)
Also there appears to be no way in the dashboard of DO to see bandwidth usage. I don't know where they say it's metered after that, because they just slowed down the speed severely when my server went over, rendering it useless for its purpose without warning.
I can’t live in noisy towns all time. Sometimes my head felt like it was about to explode. I need to make time for myself every week. But it is quite difficult because of baby cry, car signals or night lusty singing of my neighborhoods. That’s how my city lives. And I know that I’m not alone who needs in silence. That why it can be selling. We take houses far away from cities, walk in quiet and picturesque places or scale the peak of the mountain. All these efforts are focused on loneliness. When we’ll have lost in our thought and meditate a little.
A quick reading of the license[0] shows that there's no legal stumbling blocks to the code showing up in browsers, but the license doesn't mention anything about patents.

[0] https://github.com/lzfse/lzfse/blob/master/LICENSE
This is a passionate issue, written from the perspective of a fierce activist. I participated in the march against DRM in March, and it's difficult to describe the powerful emotion bursting from the protesters, as well as Harry Halpin when he pledged his resignation should it pass.

But your perspective is important.

I encourage you to write to campaigns@fsf.org; I know personally that Zak and others will value your input.
You're grasping at straws.

There is almost nowhere in the US that you can 'buy milk or pay rent' in Bitcoins.

It's a useless, fantasy currency - and you have to find some other believer in fantasy currency, hope that there is some liquidity - exchange your fantasy money for real money in order to buy real things.

Diamond/gold/porc-future prices won't go to zero overnight, and there is a global market for them. They are at least 'somewhat liquid'

There is absolutely no reason to want to be paid in Bitcoin.

And there are many reasons to not want to be paid in Bitcoin such a price volatility, liquidity, the 'exchange tax' (you'll have to pay a % cut to transfer your money into USD), and the risk of your bitcoins being stolen in one way or another (hackers etc). Your regular bank account is de-facto insured.

Every other currency makes much more sense in every way than Bitcoin.

'Bitcoin' is not a study in finance or commerce, or really even technology - it's a study of human nature, why people believe certain things, and are addicted to waves of new ideas.
There's a difference between an inclination and obviously not wanting to hear something different.
Travis security advisory: Encrypted environment variables
A great deal of places in the states have little-to-no shared (or public) greenspace within walking distance. It isn't just wealthy suburbs, but nearly entire cities. Small towns might have one such space. Larger cities (30-50k) had a few more, most were just small patches with playground equipment. Some towns I lived in actually had public green areas with playgrounds... that had no sidewalks or safe places to walk that led to them. The houses in the areas all had nice-sized yards, but I still found this curious.
It's hilarious how such a huge industry has become of something that has soberly assessed very little value or effect.

In fact, considering the massive vulnerabilities in AV software discovered by e.g. Googles Zero project, I'm pretty sure the security gain has already slipped into "negative effect" territory five years ago.
But VR is more GPU intensive than playing on a 1080p monitor. From what I remember a Nvidia 970 GTX was recommended by Valve before the 1080 GTX was released which was pretty near highest end back then.

And many VR early adopters are now buying 1080 GTX to improve the often lacking frame rates.
A Call for Community Collaboration Around Docker and SwarmKit
Honest question - who is the market for this phone?

Very security minded corporate it departments?

From first glance it would seem I would need other people to have silence circle in order for most of the features to be useful...I don't know anyone who uses it - why would I be an early adopter as a consumer?
HOW THE MEDIA SCREWED UP THE FATAL TESLA ACCIDENT
API Blueprint: human-readable API specification language
FreeType 2.6.4 released with new and better bytecode interpreter
If it's of any consolation, I knew about the connection before this article.

FWIW, "handedly" means "easily". "Won handedly" means "Won easily". Wiktionary says it's non-standard, and prefers handedly - https://en.wiktionary.org/wiki/handedly . See https://duckduckgo.com/?q=%22Won+handedly%22&t=ffsb&ia=web for other examples of "won handedly" in use.

The "show"/"shop" is indeed a typo. Here's the original: https://books.google.co.uk/books?id=NX4AAwAAQBAJ&pg=PA31&lpg... .
The new interpreter has absolutely improved rendering of fonts, at least subjectively for me.

CHANGES BETWEEN 2.6.3 and 2.6.4

I. IMPORTANT CHANGES

- A new subpixel hinting mode has been contributed by Nikolaus
Waxweiler, which is now the default rendering mode for TrueType
fonts. It implements (almost everything of) version 40 of the
bytecode engine.

The existing code base in FreeType (the `Infinality code') was
stripped to the bare minimum and all configurability removed in
the name of speed and simplicity. The configurability was
mainly aimed at legacy fonts like Arial, Times New Roman, or
Courier. [Legacy fonts are fonts that modify vertical stems to
achieve clean black-and-white bitmaps.] The new mode focuses on
applying a minimal set of rules to all fonts indiscriminately so
that modern and web fonts render well while legacy fonts render
okay.

Activation of the subpixel hinting support can be controlled
with the `TT_CONFIG_OPTION_SUBPIXEL_HINTING' configuration
option at compile time: If set to value 1, you get the old
Infinality mode (which was never the default due to its
slowness). Value 2 activates the new subpixel hinting mode, and
value 3 activates both. The default is value 2.

At run time, you can select the subpixel hinting mode with the
`interpreter-version' property (provided you have compiled in
the corresponding hinting mode); see `ftttdrv.h' for more.
Building the Custom Android Module for React Native
"Who is correct isn’t important. What should be important is that browsers put consistency across themselves first."

No way - The only way we'll end up with compatibility across browsers is to have unambiguous (as much as possible) specifications that define how they should behave and for browser users to insist their browser vendor aligns with the standard. I lived through that past and have no desire to repeat it.

If you think about it from a network theory perspective, each of the browsers is only trying to be compatible with one other party (the specification) in this mode. The alternative is that each browser is trying to be compatible with "n - 1" other parties where n is the number of browsers in the pool. And the total effort is the classic (n * (n - 1)) / 2 "connections", so the browser industry would be wasting a lot of effort.

Worse yet, there's no single release point. Consider that browser A makes changes to be compatible with browser B (because that behavior seems correct compared to browser C). Unbeknownst to them, browser B is about to change their behavior to be compatible with browser C. Now the A-team's work is either wasted or yet another incompatibility.

Browser-focused standards are the best thing that happened to the web in the last 10+ years.

- http://caniuse.com/

- http://html5readiness.com/ (now a bit dated)
The Pros and Cons of Unlimited PTO
Complexity classes of algorithms.

There are only 3 variables in a discrete logarithm problem but it takes super computers to solve. Same with prime number factorization.

Number of inputs is completely unrelated to the time to solve depending on the algorithm being used to solve the problem.
I'd definitely prefer a whitelist. Or hell, Android asks if you want to enable permissions now before using them; why not ask for a notification permission?
Who Will Bring Facebook's OpenCellular to Nigeria?
Ask HN: Most expressive pattern matching language
Which language have you learned and used that has the most expressive pattern matching constructs?
The actual form would be

http://web.mit.edu/~simsong/www/ugh.pdf#page=177

For pdf.js (used by Firefox), refer to https://github.com/mozilla/pdf.js/wiki/Viewer-options

If using Adobe Reader, refer https://www.adobe.com/content/dam/Adobe/en/devnet/acrobat/pd...

(The second variant mentioned by you that works in Firefox using pdf.js appears to be a undocumented feature!)
> for anyone who doesn't have the paper handy

You are supposed to have the paper handy. Either you know the paper by heart, or you are actually learning the paper and look at the implementation. Otherwise you really have nothing to do in this piece of code.

Even more mundane codebase are like that. Variable are named in the context of the project. If you have no familiarity with the project variable "user" or "u" means exactly the same to you: nothing.

The difference is that generally regular project are huge in size but simple, while filesystem, compression/encryption algorightm, trading algorithm are tiny but extremely complex. In the former, you use more descriptive naming because people will only have a high level knowledge of the spec. In the later, there is no difference between spec and code, extreme familiarity is necessary to touch the code and naming convention crutches are simply unnecessary.
Grenoble continues to move schools to open source
I'm under impression that USA is still segregated enough so that for many places, an address (or even districts/towns) will be a very strong indicator of race.
I hero-worship Knuth as much as anyone, but that document is frankly terrible.

Take a look at section 6. There's a flowery sentence that says no more than "Add word to vocabulary" (completely pointless if this were a method called "add_word" on a class named "Vocabulary") and then a dense chunk of completely unexplained code.
The general consensus in the Go community is that the default http.Handler is sufficient for most things. You can leverage additional middle ware or gorilla toolkit for more complex stuff. Most stuff works nicely with net/http.
Super zoom cameras are an interesting category. You can do lots of cool things with small sensors and you get a lot of reach with a very compact lens. (If you only have to focus the image on a very small area you don’t need a lot of glass to make far things appear close.)

Super zooms are in a way embracing the positive traits of small sensors. But there is more than one kind of camera. Small sensors will still have trouble in low light (since their area is smaller they capture less light) or resolution (if you want to make them capture more light you could make the pixels larger, trading off resolution, but potential noise in low light also reduces resolution).

Cameras are and always have been about capturing light and the tradeoffs involved with that. As such it is absurd to claim that “optical zoom” is what it’s all about. It was and always will be a delicate interplay of optics, light and technology (whether film emulsion or digital sensors) and there is more than one way too solve this problem.

The sensor this camera used to have was widely hailed as excellent and had moderate 16MP. 24MP isn’t such a great jump (and really not that special for an APS-C sensor), but this sensor could conceivably deliver that additional resolution with no cost in low light performance. And that would be brilliant. (But there is more than one camera in this category.)

But in a way I agree with you. Not about super zooms, that’s just silly. But about tools fit for the job. I have the X-T100 (no weather proofing, fewer control points, less solid build, identical 16MP sensor as the X-T1, cheaper) and if the X-T2 had ditched the control scheme of the X-T1/T100 I don’t think I would even consider it, even if it had 48MP. Or 96MP. I don’t need that. I need a camera that’s pleasant to use and that delivers great photos. I don’t need a megapixel monster. I need a camera I love to take in my hand. Handling, to me, is much more important than nearly anything else, beyond a certain baseline of image quality and performance.
Peer review also needs a reboot. It's epically unhelpful and slows down publishing dramatically, Think they should mandate post publication review.
> First, they realize managing notifications is highly important. They ruthlessly unsubscribe, block and restrict.

If my wife's phone is any indication this is probably more indicative of being a programmer than being a "digital native."
Hellz yes on a dashboard for unified messaging! But instead of leveraging phone numbers[1], etc., everyone would just get their own space on the web - maybe like a domain. Then all services -whether social networks or email or text whatever - could be funneled through that space/domain. Then there would be a single messaging platform app/server running on this space/domain...and it would act both as a shield but also a filter and much more!

[1] Using a space/domain on the web avoids the changing phone numbers dilemma, etc.
wow, you just fixed everything that i thought was wrong with google. thank you.
Perhaps “random fluctuations” are as much random as Brownian motion. I.e. there is cause and effect on a finer level (yet not possible to probe with current techniques), however a large number of interacting particles renders analytical prediction infinitely complex task.