skysight-inc/HackerNews huggingface dataset:
No, I mean bcrypt.

Scrypt is better than bcrypt, but mostly not in ways that make much of a difference in 2017.

PBKDF2 comes close to being materially worse than bcrypt and scrypt, because it's especially straightforward on modern hardware, but even PBKDF2 is fine.

For the most part, as long as you're using anything with a KDF-like design for your password hash, a compromise of your password database is going to reveal the very terrible passwords and only those passwords; the rest will be too costly to crack.

Right now given the choice I'd use scrypt and go slightly out of my way to get it (if there was a good 3rd party library for it and bcrypt was in the standard library and I was like a "yarn add" away from having it, I'd take that step), but I would not convert a bcrypt site to scrypt.
Agreed. It’s easy to see how the psychoactive effect of alcohol (or coffee) can build a positive association with any bitter or poison taste over time. The brain is very easy to trick. Bundle an endorphin release with any other stimulation repeatedly, and you will grow to love that sensation, as sure as Pavlov’s Dog drools at a bell.

The only blocker is closed mindedness.
She Does Digital: Free resources for learning to code
Nobody uses rainbow tables or cares to mitigate them. People care that GPU rigs get hundreds of billions of hashes-per-second[1] against a single-iteration salted hash. So all 8-char case-sensitive alphanumeric combinations can be checked in 18 minutes[2].

1 - https://gist.github.com/epixoip/a83d38f412b4737e99bbef804a27...

2 - (pow(26+26+10, 8) / 2*pow(10, 11)) / 60
> But don't you ever wonder why after 14 billion years and with a hundred million star systems in the Milky Way, we still haven't heard a peep from anyone out there?

I'd say it's unlikely to be AI, just because the AI could wipe us out and then go on to eat the universe. It's not a valid Great Filter candidate.
You are right, I suppose because we don't trade gold much, it doesn't make sense to ensure that it's secure when we transfer it. We transfer it so infrequently, there's nothing to worry about...

For the opt-in replay protection, that is a proposal which requires people to update their software to protect themselves. That's unacceptable, many people are unlikely to even know that a fork happened. Replay protection needs to be automatic for un-upgraded nodes.
I've seen this a bunch of times on hn.

Each time I read a little more and notice/learn something new.

I'll be the first to point out his flaws, but goddam Steve Jobs was a smart guy. It amazes how much he knew exactly what he was doing.
Chip Makers Are Adding ‘Brains’ Alongside Cameras’ Eyes
I have (sadly) taken this step.

I'm also saddened that a transition with such a large change in functionality for end users didn't warrant syncing up with a Long Term Support version.

There's going to be a bit of a waiting game to see which extensions get ported and with what percentage of their original functionality retained.

Then it will be decision time.
It's mostly about clicks now! If they think your story or your PI's name will drive traffic then it gets accepted.

There are still a few very well done top notch paper that gets there, and some other half-backed but very creative which have some merit to be there. But even these have the "driving ads" as their first criteria.
K-Means Clustering Tutorial in Python from Scratch
Does your KeePassX recommendation include the Windows equivalent it was ported from (KeePass)?
Everything used to be open and relatively well-defined on the platform, unless my memory is colored rosey: BIOS, MBR, HDD, etc. Generally, it still is beginning with BIOS (AFAIK, you can usually disable UEFI).

But 'pre-BIOS' vendors have created a mostly proprietary, closed hodge-podge of hardware and software. I've been trying to merely identify those components and subsystems on a new computer and it's taking many hours and information is sparse. There's TPM, PTT, ME, TXT, Boot Guard, AMT, etc. etc.

All seem to serve one or more of three purposes: 1) Manageability (for corporate IT), 2) end-user control via a Root of Trust (practical only for corporate IT for the most part), and 3) Vendor control (DRM and more) via a root of trust and closed, undocumented, obscure systems.

Is there any guide to all this? Any standardization? There were and are multiple BIOS vendors, but generally I knew what a BIOS did and does.
I think a lot of these comments are directed at Xcode and tooling, not Swift specifically. This is unfortunately just the trend with where we are at with new desktop mac software, hopefully High Sierra's focus on improvements over features will be a turning point, Xcode 9 does seem to be on the right track.

