skysight-inc/HackerNews huggingface dataset:
> I started to ask Ehrlichman a series of earnest, wonky questions that he impatiently waved away. “You want to know what this was really all about?” he asked with the bluntness of a man who, after public disgrace and a stretch in federal prison, had little left to protect. “The Nixon campaign in 1968, and the Nixon White House after that, had two enemies: the antiwar left and black people. You understand what I’m saying? We knew we couldn’t make it illegal to be either against the war or black, but by getting the public to associate the hippies with marijuana and blacks with heroin, and then criminalizing both heavily, we could disrupt those communities. We could arrest their leaders, raid their homes, break up their meetings, and vilify them night after night on the evening news. Did we know we were lying about the drugs? Of course we did.”

Self harm never had anything to do with anything.
All of my passwords are based on the website name that I'm logging in to. I have a small algorithm in my head about how to generate a password from the site name that looks at stuff like first and last letter, number of letters, some kind of prefix/suffix, etc. And I end up with a unique password around 20 characters that I don't need to remember for every website.

This way I don't ever remember a password, I just remember the system.
While I do agree that it is a human right to consume anything you want, I very much disagree that "It is virtually impossible to harm yourself" with LSD or Ganja ...

Just because you can't really physically kill yourself with the drug, doesn't mean it can't do you bad otherwise.
You're being generous.

"Web design isn't the solution. Web design is the problem."

Actually, another huge part of the problem are really crappy default entity properties by the W3C.
Payloads are insured and the insurance cost in this case is reportedly more or less the same as on a new rocket. That makes it a no-brainer.
Even if the equity was taken into account most startup equity (once you read the terms and conditions) is worth ~0. There's a few bigexits warping thenfigures but the median is pretty low.
Internal auth strictly over LDAP or SSH keys, so we don't have to worry about that.

For external things we can't integrate into that we use a password manager (self-made). People get dropped into the categories they're supposed to access, and done.
People telling each other about Uber. Mass media writing about Uber. People working for Uber.
Yup, lots of people, we are creating some new components for RhodeCode using Polymer right now. Whole team is very pleased in how nice it is to work with it.

Companies like EA, IBM, General Electric or Salesforce use it in production. Works like a charm, there were multiple sites that list some polymer projects I think.

IMO it is a mature project perfectly fine for production use today - slack community is ~5000 members and vary active - lots of job offers, lots of discussions and applications being worked on.

https://new-console.ng.bluemix.net/

https://www.battlefield.com/

https://github.com/abdonrd/PolymerProjects
With Google Mail (and Apps) anything after a + in the first part of the address is ignored, so foo+dropbox@gmail.com would be routed to foo@gmail.com. That's the easiest way to do it that I know of. No need for managing separate aliases.
Using a non-Google ecosystem phone is trivial. Hundreds of millions of people do it. I've lived on Chinese Android phones, it wasn't hard. In China, instead of being "coddled" by Facebook/Google/et al, you are "coddled" by BAT - Baidu/Alibaba/Tencent. Apps like WePay are indispensable, ergo, as long as your phone runs WePay, you can do lots of stuff.

Arguing for more Android forks is really a counter to your complaints about security issues, since it will result in even more fragmented updating schedules, given carrier control. It also contradicts your usual pimping of Windows Phone, complaining about Google's "monopoly" on Android, but supporting a monopolist (Microsoft) who won't even open source their OS.
Obama has not put any corporate whistleblowers in jail. We can debate the merits of prosecuting those who leak government secrets, but that is a separate issue from this one.
Visit Amir Najam SAP Analyst Profile on Google+
This looks pretty cool, but seems like they are invite-only for now...
Any chance you can drop an invite for a fellow HNer? :)
And they should. But they probably won't any time soon. Google is very conservative about new major changes in Google Maps, and it's a good thing.
KeePass and KeepShare are both GPL, which is already a huge improvement over "trust this largely unknown company".
We're a small company, but we have a lot of credentials that go around and we generally use Lastpass with a shared folder because it's supported on all platforms and free.

