skysight-inc/HackerNews huggingface dataset:
I'm not sure it ever was "necessary" for Wikileaks to indiscriminately release large collections of emails sent to the Turkish government, especially if the HuffPo report is correct and it pertains largely to ordinary citizens' messages.

"If you have nothing to hide, you have nothing to fear" is even less true of releasing citizens' sensitive information to the entire world (including factions in a country where people are being killed over their political actions) than it is of allowing governments to collect and share it.

Just because some of the things revealed by Wikileaks are very much in the public interest doesn't make it an entirely benign actor.
FYI, in IE 11, only the header gets centered and not the whole body.

I'm not sure if this was intended or just a bug with IE though.

Nice intro to web design. I love the simple presentation.
CRISPR gene-editing cancer research called a major breakthrough UPDATE
this is frikking awesome!
do you have any of the lvm and pipe scripts publicly available ? i'm kinda struggling with building and setting up lvm on ec2 automatically and was wondering if there is any tidbits you can pass along.
Great write up. A couple points -

I'm not sure this post is illustrative of any generally applicable considerations (re: the title) in the choice of Postgresql vs MySQL, since Uber seems to no longer be using a relational model for most of their data and is using MySQL effectively as a key-value store.

> say a developer has some code that has to email a receipt to a user. Depending on how it’s written, the code may implicitly have a database transaction that’s held open until after the email finishes sending. While it’s always bad form to let your code hold open database transactions while performing unrelated blocking I/O, the reality is that most engineers are not database experts and may not always understand this problem, especially when using an ORM that obscures low-level details like open transactions.