When I was out of the office this week, two server side java developers helped a Swift junior step through some code - they both were really surprised and impressed at just how approachable Swift is. As well, I notice daily how few runtime errors and issues we have with Swift code-bases comparatively.

I think a lot of these comments are straw-manning the language. Yeah, people don't like being beta testers, or using immature and changing software vs very mature and stable software - that's not comparing two languages themselves though.
Over 150 People Tried to Draw 10 Famous Logos from Memory
Ask HN: What is the current state of mobile development using Golang?
DNA from old skeleton suggests humanity’s been here longer than we thought
Interestingly, they do match recreational amounts pretty closely.
I think it’s unfair to discounts papers in a foreign field to one’s own as ‘minimum publishable unit’ - often the novelty and importance of a finding requires some background, which the new, longer narrative abstracts in Science are trying to provide.
With estimates of a majority of hash power being from Chinese miners, I wonder how the recent change in attitude by the Chinese government will affect the outcome of this battle.

I haven't been keeping up lately, but I would guess that whichever camp the Chinese miners were in is going to lose, since Chinese mining itself may be headed for rapid decline.
For all the maturing "UX design" has done over the years, using a computer still feels mostly like swimming in garbage. Sure, now it's pretty brand-name garbage. But I'd hardly call that an improvement.
We've had "Johnny cabs" for decades now in science fiction. People are clear on the concept. Once they work cleanly, smoothly, safely, I predict really driverless cabs will become the norm in half a decade. They need to look, feel, and be safe is all. Cabs don't have to handle all terrain; they can be constrained to known, plotted streets.
You would totally see this in the code I've been writing. I've been taking advantage of enums with associated values for things like state machines. Usually, you'll see associated values like this in a switch statement, but if you need to handle a specific case, then you'll see the `if case`.
You're not doing yourself any favours by quoting Rationalwiki on that subject. The guy who wrote that article appears to have an axe to grind with the AI risk movement in general, and Eliezer Yudkowsky in particular; as a result, it's full of misleading statements and outright lies.

Try this one instead, for a less biased take on it: https://wiki.lesswrong.com/wiki/Roko's_basilisk
My first e-mail, given to me by my school when free email accounts were not a thing yet, is from 1996 and I still use it.
I'm curious... Is this driven by management, or developers who want to learn Swift?
If it has any use at all, then it'd have to be something like that.

GP's choice of link is extremely unfortunate, given that rationalwiki has a vendetta going against the AI risk movement in general. I would recommend https://wiki.lesswrong.com/wiki/Roko's_basilisk instead.
Not just self-interact, but self-interact strongly. Photons can self-interact too, through intermediate charged particles, but do so much less often.
Pension funds will not even consider Bitcoin until it becomes much more stable. Pensions are an obligation and therefore demand much lower risk -- if a 5% change in value in a single day is not considered newsworthy there is no way pensions will make that investment.

What makes you think the end cannot come before pensions and mutual funds start investing? What if panic selling triggers a deep loss in value, which then triggers miners to shut down as the mining reward falls below the energy cost; if enough miners shut down, someone could pull off a double-spending attack, and when people see that it will further reduce their confidence in the system. The result could be that confidence in Bitcoin never recovers.

Or Bitcoin could just be a fad that slows unwinds and fades away, and twenty years from now we'll all be laughing about it over drinks. I can think of a few other technologies that were "definitely going to take over" and are barely remembered today...
The other question is, if LTC ever becomes as relevant as BTC is in the marketplace (BTC has 30x marketcap), could Charlie still retain enough power to continue to be the guiding hand?

