skysight-inc/HackerNews huggingface dataset:
I made a New Years resolution (purely for convenience of logging time) to not eat meat on weekdays. So far, I've been pretty successful at keeping it. I guess the key here is that I'm able to eat meat on weekends as a treat, which refreshes my willpower weekly. Next year, I plan on restricting my diet further, but possibly keep the less-restricted, meat-free diet on weekends.
Concerning "SHA-1 attack" and "Random GIT modifications"

http://osdir.com/ml/version-control.git/2005-06/msg00583.htm...

But seriously, if anything had been done thousands of people would have known by now.

"just append some commits to any repository"

People will notice that immediately.

The simple fact of the matter is that due to a combination of both Git's technical attributes and the Linux kernel development organization/practices, we are quite safe. This was addressed last time this topic came up, I feel you should probably read some of the responses you got that time.

If you still want to be concerned, I advise addressing this: http://git-blame.blogspot.com/2011/08/how-to-inject-maliciou...
Graphical design is not copyrightable, although the images used in making it might be.
Internet Archive starts backing up digital books on paper
Block all social garbage with adblockplus.

http://www.techairlines.com/2010/12/12/block-social-buttons-...
It sure does. Also, if you search hard enough any site will breach some accessibility guideline for a deaf, blind, mentally handicapped or epileptic user.

For example http://validator.nu/?doc=http%3A%2F%2Flightgetsin.dreamwidth... shows some possible WebAIM accessibility guidelines breaches.

- non-valid mark-up.

4.1.1 Significant HTML/XHTML validation/parsing errors are avoided.

- mixing of inline styling with external styling.

4.1.2 Markup is used in a way that facilitates accessibility.
This includes following the HTML/XHTML specifications and
using forms, form labels, frame titles, etc. appropriately.

- Using &nbsp;&nbsp; and <br> for visual spacing

See 4.1.2

- using tables for layout

See 4.1.2

- not providing a label, description or fieldset for the searchform

1.1.1 Form inputs have associated text labels or, if
labels cannot be used, a descriptive title attribute.

And, not a WebAIM guideline, but still a good accessibility guideline:

- Use a modern doctype (of the strict variant if not HTML5)

- Don't use deprecated tags like <b> for article headings.

- Provide an option to skip large lists.

If you start wielding all these guidelines and specifications like a D&D guide you are sure to bump into hostility here and there. :)
It seems that the tags for cells seems to be an important feature of this database, and they also mention it is appropriate for places where "privacy is important". Can someone explain the connection between these two? If I'm understanding right, the labeling makes it easy to address individual cells, but I'm not sure how that enhances privacy.
blacks/jews/gays/etc is a different issue entirely. You don't need to do anything special to make your service accessible to them, except perhaps in the case of gay people trying to use your dating site with a 100% straight userbase.
Unix shell scripts are fantastic for what they do. But most people find that it's easier (and more performant) to build, say, web applications using a programming language than by using shell scripts over CGI. Assuming you commit to a programming language, then you either then commit to multiparadigmatic programming and call out into shell whenever you need to do work like that, or you give up shell inside your program in favor of using the API tools inside the language. Outside of possibly perl, calling out into shell for things like that isn't very common anywhere I've ever worked, and with good reason.

Once you commit to a programming language instead of shell, then you have various types of IO to worry about. What you want might be in an array or list, a file, a database table, an xml file, or the response from a web service. Typically, you either need to write a decent chunk of code for each of these sources, either for abstraction or for marshaling.

With LINQ, all you need is a change in the upfront handling, and you can reuse the same comprehension logic across all the different data sources. This is a pretty nice deal, all things considered.

And really, one way of looking at adding comprehensions like this to languages is to make programming in languages more like chaining together code in a shell script -- something that programming in traditional Algol-descended languages is not normally like at all.
Not a big surprise. There are more opportunities for hi tech startups in the US. Also, health care is not as big an issue for young males.
Avusturya Türkiye Maçı Özeti izle 6 Eylül 2011
I don't really get the point. Unix has been fantastic at scraping and munging text for decades.

