skysight-inc/HackerNews huggingface dataset:
Let me preface this by saying: I have the upmost respect for the Webflow developers and designers...they've created a highly-functional web app with the purpose of enabling creators...the process to make such a full-featured web-browser product with such a range of capability is astounding.

That said, I disagree with the implication that Webflow, and similar products, solve the problems of code, e.g., the phrase "Do xyz without writing a line of code". Knowledge of code does constrain non-developers, but in the end, that is not the hard part. To use a quick example: the mechanics of baking responsiveness into a new site from scratch is significantly easier than the conceptual process of "What information and features should be prominent, or excised, in the mobile view of our website?"...and in my opinion, that latter problem is something that people can get into without knowing how to write code.

So despite the technical strength of the Webflow product, I don't think that it makes things easier in the end. Instead of "code", a newbie has to learn a whole new interface, a whole new set of iconography/terms (used for buttons, subheads, etc.), and last but not least, a whole new set of quirks inherent to the Webflow program. And when they become experts at this, they have spent 50-90% of their cognitive ability mastering Webflow, and the remainder understanding the creative and technical process of web development.

At some point, isn't it just better to learn some code? Not 10 years worth, but something in between that and "0 lines of code". I've used Webflow, and I'll repeat again, it is an excellent web product in execution and design...but the problem it attempts to tackle is just too big, and the abstractions it offers may ended up hindering creators in the medium-to-long run.
Maybe I was not clear. I'm not forcing you to write a book, nor saying you absolutely should.

My point is that if people like you, who are definitely more knowledgable than most in this area (most is very important here), communicate their experience, then everyone benefits. If nobody wants to write about crypto because nobody feels qualified, we're at a dead end.

When a person does write content, someone somewhere will tear it apart, for pretty good reasons: getting it right is very difficult, as you say. But that's precisely the point: to learn from our mistakes. We're not dealing with raw science, but real life implementations of theory, and this is where things usually break, as shown by your critique. The value of the book is pedagogical, not necessarily scientific.

If you have anything to say about crypto (and you clearly do), then say it. We're all the better for it! And contributions like the ones you gave here are needed. I just find the general attitude a little tiring, I'm not trying to force you into writing :)

Lastly, the most important thing, to me, is that I, as a chemist, can get on the internet and learn about these concepts from someone who understands them better than I do. Having a discussion about such topics is essential. Your contribution might not be in the deep theorems of academic cryptography, but they sure are appreciated by others like me. So if you ever want to write a book/pamphlet, go ahead, I'll buy it.
[Podcast] Smart Content Marketing With Jay Baer of Convince and Convert
[Podcast] Help Not Hype: Smart Content Marketing With Jay Baer of Convince & Convert
There are probably open source projects who are in much greater need of $10,000 than Docker, which already has millions in funding.
Awesome! We love the DC startup scene, too!

Head over to dc.started.in/apply/ and we'll start the profile process. I look forward to speaking soon!
That outdated info and impossible to get inactive username anymore since 2011.
Where does it say this account was inactive? IF it says such a thing anywhere how long was it inactive?
Always open for suggestions and feedback. Hit the contact email link. Curious to hear your feedback.
Sorry, that's not accurate. Webflow sites can be exported at a click of a button, and you own all the code. You can host anywhere you want, make any custom changes, etc.
what is the github link?
He addresses your third point in the FAQ:

Why is there no “no warranty” clause?

The WTFPL is an all-purpose license and does not cover only computer programs; it can be used for artwork, documentation and so on. As such, it only covers copying, distribution and modification. If you want to add a no warranty clause for a program, you may use the following wording in your source code:

/* This program is free software. It comes without any warranty, to
* the extent permitted by applicable law. You can redistribute it
* and/or modify it under the terms of the Do What The Fuck You Want
* To Public License, Version 2, as published by Sam Hocevar. See
* http://www.wtfpl.net/ for more details. */

http://www.wtfpl.net/faq/
I understand. I'm making a distinction you don't care about, between books about designing crypto and books about breaking crypto. We're working on a book (it would be more accurate to say that I am cheerleading Sean and Alex on to write a book). It's just not a book that would teach developers how to build crypto.
How to Teach a Robot New Skills
The account was renamed.
Interesting. If true, this seems to contradict the statement released here: http://docs.openvpn.net/important-security-notice-regarding-...

Have you contacted OpenVPN directly?
You are very right about that. They were ACH transfers.
The biggest problem WP faces is retailers.

I don't know why, but I've overheard reps at Best Buy, Radio Shack, and Verizon answer people's Windows Phone questions with "You don't want that, it's crap".
If the time does have to be displayed then it should be
in UNIX epoch time as that is the most convenient for all
concerned.

Unix time isn't monotonic: leap seconds are added by double-spending: 915148800.00 occurred twice. This means it's ambiguous, that unix timestamp refers to two different points in time, one second apart.