Gavin Andresen was that force in Bitcoin for years, as lead developer and chief evangelist, but now he plays a minor role; recently with big $$ in play and the big community split, not to mention the insane personal attacks, it is much harder to maintain influence.
Swift is the exact opposite of Javascript and if used correctly created much higher quality code than a Objective C. But the toolchain is weak and XCode 9 is a big step backwards.
what RFC describes that standard?
Would a valid cyber attack be to infect someone's machine, get these videos to play with logs that they played, and then report the person? Seems like the kind of thing that can be done relatively easily at mass scale...
I had three emails from HIBP today, for 3 different breaches: Disqus, Kickstarter and Bitly. Three, in a day. These breaches are all years old and at least one of them was set to one of my old passwords I reused in a lot of places (before moving to a pwd manager), so it could have done some real damage. The fact that it didn't happen, makes me think that salted hashing did what it was supposed to do, discouraging bruteforce decryption just enough.

Still, the state of the industry is pretty shocking. We are doing more and more stuff (super-encryption at rest, constant password rotation, password managers etc) and still breaches happen with regularity. It feels a bit like when Office started having a system to recover documents after a crash - yeah, great, but why is the crash happening so often that we need it in the first place?
> Marco Polo’s awestruck description of the palace of Kublai Kahn at Xanadu belongs to the same genre.

Uh, what? Do they mean Kubla Kahn, a poem about a fictional world by Samuel Taylor Coleridge, which came to him in an opium dream? When did Marco Polo come into it?
One may want to notify many website owners at once that it’s a good time to apply a patch in response to a security vulnerability affecting a technology they are using. Ex: WordPress, node.js, MongoDB, etc.
Haskell: Comparing Persistent with Ecto and ActiveRecord
Coincidentally, I just got my new XPS 13 today. Took it out of the box, booted it up, and was greeted by ... coil whine. Friggin coil whine. I knew this had plagued previous models of the XPS 13, but I figured Dell would have gotten their act together by now. Nope. It sounds like a bowl of Rice Krispies. A high pitched squealing sound comes out of the laptop anytime you launch a program or do anything that even remotely uses the processor. I tried booting into a USB to reinstall windows to see if that would help, and it got worse. The whole laptop would start to buzz whenever I touched the trackpad, and I starting hearing the most wonderful chirps and squeaks coming from underneath keyboard. Wonderful. I paid $1600 for what I thought was a premium laptop. Based on the OP's experience with Dell tech support, I don't even want to mess with trying to have it fixed. Nope, this piece of crap is getting returned, and I'm getting a Thinkpad.
Couldn’t you just get them to read a Wikipedia article? Send a shortened link?

Or say “I wonder what Islamic State’s policy objectives are?” to them, and wait for them to search?

In a way, it’s a little nastier than book burning — casual readers go in the fire too.
The point and click ones taught me english a lot, as the verbs and dialogs were in english as well, with no translations.
Well, common sense for one, but also https://www.ietf.org/rfc/rfc2142.txt section 4!
cf. RFC2142
That’s the biggest reason I don’t like Swift- it’s terrible syntax.

I hate let, var, func. I hate the backwards variable definitions. I hate the crazy punctionation symbols (dots, question marks).

I agree with a lot of what Smith says about Objective-C. But my biggest personal reason is the above. I find Objective-C beautiful and Swift ugly.
Norm recently did an interview with Caitlyn Jenner on his YouTube channel [1]. I found his candor and willingness to see humour in the situation was actually more respectful than the typical white-gloves approach, and it lead to some pretty interesting stories and answers to questions.

[1] https://www.youtube.com/watch?v=xuldL1m6FAs
my objections to obj C are code quality, pointers and crash rates.
(I am not an expert on anything.)

At this stage Sun was already selling networked workstations and trumpeting that "the network is the computer". DNS ramped up in 1985, while SMTP was already a few years active, and from a user's POV the good ole modern IPv4-on-Unix-machines Internet was already a reality if still not open to all comers. Speaking of Gibson, Neuromancer was already out, too. Basically Jobs was, for someone in his position—and for someone who iirc was in regular contact with Apple employee Alan Kay at this stage—more or less up to speed here, not really visionary. https://news.ycombinator.com/item?id=8317553

