kysol

One rule I follow is to: Retrieve, Analyse and Regurgitate Everything.

I was in a store one day when the clerk asked the customer for their postcode, the customer went nuts saying that he shouldn't have to tell them. Three minutes of arguing could have been shortened to "INSERT FAKE NUMBER" if he was really that against giving his real post code.

Next step would be for the app creator to login, see what they can use to create requests for other personal credentials. Facebook password reminder, they get in, then they have the user's DoB and family information (for those stupid companies still using "what's your mothers maiden name" password reminder questions).

You could probably do a fair chunk of damage, but that's all based off the fact that the user would have to be silly enough to still use the same password over multiple services. Yes I know... we've been telling them for far too long, but people still don't listen. They think that if their bank password and their email password are different then they are safe.

Everything was written below a public root, but the shared host didn't allow this, so the next thing you saw was: domain.com/publicroot/index.php^ when the new developer took over. The funniest thing was that they had internal subdomains which ended up public as well, one with full customer listings.

"Never attribute to malice that which is adequately explained by stupidity." - Hanlon's Razor

^ fake path

So many products get launched with gadgets, buttons, options, but they miss the mark on a larger scale, the product itself.

Personally I haven't used it (no real need), so I don't know what exactly it's lacking. A change password option does seem like a crucial thing to have (although I think that I read somewhere that your password is part of the key, and if that changed you'd lose access to everything that was encrypted... I could have read that wrong).

Either way, I do enjoy reading their updates, it sounds like they really do care what the community is saying, and then publicly address concerns/problems. Bug Bounty sounds promising.

First thing I thought of when I read that line was: Well yes, dropping support for older IE versions could be called discrimination, but its needed, and justified :)

What is worse are the ones that use your lack of a degree as evidence that you don't know what you're talking about... it usually comes back to bite them in the ass when their systems collapse due to the issues raised months prior, you know the ones they never listened to you about.

If and when I get around to hiring my own staff, I will be doing it based on what they have done, not what they can do (on paper).

On topic, I've never really released code due to being scared of peer-disapproval, and also paranoid from the public display of potential attack vectors I haven't seen. I don't think that I will ever open source a live project due to these issues.

You should never say "that's bad code" without giving a reason why, and or showing how to make the code better. It's like walking out of a new release block buster movie and saying in a louder than normal voice "well that movie was bad". Anyone that can hear is going to start questioning, "what movie?", "why was it bad?", and instantly they are going to start wondering if the next 3 hours of their life is going to be wasted.

Basically I put this down to a generation of self absorbed twats that like to hear their own voice, and feel all warm and fuzzy inside when ever they grunt something "amusing" to their minions.

A good source for working I've found is Stoner/Doom. It's so washed out and not in your face with insane tempo changes.

Dead Roots Stirring - Elder, Dopesmoker - Sleep, Eternal Season - Glowsun

Also for some ambient stuff take a look at:

Dredd Soundtrack - Paul Leonard-Morgan, 2nd Disc of The Awakening - Send More Paramedics, Mass Effect Soundtracks

I went Perl -> PHP and have been there ever since. Not because I'm too lazy to learn another language, but because it has done everything that I have needed it to do, and when I found something that it couldn't, I looked elsewhere for that one aspect of the project.

Isn't it our role as developers to push the boundaries of our chosen language? I'm pretty sure back when Javascript was being thrown around, they wouldn't have imagined what it is today.

Trying not to sing praises, and throwing fuel on a fire that should have died a long time ago... To each their own.

For me I was on a business trip where I fell ill prior to the flight home. Lets just say that it wasn't pretty, my girlfriend picked me up from the Airport struggling to stand up. The next week I wasn't able to eat anything surviving on water.

Seeing that I consumed an unhealthy amount of coffee daily, and how I hadn't had one in a week, I decided to make the break while I could. I was already weak from what ever I had picked up on that trip, but it was nothing to the next few weeks. I was lucky to only get mild headaches, but the lethargy and the sleepless nights drove me insane.

Having read this article, I'm now re-thinking what I eat as well. I too challenge the heat of my curries... and thanks to desk jobs I don't get out that much. Looks like I'll be changing things shortly.

One kicker that has happened to my health since this change, an ailment that I had never had prior to the removal of coffee, has caffeine as a way to help reduce the effects. My body... hates me.

My current theory about movies at the moment is that all these crappy movies get made just to put a trailer to a big "block buster" at the start. After cost + advertising - box office revenue is taken into account, the end cost is probably less than it would cost normally to mass market the initial trailer. -- The reason why bad movies get made :D

