jeromeparadis

Very funny article. I've met some clueless "entrepreneurs" during the years but Bob really tops them all.

Notman is an awesome place for hackers in Montreal and I'm glad they plan to double the events space. More hacking with more breathing room. Can't go wrong with this! ;)

I'm puzzled. For the kind of service they want to offer, to have such newbie security vulnerabilities makes you wonder if it even works. It's the kind of flaw that any moderately experienced developer never leaves opened.

My opinion is that the features you are working on are not really specific for a new blogging platform. If you want to test these features in the blogosphere, I would recommend building a WordPress plugin to test the waters without having to reinvent the rest. If that interest you, you can also distribute a template with the plugin included and make a demo (or use it for your own blog) to show it off.

That way, you would be able to focus on what's important to you.

Great timing. I recently began working on a project where I ran into the problem of cross-domain fonts in Firefox trying to serve static assets from S3 to CloudFront. Had to resort using my own nginx proxy through CloudFront for fonts and add an additional request to the page. Finally, problem solved!

Just permanently redirect requests that are missing a prefix to www.mailrox.com. Problem solved.

Seriously? PRC are selling to people with disabilities a software with a Windows 7 tablet: https://store.prentrom.com/product_info.php/cPath/11/product...

And check the options... +475$ for an additional 2GB of RAM! Prices for other options are as outrageous.

I don't know what price Speak for Yourself was selling for but I'm glad they are making these kind of tools more accessible.

Do they have a domain lookup form that we can check without registering?

It happened to me. It happens the drives had a bug where there death time was hardcoded in the drives. Past a predetermined time of usage, they would fail. Of course, I never believed RAID was a backup strategy so I was able to recover.

I've had a lot of lucid dreams in my life. I never did anything special as far as I know. I began having then fairly early, like 7-8 years old and I suspect it happened as a way to take control of and avoid nightmares. Gaining the ability to realize it's a dream and escape by flying was a great way to change nightmares to fun experiences where I gained confidence by deciding to tauntthese nightmares and fly off or whatever I wanted.

From my teens to my early thirties, I would say that more than 50% of my dreams were lucid and were more about fun with friends and showing off. With time, I even gained the ability to wake up on demand from my dream. My cue is that I can close my eyes in my dream and when I open them, I wake up in real life. With practice, I can even close my eyes again and get to sleep again to join back the dream if I do it fast enough. I sometimes was able to wake up and join back a dream this 2-3 times per dream.

Now at 40, lucid dream are much less frequent but happen from time to time.

By the way, I could never decide what to dream about before going to sleep (except joining back a dream). Then again, it never occurred to me it could be possible.

But, it always cool and a joy to experience. I suspect Neo go his idea to hack the Matric because of lucid dreaming!

Most people I talked to about this have trouble believing me it's possible. It's usually the few who experienced lucid dreams who believe me.

I agree. The problem with some design these days is when it focuses too much on form and not enough on function. Great design by definition is form meets function. For apps, a great design means that the visuals don't come in the way of intuitive interactions. The visuals need to support and enhance the user interaction with inputs and outputs. Then you have great design.

I wonder what's the performance hit of having a thread per request. I liked everything I say, but yes, having a single threaded node removes a lot of overhead.

For example, if you need to scrape the DOM content for content loaded dynamically by JavaScript, PhantomJS will allow you to do the job. Or take snapshots of Web sites as they appear to users.

Damn! Thanks. I guess I'll try it with VMWare on my PC.

Has anyone tried running it under Parallels Desktop 7? Thanks.

Why streaming only? I should be able to download it to any device.

Also, don't forget to ban region locking: if you want to change or beat Hollywood, have the movie available as soon as possible to conveniently purchase and play from every country when you want on any platform from. Then you're really changing the game and are a viable alternative to torrents.

Maybe a startup is simply an unproven business and once it makes profit and has a proven business model, you can call stop calling it a startup?

As the CTO of a startup you recently closed an investment round, I think the more appropriate question would be: "with the money you got and your budget, how long can you survive?". I would have no problem answering this to a prospective candidate. Without making sizable revenues or closing another round at some point, a startup will run out of cash.

I've never had problems with the traditional method of the developer enhancing the designer's static HTML file to make them dynamic. further down the road, it's pretty rare presentation tweaks will break the tempting logic.

However, the biggest problem I've had with any designer is the refactoring of html ids and class that breaks AJAX or jQuery code. So the remaining problem, which is the biggest in my opinion, isn't addressed in your approach. Designers still need to be aware of jQuery/AJAX application logic to avoid breaking stuff. My approach to this problem is to use and document custom HTML properties for your jQuery/AJAX hooks. However, it doesn't solve the problem of updating part of the presentation which still relies on the markup structure.

