skysight-inc/HackerNews huggingface dataset:
I agree with "Security is a process, not a product." AFAIK security is important for WordPress team. There is a lot of good documentation on a project site and there are some materials from WordCamps (fe. http://codex.wordpress.org/Hardening_WordPress)

Latest WP "hack" via botnets was because of weak logins and passwords which are set by the users. Can you blame WP devs for that?

Speaking about upgrading; making updates easier it`s also one of the goals of the project. Also it isn`t that hard when you develop WP sites using information from WordPress Codex docs.

I hope it will get better with time, and as i wrote people are working to get things better. Sorry to hear that you are not going to recommend WordPress any longer.
>bad movie night

This is how/why my family and I watch it. It's fun(ish) if you go in with that mindset. Even so, it can be a complete cringe-fest at times.
And this is why I haven't been running gnome since 2.2
An app using Facebook's API cannot delete objects not created by itself (e.g. cannot delete posts or photos). So either this requires you install a browser extension or it's fake.
Wouldn't that be a problem for large projects such as gnome or firefox ? Devs would have to spend some precious time curating the bug tracker issues and explaining decisions and educating users instead of using the bug tracker for its intended use: to track bug.
> 'No' and a link to the relevant reason and workaround should be fine

Yes, the original answer is "just" missing the link. As is also the answer to the why comment.
I can think of an open source project for a popular node.js debugger that has similar problems.

https://github.com/dannycoates/node-inspector/issues?labels=...
P-80 Shooting star: A great skunk works project for the US Army
Consider that dissonance: a website is a magic black box from the outside.

That will work to your advantage, you can skip the technical details and make it as efficient as possible. This means you should focus on selling the site as a solution to a business problem. Working out what that is, is the hard part. Many times the client has no idea and no goals.

Another advantage is the visual nature of the web. Details of what a site actually does are mostly visual elements. This means the Designer and Coder will be one in the eyes of the client, if the coder exists at all. I recently learned this lesson the hard way: I as a developer, brought on a designer friend to help with a contract. Introduced them to the client and we put in a bid. Soon, a design firm came in and took the contract, selling a design and insisting on bundling all development.

My mistake was the disconnection between designer and developer. The client doesn't know or care. Bad client? Maybe, but it seems like a common theme to me.
Yes, but an awful lot of small businesses (plumber, dog walker, restaurant, transmission shop, barber, etc) just need a basic brochure-ware site with some text, a few photos, an address, phone number and hours and maybe a contact form or hosted email. 1&1, Wix, Webs, Weebly, Wordpress.com, GoDaddy, Homestead/Intuit, Vistaprint, and probably 100 other places offer that DIY/lightly configured site offering. If that's the thing your (non-)client needs, why should they pay 100x that for something no functionally better for them? They don't want a website. They want more revenue, and they want their customers to be able to find, learn about, and choose them; a website is just a means to that end...

Disclaimer: I work for Vistaprint, who also owns Webs, and I always speak only for myself on news.yc, never for my employer.
I think that the 'everyone should learn programming' idea conflates a few things, most of which are good.

- simple automation and tool usage

How many billions of hours of productivity are lost because people are manually retyping or reformatting data that could be quickly and easily scripted (with only basic knowledge) or done using commands/tools already present on the system? Quite a lot. How much more effective could people be if they could run even simple queries against the data in their domain? These things aren't difficult, people just don't know that they can do them.

- making things more efficient

Related to the above, a basic understanding of how to handle data in a way that can be processed, and how to make things organized and open to processing, could go a long way. It doesn't take much programming to realize that text files are much easier to process than Word documents, or that a consistently-formatted spreadsheet is reusable while one with the data scattered around for visual effect is not.

- learning to distinguish between things that are easy or difficult to do with programming

Lots of good ideas get nixed because someone doesn't want to spend a lot of time and money, or bother the developers, when in reality it's something that could be done in about the time it took to describe it (or less). And we all have plenty of examples of people assuming that something difficult should be quick, easy, and cheap. While it takes a lifetime of experience to be good at estimating such things, and it varies greatly depending on domain and tools used, a little bit of knowledge of how computers work could go a long way in some cases.

And for those who say that programming is not for everyone, think of basic math and accounting. Everyone may not be a professional accountant, but everyone has to deal with money. Would you want someone in charge who doesn't even understand that costs need to be lower than revenues to generate a profit? Or that doesn't know how to calculate 5% of $10,000? Some basic knowledge is useful regardless of what you do.
Wouldn't the new bittorrent sync software be useful too in that case ?
Asking for feedback is much different than selling a product. I'm not sure your experience would have been the same if it were a cold sales call.
This is valid, I really do appreciate the response. I have no I intention of trying to offend, I was just going through a chain of reasoning in my head and really just wanted to know if there was a flaw.

It does seem like there was, so thank you for enlightening me.
Well, the point I suppose is the person filing the issue thought it was a bug. Apparently the removal didn't make any release notes, so why believe otherwise?

The reason you have these discussions on the issue tracker is so when the next person comes along to file the issue, he/she now has the relevant context. Randomly guessing at which group to search and post to hardly helps in discovery. If you don't want discussion, disable the comments. But that's hardly conducive to good community teamwork.

And I'm really not aware of any project that only uses a "bug tracker." They almost all track issues, ranging anywhere from bugs to new feature requests. Maybe Gnome is different in this regard, but I don't think it's crazy for someone to believe otherwise. Redirecting conversation smacks of a "bugger off" mentality.
It's the http://www.arcadebliss.com/game/russian-roulette.htm of its decade...
alt+print screen in windows. It takes a picture of your current application. I use it all the time.
Eh, maybe you don't use Photoshop much but this barely similar to the Magic Wand in any way other than selecting a part of an image. Magic Wand doesn't give you a nice live preview of the alpha channel for starters.
The problem is that mortality rates are always exaggerated, because the people that contract the virus and get very sick are the ones that come to medical attention. If 10x more people contracted the virus and fought it off, and never went to a hospital or contacted a doctor, no one would be able to factor them in and reduce the mortality by a factor of 10. That's why mortality rates tend to decrease in newly-discovered diseases, we start to look harder for people infected but not killed by them.

Of course this isn't a reason to be complacent.
In my opinion, if you have cofounders, you should split the equity evenly. If you are uncomfortable splitting ownership evenly because you don't think your cofounders will work hard enough in the future, you probably shouldn't start a company with them.

If you're concerned about fairly valuing the work put in until now, a month's work, even if you had done 100% of it yourself to date, is a small, small portion of the total work required to get to cruising altitude. This is a multi-year journey, after all.
What were the older incarnations of the cloud?
> If the people requesting the feature care enough, they should go through the hoops necessary to (edit: learn how to code and) become part of the core team.

Why? so they can argue will fellow core devs?

> For this _particular_ feature, it's a "rampant layering violation" -- translucent windows have been available in compositing window managers (Compiz, and whatever that thing that KDE uses) for at least three or four years.

NOPE. Setting the transparency by compiz would make the whole window transparent, including the text, which makes the transparency useless. You need the background to be (semi) transparent, and the text to be fully opaque. This is a non-solution.
Dude you don't have to be an asshole, I was really just honestly asking for people to give me some honest feedback on my line of thought.
I can show you 10 studies to counter each study you just posted, so all these "studies" are useless. At the end of the day, 11,000 people are dying in the US per year vs. only tens or hundreds in other countries where they have proper gun laws. I know the US population is higher, so let's take it by ratio: the rate per 100,000 population per year in the US is 10.20. The US ranks 57 in the world. In the UK, the rate is 0.25, and they rank 5. Japan ranks 1st with a rate of 0.07. It doesn't look like you care about ranking high with the rest of the civil societies in the world. I frankly couldn't care less about the "right to bear arms". A right made in the 1700's when militias were there to fight the British. You don't realise we're 300 years ahead now, do you?

And yes, I did make up my mind a long time ago. I simply can't wrap my head around two things: guns & death penalty. To me, these are primitive issues that if we're really a civil society, we really shouldn't be discussing them in 2013.

I think we should end the argument. A HN discussion will not stop you from carrying a concealed weapon, nor will it alter my views.
I do the same. I make notes on a web page, book or slide deck in emacs by setting transparency. If someone came along and removed it to just because of internal code changes I don't care about I would also be angrily posting on bug reports. http://justinsboringpage.blogspot.ca/2009/10/transparent-ema...
Anecdotal evidence tending the other way: I worked for a small company years ago where the owner had an almost superstitious respect for the programmers because he had tried and failed to learn some programming. Everyone else--including people who knew far about the workings of the systems than he did--he regarded as readily replaceable and looked down on.
Probably too dangerous to bring back inside with several pounds of ammonia in it. Might as well just let it RIP outside.
Commands like Remove-Item have familiar aliases like rm by default. If you see code in tools like Psake, etc. it would be very verbose, because the intention is to have readable code. But you sure can use the aliases for everyday use.
Is there any way for a Vim session to span multiple monitors? Multiple terminals? That is what I would like more than anything.
No affiliation with Gnome or any desktop project here, so don't blame them if you disagree with me.

The people complaining when they're upset do not necessarily represent everybody. Actually the people who are so vocal as to post the same bug 8 times and tar the project on Hacker News with lots of misrepresentations of what happened are probably not the most helpful to the community. Let those determine the direction of a project and you will continuously add features without any technical direction until it becomes bloated, a nightmare to fix or extend, and the only tastes served are this one bitter, vocal minority that becomes your entire community.

Maybe you should buy a commercial OS and try complaining to the salesmen, see how much they will charge you to ensure that arbitrary custom feature X ends up in the next release.
So, the moral of this story is "communicate clearly the first time or you're going to end up having to communicate clearly about seven or eight times."

That said, I don't understand why he felt he had to keep explaining it. He could have just copied and pasted the answer or closed the bug as a duplicate of the original one that reported the bug. In the original he could have posted a kind explanation about it, and linked to it from the duplicates that followed.

I understand what it's like to get tired and short tempered. I used to moderate an online community primarily of middle schoolers and high schoolers. But ultimately, you end up hurting the community you're supporting more by not doing things The Right Way™ the first time around. You hurt it even further when you fail to acknowledge that you're tired, short tempered, and should probably just go to bed and deal with it in the morning.

Maybe I just expect adults to behave like adults, but "he didn't feel like explaining it again" doesn't float with me as a valid justification for how he handled the issue. It would have taken a comment and a link to deal with it the correct way. Live and learn, sure, but the attitude reflected in his response appears (to me, at least, with my limited visibility) to be reflective of a systemic attitude surrounding GNOME development. And that's no good.
Perhaps not for honest folk like yourself, but there are obvious ways that it could be used for evil - set up an access point with the same name and MAC address to sniff traffic and/or perform all sorts of man-in-the-middle attacks.
Open Source Is Better Than the Closed Stuff (Until You Hit 1 Million Lines)
The Remixing Dilemma: The Trade-off Between Generativity and Originality
It gets better when you look at his "about" page. All his startups failed, yet he still thinks he has something interesting enough to say that he needs a blog to put all this amazing content he's going to write in the future.

Most people start with freelancing then move on to start ups when they get sick of playing client roulette. He went the other way around. There's probably an interesting story there, something way more compelling than rehashing Tim Ferriss and Ramit Sethi in the most schlocky way possible. But it doesn't look like he'd know how to tell it.
The way I though you spin it is with the gun facing up. The would negate the gravity effect. And yes, people "play" it, stupid drunk people.
How many fart apps do we need?
but again, if it is just about the default behaviour which we debate, one can simply disable the overcommit

vm.overcommit_memory = 2

see https://www.kernel.org/doc/Documentation/vm/overcommit-accou...
Ask HN: Review my startup, JobKaster.com
It's been a long road to get here. I started this journey over a year and a half ago. After spending almost $10K on overseas developers, to learning that I can't do this alone and what a mistake that was, to finding a cofounder as passionate as I am, and to founding an actual team of allstar devs... We're finally releasing JobKaster Beta.

It's nowhere near where we want it to be, but it's time to get it out there.

I would love to get some feedback from the HN community. I know we need more jobs and to update the design. What else do you see that we can improve upon?

Link: www.jobkaster.com

Thanks,

Paul
I don't understand why they felt the need to defy standards with powershell. It's not similar to anything else i'm familiar with. All they had to do was copy bash and port some of the GNU tools.
What kind of gallery do you prefer?
I think it's telling that even before clicking the link, I knew precisely what it was about, even though I haven't used Gnome in years and never knew the terminal ever gained or lost the ability to have a transparent background. Actually, compare and contrast with this bug report https://bugs.kde.org/show_bug.cgi?id=198175 about a similar feature in kde's terminal.
Wait. You don't use hjkl and you also don't use the arrow keys anymore. So how would you, say, move left one character?

Most experienced vim users consider movement using the hjkl keys to be essential to the efficient use of vim. Some even go so far as to recommend unmapping the arrow keys altogether.

As someone who's used vim for about 20 years, I have to agree with them. If you don't use the hjkl keys for movement, you're almost certainly making your editing experience less efficient and more painful than it would be if you just buckled down and learned them.

There's a very good reason for keeping the most-used movement keys on the home row: you don't have to move your fingers off the home row to use them. Arrow keys and virtually all other motion keys are less efficient for this reason.

The more you have to move your hands and fingers, the less efficient your movement will be. Moving your hand back and forth to the arrow keys might not seem so much, but over time it adds up.

The truth is that becoming comfortable with the hjkl keys is no more difficult or unpleasant than playing nethack for a little while. You'll find yourself becoming an hjkl master in no time.
A curl I knew name of Alice wanted to know. I said ALGOL2 in case I could Ada. It was quite an Eiffel, but then a dog REXX, bit me, so I FORT,RAN home #ish.

You could not make me return, not for Ruby or Perls could she Lua me back there.
Last year alone four people died in the US while playing the game. http://www.huffingtonpost.com/2012/09/05/dion-von-mays-dies-...
The problem it solves is the following: Netflix needs DRM to get content deals, Microsoft wants to get rid of Silverlight which Netflix currently depends on, Google wants to be able to play Netflix on their Chromebook. All would much prefer if DRM was painted in the positive lights of HTML5.

Silverlight and Flash are reproducing the browser's HTML5 video functionalities of decoding and displaying videos. EMEs are the minimum necessary to add DRM to this existing setup.

They don't care about iOS or Linux, they're just pushing forward their aligned interests.
That's only 20,000 documents. A good start, I guess. But there's a tremendous amount missing from that collection..
> I've given some thought to how one might work with a MVCC/MGA system ...

Yes, it's an interesting problem. That's exactly what makes it fly paper ;)

