rubynerd

SMTP was a piece of cake (apart from a weird SSL bug, which took up the majority of my time), but IMAP does look significantly trickier from the RFC

I would love to be in a place where IMAP isn't needed, and I plan to use my own API's for the client applications

Thank you for the code, in any case, it looks like a good laugh to read :D

I've had great fun looking at AirTraffic from gaug.es, although thank you for the recommendation for Mixpanel, I'll look into it

Thank you for reporting it though

Any criticism is good right about now

It's very much a competitor to GMail, in that it's essentially GMail with some filtering and IMAP magic on top

To start with, my problem that I am attempting to solve is notifications for things I'm not interested in in the middle of the day, which I have attempted to solve with notifications + funnel

The distinctive advantage is the ability to modify when email is sent to you, plus the ability to filter different types of email (transactional, newsletter, human beings)

You're right on the unprofessional copy, I'm sorry, and the punctuation mistakes are simply a flaw in my English (It is my first language, there is no excuse)

I spent 3 months on the backend making sure it receives email perfectly, and securely, and I could not find a mail server written in Ruby which I could modify and add features like Funnel to

It supports IMAP, IMAP is the primary method which devices will retrieve email with (ActiveSync is patented by Microsoft, who would like licensing fees)

It will also support Android, as in, the native mail app on Android, I am just prioritising iOS first because it avoids competition with native GMail, which as one person, is nigh on impossible

Yes, it's primarily geared towards iOS devices for now, because I don't think I can compete with the GMail + Android paring yet

Thank you very much for the criticism, I'll do some changes now

EDIT: changes are live, viva la full stop.

As for the icons, they are a very tricky subject, I intended to create symbols for major features such as Funnel and Triage and have common icons for everything else, but it seems I've failed there

Which icons don't you like?

This is quite a big issue, what OS/browser are you using?

Design is something I find quite difficult, and I usually keep my head in the backend

I really, really, really want to hire a designer so I can stay there, but being self-funded makes that impossible

It's an absolute nightmare. It won't stay alive for more than 10 minutes without some form of OpenSSL error, and I've even managed to create some kind of weird condition where pure bytes and other garbage are read off the socket

What really concerns me is the lack of documentation for this. It's SSL, out of any piece of Ruby I would like it to be the most documentated/most maintained/easy to find help with piece, but instead, I've been stuck with this giant piece of broken code for three months with no idea where to et help

The point being, it's all very well saying massive companies with engineers on tap are supporting these technologies. But for a startup with one person at the keyboard, they are figuratively screwed. I'm still holding out for the possibility that there is somewhere in the world someone who understands how to securely handle OpenSSL sockets in Ruby, I really do.

I refuse to go to MVP with a server which is raising exceptions left right and center, and at the moment, that's gonna kill the startup dead in its tracks.

Computing, we still use VB6 for coursework, Chemistry, everything is photocopied with ye olde dates on

Props to him for attempting to introduce variety into lesson plans, thankfully, today is the last day of copying out photocopy masters from a whiteboard onto paper

The best thing? I think I've lost the majority of marks for using RSpec instead of 100 screenshots

Are session cookies OK are under this law?

At the moment, I have a terrible, terrible portfolio/resume, so getting a job isn't on the horizon yet, but if I do I'll be learning to drive pretty sharp-ish

At this precise time in my life, one of the most important things in my life is getting code written for a portfolio

I'm in the middle of the sticks at the moment, but hopefully to a town with a train link to London, which would be amazing if I could pay for trips to London for meetups :D

I don't have an account, so I basically just closed the tab

First impressions, your product allows me to give people e-gifts that are actually worth something instead of pixels

But, the whacking great "Facebook" button makes me kinda close the tab

Give me the ability to import my iPhone's contact book (Protip: iCloud is a single page app backed by some client-side MVC framework, so basically a free JSON API once you've got the login stuff worked out), then overlay reminders x days in advance on my iCalendar to go to your service and buy a gift, then you can handle everything from there

But, I'm always an edge case :)

Good luck, I hope you work everything out OK

Freaky benchmarks + closed source + that attitude => closes tab

Nginx recently had a security advisory, about a hole which was found by a third party. I doubt this would happen with G-WAN, which leaves me feeling scared.

I can't just trust a binary from someone which states that "protecting the NSA from injecting backdoors because it's too hard to track who put them in" is a valid reason for not open-sourcing the thing

