skysight-inc/HackerNews huggingface dataset:
I dropped over 40 grand when I could have spent $100
You are not too far from carving your header in a JPEG file there. Some may remember good ol' times when most web sites did so. It was the same reason: someone decided the size must be fixed for the header to be following a fixed grid or corporate design paper, or something the like.

You couldn't select the text, it was heavy, ugly, hackish, crawling against the grain of HTML, which is elastic. Now we know better, and let content flow, adjust itself, at the will of the users (on the desktop).

This was the Dark Ages of the Web, why do we need to go through the same lows on mobile?
Parse Named to the Facebook Technology Partners Program
And we have a linkbait title of year winner.

Now ... if the Congress has decided that some citizens should not have firearms (felons,people with mental health issues) and that is in compliance with the second amendment then a law that only enables better enforcement of said decision is not eroding said amendment.

CISPA - the cloud should be codified as an extension of one's home. With all the protections that come from it - if the landlord could not voluntarily open the door of a tenant's apartment without court order for a policeman then google should not be able to give my emails to US without one too.
Mobile web version of Gmail is a very stripped down version actually. Thankfully so, but notice that even Google could not take its full-fledged Gmail app to the tablet browser (I don't expect it on a smartphone anyway).

In other words user don't get the fuller experience of web like they do on desktops. And that's exactly the point of this thread.
Analogous to that, in Germany don't beep out any swearwords on television, which is why American celebrities appearing on TV here swear vedammt oft. For example this eminem interview

http://www.dailymotion.com/video/x98y4u_eminem-interview-on-...

It's at 2:30 where he talks about it. And swears a "little".
Nice, looking forward to the switch to OSM.

A message to the `talk' OSM mailing list might attract some attention, although there may be a more appropriate list.

An idea I had was that maybe you could form an arrangement where any OWM apps include PressureNET reporting. (In fact the same for OSM apps, you could talk to some of the developers (there are lists of android apps on the OSM wiki) because I know a few apps already include optional reporting of other things to OpenXYZMap-like projects)
Not sure about the app, but on the web interface you can seek inside a track by clicking around the disc image.
You counter with something like "Great sites can be built using any technology. What's important is to determine your needs and make something great that fulfills them." Then steer them away from the technology and back to their needs.
A major problem with BTC as a reserve currency is the way it is generated (mining) and reclaimed (fees). An entity with significant computational power would be able to maintain significant control over the reserve currency. It's feasible that early adopters, then, would be holding significant percentages of the reserve currency. What would motivate later adopters to convert when they have perfectly viable reserves already (gold, USD, etc) that's more equitably (well, from their perspective at least) distributed?

Second problem, it requires a major shift in the motivation of many adopters (anti-fiat, anti-fractional reserve banking).
US-based?
I admit I didn't look further than the connection "account less than two weeks old, never contributed, is the game's designer".

For the interesting bit, it's sadly pretty absent: there's no "story" to this, no angle. Just "look at my KS" and even on the KS page, no story, nothing about the creators,...
By the same logic, the idea that in order to give a car to one's teenage child one must go to a government office and get said teenager licensed is also absurd.

Lets not forget that guns are devices whose primary function is to kill things very efficiently. I'd argue that if you're not willing to spend $50-$100 and wait a few days, then you're not treating that kind of transfer of power with the respect it deserves.
Ah, well, I meant fixed in the CSS sense rather than the "exact size" sense.
Blue Drop Awards voting, Drupal.org D7 upgrade & more in TheWeeklyDrop Issue 82
While I am pro gun control, I actually agree with you here: we really should have a constitutional amendment to nullify the second amendment.

One of the big problems with that is that culturally, the first ten amendments are bulletproof. If the second amendment had been "the right to own slaves shall not be abridged", I think we might be in the same position today of creatively reïnterpreting it rather than besmirching something we have unwisely clad in the nominative armor "Bill of Rights".
As an API and security professional I've found to be secure and performant one should do the following with APIs:

- Dont listen on HTTP, force HTTPS (Tune your ciphers! see https://www.ssllabs.com/ssltest/index.html)

- Ensure that any client libraries you supply for API interaction must verify the server certificate

- Only use the users password to obtain a long random key from the server either through an admin web interface where possible or by an API request that supplies the username and password and receives the key.

- Make authenticated requests of the API with the key

- Store any passwords as bcrypt hash in the DB for security

- Only store the key as SHA2-256 hash in your DB for performance

- Actually yes do use HTTP Basic as it's a convenient way to transmit the key (see how Stripe does it) making things easy for your users and perfectly secure as long as you prohibit plain HTTP.

- Stay the heck away from HMAC's and signing requests, you have SSL, properly tuned it's secure. HMAC is pointless here and really confuses the users.
If you're interested : http://blog.teamtreehouse.com/web-developer-treehouse-teache...

:)
I really should make some time and do the final 5% (and get it online) on a feed reader I spent a couple of weeks building a few weeks ago…
Interestingly, a recent survey of enterprise Google domains found Lucidchart as the 8th most popular web application in enterprises:

http://www.forbes.com/sites/joemckendrick/2013/03/27/20-most...

What is not working for companies today is the $250 - $1000 price tag for each license of Microsoft Visio.
Try Scala
Ask HN: Israeli Startups looking for Interns? 
Hi, I'm an NYU student doing App Academy this summer (Rails Dev Bootcamp). I'll be in Tel-Aviv for the Fall Semester and I would love to work for an Israeli company while I'm there.

Some Skills I have: Using Excel + Python to do financial analysis on CDO's, CLO's as well as CMBS and RMBS securities, fundamental research (Due diligence etc), Community Management/ product support.

Skills I will have after this summer: Full stack rails development

If you're hiring I would love to learn more about your company and what you're building
We are just planning our migration away from the HP3000 platform and the MANMAN ERP. I am eternally grateful that the Sys Manager didn't let them customize the source and instead used the ancient reporting tools (QUIZ, QTP) to create report driven work solutions.
Otherwise the next three-years of my life would have been a nightmare of deciphering Fortran77 programs.
Surprisingly, if you have HP3000 and MANMAN on your resume, you will get a surprising amount of job calls.
"How I went from content to PR-Marketing and spun it"
> "Well people'll probably use escrow services on top of bitcoin to prevent dishonest merchants..."

Probably? There are already escrow services for Bitcoin that heavily used.
There will probably be a blog post in a couple of months about the latest infrastructure changes that we've added. Keep an eye out for that.
Foursquare's Head of Search/Data Talks About The "First Time User" Experience
Downvoted for off topic agenda-driven/like comments. No one asked, "What are the organic food myths?" yet you felt compelled to post them anyway. Why? That's the agenda part of it - you have some internal reason for posting an off-topic comment that you didn't share.
25% Discount for Intro to Exploit Development Class
I love how I got downvoted for mentioning git clone deploys.

> What's wrong with a git clone deployment, why is deploying as a package better, (...)

The advantage is that you can have a release process, where you update the package's __version__, compile/minify the files you need, build documentation, and so on, until you have a deployable branch that you can tag and upload to the repository. This way you have a reproducible history of releases, it's easier to inspect which version is deployed, you have hooks for installation (for instance, you can abort installation if the tests fail on production), etc. Mainly this:

Crank out code -> Run a makefile/fabfile to update version/compile/minify/build whatever -> Export a tag -> Build an sdist/bdist -> Install on production

I believe too many things grew inside Django (e.g. collectstatic) that really shouldn't be part of the framework at all. Another thing that bothers me is South: you need to push a release to production, then run a migration, because the migration is part of the codebase. Well, the migration really should be part of the installation process. There are corner cases where this is an issue - for instance, worker processes reloading before your migration is complete would use the new, wrong model definitions, and suddenly you have a broken release on production.

For all effects, your Django project should just be a valid Python package that you can pip install in a virtualenv inside your server (lets say, /opt/<myproject>) and you're done with it. This way you can freeze the environment on production, pip can handle upgrade/downgrade, you don't have to care about *.pyc hell, etc.

> and how does one implement it correctly?

I should probably upload a project template with a workable setup.py to github.
In the Option 1 case, what happens when you finally have to "hire someone with more experience/knowledge"?
NSA Top Secret Cryptolog Crossword Puzzles
Debian Wheezy release schedule
This is not arbitrary at all and has definition by industry standards. Passwords are used by people. Keys by machines. This requires different security policies. Passwords will have complexity rules and shorter expiration policies such as 90 days. Keys should have rollover policies around a year or so.
By asking all these questions, you're ensuring you provide a better service than a generic competitor. Don't sell a technology/service - sell a business solution! This idea is the core argument that patio11 is always driving home. By selling a solution you make it much easier to get away from hourly rates. Or at the very least, enable you to increase your rate to silly money levels.
Mind if I get in touch with you for a little customer interview?
I would have a beer with that guy.
Depending on the application and the space available, yes. That's why some aren't fixed, and some are hidden once you scroll after a certain point.
Fake Steve Jobs?

Edit: Ah Fake Steve Jobs = Dan Lyons.
If your app has a lot of rich client functionality, it can be a lot easier to just use JSON data with client side MVC rather than having to constantly regenerate everything on the server, especially when several parts of the page need to be updated at once and a lot more performant.
It's orthogonal. Create your base image, at deploy time, create a virtualenv and install your specific artifacts.
Javascript 3D Game Engine
WebGL 3D Component Based Game Engine
Noriben – Your Personal, Portable Malware Sandbox
I can't answer your question, but in this example, it's the context, not that name, that is offensive. I doubt it's even linguistically possible to make a reliable classifier.
The Glorious Glasgow Haskell Compilation System is truly glorious
Apple reportedly stops placing Mac component orders
That sort of platform migration should be handled using some sort of capex methodology. We are in the midst of four ERP migrations (at four facilities) and their funding is expensed out over 10 years to keep from taking a big initial hit to the books.
You might want to put a s/United/the United/ wrapper around your geolocation function -- currently it says you ship "even to United States".

BTW, I still remember the time you set up a webcam and let visitors from around the world make your computer talk. Was that while you were in Japan?
Snapchat Recovery - Snap Spam (Ew.)
Can your regex tester do this?
I plug it into my radio speaker through the aux in cable in my living room.
Users should use "a long random key"

But you should store "the key as SHA2-256 hash in your DB"

why hash it?
This is crazy talk. There's absolutely no reason the constitution couldn't be right about some things and wrong about others.
The importance of open code
A nice (and shorter) article from Marco Arment on Phish: http://www.marco.org/2011/05/26/geek-intro-to-phish
Wait for the Haswell. It's only a few months away.
You have the Constitutional right to join a well-regulated militia.
It's definitely too bad you ended up so far out in the inaka. My girlfriend studied at Kumamoto and the time I spent there with her was absolutely a blast... the furthest I've been out was somewhere in Gunma that you could only get to via diesel trolley, and I can't imagine actually living there, despite being only an hour from a large group of people.

I did smile -- well, grin like an idiot -- when I saw "Candy Japan." That's you? Congratulations! That's a very cool service, and the first time I read about it I was both impressed and very jealous.
You've described OAuth in part with its refresh and access tokens.
I tend to use an api_key, because it's easier to manage. I'll setup a route to authenticate, where I'll use basic auth to return an api_key, and the remainder of the api either requires an api_key or no authentication at all.

For Rails developers, Ryan Bates does a great job of explaining a few ways to secure your api.

http://railscasts.com/episodes/352-securing-an-api
Odd Things You Can Do with an iPhone
"I don't understand the whole "things were different in the 1800's when they wrote the 2nd amendment" argument"

That's not the argument I'm making. I think you're misreading me, or perhaps I was not perfectly clear. Let's give the reader the benefit of the doubt and assume it's on me.

"Isn't that why they added the whole Amendment process?"

Yes, and that's part of my point.

I'm not arguing for a reinterpretation of the Constitution. I'm arguing against the idea that everything in the Constitution is of equivalent weight and is equally sacrosanct, unchanged by time and circumstances. Amendments are our remedies to said change, if/when the need arises.

The author's insinuation -- that you have to take everything in the Constitution at equal value, or else you're a hypocrite -- is a false equivalency.
What valid purpose? The Internet does not need more regulation. The FBI/CIA do not need easier access to everyone's communication. Please demonstrate what the threat is requiring FBI and CIA to read my emails and access my entire browsing history.

Let me guess... "Terrorism."
I don't know what/where/how but there's a timeline in place for spraying the fruits. They need to be sprayed with chemical "a" at "b" days of age, and then perhaps with chemical "c" at "d" days after/before "e" event (flowering, budding, being pulled, etc). These would be timed in a such a way as to prevent specific insects or diseases that are interested in the plant at those times. For example, it might be that the pesticide for fruit flies isn't applied until after the fruit has developed.

That being said, all pesticides have an "inert" date at which point the chemical is not doing anything. I'd be interested in learning whether that date is after the sell date. If not, then your post raises a really important question. If the pesticide's chemical(s) are inert before it is sold, then it puts it to bed, I think. I don't know enough about pesticides/organic to know where to even look for stuff like that though.
Ahead of their time: technologies that came too soon
This may be decent advice for security purposes but unless I can test your API directly from the commandline using CURL I am unlikely to ever get as far as trying out your service.

In other words, use HTTP BASIC (or similar) if you want new users.
Most common reason for insisting on technology X in my experience is because they have someone in house who knows X and they don't want to be stuck pay $$$/hour every time they need to make a minor tweak or update.
The technical operation is not the ideology behind Bitcoin, and it certainly isn't the whole of how Bitcoin is used.

There's plenty of utopian fantasy surrounding it and a fascinating social dynamic that has absolutely nothing to do with "sound mathematical proofs and concepts" but more intangible qualities assigned to it by its proponents.
Thanks jeffbarr for valuable information...
This is true about every product. Focus on the customer's needs / pains and provide a solution. The underlying technology either doesn't matter at all or is an insignificant part of it.

Put solutions first and then when you discuss technology always take into consideration your client's level of expertise. If the client is non-technical keep technical discussions as high level as possible. Highlight ease of use and how non-technical the product is. If the client is a technical non-developer / power user highlight technical features they'll use. Developer level clients can usually figure out the tech themselves but talk some shop to build rapport.
Progressive Types
I feel the same way. When I chat with clients about a project, I focus on their business and clients. I get involved a little bit, see what they are all about (and after that they want to hire me as their employee, but that's another story, I should start blogging about it, hah!) I will definitely try to take the "Do not mention technology" approach to see how this may change things.
The thing that gets forgotten is businesses do not have technology problems. Businesses have business problems that technology may help with.

Customers, and end users especially, rarely care what you code in, or what you're using. This does not automatically mean closed or proprietary solutions, only a reflection of whether you've built enough trust with them.

Customers are hiring you to be the guide through the decisions that they need to find and make to ensure they have the ability to communicate how they wish to on their website moving forward. Spending time trying to compare megabytes and Wordpress' doesn't communicate solution for them so quite often they will go for the sizzle rather than the steak.
Gold dropped 9.4% a few days ago. That had little to do with what the majority thought instead people wanted to sell slightly more gold than people wanted to buy and the price dropped.

Ass to messing with the block chain, the real problem is a 51% attack is one that people don't know for a while, start randomly seeding bad transactions and there is no obvious point as to which where good transactions and which where bad ones. People my suggest reversing all transactions but if you traded bit-coins for stuff your now out your bit-coins and your stuff. Net result Bitcoin's probably dies.
Well, yes, I guess there'll always be clients like that. I've generally been quite fortunate that I've been able to be fairly selective in life about who I work with/for, and I've rejected as many clients (more in fact) than have rejected me.

Saying that though, in those kinds of situations I do usually try and have a conversation with them about why they want to make those calls - they're paying me (or wishing to) for my professional expertise, and part of that is about educating people around surface choices which seem like a bargain but come with potential hidden costs and disasters. Some can't be helped of course :)
That's not what hypocritical means.
BizSpark does (for up to 3 years); DreamSpark does not include the Ultimate edition of Visual Studio.

https://www.dreamspark.com/student/software-catalog.aspx
Okay, now THAT's interesting (as in "got a story/angle") and HN-related :)
Here's how I sell charging what I do for web development on top of WP/Drupal/RoR/whatever (if it comes up, which is rarely does unless the customer asks about tech):

"We're planning on using <CMS/Framework" to implement your solution. The reason for this is that <CMS/Framework> allows us to make a running start in development. For example, you do not want to be paying us to write code to manage logging in to your website. That's been done a million times and we don't want you investing into the reinvention of the wheel. Using <CMS/Framework> give us things like managing users and logins. It allows the money that you're investing to be spent on those things that makes your solution unique, those important little details that have brought us to the point where we're talking about building custom software."
Yeah, but things _were_ different in the 1700s when they wrote it. At the time there was no standing army, each state had a militia and citizens were often responsible for providing their own equipment. The 2nd amendment seems to have been aimed mostly at state governments, sort of a "when we need your militia, you'd better have one we can use".

The reading where being armed is a protected right of each individual _is_ a reinterpretation, and a fairly recent one at that. http://backstoryradio.org/straight-shot-guns-in-america-2/ (podcast, but well worth the time) has a wonderful summary of how this view has evolved over the last 2.5 centuries.
You should almost never know a users plaintext password. Outside of a small set of scenarios you're likely doing something very wrong if you need a users plaintext passwords. Passwords should almost always be bcrypt'd.
Because the scope will be misused, and the data will be given away. It's not like the US government doesn't have an extensive history of privacy & rights abuses.

Tasers were passed as an alternative to shooting a suspect, now they're used routinely for detainment. The various terrorism laws are now being used clearly outside the scope of terrorism (hackers, drugs, etc). The DMCA is being all kinds of abused outside its scope.

This is what we're rightly-concerned about.
Absolutely true. However, I have a hard time disagreeing with the OA's general thesis. Maintainability is not something that fits in a client pitch unless the client already is aware of it as an issue. Especially getting into the nitty gritty of technology choice is a rabbit hole that is not going to help you win a project, because 99% of the time the client doesn't have the expertise to evaluate whatever claims you make about the relative maintainability of different solutions.

When it comes to winning bids, you need to speak the client's language and address the concerns they have. That's not to say you don't have an ethical obligation to consider long-term maintenance and other issues that are off the client's radar, but if you talk about it too much with a prospective client who isn't aware of it you will appear to be out of touch and not understanding their real needs.