The only thing that bothers me (and can't be circumvented because of browserdesign) is the ability to get plaintext passwords from autocompleted forms. So if an employee wants to write down a password, there's nothing stopping them.

For access to our servers we require everyone to use SSH keys.
Mostly people who work at Google then?
Does it support encryption yet? Also, you'd have to auto-pin all your files, or risk losing them.

I think GlusterFS (battle-proof, but file-wise and assumes an administrator with access to everything) assumes or infinit.sh (robust ACL, but young, not open-source) better addresses those use-cases.
For gmail, if you have someone@gmail.com, you can just append +anything to your address like this: someone+anything@gmail.com. It will still end up in your mailbox without having to set up anything. See https://gmail.googleblog.com/2008/03/2-hidden-ways-to-get-mo...

I would assume that google apps version of gmail offers something similar.
H1B is a classic case of how legislators are far away from reality.

Increasing minimum wage does not help it creates a bigger problem. A lot of smaller companies will happily show $100,000 salary to their employee while paying only $30,000. This is technically a fraud but the companies do it all the time. Google or Facebook wont be able to do it but those consulting companies could.

Here are my suggestions:

1. Do not allow consulting companies to file H1B at all. If the person is specialized then let some company hire him/her full time. Create a separate visa category for consulting work for foreign companies trying to send their staff to USA.

2. Scrap H4 and give EAD to the H1B spouse. Most of the illegal things about H1B is because of the desperate attempts by H1Bs to get the well educated spouse be productive. Also given that most H1B are male this is also a very anti-women thing to do by putting women out of work. My wife enrolled for F1 in a small university just to get an OPT EAD. Wasting $20K and 2 years for a completely useless masters degree.

3. Have a clear and simple path to green-card for H1Bs.
Why Data Science Is Importnat for Digital Selling
That wouldn't really be a proper salt, although technically it would fulfil the purpose of a salt, which is to prevent lookup tables being used.
I find intolerance in general mystifying. Inconvenience is inescapable. From my earliest age as a toddler, I was never bothered by cigarette smoke; in fact it was pleasant to me to breathe it in, and this used to give people some amusement. I myself have however never smoked a single cigarette. Now OTOH, I have always found even a whiff of perfume to be repellent and literally sickening. But I would never dream of trying to regulate either one.
High Times and Low Tides at Reefer Beach
SHA1 is not necessarily weaker. They might have used many rounds of hashing, which could have made them even stronger.
Family Law Attorney Tampa
LSD is illegal because of 60's era moral panic, plus the drug companies trying to divert attention away from the harm that amphetamines were causing.
That should be soluble though. E.g. standardized smartcards that cellphones and terminals know how to communicate with.
SSL client certificates. If only the browser UX for them didn't suck.
Encrypt the files before adding to IPFS and then decrypt after receiving them. Support for encryption will be built-in into IPFS in the future but for now, this solution works. There is a issue tracking this here: https://github.com/ipfs/faq/issues/6

Also, when adding files yourself, those files become pinned by the default. Getting files won't pin automatically however. You have some more information about pinning here: https://github.com/ipfs/examples/tree/master/examples/pinnin...
Most alcoholic drinks are extremely acquired tastes. Try finding people who haven't drunk much alcohol before adulthood and give them tastes of a selection of beers and wines, and I'd be willing to bet that most would find most of them disgusting.

I'm 41, and I still haven't acquired a taste for beer. I find it absolutely awful. I can tolerate most wines, but outside of extremely sweet dessert wines I have never tasted any that actually taste particularly enjoyable to me. I'm sure I could change that if I forced myself to drink more, but I don't really have any incentive to do so.

There are liquors that taste nice to me, but they are generally the ones that hide the alcohol taste quite well, like e.g. amaretto.

I'm sure taste is an element of it, but the point being that very few alcoholic drinks taste nice until you've spent a lot of time getting accustomed to the taste of alcohol without enjoying the taste first due to social expectations or a desire to get drunk.
India could be a tax issue.

As a tech sector APAC manager I have been instructed more than once not to visit. Not for any internal conference, and definitely not for any customer contact, and to take verifiable steps to avoid making "management decisions" if visiting for a holiday. Typical quote, "You do not want to be the guy that triggered tax obligations for us in India".

IANAL but I believe it's due to the broad framing of India's "place of effective management" rules.

This sort of thing ends up being mostly to Singapore's benefit, transnationals won't place their APAC region office in India as a result.
Just imagine what would've happened to the Internet, if governments of the world knew then what they know now about it.

"Porn? Anyone can just say anything they want "without repercussions"? Propaganda by other governments? Communicating without being able to intercept them like we do through the phone lines? My god, what an awful thing this Internet is! We better lock it down tight!"

I think it would've been worse than what Chinese government did to it in its own country. Perhaps something more along the lines of Zuckerberg's "charitable" Internet.org/Free Basics service.

That's why I never supported Free Basics. Can you imagine what it would've done to a country like Uganda or somewhere where people have no idea what the real Internet is? They would've grown up knowing only 100 (or perhaps 1,000 eventually) websites that are fully curated by both Facebook and the local governments. Nothing else would be allowed.

These tight regulations on Bitcoin and other similar technologies will definitely limit their potential, in ways we may not even understand yet, if that experimentation that was supposed to happen, never does.
Amazon seem to be coming up with something new everyday!
I am not sure what that means. Politicians can suppress wages ? When have they done it in past ? Isn't the overwhelming support for illegal immigrants in USA from democratic party similar to what you are talking ? Why is that there is such a massive support for illegal mexicans but not for legally immigrating highly educated Indian and Chinese ?
Orkney Islands – “Egypt of the North”
Consumers in London welcome EU Apple tax ruling
You forgot the Philippines.
President Duterte has summarily executed nearly 2,000 suspected drug dealers and users since July 1st and vowed to execute 98,000 more.

http://time.com/4462352/rodrigo-duterte-drug-war-drugs-phili...
Just curious, pro or against guns?

I suppose against, meaning you want a candidat who wants tight regulation?
There have been some articles about automatic KeePass updates being vulnerable. This section clarifies the situation and its resolution.

First of all, we would like to note that KeePass cannot update itself. KeePass does support checking for updates (optional; by downloading a version information file, comparing the available with the installed version number, and displaying a notification if necessary). However, it neither downloads nor installs any new version automatically. Users have to do this manually.

KeePass can be downloaded from many servers (SourceForge with its many mirror servers, FossHub, etc.). In order to make sure that the downloaded file is official, users should check whether the file is digitally signed (Authenticode; all KeePass binaries are signed, including the installer, KeePass.exe and all other EXE and DLL files). The digital signature can be checked using Windows Explorer by right-clicking the file -> 'Properties' -> tab 'Digital Signatures' (the expected signer name is 'Open Source Developer, Dominik Reichl'). When running the installer, the UAC dialog displays the digital signature information, i.e. users who carefully read the UAC dialog do not have to inspect the file properties separately. This is recommended for all users, independent of where you download KeePass from.

The KeePass website links to SourceForge for downloading KeePass. However, even if SourceForge (or the KeePass website) is compromised and serves a malicious download, users who check the digital signature will notice the attack and will not run the malware. Note that HTTPS cannot prevent an attack via a compromise of the download server; checking the digital signature does.

The version information file is downloaded from the KeePass website over HTTP. Thus a man in the middle (someone who can intercept your connection to the KeePass website) could have returned an incorrect version information file, possibly making KeePass display a notification that a new KeePass version is available. However, the next steps (downloading and installing the new version) must be carried out by the user manually, and here users who check the digital signature will notice the attack.

Resolution. In order to prevent a man in the middle from making KeePass display incorrect version information (even though this does not imply a successful attack, see above), the version information file is now digitally signed (using RSA-4096 and SHA-512). KeePass 2.34 and higher only accept such a digitally signed version information file. Furthermore, the version information file is now downloaded over HTTPS.

http://keepass.info/help/kb/sec_issues.html#updsig
“The design of C++” – lecture by Bjarne Stroustrup
http://keepass.info/help/kb/sec_issues.html#updsig

There have been some articles about automatic KeePass updates being vulnerable. This section clarifies the situation and its resolution.

First of all, we would like to note that KeePass cannot update itself. KeePass does support checking for updates (optional; by downloading a version information file, comparing the available with the installed version number, and displaying a notification if necessary). However, it neither downloads nor installs any new version automatically. Users have to do this manually.

KeePass can be downloaded from many servers (SourceForge with its many mirror servers, FossHub, etc.). In order to make sure that the downloaded file is official, users should check whether the file is digitally signed (Authenticode; all KeePass binaries are signed, including the installer, KeePass.exe and all other EXE and DLL files). The digital signature can be checked using Windows Explorer by right-clicking the file -> 'Properties' -> tab 'Digital Signatures' (the expected signer name is 'Open Source Developer, Dominik Reichl'). When running the installer, the UAC dialog displays the digital signature information, i.e. users who carefully read the UAC dialog do not have to inspect the file properties separately. This is recommended for all users, independent of where you download KeePass from.

The KeePass website links to SourceForge for downloading KeePass. However, even if SourceForge (or the KeePass website) is compromised and serves a malicious download, users who check the digital signature will notice the attack and will not run the malware. Note that HTTPS cannot prevent an attack via a compromise of the download server; checking the digital signature does.

The version information file is downloaded from the KeePass website over HTTP. Thus a man in the middle (someone who can intercept your connection to the KeePass website) could have returned an incorrect version information file, possibly making KeePass display a notification that a new KeePass version is available. However, the next steps (downloading and installing the new version) must be carried out by the user manually, and here users who check the digital signature will notice the attack.

Resolution. In order to prevent a man in the middle from making KeePass display incorrect version information (even though this does not imply a successful attack, see above), the version information file is now digitally signed (using RSA-4096 and SHA-512). KeePass 2.34 and higher only accept such a digitally signed version information file. Furthermore, the version information file is now downloaded over HTTPS.
As a service provider there is something you can do about it: Use well known out-of-band 2FA specs such as TOTP. Those are compatible with Google Authenticator and don't require a phone number, which is a massive inconvenience (not always available, not available in every country, SMS not reliable, requires an ID, not free, leaks personal information to the service provider, ...)
Ah, good to know. Still, you end up having to develop your own ACL system if you have multiple users (eg. family). Especially, shared directories are tricky.
I fondly remember from my childhood the smell of wood smoke from fireplaces, and leaves being burned in piles in people's yards. Namby-pambyism has not yet stopped all burning in my town, and I occasionally get reminders of those days.

The spice of life is like spice in food.
Google don't quite directly support this, but the multi-user support and account switching are actually quite good and robust. My understanding is that multiple accounts have effectively no correspondence -- your individual accounts do not trust one another, which makes a lot of sense.

You still don't transparently switch modes in different spaces, but you can supply that.

The "change my ID by space" model, along with a non-advertising revenue plan, is Imzy. Actually, they take this one step further, in that you can opt to be anonymous (with a freshly-created, random username) in any given post (if allowed within the community). That and some other features are interesting.

The actual experience leaves a great deal to be desired, in my experience. On-demand anonymity like that does lead to a huge potential for abuse, and requires very active moderation. I found myself the subject of unceasing attacks in a thread in which the Imzy CEO and community manager were each prresent, and where the latter denied that there was a problem. One of the community leads finally came in and locked the thread -- a mail glitch had dumped all alerts to her spam folder, and activity in that profile is usually far less than what had appeared (the post is over 60% of all comments to date, over the past several months).

https://www.reddit.com/r/dredmorbius/comments/500ysb/the_imz...
Do you deal with any situations where public/private keys are used instead of passwords?
Snapchat Launches on Demand Filters
No wonder they have such high resale value! I dream of driving a Tesla :)
And yet, even if all of those hadn't occurred, do you really think it likely people would switch en-mass? What would be the benefit? Circles? What is the major pain point of Facebook that another social network would solve so convincingly to cause their users to bear the costs of switching?