EDIT:

But you still can rely on custom HTML properties to define updatable sections. While I find this approach better, a designer can still screw this by refactoring and omitting these custom properties.

So, relying on IDs and classes through server-side DOM manipulation further acerbates the problem. It's an approach of relying on markup on the server side instead of simply rendering. It adds an additional layer of possible breakage.

I don't buy the first point. Maybe my friends don't share everything sad, but some do share hardships and from experience, Facebook friends can sometimes become and additional support group. For example, when our baby was having cardiac surgery, my wife and I decided to share some of our experience and the positive is that you can keep your friends informed and get a lot of moral support when you most need it. It was awesome. Some of that support translated in real life too. It doesn't replace family or close friends that are present in your real life during these times, but it can be a valuable addition.

Same thing for the third point. Wether with Twitter or Facebook, we've had many real life impromptu meet ups we would never had before these tools because of status updates.

Social networks are tools. What matters is how you and your friends are using these. Of course, some friends only use these for self promotion or self gratification but you tend to notice and behaviors and filter out those updates that never lead to mean something.

On the other hand, if your life is miserable in the first place, I can see cases where Facebook could make your life more miserable. Again, it all depends on how your use it, your attitude and what you make of it.

As a developer who wants to integrate a few new open graph verbs, I'm wondering if this behavior can be bypassed? I don't want a registration wall for people to view our content.

Any developers here know if it's possible to bypass?

Thanks?

Looks quite promising. I've played a lot with node.js, Redis and pub/sub wrappers around socket.io and I came to the conclusion that it's this kind of architecture that does the job of scaling well horizontally until Redis becomes the bottleneck.

I'll dig in the source code as I'm very interested in how it's implemented.

I'm the co-founder/CTO of a startup and I agree: when I'm not in front of the computer coding, I'm always planning.

I'm on the fence on this one. Other startups that went this route simply fired these employees to get back unvested shares or options. To Pincus' credit, he at least gives them the opportunity to renegociate. On the other hand, I agree the fact he may want to keep them instead of firing them sounds fishy.

The problem isn't Microsoft tactics with patents. The problem is software patents.

Same problem on my iPad but I found the solution: use 2 fingers to scroll.

I see you fixed it. Cool. By the way, I've been using Redis extensively for a while and your tutorial is quite good. Congrats!

Yes. I prefer something more lightweight. But SOAP is a protocol. What I propose are standards for common use cases that are not as general purpose.

Example, Facebook API allows querying, interacting with the social graph, profiles, photos, feeds, events, etc. These are use cases commonly used on photo apps, social networks, eventing, etc. But it's proprietary. Now imagine an open source standard similar to that but that can define such building blocks including other scenarios such as contacting a web site owner (about page, contact page), querying/posting articles to a web site, querying/doing transactions with products/services, etc. Once you go through all scenarios, then the problem that remains will be more about agents/authorities/reputation/security of allowing someone to interact with services. With better access for apps to interact directly with content by bypassing the current web presentation layer to avoid spam/fraud.

In part 2, correct me if I'm wrong, but isn't the member you're adding for jobs a key? Isn't the code to see if it's already a member unnecessary? It shouldn't add duplicates since the member's value doesn't change (it's a key). Granted, it's unnecessary to re-add the key to the jobs sorted set as the code does, but the explanation doesn't seem right. On the other hand, you could call zadd again to change the score.

Totally agree.

In my opinion, the problem of separation of data and presentation won't be solved by markup or CSS.

If a Web page is to contain data and a service wants to act on this data, it has to scrape the Web page. Which is even harder with scripted pages. But scraping data isn't a solution. The semantic web may try to have web developers bring sense to data on a web page, but the problem remains. It's just a markup patch. It's doesn't define how to act on that data. Web Intents are just another patch to markup to bring verbs.

Direct access to the data sources with well define methods to act on that data and interact with it (instead of using form) is what works today through APIs. What doesn't work is that there aren't a lot of open standards APIs. Most well used APIs are proprietary and Facebook's a good example. I believe standard bodies should put their brains and efforts on defining API standards. Some standards APIs some clunky, are in use in B2B in the back ends but there's not much of it on the consumer facing Web. We must move forward to push separation of presentation, data and verbs for the whole Web, one small step at a time.

If most use cases on the Web used standard APIs, we would have true separation of content and presentation. We would even have the verbs to exchange/create understandable content. Then, you can use HTML/CSS to adapt a UI to any device with true separation.

That's the way we build apps and sites today and with standard, it would pave the way to a more exciting future.

So one day, if I want to have my own customized UI for that new holographic/gesture recognition device to shop with my preferred merchants, I just have to build an app and I'll be able to browse their merchandise, sort it like I want and finalize a transaction without even visiting their Web site.