In the current TL;DR user ecosystem, anything wordy, or involving use of page scroll has already lost the attention of most. When was the last time you heard someone complain that an image was too big (yes I know it happens, but that's either due to poor UI or just a jerk wad wanting to complain for the sake of hearing their own voice).

Having been one of the ones that landed on your revamped page, I honestly wouldn't have stayed around for too long on the original version. I would have skimmed through the list to see if there was anything relevant to myself, opened a new tab for each one, then left. The images, although they didn't give much to the content of the page, made it more enticing to click through, even on articles that didn't interest me.

What you might want to do is follow-ups, get people coming back. A lot will probably bookmark to read again later when they are interested, but those that have already got what they wanted are now lost unless you hook them again.

Google+ is alive and kicking (although the HN Community is constantly getting bombarded with people asking about "Hacking", I would say that a majority of the users I've seen are worth associating with (compared to FB)). There's a somewhat active RasPi community there now posting articles about everything and anything RasPi related. You should probably head over there and give it a go.

Thanks for the original article as well.

  The publisher of "PRODUCT" has been notified and is
  responsible for delivering this product. JetBrains s.r.o
  will deliver the product within 48 hours.

I'd guess that the tube site is getting some sort of service fee for allowing the sites to have a "premium" service, as well as some sort of kick back depending on the conversion rate from leads generated by the content (why the premium videos are generally listed higher).

If you think that 1) the videos are legit and that guy just happened to stumble across those two girls in the woods, then you're also going to also believe that 2) most of the content is amateur. - It's a sad truth that the industry preys on the weak minded.

I'd say that a fair amount is self-uploaded (via content bought from providers, or produced specifically for the site), but a majority is uploaded from other content houses to try to promote themselves. Think Free to air TV... average crap shows, filled with 80% advertising.

The biggest issue back in the day was Content licencing, which with today's whole DMCA crap, I would expect it to be far worse on a user-generated content site. If you licensed images for a specific domain and they appeared on another domain you owned, you would have legal representatives sending you emails (most of the time you would just do a deal with the owners and extend the license). This wasn't the result of the content being found by the owner, this was from organised firms that were hired just to scan images and videos looking for specific sets that they represented. When I hear about user-generated content sites these days, I think of one giant nightmare when it comes to content.

It's easy enough to throw something together and try to make some money from advertising, but to be successful in that industry boils down to 3 things. Traffic, Quality and Retention.

- You won't get subscribers without Traffic (fairly simple). If you think that you can get organic traffic off the bat, think twice. You'll need to set up some deals with guys who own key domains to have them funnel traffic through to you. (I don't know if this sort of market still exists, but I can't see that it would have died off)

- To convert the subscribers you need Quality or unique content (which the successful sites will usually do in-house or through companies that will work with them to produce unique content). If you're going to throw up a few galleries of cheap $5 content sets that everyone has seen before, you're not going to get the conversion.

- Retention, is a tricky one. Back in the day you used to count on the subscriber, doing a one off then forgetting stinging them with a re-bill or two, or three. Then when they got their bill they were too embarrassed to challenge they usually silently cancelled. As I said before, around the time I left, Visa was starting to really crack down on charge backs as subscribers had actually grown a pair and started wanting their money back. The only way to fight this is to offer what you advertise and more. You won't keep everyone happy, but you'll see a nicer charge-back rate.

For the record, I was a coder, I wasn't the guy behind the camera, or even the guy that designed the sites. I dealt with the systems, and kept them running. It's not a glamorous title to throw around at dinner parties, but it does bring up some interesting conversations when you start talking about the things that you seen in the industry.

Considering it's an IE specific tag, I tried with IE and gmail, I couldn't get it to download anything, even when allowing remote images. IE was too bugged out trying to render gmail (not hating, stating).

I do agree that the bite looks like a head, but it doesn't look the same as the one in the link above, especially when you take into account the missing "Steve Jobs" and "1955-2011".

I'd put it down to a freakish break line causing fragmentation around the bite. Backplate looks identical to mine (minus the damage).

Coding drunk is not for everyone, it won't make you into a super-coder that can do everything magically, but if you're like some of us, where perfection limits production, being tipsy or totally drunk breaks those barriers and allows you to just do the job.

<div id="yo-dawg"> <div id="i-put-div-in-your-div"> <div id="so-you-can-div-while-you-div">This site built in Muse (code name) by Adobe®</div> </div> </div>

I don't think the document was anti-backwards compatibility, just well, you know clients... they are always wanting the look like a Porsche, while still driving a rusty old pick-up.

They are just trying to justify the lack of support in an easy to swallow way. You want support, expect to pay for it, but realize that the money you're paying will only benefit a small percentage of your audience (you included).

Everyone's had (and still get) those clients using IE5, saying that if it doesn't work for them, it won't work for the rest of the internet.