I have to very seriously disagree here, ORMs make a lot of things easy - and you can get away with building stuff for a while without understanding the underlying databases or SQL but only to a certain scale (I'd say more like medium-scale, definitely not large or Uber level). If you have engineers writing code that interacts with a database without understanding transactional semantics, the engineer in question not the database is the problem.

> We started out with Postgres 9.1 and successfully completed the upgrade process to move to Postgres 9.2. However, the process took so many hours that we couldn’t afford to do the process again.

There seem to be ways [0][1] to do online upgrades with Postgres (before logical decoding in 9.4), although I haven't personally used them. Not sure if they explored these options at Uber or not?

[0] https://github.com/markokr/skytools
[1] http://slony.info/
This is welcome, but I wonder how Brexit will affect all this in the long run.
I know I can backup the contents of Google Authenticator on iOS if I perform iTunes backups with the "Encrypt backup" option checked. I'd wager that many who are backing up their phones don't have this checked, and don't realize if they have to restore their phone that the gAuth app will pretend you just installed it from scratch with no codes.

I'm not sure what the backup situation is with Android.

I've started backing up the actual strings that the app uses to generate the codes in an encrypted vault. You usually have to manually have these strings shown to you in lieu of a QR code. While creating another avenue for someone to hack you, at least I have a backup as well as a way to add a second device go show me codes. This is definitely beyond the capacity of the average user.

I think there might be online services that handle keeping codes for you? Like you can install an app on your phone, log into an account, and it presents you with all of your codes. Anyone have a recommendation for one of these that works well for them?
Who defines 'necessity'?
This is a little unfair.

I agree with you in spirit, but this policy is pretty damn close: note that "primary caregiver" leave is also a full 16 weeks. I've seen companies move away from "maternity" vs. "paternity" terms and just talk about "primary caregiver" and "secondary caregiver". Which not only gets away from the gender-specific career costs, but also covers non-birth parents (e.g., adoption, surrogates).[1]

In other words, the father[2] is more than able to step into the primary caregiver role and allow the mother to return to work and minimize career impact.

Now, there's a separate argument that both parents should get equal time off. I agree with that view as well, but it's a different philosophical argument.

Finally, I would be interested to know if there's a tenure requirement for parental leave at Basecamp. It's often 12 months "vesting", which is a bummer for those with children on the horizon. I recently switched jobs and had a kid: I gave up an 8-week parental leave benefit at my old company for no benefit whatsoever at the new one. I made the decision that the cost (losing the benefit) was worth the opportunity, but I could see others deferring a job change in that instance. This is a rather insidious form of Family Responsibilities Discrimination that adds a career cost to both men and women (and moreso for women).

[1] Traditional maternity policies are often focused on the medical aspects of childbirth rather than newborn bonding and care.

[2] Replace with other terms as appropriate.
So basically, if you don't intend to use it as a relational database, and you have enough scale to run cross-data-center (and across-the-world) master-master replication, then you should maybe switch from PostgreSQL to MySQL?
>Yes. Aptitude with screwing around with a GUI isn't very relevant.

It is relevant to actual stuff they want done.

Unless they are programmers aptitude in screwing around with cli commands isn't very relevant.
You nailed it.

Chronic pain can be really, really, debilitating.

Think about what you are going to do in a few hours. Maybe you'll hop on public transit to meetup with someone. Or maybe bike somewhere. Or take a shower. Or make a sandwich. Or make love.

Now imagine if you had a really bad joint (ankle, knee) or back. Suddenly, taking public transit has additional complexities, like does the station have a lot of stairs and a lengthy distance to the train? Will I be able to get a seat? Or if I'm biking, is my commute going to flare up my joint/back? If I take a shower, I can't stand too long lest a joint start to get painful. Besides, I have to 'save' my pain threshold for situations that are a bit less controlled like walking to the bank or returning an item.

Whereas most people can spend 100% concentration on their surroundings, I have to expend mental energy thinking "Where's the next seat? How long am I standing up for? Am I causing damage to myself?" When science and medicine can't do much, and quality of life drops dramatically, it's hard not to think about alternatives.

Death is permanent but it does have one advantage: it's silent. There's no more pain.
CitusDB is essentially vanilla Postgres now that they've moved their implementation to an extension.

It won't specifically address the problems posted here, but will solve other ones like trying to scale a system beyond a single node.
The article could be summed up as "Postgres is not a distributed database." MySQL isn't either, although it certainly has more friendly replication technology. I think it's a lot more likely that what's really happening here is that they've designed their "schemaless" schema or its supporting software to handle the kind of soft errors that MySQL is permitting and Postgres was not.

We have MySQL replication across the country where I work and I certainly wouldn't characterize it as robust; it fails every 3-6 months. MySQL replication is certainly a lot older and easier to use than Postgres's, but SQL databases are fundamentally CP systems. When you say "This design means that replicas can routinely lag seconds behind master, and therefore it is easy to write code that results in killed transactions" it sounds like you're blaming the way replication was implemented for a physical problem. There is no way to design a replication system such that two highly-consistent databases can achieve perfect availability in the face of real-world networks. A worse protocol can exacerbate the problem, but a better one can't make it go away.

I have never seen corruption with Postgres (unlike MySQL), but I have never tried cross-datacenter replication with it. Apart from that, Postgres generally seems to do much better with consistency than MySQL does, where DDL statements are not transactional, etc. So I am not surprised to hear that their system trips harder on Postgres's more aggressive consistency.

In short, I suspect a more robust solution to their problem is a NoSQL database. On the other hand, it sounds like they want a combination of availability and consistency that will be difficult to get off-the-shelf. I'm glad they found a way to make it work. I wouldn't generally choose Postgres for a scalable system with an aggressive availability constraint--but then again, I wouldn't choose MySQL either, and I generally avoid problems that demand highly scalable, highly available solutions.
the same world where mysql lets you corrupt your own data. did you just stop reading? in what world does a data corruption event prompt you to change platforms to another platform that has a history of data corruption?
They are probably actually confusing Paramount Television (which was a name retained by CBS after the CBS/Viacom split through 2009, when the unit was renamed CBS Television Studios) with Paramount Television (the unit of Paramount Pictures, which resurrected the unit name in 2014 or so.)
I think this would be very helpful to plan things and have a good food while on road.
Love this! Step by step explanation of how to do something which literally shows rather than tells.
It's not, most likely. A working 2-factor scheme needs two devices and communication channels to the end user that are completely independent of each other.

If your mobile phone links to an account somewhere (e.g. Google account) that you can also access from the other device (e.g. a PC), and security-related settings can be changed from the other device, too, then that's insecure out-of-the-box.
Sort of reminds me of what Bob Ross from the Joy of Painting does in a couple of strokes... :)
Interesting.