http://en.wikipedia.org/wiki/Unix_time

TAI is used for atomic clocks, then converted to UTC or unix time for consumption by ordinary time consumers.
I feel as though this would be a good opportunity to remind people that choosing an Internet handle that has any connection to your public identity name is not necessarily a good idea. The potential name space for memorable, usable, easily-typed handles is much larger than the list in the baby names book, and there is value in avoiding collisions.

As my own public name is two of the most common first names and one of the most common last names in the Anglophone world, I am not altogether unfamiliar with the disutility in using a common name.

Aside from that, in the real world, we have a host of disambiguators available to tell the difference between two individuals with similar names. There is no particular reason why a site's user handle would need to be unique. The data store should probably be keying everything on a serial ID number anyway. Just as the DNS exists to associate names with IP numbers, a handle resolver could use disambiguators as needed to minimize disruption of the user experience due to non-uniqueness.

If you log in from a new device with a new IP address, you might be asked "Which 'kathleen' are you?" once, and get a small "I'm a different 'kathleen'" link thereafter. If you're a giant like Facebook, there is probably more utility in allowing people to have short, non-unique user handles with an on-demand disambiguation system than in a system required to enforce user handle uniqueness.
You're not actually contradicting his statement, you know. A good many of Blackberry's problems trace back to the company's owners.
we sure do. ping us through contact form with deets, will send beer!

Would love to hear any feedback you have.
Thanks, but we're actively avoiding publishers.
github pages =)
i know, you scared? wakes you up a little doesn't it? :)
It's fortunate that it was posted again as a topic, as I didn't see the original comment thread and wouldn't have read this review otherwise, and I learned things from it.
So you prefer a society that rewards winning the genetic lottery? I guess the others that lose can just serve the likes of you their entire life? What kind of talents do you suppose are from nature vs nurture?
Isnt dont use any license and dont put (c) more simple?
Only the higher Webflow plans have export. The cheapest plan doesn't let you export.
Speaking of Java crypto, I have a question. Is it possible a garbage collector might be dangerous to crypto code? I've seen it mentioned on HN that maybe we should be worried about implementing crypto code in a language with a non-deterministic GC, but sadly I can't find those comments right now.

TextSecure's crypto is implemented in Java, which is of course garbage collected. Some cursory Googling suggests that Java's GC will suspend the main execution thread during each GC op: http://javabook.compuware.com/content/memory/reduce-garbage-...

I'm guessing the concern is that an attacker might somehow discover a way to use the GC to recover sensitive info. It seems like having a GC might cause some other trouble, like making it hard to wipe sensitive data from memory once it's no longer needed: http://books.google.com/books?id=43pcI3in1DcC&pg=PA122&lpg=P...

Since TextSecure is currently believed to be secure and high-quality, then it must be true GCs aren't fundamentally dangerous to crypto code, right? (Or at least that Java's GC on Android isn't dangerous to crypto.) If a GC is dangerous to crypto code, then TextSecure would be vulnerable to those dangers.

Do you happen to know whether cryptographers as of 2014 generally believe GCs are/aren't/might be dangerous to crypto code? Are there any known attack vectors or proofs of concept? (It would be awesome if anyone could point out any whitepapers on the subject.)
Out of curiosity, how could it have been better?
It's probably worth a mention that (a) there were lots of flops in the early YC batches too, you've just forgotten them, and (b) it takes a few years for any startup to take off so of course earlier YC startups will seem more successful.
Read the article, not just the headline. ;)

"A few months ago while tagging my wife “at”Kathleen on Instagram I noticed her username was no longer displaying as “@kathleen”, but rather “_____kathleen”."
Computer simulations teaching themselves to walk
Ask HN: I forgot my HN password. How could I reset it?
"IRS begins new PR campaign to solicit donations from Silicon Valley for politicians on tax policy committees."
hit the contact link, shoot me a note, would love to hear your feedback.
Not interested in SaaS unless there is an offline version. I like to own my software not rent it.
They have. http://www.ablogtowatch.com/bathys-hawaii-cesium-133-atomic-...
I can vouch for UMBC. UMBC has a strong talent pool. Sadly, many CS grads end up working in cyber security in VA, MD or DC. Although, I do personally know a few who got jobs at Google and Zynga.

I do agree that startups in DC lack young people. I've tried to go to two hacker/startup meetups in DC. Both times, it sucked. These hackers/startups guys were too old for me. It just didn't click and I left.
I think that the concern crypto engineers have with garbage collected runtimes is held in tension by the equal and opposite force of their concern about memory corruption bugs in C. It's a concern, but an inchoate concern.
120mW, 3.3V? Totally doable as a wristwatch.

I guess this is sarcasm? Typical quartz wristwatch power consumption is closer to .01mW.