Speaking of Sun workstations though, remember that at the time of this 1985 interview Jobs was about four months from being fired from Apple. The Big Mac project he'd been pushing at the time looks very much like his attempt to do basically a NeXT—a networked Unix workstation with a new GUI layer and Mac/Apple fairy dust—inside Apple as the next Macintosh, and he founded NeXT by the end of the year in response to Gassée's termination of Big Mac after he (Jobs) left (basically in favour of the more incremental Macintosh II, it seems).
If looking at the mark they made worldwide, I feel the Hilux serie is even stronger than the Prius. Of course "the Hilux war" is a bit harder to use in a marketing campaign.
Previous discussion on Disqus 3rd party tracking:

https://news.ycombinator.com/item?id=14170041

https://news.ycombinator.com/item?id=15334207
Ugliness. That’s a primary reason too.

Difficult ness in a bad syntax. Also a primary reason.
If you're transacting with an exchange or a merchant and accidentally send both coins (as a result of a replay attack) instead of one, they're going to give it back. It's not nearly the disaster this article makes it out to be.

The only case where this is a problem are business to consumer transactions and p2p txs both of which you rarely do, if ever if you use BTC as a store of value.
i agree with all your points , but despite the superficial syntax similarity, Swift’s strong typing, optionals and slow compilation make it the anti-javascript.
"Friend of yours Bernaaard ?"
Well, except they explicitly call the non-sentient ones female (also stupid, and property), and the sentient ones are both referred to as male.
Kublai Khan, an emperor of the Mongol Empire in the 13th century.

https://en.wikipedia.org/wiki/Kublai_Khan
I learned vim by trying to learn Ruby/Rails(my first experience with programming). It got tedious to open files by looking them up in the Mac Os Finder. Then one day, someone showed me how to tell an application to open a file via the command line. I'm a noob.
Vim found its way into my workflow, and I haven't looked back.
There are now fewer black women in tech than there were 10 years ago
Does this mean I can finally train deep learning models on my laptop's Intel GPU?
It is though...

He's not arguing that stars shouldn't exist; he's arguing that funding decisions should be less influenced by "star power" and there are policy tweaks that could help achieve that.

It's worth noting that at the NIH (etc), you don't really know who "the allocators" are. Program managers make the final funding decisions, but they rely heavily on peer review and you don't know who in the study section will be reviewing your proposal. Changing this so they don't know the proposer's identities either might help.
Not close to true. Swift apps are only slightly larger, and no one cares how big your apps code is when media is 90% of most commercial apps sizes.
I'm afraid you read "what should we do" in much more general sense than the original author. I think that algorithm answers a narrower question of "what should we do to optimize monetary resource allocation", and it only answers within the boundaries you set, for instance, trust and reputation play major roles.
Does anyone use AppCode? How does it stack up to Xcode for Swift development?
> two groups of people implement the same thing

The obvious problem with that is that dynamically typed languages are great for prototyping things ... and implementing something quickly for a study sounds like prototyping.