Less flexible: suppose your framework is doing dynamic form generation on top of wxPython. You could have a date picker as a radio box item if you wanted. However it would probably not a be a good use of time to support that in your MDA system.

Harder to debug: Usually, bugs in the auto-form-generation infrastructure are "trickier" than the bugs you would get if you just wrote the forms.

A lot of the use cases for dynamic form generation are adequately served by automatic scaffolding in django/rails/turbogears or on the enterprisey side, technologies like Oracle forms and its successors.
Can you name any software that doesn't have an internal API that's not meant for use by 3rd parties?
I recently helped some friends design the bylaws and rules of order for their new startup. None of the founders are working on it full-time, and the goal was to ensure longevity and fairness despite this.

All founders are to receive an equal profit share, and equal ownership, period. (Project governance is separate from company governance, and share ownership is separate from profit sharing percentage. If you quit, you might keep some of your shares, but only current employees share in profits.)

Effort isn't classified by raw hours worked. You're not farmers, tilling in a field, where the more time you spend the more crops you plant. You're white collar creative class and information workers, where one engineer may write 10x the LOC as the other two, but have absolutely no business skills, social skills, or common sense. Your MBA founder may be utterly useless until it comes time to get up in front of an audience and convince them to write you a check. Your designer founder might be idle 9/10 of the time because it takes you that long to implement their research and work. If they're your cofounders and not just your friends, then you picked them for a reason, and they will provide value.