You could do it with a rechargeable battery, like a smartwatch, though you'd be recharging it every night, like your phone.
DevOps is really the traditional Unix admin role, however the operator role has now be renamed sysadmin in most companies.
I'm the founder and CEO of Webflow, and I can't agree enough with your statement that code is not the hard part. That's why we're trying to create tools for designers to help them focus on the hard parts (content, usability, etc).

I love what Bret Victor says about this in his Magic Ink paper [1]. Replace "information software" with "web applications" as you read it:

"I suggest that the design of information software should be approached initially and primarily as a graphic design project. The foremost concern should be appearance—what and how information is presented. The designer should ask: What is relevant information? What questions will the viewer ask? What situations will she want to compare? What decision is she trying to make? How can the data be presented most effectively? How can the visual vocabulary and techniques of graphic design be employed to direct the user’s eyes to the solution? The designer must start by considering what the software looks like, because the user is using it to learn, and she learns by looking at it."

The act of creating a solution IS the hard part, not tweaking CSS properties or knowing how to integrate Bootstrap components just right. All those things should just get out of the way and let creatives do the important work, without bogging down in the implementation details.

In case you're interested, I wrote a bit more about this on our blog a while ago: http://blog.webflow.com/designers-will-rule-the-web

[1] http://worrydream.com/MagicInk/
You must have stopped reading before "and told her about it"
Thanks for doing this, looks great, perfect timing for me to move my node-cron jobs out of my node app so I can have some separation of concern.

edit - yes please on support for more db choices
Automated functions, like storing money, transfers, (digital?) check processing, buying indices - all on explicit commands and with fees - even storing money - but dirt cheap.

After that we can talk about less clear-cut functions, like various kinds of investments or loan offerings.
This might help:

> I reviewed several SSL implementations for coding style: OpenSSL, NSS, GnuTLS, JSSE, Botan, MatrixSSL and PolarSSL. I looked at how buffers are handled in parsers and writers. Of all of them, I think only JSSE, i.e. pure Java, can be trusted to be free of buffer overflows. It suggests that a good webserver for security-critical applications would be Tomcat, without native extensions.

http://tstarling.com/blog/2014/04/ssl-implementations-compar...
The Terms of Service of every social media platform you've ever signed up for contain language that allows the service provider to "unilaterally revoke" your account at any time, for (nearly) any reason. There is no system of due process, because your rights are not being infringed in any way. You have no right to use a private service.

If you think this status quo is unacceptable, then don't use these proprietary web services. Take control of your web presence and your "interactions with the entire world." Support projects like Diaspora and Pump.io, and run your own instance of their federated platforms. Your username cannot be taken away when you are the service provider.
Cute, although if you promisify all your async primitives promises are throw safe and the Bluebird library makes this really easy.

I hope they're able to get to as fast as Bluebird performance , which is almost as fast as callbacks and faster than the async module.
Is dynamically-allocated memory considered documented state? How about temp files? Network connections to new peers? Consensus changes in the network? What defines documentation, or state?

When you say "100% predictable", I think you might be discounting the fact that most services change as they run, and while they may have a finite set of operations, those operations' outcomes vary depending on input. Determinism does not work so well in network services. On top of that, most services are sufficiently complex that there does not exist enough tools to support them in a completely automated way.

Or, maybe I should modify my original statements to say that disposable services do exist, but are only useful short-lived with very specific use cases. I don't see the point in handicapping yourself for some theoretical ideal of predicable operations. Even with unpredictable services in an undocumented state, they can be managed to work quite well in the real world and happen to run gigantic pieces of infrastructure without issue.

I don't find containers to be the cheapest way to scale. The old model of just running a bunch of random apps on a single host is really cheap scaling. Containers just reduce the size and scope of the host and take process-level resource management to the host level, which has been done decades ago in the OS, but it didn't really catch on too well.

In order to dynamically adjust the load on your JBOA (Just a Bunch of Applications) platform to make it as efficient as possible, you adjust the distribution of requests to your services, versus containers where you adjust the distribution of your containers. Of course it depends on whether your app stack/services is designed properly, and since they seldom are it's not always very efficient in practice. What you consider cheap will probably change based on what kind of crap you have to manage.

In any case, how you use SSH is totally up to you, and it does not have to result in evilness or undocumented state. Just don't use it wrongly.
This got me thinking: How can you tell that two clocks are 22 nanoseconds apart? I mean, it's not like you can look at a display or anything.

This is a bit of a rhetorical question, I'm sure Google holds many answers involving decaying isotopes or measuring laser pulses or something.
EverCookies – Track anonymous users
Email Marketing Tip: How to create email content that doesn't suck
Perhaps the reason people are not commenting on the correctness as much is that it is, broadly, correct. It's quite difficult to add to a discussion when it's already right - there's no debate to be had.
> And done. No sysadmin needed, Adam can now identify and fix his own problems.