I read previously that tallness is fairly dependent on good nutrition, which would correlate with overall increase in welfare/quality of life.
Yeah, I don't know why people get surgery considering perioperative mortality[1]

[1] https://en.wikipedia.org/wiki/Perioperative_mortality

/s

Obviously people die all the time and the cause of death can be attributed to any number of activities that are otherwise beneficial to the vast majority of people who undertake them.
There appears to be a copy on Youtube: https://www.youtube.com/watch?v=xjDLakFBzWM
Lovely! Definitely like the style here and the focus on content first. Like other people have said it's similar to Motherfucking Website[1], and a Better Motherfucking Website[2]. I'll need to start including this when I link to those two.

For my website[3] I'm really trying to keep weight on the wire down too so I am opting to skip the custom font and header image. It's quite nice to have 10-15kb pages in the age of the web obesity crises[4]. A header image and a custom font does have a big effect on how personal the content ends up though.

[1] - http://motherfuckingwebsite.com/

[2] - http://bettermotherfuckingwebsite.com/

[3] - https://hugotunius.se

[4] - http://idlewords.com/talks/website_obesity.htm
What were their reasons for planting another monoculture, after the last one ended so badly? It seems obvious to me that an urban mixed forest would be more resilient against disease -- so I'm guessing that urban planners had some reason I'm not thinking of...
So PG has a process pool instead of a thread pool. (I doubt either database is spawning procs/thds anew willy nilly for each request).

This means the PG has explicit IPC overhead, vs the quick and seductive path (to the dark side?) of simply sharing memory between threads. Safety vs speed.
When you say "convenient" you're really saying "inexpensive". At least in the US, HBO NOW is only $14.99, which for a season of a TV show is not ridiculous (by comparison to what other shows cost on DVD or streaming through Amazon), made less ridiculous by the fact that you actually have access to all seasons of that show.

As for whether it's stealing or not, it seems difficult to rationalize it. Is sneaking in to see a movie stealing? Is stealing perishable food stealing (or is it only stealing if all of the rest of the food is purchased before it spoils)?