When profit sharing is the only way to get earnings, it aligns your interest better with the company's. You have to help the company earn more money if you want to personally earn more money.

See this old advice from game industry mentor Dave Taylor: http://slashdot.org/comments.pl?sid=57975&cid=5575246 and this Joel Spolsky answer: http://answers.onstartups.com/questions/6949/forming-a-new-s...
Well, if it's the case that there's a 1/6000 chance that the first guy gets hit, it's 5999/6000 chance that the third guy gets it. (Not true, but it's gesturally correct).

So I imagine the odds are much less skewed or NOBODY forgets the spin between rounds. Also, if you don't spin between rounds and you're the 6th person to try it... this isn't really a game of risk anymore.
I find it interesting that you use the word 'guise' in a post defending the code removal. There is still no explanation for the removal except for "wasn't worth it", which is pretty lacking by itself.

And the way you resolve a repeated bug report is to link it to the last one and close-duplicate. You don't even need to respond at all.

In short: What you've explained is more reasonable but it's still opaque and unhelpful; someone involved should summarize why it was removed and if it could be rewritten and put back in.
No one liner? Im disappointed. Did you read the commnt at the end?
If that's their stated goal, then they should just come out with it and let all of the users that spend a good majority of their time in terminals migrate to something else. I have a sneaking suspicion that GNOME usage would take a nosedive if they were to do this.
If you want a workaround, install xfce4-terminal. It's a fork of GNOME terminal and retains all of the settings that GNOME removed, including background transparency. It also appears to be faster.
There's a simple fix for this, and other, GNOME related issues...

Get rid of GNOME!

I can do as much, and be as productive, without using a specific DE, by setting up my GUI to use a simple tiling Window Manager (DWM) along with dmenu.

Seriously, there are a myriad of Terminal Emulators available which are not desktop specific, and configuration is merely accomplished by editing a plain text file.

Why is this crap even on the front page of HN?
All enum types look a bit sad when you're used to the full algebraic sum types + pattern matching provided by a functional language
And that was exactly the criticism, wasn't it? "Overcommit-by-default nonsense". I didn't write the original, just trying to parse it. (And with that aspect I kind of agree, it's a goofy behavior.)

I guess there's another, somewhat social aspect of making that the default: everyone else coding on the platform assumes the behavior is the other way, so I suspect when you set that flag to off, your other software starts crashing on null pointer dereferences because no one thinks malloc can fail.