> Graphite, logship, nagios, and some development which pulls all of this data together can create some virtually magical systems.

Who do you think pulls all that data together? DevOps/Sysadmins.

I build and wrap together the tools that make your job easier. And I take pride in that. I'm also on call so you don't have to be.

Relevant XKCD: https://xkcd.com/705/
My point was more about the way you leapt from tptacek's review of the crypto book to the incident on the bus, which implies that they're comparable situations, when really they're not. Not all cluelessness is equal.

> I take exception to your post

I demand satisfaction! Pistols at dawn, my good fellow! Pistols at dawn!
I haven't measured it, but I've noticed a correlation in this community between the valuation of a company and the number of apologists in situations like this.
Ask HN: openSSL/heartbleed for internal company apps?
Are you bothering to check openSSL versions for internal apps like:

- revision control
- wikis
- tool installs like perl, python (because of LDAP authentication)

Looking around it seems like Perforce and Subversion had heartbleed vulnerabilities for specific configurations.

Looking through various LDAP plugins for different tools, they may use a version of openSSL that is vulnerable.

Should we be patching openSSL on all of the linux boxes and not just web servers?
There's no reason to expect professionalism from a company that proudly portrays itself as a gang of leering adolescents.
Agree, I switched all my domains. Turned out to be much easier than I thought. I'm not endorsed by them either, just a very happy customer.
What I think is interesting about this is more the general case than this specific example. I'd say that people's social media handles are becoming more and more important to them, so loss of them becomes increasingly bad.

A lot of people in the tech world are probably more known by things like their twitter handle than their real name.

With free services (and indeed perhaps with paid for) there's not a lot to stop a company changing the ToS to allow for usernames to be transferred as they like(assuming it's not already in the ToS).

Now if your chosen handle is pretty niche (no one who's not a fan of 90's ADnD settings is likely to want mine), it's probably not a big risk, but for other ones it seems plausible to suggest that a company might start seeing them as a valuable asset, to be monetized..
I think that personally that's the place that genericity and inference live. I never write types as concrete as

'a . 'b -> 'b

but instead write code and let the inferencer tell me how general it might be then use that information to peel apart layers which don't need to be conflated.

This isn't tied to this example, of course. I think generally static types get misused the thought is that they don't let you experiment with code. I think that they don't let you experiment with code in the same way that dynamic types do, but I don't think they're at all impeded for that. It just takes investment into a different kind of experimentation.
Needs backlog with priority value, progress state... basically paper trail.

Also, I like the idea of this project, but I hate the pitch. I don't know why. Maybe it is because programmers already go above and beyond, taking care of the stuff that no-one else thinks over. I would actually suggest investing time in looking to fund better development. Just my 2 cents - great idea, best of luck!
Getting physical with Productivity (& Kanban boards)
Generators are the best, though I'm starting to worry I'm using them too much.

edit: I'm using koa, so co is working in the background here. Should have said that earlier, my bad.

var save = function*(){
try {
yield db.insertUser();
} catch (e) {
throw e;
}
}
Not Everyone Needs to Learn to Code – But Here's What They Should Know
I personally know someone who acquired an inactive username within the last year. You might need connections: this individual used to work at Twitter.
I don't think you're at fault for anything. There's nothing inappropriate in your review.

It's ridiculous to simultaneously say that a piece of writing devoid of context is being classified in a certain way and to say that it contains that's inappropriate for that classification.

The mere presence of phrases like "I am not making this up" tells you that this piece is not intended to be too serious. To say that it's intended seriously but contains non-serious language is a flat-out contradiction.

It could make sense if it was published in some context, like a serious blog or a news site or something, which implied seriousness. But it's a naked text file on the internet. It doesn't have to take a serious tone.
That story is the best thing I've read all day, thank you.
I don't think this is worthy of the front page. It's not useful or clever whatsoever.
Although the validity of the license could be disputed because of the obscurity of the permission, the legal recourse you'd have is the "estoppel". Meaning if I have a license (and thus the author's permission that goes with it) to act, and the author later sues me for something that is already permitted, the estoppel defense is raised to dismiss the claim.
I know you're being sarcastic, but it's viable if you have the right marketing.

> But if you want a REAL story, we have a premium standup desk made from reclaimed wood from work camps run by the Khmer Rouge for US$3000.

Yes it's a joke but from a non-Cambodian's point of view, this is like selling memorabilia from the 3rd Reich or Imperial Japan ala WWII.

After reading your comment and seeing stuff like Swatzikas (the day version) being displayed in mainstream department stores, or pictures from concentration camps being displayed in restaurants; I often wonder why people in Asia seem so ignorant or insensitive to historical atrocities. Is it because history education over there is near non-existent or do they just suck? Or is it because most people are just indifferent to history?