curl http://weather.yahoo.com/united-states/california/san-jose-2488042/ | sed '/Current conditions/s/.*id="yw-temp">\([0-9]\+\).*/\1/'

It may be fragile, but any method of extracting data out of HTML is going to be fragile when the provider changes design or layout.

A tiny bit of knowledge of grep, sed, and awk, and other simple unix text utilities such as join, comm, cut, paste, goes a long long way.
Here in the UK it's interesting to note that, while text speak was all the rage a few years ago, it faded out.

It was replaceddddd by making wordssss actuallllllly longerrrrrr for no reeeeaaaasonnnnn!!!

Now the text speak is a bit more reined in and not totally incomprehensible like it used to get.
On the contrary, its the SQL database thats "digging up the necessary information through quite a few steps" it just that massive effort required by the SQL server is hidden from you, the programmer, by a one line bit of text called a SQL statement. So you do it all the time. Indeed we've been taught that denormalizing is the "proper" thing to do because otherwise "Bugs happen and referential constraints go a long way towards keeping your data clean."

Digging kills you. I assert that SQL does the digging automatically, and thats exactly why it doesnt scale.
HTC Sneaks Spying App into Android 2.3.4 Phones
No, but iOS is a derivation of OS X, so you have to take all the iDevices into account too. Probably Linux still has the numbers.
For illustration (probably wrong again):

curl 'http://weather.yahooapis.com/forecastrss?w=615702&u=c' | \
xmlstarlet sel -N 'y=http://xml.weather.yahoo.com/ns/rss/1.0' \
-t -m '//y:forecast' -v '@text'

edit: corrected xml line
I'm sure the particles of his ash have some kind of rotation in their space journey.
svn co https://svn.apache.org/repos/asf/incubator/accumulo

doesn't seem to work
Good question, I played the Devil's Advocate inside my mind. Here is what I get as return / output: All the traditional elements of marketing are different:

a) Is the target market specific?

Yes for q. & s., no for c.c.

b) Is the target market pro. / high-end users with high sense of fidelity to the topic / site / brand or casual consumers?

Yes for q. & s., no for c.c.

c) Does the target audience return to said sites regularly, participate in a community (with hierarchies, badges, comments and replies etc..)?

Yes for q. & s., no for c.c.

d) Do the specific topics discussed get relevant links from blogs, tuts sites etc.. from similiar fields

Yes for q. & s., no for c.c.

This is simply the tip of the iceberg.
The optimal way to solve this is to invest more money in screen-readers. Unlike robotic wheelchairs climbing stairs, software can be copied for free once it's developed. If the government wants to step in, they can provide purchase vouchers to the disabled and let them drive the direction of screen-reading innovation.
Where my grandparents live there is nothing, no school, no shops no bus stop, only a comunity center and a part time church.

20k is a town. 100 people is nothing.
Well, if they get a hundred complaints from potential or former customers saying they won't eat there until it's fixed, something may happen. Some of these problems are only soluble by mass, organized action. Suppose there were a blind guy standing outside your restaurant, handing patrons informative pamphlets? How long would it take for a few infuriated regulars telling him they wouldn't be back till the problem was fixed to get the owner's attention to the problem? Just sayin': squeaky wheels get greased.
The software engineer in me says this can be solved by more intelligent screen-reading technology.
Came here thinking I'd find out the answer. Can you add the "Ask HN:" prefix, as well as a question mark?

Anyways, a start from Hipmunk FAQ (though no exact calculation mentioned):

"What is Agony, and why would I want to sort by it?

