jeromeparadis

Probably not the target customer indeed. Try doing 3 legs in 3 different same coast cities in a single day for in-person meetings. It's only possible with private jets as you can dictate the time to depart.

It's rather the sign of an abusive HN-specific editorial title. The op read the article way deeper than between the lines.

Maybe they should have shown a bunch of children around the iPad brainstorming enthusiastically on how the next move to program on the robot?

I find the service interesting. But, I suppose lead research is done through outsourcing somewhere cheap because at 800$ per month for 20hrs/week, how can they make a profit? It amounts to about 10$ an hour.

At least, these scams would ship you something! It would remind you they decided to scam you by sending you an overprice item. Justfab got the genius idea that it is much more profitable to have apparently nicely priced items that you won't order or receive but still be charged for.

I don't bother with backups on Windows or Mac since I made the wise decision to backup every computer, Mac or PC using Crashplan to NAS and cloud.

I would have once been mad with this Microsoft feature removal. However, I've come to realize than neither Microsoft's or Apple's backup solutions satisfactory for my needs. Time machine is arguably better... until it decides to stop working. Since I've been on CrahPlan, no problems on any computer. I've had one laptop that shorted since then and it was easy enough to recover my files.

I had helped a friend report a security vulnerability to Facebook. It was similar in the sense that it allowed anyone who knew 2 Facebook usernames (easy to do) to post a private message to someone that would appear to come from a friend. You didn't even need to be authenticated on Facebook to do it and could do post it from any machine on the Internet.

At first Facebook was similarly dismissive that it wasn't a bug. My friend pushed a bit to convince them with additional details and examples of how it could be easily used for exploits. They finally saw the light. The bug was fixed and my friend got paid $1K which wasn't much for the bug's seriousness. In any case it got fixed and my friend got acknowledged so it's OK.

It's a bit of a pity, thought, that they didn't see it to be serious at first. I would have expected any mediocre engineer to skip a hearth beat when learning of such a bug in their system.

These sound awesome. Any pointers on how to modify these for Ubuntu machines?

There's Picade, a kickstarter project with Integrated screen. They're a late bug give regular news on the project.

http://www.kickstarter.com/projects/pimoroni/picade-the-arca...

However, the linked project should work if you're TV has an HDMI or DVI connection.

Now let's fire up lynx which I haven't used since before IE 4.

That's why I always paste to my text editor and copy from there before pasting anything from a Web page.

Awesome! I've been waiting for this for a while.

A more appropriate title would have been "What it's like to wake up after dying". Glad he's feeling great.

He's mainly lucky someone who know CPR was around soon after his cardiac failure. That's the main reason why he defied statistics and it stacked odds in his favor. Otherwise, more than 4 minutes before intervention and you're almost guaranteed to be dead or at least brain damaged.

Which is the reason I stopped playing with it. I'm in Canada. As so many of my friends from different countries were on it but not from the US, I suppose the drop may have been quite substantial.

Very original! Although it's a joke, it boggles the mind he actually thought of it and implemented it. Kudos!

HAProxy works Wellington for node.js websocket apps.

Yeah. These practices are plain stupid and I do the same. YOU tell me who you are and I'll call you. Don't even give me your number because it could still be a trap. For example, if it's a credit card company, if I can't call back at the number on the back of the card to know what's this about, they're doing something wrong.

What he said... That's what I've been doing since the 90s. It works well.

And, to answer the question what steps to do when they don't pay: not much you can do other than asking. There aren't any worthwhile legal resources for businesses or freelancers to be paid.

However, to not get there, make sure the payment schedule covers your work hours including profit and if they don't respect the schedule, stop working and mention there will be a delay in delivery. As he said, choosing well your client by avoiding people who are too difficult from the start usually avoids the worst kind of clients. As soon as your guts sees a red flag, don't ignore it and walk away. Your instinct is rarely wrong when sizing trustworthiness.

I think she's on to something with fun educational DIY robotics projects. I wished my sun was a bit older, but I'll probably chip in anyways.

Well, since were talking about a technique to avoid email rendering limitations, just add some clicks to the Web UI to allow digging in further.

Thanks for the answers! Very helpful.

What are the clouds of your choice other than Azure? I don't see them mentioned in the tutorial. I'm on Windows but my Python projects are on a Ubuntu VM and I push to AWS, Racksace Coud, dedicated servers, etc. My project can also interact with the shell, phantomjs, node js, Redis, etc. How can I benefit from the VS IDE for my python projects? I've seen mentions of Linux clients but not sure what they mean. thanks. I'm dearly looking for a good IDE with debugging support.

Personally, I like the approach of the tutorial.

It starts with the amount of code you would usually write if you were to write an API by hand and then simplifies things along the road. At the end it makes it clear how the framework can be simple to use while you've learned how to use it behind the hood if the magic needs tweaking.

My bad, your webhook proposal, thinking of it, would indeed facilitate immensely the integrity between our database and the S3 files.

It would require us coding a scheduler. But it would be easy to write and would be way more efficient (than what we can do today). Would simply need to check your notifications against our database and accordingly clean up/validate the files in the S3 buckets.

Great stuff.

Yeah, we'll manage it exactly as you mention and do some cleanup.

As for the idea of webhooks, in our case, we wouldn't need the content, just the meta data. That's what we already do anyway: we only store references to the S3 files we created. The idea is that it simplifies be able to run multiple Web server instances by having this user generated content offsite.

My concern was really more about us confirming what we receive to you so you could do the cleanup of non acknowledged files instead of us doing it. What you are suggesting is an additional verification that can have value but doesn't address the question of constituency between what ends up in our S3 buckets and what we end up being aware off in our app. In any case, no big worry but I'll email you details.

Hi!

Thanks for this update. This addresses a great security concern so that our buckets cannot be abused (especially filled) from outside of our apps.

I still have a remaining concern which is more about consistency. If you authorize users to upload for your app with a policy, they still can upload anything to their will without your app even knowing about it. Sure, the new policies can ensure that they won't be able to read what they upload if it never reaches your app but they still can upload huge amounts of data in your buckets without that data even being used or known of by the app.

I sure could write a backend scheduled task to clean up unknown files in our buckets.

But, what I would eventually like to see is a way to acknowledge that file handles we're received by the app. If, after a specified timeout no acknowledgement has been received from our app, then these files would be deemed dirty and you would then be able to clean up your servers and our buckets from these files.

Does my concern make any sense?

In any case, thanks again for this update. This remaining concern can be worked around and this update really mitigates the risk of someone wanting to abuse our buckets for malicious reasons.

Nice! It takes dedication to release something like this. The look is awesome, the atmosphere sounds creepy and intriguing. I haven't played it yet but looking forward to purchase it.

I suppose it really depends on the use case. For example, there aren't probably any tables corresponding to an API call. If I wanted to collect stats on different API calls and other stuff not related to my models, I would prefer avoiding a database count update and would rather make a single incr call to a Redis key.

Well, to be fair, the cached counts are incremented by Redis through the incr command. So, no pre-calculation here. It can be interesting also to aggregate metrics of floats using the incrbyfloat command.

Your response time is awesome!

I'm about to implement filepicker.io for a project and really do not mind any kind of server-side integration that would avoid chances of malicious users abusing the service against our filepicker.io or S3 usage.