It shows a very good 'State of the Machine' at the current moment in time, but it does feel slightly like candy

One major, major thing I would add to convert this into something I would use for my 'strtup' is time, and the ability to see what happened at a time, or event

I am basing this on the 'live demo', but it seems like a report on what's happening now, which isn't really that useful in the grand scheme of things. For instance, if I drop a new feature or blog post on HN, I want to see what effect that will have on my application, and what users do and where they go after first opening that email or clicking on that link

This may seem insane, but I promise I am going somewhere. In my GCSE Physics exam, we were given energy diagrams, and told to do things with them like fill in the blanks. On the left, there was a kind of 'origin', which represented the energy given out by an object. So say a lightbulb gives out 80% light, and 20% heat energy, that would be represented by a 10cm wide arrow on the left hand side, which then breaks into a 8cm wide arrow pointing right, and a 2cm wide arrow breaking off from the main chunk and pointing downwards, to represent waste energy.

This loops back into analysis, say when Flow was first posted onto HN. You could break that down into signups, showing where people dropped off, what pages they viewed and where they went from there, and then render that in a pretty diagram, hopefully showing you where the friction points are

I do also have two minor issues I picked up on from Flow, and I suppose Mixpanel

Given it's a free product, which may or may not have the aim of pushing users into Mixpanl, I could not find any obvious links to https://mixpanel.com on the main page. Which was kind of sad, I wanted to read more about Mixpanel and what the bread-making product does, and how it sustains this free app

Secondly, I emailed Mixpanel back in January asking about details for an internship. Since then, I have received a grand total of nothing from them. Which is sad, metrics and user statistics are two things I thoroughly enjoy, and I would love to work with Mixpanel to build things like this

Working with him to do what? He pissed about a little with WebInspector, it doesn't make him a security consultant

He threatened to do more damage to your site, why wouldn't you suspend someone like that?

I would be very concerned about this backfiring, but, I would hack Rails a little to report when anybody attempts to use this glitch and wire that into Hubot(TM), so if he does attempt to use this same hole again, the devs are warned instantly

One feature I would love to see in RubyGems is man pages for gems, because man pages are underused and I can't go and look Github documentation up quickly as I have to break out of my dev box and go and open Chrome and look it up there

I would still use https://github.com/rtomayko/ronn, simply for the pretty HTML pages though

iCloud doesn't poll your phone every damn minute to check if it still has that number's SIM card inserted

The author even acknowledges it's a bug, and still calls it a "lock-in"

Secondly, iMessage and SMS messages are, with the exception for colourblind people, very distinctive: if you can't tell the difference between blue and green, you have an issue. The fact that it took a director to figure this out astounds me.

Thirdly, the author's insinuation that the senders iPhone "intercepts" a text is false: the phone knows there is an iMessage compatible device associated with this number (consider the recievers service being cut, but they keep the phone on WiFi), and so it sends it as an iMessage. It's not actively going "Oh this user has swapped to an Android device, let's piss him off in every way possible and treat this text as an iMessage, that'll get him!", it's working with the data it has in an attempt to be helpful to the receiver: they've run out of PAYG credit and can no longer sustain a data connection, but are in range of WiFi, so iMessage still stays online. It is trying to be helpful to the user, not a massive wanker

Admittedly, they should check to see if a SIM card is still in the phone on boot, then register with iMessage

In comparison to BBM, the only reason this is considered "lock-in" is because texts and iMessages are in the same place instead of two separate places

Disable iMessage and turn the damn iPhone off for a week, then if that fails, run to an Apple Store

Also, don't assume the worst, you will somewhere along the line regret it, and wonder "what if". You don't want to be on your deathbed with regrets

P.S. if someone reading this has access to Apple's fabled Bug Reporter/Radar, file this behaviour as a "bug", or, if you're in a baiting mood, "lock-in feature". I would if I could.

Assuming this is an actual API, consider a rouge script slamming your API, whoops, your main app is out as well, nobody is signing up for your service.

Assuming this is for backbone/batman/other-generic-clientside-framework, nope. Too much JavaScript makes everything seem sluggish, and I really don't want to reimplement everything twice (once in Rails for conventional browsers and for people who disable JavaScript, second in client-side MVC)

You missed the small link at the bottom of the pricing grid