Legalities aside, ethically it seems pretty clear; if everyone acted as you propose to act, then there would either be no reward for producing content, or content producers would need to physically lock down the ability to view the content (like having movies or TV shows only available in theaters).
Making a lot of "buzz-word" errors like that, I now use the simple heuristic: choose the oldest available technology that solves your problem.
Also known as Lindy effect
https://en.wikipedia.org/wiki/Lindy_effect
A Loophole in the Right to Be Forgotten
Tools such as the percona toolkit (https://www.percona.com/software/mysql-tools/percona-toolkit) provide the ability to perform safe and performant online alters for MySQL. Behind the scenes it actually creates a new table with the new schema and utilizes triggers to apply writes to the new table as the original data is being copied. Once it completes the table is renamed and the triggers are removed.

Percona also recommends using this tool to safely perform alters for any Galera-based replication product (Percona XtraDB Cluster, MariaDB Galera Cluster, etc.)
Ask HN: CS graduate programs in Canadá
What are good CS graduate programs in the Toronto area?
But the school is also closed during the summer? Where I live there is free daycare for kids up to 12 (?) or so during holidays, but many people take some vacation days during the year and maybe 3-4 weeks during the summer.
So the major issue detailed here is that postgres basically uses immutables rows which creates performance issues with writes.

Just read about their new schemaless db in their blog an the first paragraph contains this:

"The basic entity of data is called a cell. It is immutable, and once written, it cannot be overwritten. (In special cases, we can delete old records.) A cell is referenced by a row key, column name, and ref key. A cell’s contents are updated by writing a new version with a higher ref key but same row key and column name."

So, mmm..., not saying that postgres didn't pose a problem for them but I think postgres' db model fits better to their new db then mysql. They probably had to work really hard to get mysql to work like postgres.

Without this issue, it looks like two things needed.to be done with postgres that would have solved their problems have indexes that point to primary id and do logical replication (which they say a plugin solved in 9.4).

Is this a case of "I got burned by something so I won't use it again"
Needs to add width: 100% to the max-width statement. Annoying nuance.
It's one of the plots on The Expanse, a reality grounded SciFi set about 500 years from now.

A large Mormon colony ship is being constructed for a one way, multi-generational trip outside the solar system.
In my experience DB connections are overwhelmingly idle. Even if you omit the obvious dead times between requests and consider only actively executing connections, a request will spend most of the time waiting for a resource or another (read IO, commit flush, latches, locks). It takes an extraordinarily well tuned app to be able to drive all connections to be anywhere near 100% CPU bound and never conflict or wait.
Sure but that's a big monthly expense.
The Campaign to Make You Eat Kimchi
> the very specific Uber use-case

Other than the "schemaless" layer, the issues mentioned are fairly common.
How much would it cost to make one?
Makes sense even on the naive level.

The heart has to work harder, so the heart problems.

Body volume is larger, therefore more chances for cancer.
I used both Postgres and MySQL and in my opinion encodings are more difficult to setup with Postgres. You need to change some "template" when creating a database to use unicode. Otherwise it will use latin1. I do not even understand what a database "template" is, how it is related to encodings, and why it is so overcomplicated.

In MySQL there is no templates and you can change the encoding of a table at any time using ALTER TABLE statement.

And in cloud IDEs like c9.io you cannot use unicode collations in Postgres because they need to be installed separately and they are not installed.
My friend did the MSc in Applied Computing from U of T and liked it enough to do PhD there as well: http://web.cs.toronto.edu/Graduate/prospective_gradwhy/mscac...
It's good to know that it exists (and that it's not included in -Wall -Wextra) but it's not quite what I'm looking for. The cast itself is well defined --- it's the subsequent write that is the issue. While it wouldn't be possible to catch all of these, those that are caught are likely genuine bugs.

That said, it looks like -Wcast-qual is also supported by clang and icc. Clang includes it in "-Weverything", which gcc and icc do not support. Even if not ideal for this issue, I'm sure there are cases where it would help to catch bugs.
missing a backup? i don't think google ever really deletes anything from their servers... even if you request deletion, they will still keep your data
Yes, quite sure since I use Google Voice so all of my calls and SMS's go through their infrastructure. And even if I didn't use GV, I use their dialer, SMS, and contacts app, so they already can already see all of my calls, SMS's, and contacts.
Koding open-sources its cloud IDE, integrates it into GitLab
Thank you for introducing me to "heap only tuples", I did not know about it. From what I read about it from Postgres's documentation[0], it would have helped in the updates where no indexed column was updated.

0: https://wiki.postgresql.org/wiki/Index-only_scans#Interactio...
Why would they lower prices? The government mandates we MUST have insurance, so they know they've got a continued source of business. They'll simply increase profits. The average American has absolutely no way to correlate the amount they pay for insurance to what it costs the insurance company.
My claim was that you don't want to hit the bottom. If the bottom is "very short", isn't that worse? I don't know the numbers for Apple's keyboards? You activate after about 2mm on a typical mechanical keyboard. You hit bottom around 4mm, which of course, you don't want to do.
Demo appears to be broken in Firefox and Chromium.

When it works, and if it meets the guidelines, this might make a good "Show HN".