That have been dozens of other networks launched besides G+, none of them have garnered significant traction. Only mobile chat products that utilize phone numbers and contacts to build a network have really made a dent.

The vast majority of users of G+ never experienced blocking, didn't care about nymwars, etc. These are edge-user complaints. It causes distress in early adopters and the technorati but is meaningless to most people.

If you look at WhatsApp and Instagram, it turns out the majority of Facebook's users didn't care about 90% of their features. They just want to share photos and sent short messages.

My point is, those who are deeply about these things focus on edge case features that make a ton of difference to them, but are invisible to most people. Hell, I've rarely used Facebook search to search for anything other than a Contact. I suspect most people don't use the Search feature much, or lists, or groups, and all of the other dials and knobs.

Much of the world's communications by average people now runs on WhatsApp, iMessenger, WeChat, LINE, etc, because the use case for most people is not to be a public persona with a subscriber base, to conduct arguments and discussions with them.
> You've never seen people permanently harmed by bad things written about them online?

I certainly have, but the harm seems to have little to do with whether the allegations are actually true.
Ah, are they going to make a minifier based on Bublé (https://buble.surge.sh/), too? Perhaps they could call it Bublili.
Are you Eric, formerly of QSC?
I think this quote is complete bunk. It comes from here: http://harpers.org/archive/2016/04/legalize-it-all/

This is Dan Baum recalling a conversation with a dead Ehrlichmann after he got out of prison, 20 years after he served with Nixon. Dan puts quotes around this passage but I don't believe for a second that that is what Ehrlichmann said. And Ehrlichmann died 17 years ago, so he's not around to defend himself.
> Inconvenience is inescapable.

So let's not add to it.

> But I would never dream of trying to regulate either one.

You will most likely feel different if you or your loved ones ever suffer from the effects of second hand smoking.
Oh I agree, but I've seen too many "clever" systems which derive the salt from something like the username or another field or fields in the DB.

Just because there is no obvious salt now doesn't mean it's not there. Only Dropbox knows how it worked at this point.
"it's simply easier to manage a workforce who rolls into the office and is locally present, though yes, remote (or occasional from-home) management is possible."

As an employee with years of experience working remotely and employer myself now I disagree.

In my opinion it is easier to manage people remotely now, at least in the areas I work(IT). You can focus on the output someone produces without the interference of distractions.

As an example if someone goes and checks early in the morning in the Office, goes home late, it can distract employer opinion on this person being a great value to the company, while in reality her productivity is low.

Another example is having someone that talks a lot(extroverts)(high profile people). People that talk little externally look as they do not exist, but on jobs like programming they can run circles around the extroverts.

While you do remote work you don't care someone spends all day having sex in her house(good for them) if it provides great value for the company, value that is very easy to measure, as the only thing you get is the output work you get from your workers.

Do you like to work at 3 o'clock in the morning? I don't care. You are in pajamas in your house? I don't care. You like tattoos? I don't care. Do you have children? I don't care.

Are you productive? I care.

The main problem with remote working is that is it rare and we don't have all the experience of recent century of factories and offices history to learn from. But if you go even farther in time you will realize working from home was the normal thing to do before industrialization.