skysight-inc/HackerNews huggingface dataset:
You can stuff ballot boxes, that's where the term comes from. Nothing is "hack-proof."

I think it's funny that people are freaking out on HN about this. The hacks at Defcon all took a long time to do, and I believe all required keys to the machines, and all were done on older voting machines. There has been no evidence of people hacking machines during the elections. Stuffing ballot boxes and other forms of voting fraud have been around for a long time, and nothing we do is going to stop it 100%.

Also voting machines generally have paper copies that print off the back of the machine that are anonymized but can be matched if foul play is called into question, at least in my area. Couple that with monitors that stand near machines or walk around and I feel pretty comfortable with electronic voting.

The only plausible hack would be an inside job, but I too find this difficult to believe. It would takes tons and tons of people to hack the machines if it required physical access. You'd have to hack ever machine, and even when you were done there are so many districts it would be nearly impossible to swing the election in any meaningful way.
Or build something like an Earthship (http://earthship.com/). I know that these can air condition a house in New Mexico through geothermal heat transfer, however no idea how they handle the more humid summers of the South East.
The most computerization I'm comfortable with for voting is having machines count paper ballots.
Plus if you sell on Amazon I bet you buy more too.
After getting hit by this yesterday and finding it not very easy to find which extension was affected I went through a big extension purge. Most of the extensions I had installed I never really ever used.
> When I'm asked to change my style, I am - quite literally - asked to deny a fundamental Truth of my being.

Ugh. Come on.

I used to indent with 4 spaces. I lead a team where in the early days I added linting and had to decide one rules. Some of these I felt fine about - semicolons, for instance. But others the team had a fairly unanimous feeling about, 2 spaces being one of them. So I set the linter to 2 spaces, and now that's what I use for everything. I like it.

If we didn't have linting to standardise this and other rules across the codebase, it'd be a mess. It's one thing to be able to identify who's written a thing, but it should be a subtlety in amongst consistency. Not a glaring stylistic mis-match.

https://github.com/prettier/prettier looks promising, on this topic.

Edit: a rebuttal https://news.ycombinator.com/item?id=14921580
A pepper is shared among all users of a site. That's what makes it different from a salt.

Or are you saying that the exact same hash was found in multiple separate database dumps? I didn't see any indication of that in the article.
I just tried it and looks like the GFW doesn't block it yet. Upload speed was surprisingly good too, much better than I ever get downloading foreign websites.
Hmm, I have to confess I was cribbing this example from a link above. I'll dive further on it and see where I got lost.

I am a bit fuddled on the claim that HTML5 was determined not to be an opt-in schema. I'm probably colored because most of my docs by when I was actually caring about this were using the xhtml doctype. So, for me it definitely was a sort of "opt-in" and a migration. Which, frankly, is logical and makes the most sense.

So, I grant that the "existing documents" problem presented a ton of not well formatted documents. But, a large chunk of existing code presents with excessive warnings. The solution there is not to just give up, but to come up with better tools and guide people to the higher quality paths.

In the end, I fully accept this as something I will just have to agree to disagree on. My assertion is that contortions to not raise the bar on the creation of documents did little to advance the state of the web. I do not have a clear path on how to test this assertion. And have since moved on from web development.
It's really sad that this is what Wikileaks has turned into.

Regardless of the authenticity of the information, they clearly only release information when it is politically beneficial for their(?) motives.
Are there dating apps based around other hobbies, or is it just religion?
Really? Empty promises? Here you go:

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

And he's about to pull it off again with Tesla. I guess we'll have to wait and see.
I find that on some sites if I click in the username field and alt tab to keepass or any other function I'm suddenly not in the txt field on the site... thus I can't trigger auto type at times.
Totally agree with this article. An Emperor-has-no-clothes situation which baffles me that more programmers don't see as obviously as I do is the following sequence of logic:

1. If the code format check can be automated, then the code format change can be automated.

2. If the code format change can be automated, then the change could be applied as you type, or as the code is loaded.

3. If the format change is applied as the file is loaded, it could just as easily be an editor view-setting, much like syntax highlighting or font size.

4. QED we're collectively wasting time on a lot of pointless B.S. that should just be a checkbox on the Tools... Options menu.

Or to put it another way: the fact that editor background colors, font, and text coloration are not part of plaintext files, but whitespace and line breaks are (and that plaintext files, as opposed to databases, are used to store program code) is an historical accident. One could easily imagine an alternative history in which things played out differently in terms of what is and is not a "view option" vs intrinsic to the source text.

For example, a lot of developers seem to like the white-on-black or "midnight" theme for their IDE; personally, I hate it, and prefer black text on paper-white background. I just thank goodness that that is an editor option, rather than that being encoded by the source file. If it were, maybe we'd have requirements like every source file needs to be on a black background, except for viewmodels which need to use a purple background, etc.

When I'm not forced to use a coding standard, I use line breaks, spacing, etc. to communicate whatever I think is important about a particular section of code, rather than following a prescribed format mechanically. Indeed, breaking style in a particular section can be used to show "hey, something different is happening here".

However, if people are going to get pedantic about style choices which have no effect on compiler parsing or output, I would gladly trade away this freedom of expression in return to gain freedom from code-formatting-busywork by making all of these formatting choices be part of the editor view options. Then if a busybody has an opinion about non-functional source formatting, let him change the settings on his own IDE.
"Reason is itself a matter of faith. It is an act of faith to assert that our thoughts have any relation to reality at all. " Maybe reading some Chesterton would help.
Even if they use open source software, what guarantee is there that version of the software deployed on the machines is the same as one people can inspect?
His examples are kind of strange.

First, I don't really consider const vs let to be the same kind of stylistic rule as single quotes vs. double quotes. Single quotes vs double quotes really don't matter too much. Const vs. let though don't mean the same thing at all, and using them correctly can go a long way to reducing cognitive load. The two keywords simply don't mean the same thing and if his linter is complaining often, it's probably because he doesn't understand the difference.

And if you can't standardize on tabs vs. spaces, you're going to have all sorts of trouble in your commits. This is basic stuff. This article reads like the author has spent his entire career working on individual projects, and doesn't really understand working with a team.
> as a pentester was that "storing passwords in plaintext" would be a low-severity finding

I suspect that's because you're viewing the situation as a pentester not a user. A plaintext password (on its own) doesn't do a pentester much good until they've already gained control of the system. However, once someone has control of the system then plaintext passwords are a threat to users because a lot of people are vulnerable to common password reuse.
But we should see something, somewhere…!

There must be at least one example of an all female company you can point to with clear advantage over mixed-gender competition if the pay gap is at all real, and certainly if it’s over 30% as claimed by, among others, president Obama.

Either the pay gap is too small to matter, or it simply does not exist. So far all evidence favors the latter.

This shouldn’t be surprising—after all wage discrimination has been illegal in United States for over 40 years.

The claim that there’s some widespread corruption, perhaps even a conspiracy, should be treated as any other extraordinary claim. With extraordinary skepticism.
> The Allied Powers had seemingly learned the lessons of Versailles and didn't try to punish the losers (well, not as much), instead letting them grow.

This was true for Germany but not for japan. Due to hard feelings over ww2 and of course racial animosity/hatred, our plan for japan was deindustrialization. We wanted japan to be at least a few decades behind the US and turn more of their nation into docile agrarian farmers. We also instituted starvation policy to thin out and subjugate the japanese. There was rampant starvation in japan in the first few years after ww2.

We had troops specifically assigned to destroy japanese industrial/engineering/science capacity. One of the most famous was the destruction of japan's cyclotron.

https://youtu.be/hJRxchhBbNQ

Keep in mind that we were an extremely racist nation 70 years ago and we had just nuked and firebombed japan into complete rubble. Whereas germans were "our white aryan brothers" ( it's absurd to think it now, but that's how the leaders of the US thought back then ) and we felt an obligation to rehabilitate them, the japanese were viewed as inferior asians with plenty of motive to attack the US again.

The only reason japan was allowed to reindustrialize was the soviet threat and the korean war. We needed japan to help seal off the soviets, chinese and north koreans.

It's fascinating stuff. If the communist threat didn't exist and the korean war never occurred, japan might be a more agrarian society today controlled by the US administrators.
HPE Has Constructed the Largest Single-Memory Computer System Ever Built
Wikileaks is a tool of the KGB. Why are we sharing their disinformation here?
Is it possible that perfect is the enemy of good here? You could choose a lower ratio of battery storage to average use and just use non-carbon neutral peaker plants for the few days in winter where there's a shortfall of renewable energy. Still a huge boost to renewable energy, still a huge reduction in carbon emissions.
I subscribe to weekly newsletters for languages I'm interested in learning, so right now that's how I find my Go, Rust, Ruby, and Elixir stuff.

HackerNews and the programming subreddits so far have done the trick for me.
It's quite easy to make them disappear or bulk fill them. Like bank notes, paper ballots can be counterfeited.

Canton of Geneva have open sourced their voting app. https://github.com/republique-et-canton-de-geneve/chvote-1-0

Of course there will never be a perfect way. However, I have a feeling that by multiplying voting methods, fraud impact can be contained. Mail vote increases the number of people voting and have the same positive effect (drowning a fraud in valid results).
Likely because it needs a IRC server to set up the handshake, and the exposure of IP addresses. Never mind that DCC and NAT don't mix well.
> So, for example, all users have to take a selfie via the app so their profile can be manually verified to help boost trust and keep out spammers; users don’t have to provide their real name though, and can choose not to display photos on their profiles or blur photos unless there’s an active match. Users are also asked to rate others they have interacted with — and these ratings are fed into the matching algorithm, with the aim of surfacing “quality users” and promoting positive behaviors.

All of this sounds like a big improvement on Tinder. I'm not Muslim, but I'd try a dating site that worked like this. They should open it up but allow users to restrict to the Muslim subset if they choose.
NPM Blog: `crossenv` malware on the npm registry
It is sensible to thing the care about what other people think. We live in a society - and there are norms, standards, and values associated with our community. We shouldn't want to be people who can ignore the genuine values of our community. In many ways, I'm just arguing for "love your neighbor" as extending to caring about the values of your community - even when you disagree with them.
The relevant lines:

> we are going to switch over Wayland by default on 17.10. The Xorg session will still be available alongside. This enables us to get some good set of feedback to be ready and make our final decision for our next LTS, 18.04.
Why Most Companies Fail at Moving Up or Down Market
Thanks, this worked well, though now I have to decide if I migrate the original app to Gorm as well...
The value linters should (hopefully) provide is to keep code reviews focussed on actually important things instead of having to renegotiate naming, spacing, and other "arbitrary" things. Also, a decent linter for JavaScript will detect some obviously buggy code.
They are closed, but not deleted.

And as a community, the community decided that they want to keep Stackoverflow for specific programming problems, not those that are opinion based.

It is unfortunate that your POV differs from what the general consensus of the community.
I agree and appreciate that, but I don't know that it's always true. The problem is that a lot of documentation and man pages out there just aren't written well. They bury the lede and make you dig around to figure out how to do that simple thing you want to do. Googling for something and immediately finding that specific question on SO even if you could go look it up in pages of docs is a time saver.

Edit: Or perhaps the library has poor usability. I've been doing python programming for 6 years now and know the standard library like the back of my hand, but if I have to do anything reasonably complex with datetime you can bet I'll probably just look for someone on SO that has had the same problem and crib the answer.
Yeah, I think you're closer, as long as you pronounce the own like owned rather than pow-n, as I read it at first.
What kind of electric car costs $8500? Used Leaf?
WeTransfer has been around a long time and is exactly the same.
In general, I don't really give a shit about style - I could care less about tabs vs spaces, semicolons vs ASI, etc.

I just want it to be consistent, readable, and not pollute my code reviews with superfluous changes.

So, I prettymuch only use style rules that can be enforced and corrected automatically (usually with `eslint . --fix`). Anything else is just annoying.

I'm also a huge fan of prettier and starting to use it everywhere - https://github.com/prettier/prettier
China holds drill to shut down 'harmful' websites
I think the details were pretty interesting, so let me expand your summary:

1. Someone gets permission to hack their friend
2. They find their email / phone number online
3. They lookup old password leaks for the email
3.1. They find their password hash (salted) in the Tumblr dump
3.2. Tumblr turned out to use the same hash for everybody, so the author
finds other accounts with the same hash, follows them to a LinkedIn
leak (unsalted), and successfully recovers the password
3.3. The password turns out not to work (changed some time ago)
4. They end up setting up a fake page to phish their friend
4.1. First phishing attempt produces... the old password that is already
known through point 3.
4.2. Second attempt is modified to reject user input a few times, producing
another password, which happens to work
4.3. The victim grows suspicious of the phishing e-mails, but another
message puts those suspicions to rest
5. They wait until their friend falls asleep to reset the Twitter password and (later, in the same way) capture
their LinkedIn account
6. They photoshop their profile pictures to subtly include a Mario character, and they
make their friend follow a bunch of fake Mario accounts on Twitter
6.1. When that doesn't get noticed, they redo the trick in a much less subtle way
7. Friend notices, they meetup to swap stories (the friend doesn't follow the fake Mario accounts)
The excitement wasn't all the universal. I remember we advertised our CMS as "100% Java- and JavaScript-free" ;-)
Use paper voting, or if you want everyone to have easier access use mail-in paper voting.
Yes, I understand the reason for keeping a slow legacy option available.

Even in your situation, if you're doing this for work and IT calls you up, you just tell them what you're doing. "I'm downloading a very large file over Bittorrent because it's 50% faster than the HTTP download and I'd like to do some work today. Is that all? Thanks. Bye."

In some places you'd get that call from IT just for downloading a large file. Getting a call doesn't mean you're doing something wrong, they're just checking it's you, not malware, and that it's for work. If they haven't already blocked it, have at it.
WeTransfer does auto delete after 7 days I believe and on the plus plan you can do things like password protect links.
Or, for those who are versed in IPA: /pɔ̃.tʂki/.

* There is no individually-pronounced "n" sound; it is built entirely into the nasalized vowel.

* The /ʂ/ sound is actually a laminal retroflex. This is best described as making a "sh" sound, but with the blade of the tongue.
The point is that paper ballots are harder to tamper with. To the point that at scale it becomes impossible to rig an election in the vast majority of cases.

Some things don't need a technological solution. Pen and paper and thumb dye generally work just fine.
We can send files all day long between computers. It's the political layer that's unsolved: privacy, identity, trust, and authorization.
>[+] One of my first conversations with a boss at a traditionally managed Japanese company involved my expected timeline to get married and what the company's role in that process would be; my boss assumed that it would be sourcing the bride.

This was the example I was thinking of when reading the first part of your message. I'm glad you said it because I feared it would've been seen as an exaggeration if I added it as an example I've heard of.

So to anyone who is reading about this and doesn't trust a single anonymous source, let this second anonymous source add on that I've read about the same behavior, and even more disturbing behavior happening to unmarried female employees (where do you think they source the brides from?).

That said, I've heard about these cases at a few companies. I do not have sufficient evidence to generalize beyond that, only to point out that it does happen (and is tolerated by the legal system, no chance of that in the US), not the rate at which it happens nor if it is a fair generalization of Japanese companies in general.
In Michigan people will unabashedly say poonchkee. I've stopped arguing about it with people :).
Duplicate of https://news.ycombinator.com/item?id=14919845
Our selection process is as follows: "Does your daddy have money?"
On that point, Superforecasting by Tetlock is an excellent book on softer analysis, which will make perfect sense to quant readers.
Transitioning entirely to neural machine translation
That's how isolation is implemented. MVCC is not compatible with any standard SQL level, but it is used for the lower ones.
At some level most things cannot be consistently proven though -- mathematics is premised in axioms that are not complete and consistent insofar as they cannot be proven by the systems of mathematics. They have to be taken as true, however, for the remaining systems of mathematics to be consistent. See Godel's Incompleteness Theorems: https://en.m.wikipedia.org/wiki/Gödel%27s_incompleteness_the...

The larger point is that derogatory comments about belief systems only point to the speakers subjective inability to comprehend said system, nothing objective about the system itself.
Pretty much.

The world got paranoid, as any exposed port to the raw net is seen as an invite to worms.
Surely this is going to be incredibly expensive in the long-run for Mozilla? I can't quite get what their play is with this service.
If you were sending a 3 file to 3 people, just use WeTransfer
Came here to recommend that.

Instead, use open source hardware. Use pen and paper!

:-)
Or better a cookoo filter:

http://dl.acm.org/citation.cfm?doid=2674005.2674994
North America was devoid of human/hominid life when the Bering Strait migration occurred.
Every Synology NAS has sharing features built-in, and the software is pretty nice on both web and mobile.
> impossible to build hack-proof voting terminals.

Suppose they do build a hack-proof voting terminal - how can you tell that's what you're voting on, and not a compromised machine with identical appearance? De-cap all the chips and put them under an electron-microscope?
I was hoping he was being sarcastic. Oh boy. Impressive technical achievement though.
> You just have to know what a carry propagation bug is

This is one of the things that drives me nuts about the crypto community. The natural response upon reading, "You just have to know X" if you don't already know is to go search for X. Well, if you go search for "carry propagation bug" you will find lots of examples of carry propagation bugs being found and fixed, but no explanation of what one is. The thing that "you just have to know" is not so easy to find. The courteous thing to do when mentioning something that "you just have to know" but which is not easy to find is to provide a pointer or a short in-line explanation. When you don't do that you leave your reader with no choice but to publicly expose their ignorance of this purportedly crucial knowledge by asking, which I will now proceed to do as a public service: What the hell is a carry propagation bug? Where do you look for them? And what is their impact?

And while we're at it, what are "table stakes"?
Security through obscurity is a factor in physical security, but locks are really not an example of that. The construction of most locks is well documented, or easy to reverse engineer by buying an identical lock. The thing keeping a lock secure is the key, which is a regular secret just like any crypto key. Nobody would claim ssh does security by obscurity because anyone who knows my key can get into my server.
I don't believe there is anything in the in the religion that requires it and that interfaith unions are acceptable provided they are between Ahl al-Kitab("People of the Book) - Jews, Christian and Zoroastrians.
I doubt this is the case at least in the US. Polls are staffed locally by volunteers who are quite often members of the local community. Others can (and do) stay and witness the counting of votes when polls close. I think it would be pretty obvious if what got posted didn't line up with what you witnessed first hand just a few hours before, especially when you can walk down the street and ask your sister what she counted.