We know that price isn't the only factor that goes into purchasing a flight. While other sites sort by price, Hipmunk automatically sorts results by "Agony," which is primarily a combination of price, flight duration, and number of stopovers."
I read this article with a concern about an app I've worked on, where we intended to go thru an add accessibility support in after the first release, but it (and a bunch of other improvements) got dropped when priorities changed. I was reading to see if I could judge how our app (which should be mostly accessible) might have worked for this person... but they never mentioned what their disability was in their sample letter, and so I had no clue, and couldn't hazard a guess. (Except maybe that they are blind? Though I don't have enough clues to be at all confident in that guess.)

I wonder if part of the non-response they got was because they never explained what their disability was in their letters. I understand it really isn't some pizza restaurant's business to need to know it, but if they left that off, then it is hard for someone to understand their dificulty-- they might even read the email too fast and not even realize there is a disability at all. Thus it just sounds like someone who can't describe why the real problem is, and is instead giving web development advice to a customer service rep who, more likely than not, has no ability to even parse the email into actionable or useful information for the developers simply because the context is dropped by missing this key bit of information. (Even though the advice is useful to someone who is a web developer, even without knowing the disability, the CSR may not realize that.)

That said, I have gone thru a recent terrible experience attempting to deal with a company who is bringing in $150million a month in revenue, and can't be bothered to have CSRs actually read letters. Over the course of a dozen back and for the responses, each form letter I got from them, was written by a different person, and seemingly responded to a random word or two from my previous message, where they clearly didn't' read the whole ticket or even take a few minutes to actually comprehend what I was saying.

There's some really bad customer service out there, even from companies that at least don't have lack of budget as an excuse.
Most people would consider it Internet Explorer's fault if it crashed on the majority of webpages.
>"I've often thought that combining hacker/maker spaces, good digital libraries and some communal living would make an excellent, low-cost fellowship for people looking to experiment for a couple of years. Related as I characterize the arrangement as monastic."
/WHEN/ I move out to SF and /when/ I have lots of cash this is exactly what I'm going to do.
LimeWire Settles With Record Labels, Still Faces $1 Billion Claim
They seem to be access tags, not just arbitrary tags. I interpret it as item-level ACLs, something like row-level security in SQL databases.
Interesting, I may begin contributing to that. I strongly believe this a problem to be solved by technology, not heavy-handed legislation that will add billions of dollars of costs to web development and innovation.
The example happens to use "munging" text, but I think the GP is trying to make the point that you can't use sed (effectively) to parse, for instance, a collection of database entries from an SQL server in the same way that LINQ would be able to do so.

The tl;dr I got from the article was LINQ is effective at working with sets of data; not just sets of text data from a text file.
but they never mentioned what their disability was

From the article: ...making it inaccessible to blind and low vision users.
I see it not as a subsidy but more of an insurance premium. We all put in a little bit of extra effort in exchange for not being royally screwed if it happens to us. The progress of civilization seems to go hand-in-hand with these sorts of arrangements. That's probably because there are so many ways to be royally screwed that, if we didn't look out for each other, everyone would be screwed in one way or another.

But there needs to be economic incentives for this to work (and regulation is an economic incentive). Asking a business to be altruistic is like asking a bear to not eat your trash.
Bfdev - A Brainfuck IDE
Create more value than you capture
Yes, that is a very important point, precisely because people do not want to focus their attention upon it.

Google has gone from a company that does not do any "evil" to a company that tries to make a progressive / positive impact and therefore they feel entitled to collecting more information about their users than they ever thought they would need at the beginning.

In that sense Google is like the government in the original Austrian economics. From utility to expansive progressive force. But with what results this time?

Edit: this reminds me off the "Faceback" app from the movie Good Guys.
Dell launches tiny, Via Nano-based servers
No, there are countries that still have a little bit of reason left.
My-egames - Collection of free browsergames
Actually, the economics didn't work out to favor discrimination. The change was not as slow as many people liked, of course, but the change was there. Where discrimination was really entrenched and difficult to change was in government. It was racist government policies that really kept segments of the population down, and in fact, many of those racist policies still exist today. For instance, the primary motivators of the anti-drug and anti-gun laws were racist. "Saturday night specials" were regulated because they were popular among poor blacks for self defense. The sawed off shotgun, which is actually safer (because the shorter barrel means wider shot spread and makes the firearm less lethal) ware popular among italians who wanted protection from the mob, so the mob leaned on white politicians and got them banned, good for the mob, and served white political ambitions, etc.

Where there has been no supply (the small country example) blacks, for instance, often would band together and form businesses that served their community. This was inhibited by government regulations that would often deny them the "license" needed to operate that business... but it was not economics that kept those businesses from forming, it was regulation. (And where there wasn't regulation, the businesses would form.)
It's just a proposal atm. The svn-repo is one of the items they are requesting from ASF
The third iteration thing is exactly what I was thinking when I read this thread. First attempt works, but it's pretty shoddy. Do it again and you get something better but still has room for improvement. By the third it's still not perfect but it's good enough to make you happy you did a good job.

My other benchmark of bad code is that you know it's bad when you have to hack it to add a new feature, and the only way to remedy that is to re-factor most, if not all, of your codebase.

I've had to do this a lot lately because I've not had chance to iterate. I know full well the code is bad. It works but it's not easily maintainable, and since it's in the context of a REST API there's a shitload of code we now have to duplicate - with minor differences - to add functionality I didn't have the foresight to plan from the start.

That of course is also the side effect of being given an entire project to do by yourself while the rest of your team does other things. The insight and assistance from colleagues or team-mates, or even friends if it comes to it, is just as valuable for writing good code. Knowledge has to come from somewhere.
Ask HN: Why does "remote" in a job posting really mean "remote...from the US"?
Recently, I've been looking to relocate outside of the US. The city I would be relocating to is one of the largest cities in the world. There is reliable (cheap!) internet service, and the government is reasonably open regarding internet access (at least on par with, for example, Australia). In fact, I've already worked remotely from this location for short (2 week) stints in the past, and I found I had no problem getting the work done or keeping in touch with the team.

So why is it that every time I respond to a job advertisement claiming a "remote" position, the recruiters hesitate as soon as I mention moving away from the US? My understanding is that the burden of working out tax and other monetary considerations would be completely on me. I'm more than happy to adjust my schedule to the time-zone of the majority of the rest of the team.

Obviously, I could understand why some sectors of the industry would be wary (issues with export controls, etc.), but even basic web shops have been hesitating or outright turning me down. So my question is: is there some legitimate business concern to limit remote workers to "within the US"? or is reluctance to hire overseas remote employees based primarily on unfounded fears?

What should I be doing to improve my odds of finding the right position?
Actually, I wasn't referring to gross vs. net revenue. I was referring to recognized revenue vs. cash on hand. If I can convince someone to give me $500 but I owe it all back to them, my only revenue should be interest/proceeds from investment of the $500 when actually earned – but the $500 on hand is not counted as my revenue. If my obligation to repay the $500 were to end, then it would become revenue.

I believe there are accounting strategies that might be exceptions to this, but I've never encountered any public companies can get away with using them.
I'm sorry, but "I was disappointed" and "I wish you would take steps" probably gets you grief. Asking usually doesn't. "Please" also helps (and its absence doesn't).

I mean, come on. I'm sorry company X site was all but useless to you. It would be nice if they made an extra effort to make it more accessible. But they don't have to. They spend their own money, time and effort to build the site, and they get to decide what their priorities are. Asking is okay, but so is refusal.
Maybe CBS is building a Tricorder app?
Asking a business to be altruistic is like asking a bear to not eat your trash.

I get kinda annoyed by Capitalism Means Being A Heartless Bastard, because it doesn't. Businesses are routinely altruistic for the same reason that businesses are routinely greedy: like soylent green, they're made out of people.
wow, what is the fetish with assembly language this week?
Sure. PR fallout or DDoSing support offers additional leverage to mere and minimal lost business.

Especially really large companies don’t want to have an attack surface called “They don’t care about disabled people!” (There are also other reasons why larger companies have more incentives to be accessible.)

Evidently, however, that’s not enough. It’s hard to create public outrage. It’s hard to organize. Hard enough that being hit by outrage or being swamped by phone calls is quite unlikely. It’s a simple numbers game.

People don’t want to organize shitstorms all the time. They have better things to do.
Honestly this is nothing new. Selling commodities of any kind has alwas sucked unless you can do it at scale (which is basically impossible when the limiting input is ones time).

For a short time industrialization meant that the least skilled could produce as much as the most skilled, but as pg argued that was as special case of a special situation. I know of no case where it has happened before or after, anywere.

If you only have commodity skills, the best thing you can do is to go down to the nearest community college.
>That's why economic forces didn't do much to open up things for blacks in the south between the Civil War and the era of Federal civil rights law.

Perhaps, though the fact that states felt the need to enact Jim Crow laws lends some doubt to that claim.
Why QWERTY Smartphones are a dying breed.
Great stuff dude!
iPhone developers: Never considered supporting Apple's VoiceOver technology before? Setting aside positive karma, here's an awesome reason to do it: your app needs to be accessible in order to work with the best functional testing framework out there, KIF [1] (https://github.com/square/kif)

Write tests with KIF, ensure that blind and low-vision users can use your app, ensure that your app is functional. What's not to love?

[1] i'm totally unaffiliated with Square, its creators. I just happen to be in love with it, that's all.
I find interesting the notion that web apps ought to be written to support screen readers instead of screen readers being written to work with extant web apps.

I also suspect any hostile response would be due in part to the concern that someone is going to swing the big bat of government at them.
Trabajo en Casa
Lack of outrage is the phenomena here, not the lack of respect for privacy. It's not that Americans don't value privacy, I think we do. Rather, it is the general attitude against outrage or, perhaps, against complaining, what differentiates the US from Europe.

The country doesn't have a healthcare system for citizens outside of the military, and there's no outrage. Does this mean "there is strong evidence that USA as a nation" doesn't value not dying?

"Don't seek government help, work harder, smile more and make more money" appears to be the answer/advice to those who complain/express outrage. Then you can buy yourself healthcare, privacy or anything you wish.
How to Change the Port on tomcat
From my experience or learning rather while studying psych I came to believe that as all successful or enjoyable actions are rewarded by dopamine (everything from grasping a spoon so smoking crack). Also, the more closely an action and its reward are pared to one-another in time the greater the strength of the feeling of "that was a good choice or Success!".
So it seems to follow that giving in sooner rather than later (for some potentially greater reward - delayed gratification) rewards the brain more and does so faster thus reinforcing that behavior model more and more successfully over and over.

Because delayed gratification is well, delayed, the chemical reinforcements in the brain don't happen (or happen in some other way that is more conscious rather than instantaneous without reflection). So for a child who has not developed the ability to delay gratification it becomes now or never and that mental reward structure can really hurt them later in life.
Thanks for posting.
" The core codebase consists of 200,000 lines of code (mainly Java) and 100s of pages of documentation."

100s of pages of documentation is a promising start for any open source project.
The API Culture
It sounds like Oracle's Label security applied to Hadoop.

It'll be a challenge because Label security slows things down quite a bit.
MVP stands for Minimum Viable Product. There has to actually be something for it to be a Product.
And how would you uncompress it?

B4 bs ws 2 lt.
> but it (and a bunch of other improvements) got dropped when priorities changed

More CTO's with disabilities need to be hired.
ok, so let's go back to this for example: http://news.ycombinator.com/item?id=2908015 (I am nothing).

As the author says: "I am nothing, and so I am finally free to be myself.".

Does being 'myself' mean I lack willpower and thus just ignore everything and everyone else and focus on myself?

Thing is, in my opinion having good self control wins over being myself (which I think is on the edge of being selfish).

I wonder what you guys think on the question 'being myself' vs 'self-control' ?