But statically typed languages really shine for maintenance and refactoring.
publicly-funded grants
Question: why do we still use sequential ID's for identifying objects in data stores? There are many known problems with using numeric ID's (anyone remember Twitter's overflow issue), so when they are sent to a remote system, they should probably be strings anyways. Sorting or doing math on ID's is basically useless. Memory savings are the only thing I can think of, and while yes that's a nice feature, when a cluster of N nodes is generating ID's that are supposed to be globally unique, aren't UUID-type things better?
Your DNA is like a datacenter with a billion nodes that all start out with the same content in DRAM. Although error correction can compensate for most bit flips, at this scale you still get a really low mean time between failures, leading to differing memory contents over time.
> The surfing activities of those users who receive a Firefox version with Cliqz are sent to the Cliqz servers; including the URLs of the pages they visit.

Yeah thanks but no thanks.
It's just getting used to []][[][]] and having brackets and @property and lots of things a little different that most first languages people learn nowadays. If you're coming from C, then moving to Objective-C might feel different than coming from languages people tend to learn first nowadays. As someone coming from C++ (and others) when I started programming 4ish years ago, it definitely felt unnatural, but learned to appreciated it a lot and found it pretty sensible. Except for blocks...

It has made me really want to look into learning Smalltalk as a throwback hobby.
It is unusual. The article outright quotes an expert on that.
tl;dr can someone summarize for non-German readers?

Why?
The proton is something like 100000 times smaller than the orbit of the electron. Both are not usual object, so there are a lot of technical details about how you define the size of each one, but the proton is definitively much smaller than the hydrogen atom.

The electron is inside the proton only a tiny amount of time [1] but it's enough to measure it.

[1] A better explanation should use probabilities and wave functions, but the main idea is that.
Well, it's certainly not me, but I was curious and did some digging. I part of the benefit is (shocker) that they're close to the equator and don't have the same shift in hours of day and night that occur with the seasons as other latitudes do.
Yeah, FOUR different cities "rather than being concentrated". So no, Luxembourg is not "the" capital city of the EU, it's one among a number of institutional seats (a number that is expanding, btw; anything that is not set in treaties is being pushed elsewhere).
I wish I could participate, but the UI seems broken https://imgur.com/gallery/5yJxs
Numbers going off the screen, and over other text.

Edit: it seems to work fine on iPhone but not iPad.
It's also the engineer's job to make rent and pay their health insurance despite unreasonable demands. But apparently the only part of this labor issue we want to discuss is the nobility of sacrifice.
A larger team benefits more from the ability to write higher quality code with Swift. Fewer or no crashes is s better customer benefit than some hypothetical minor performance benefit. The toolchain does suck though, if Apple (or done one else) fixes the toolchain Objective C is done as a viable language.
I think this is true. He was a master at removing things to get the essential core, but sometimes it felt over-remorselessly. the one-button thing. A good example of cheap and works: I'm told the floppy disk controller on the apple II or III was a finite state machine implemented by gate logic and two PROM memories. I used a lisa in its year of release and the difference between a lisa and what emerged as that generation of mac was pretty high, but the core? much the same. Appletalk on twisted pair? no addresses but zeroconf: every device named itself. That was smart.
I don't think many people (even graduate students and postdocs) realize how much money universities suck in with grants. For every RO1 a professor gets, the university gets to add a substantial (typically greater than 50%) indirect costs. The PIs don't care because their budget is the same, but what it means is that there are fewer grants being handed out. Then the PIs somtimes pay for the "training" that graduate students and postdocs get using their own funds. For a top university, this can be 50K/year.
An interesting thought, but there's some other factors at play. Navigating through views typically proceeds from left to right, which is why the back button is on the left side. I suppose you could change the direction of the animations, too. That seems unnatural in the context of a left-to-right language though.
What precludes you from including a comment with a link to the signed version of the file with ".asc" appended to the filename?
wonder how would that impact google fi? if it would mean adding a new carrier like verizon or att, I am in.
The article talks about something I'm curious about: which hand you hold your phone with and which hand you tap with.

I'm more or less right-handed - fairly ambidextrous for many things - but I write with my right hand.

I always hold a phone or similar device with my left hand and tap on it with my right hand, like the middle example in the three illustrations on the blue background midway through the article (the one that it says 36% of users do it this way).

It never once occurred to me to hold a phone with my right hand and tap on it with my right thumb, like the leftmost illustration in that image (49% of users).

If I do tap with my thumb, I still have the phone in my left hand and use my left thumb.

I think this comes from my earlier days with pads of paper and a pen or pencil. I wanted to write with my right hand, so naturally I held the pad in my left hand and the pen in my right hand.

Of course I've always assumed everyone does it this way: hold the device in your non-dominant hand and tap on it (or write/draw on it with a stylus) with the dominant hand.

It's a total surprise to me that people would actually hold a phone or device with their dominant hand. I guess it makes sense if you're always using it in a one-handed manner, but for me it is just something that never even came to mind as something to try. Since I'm holding it in my left hand anyway, if I do use a thumb it will be my left thumb.

Not saying one way or the other is right or wrong, of course. I wonder if this is one of those things where people fall into one of two (or more) groups, and don't even know the other groups exist?
Restart XCode 9 every 2 hours. SourceKitService is eating up your available memory.