Show HN guidelines: https://news.ycombinator.com/showhn.html
Wonderful! For a moment at the start though, I wondered how such a poorly designed page, could teach anything about web design. Then I clicked the first link... :)
Peru Scrambles to Drive Out Illegal Gold Mining and Save Precious Land
Congrats Daniel and team! Awesome work!
Yep! saurik's reply above sheds some light on the issue (read more important than write). Also, to the downvoter, sometimes the solution to a bug report is improved and more visible documentation of existing features.
Shouldn't the drop in revenues be balanced by the decrease in payouts?
As a maintainer of the projec,t it's cool to see the Fluentd plugin in the repo: https://github.com/eventql/fluent-plugin-eventql
Don't know if it's still an issue, but I once setup mysql, with an id of binary(16) to store UUIDs, and used 0-padded conversions for legacy id's... when trying to port over existing records I discovered the index on a binary field was a "case-insensitive" textual index by default, so started getting conflicts when the ascii equivalent of "a" and "A" as a byte was inserted, etc. This was about 15 or so years ago, but the irksome nature still sticks with me to this day.
Skeuomorphic icons are probably OK, but skeumorphic behavior is horrific. Consider the awfulness of the Mountain Lion era address book and calendar that tried to emulate the behavior of physical objects by imitating their limitations. That, for me, was the nadir of OS X usability. It might have been great for someone who'd literally never seen a computer before, but anyone who wanted to navigate a calendar without flipping through months one page at a time had a real fight on their hands.

If you want an icon that looks like a physical object, OK. I can probably live with that. But the moment you want to extend that to making the app act like the object its icon represents, you've lost me. Perhaps Ive et al decided that having a realistic Notes icon attached to a non-notebook-like app was more confusing than keeping the old one? That certainly seems justifiable.

Also: who cares what the Safari compass looks like? To me, "compass" means "compass". It's never represented a safari to me (not that "safari-the-adventure" represented "Safari-the-browser"). What would that skeumorphic icon be anyway - a rifle?

This is what we used to have: http://venturebeat.com/2012/10/30/skeuomorphic-design-or-one... . I couldn't have been happier when Mavericks ditched all that. It wasn't perfect, to be sure, but it went a long way to restoring artificially-lost usability.

The article feels to me as though the author is caught up in nostalgia. That's fine, but not mistake "I liked it that way" for "that way was objectively better".
My parents had a contact book when I was little (back in the 80s), but they eventually went to a system of cards standing up in a tray separated by last letter. It made it easy to pull it out when you wanted to make a call. They now have a mixed system where their most used phone numbers are in their iPhone contacts, but they have still have that tray for everybody else.

I had a contacts section in my DayTimer back in the 90s, but I've used a contacts program ever since I switched to using a computer-based calendar.
Out of curiosity: What cultural reasons?
Clones of Dolly the Sheep Have Aged Like Any Other Sheep, Study Says
The article's title is a little misleading. This would shrink the market as a whole. Revenue would go down and earnings would go down as a result. However, it wouldn't have to affect profitability.

In fact, profitability would probably go up on these policies initially since the safety benefit would be immediate, but the implied risk in the policies would only come down over time as the safety works it's way into statistics.

(Apologies if I'm not using correct terms. Not an actuary.)
About eleven years ago I started having crippling RSI in my hands and wrists. I fit the typical patient... Type all day sitting at a desk.

Posted about it on Slashdot and someone told me to look up TMS. Changed my life. After years of problems it completely went away in weeks. After years of searching for ergonomic solutions it was bizarre that following TMS treatment cured it in weeks and now I don't do anything ergonomic and I have had no problems for over a decade.

More info... http://www.rsi.deas.harvard.edu/mb_what_is.html

http://m.youtube.com/watch?v=vsR4wydiIBI
Not so much I guess for memberstates excluding Britain, because since this is a conclusion made by the EC it can be used as precedence in any other member state even though it has been brought up in the UK pre-Brexit.

The situation in Britain however could be overturned the moment article 50 gets activated and its no longer a EU member state (and thus no longer falls under its legislation).
Survey Suggests a Public Wariness of Enhanced Humans
Keep the original article title as-is when submitting to HN.
Thank you for the feedback!
Common Go for Data Science Questions
Well done :-) https://twitter.com/LeviNotik/status/757991465649778689