chris_vannoy's comments

Yeah. Today was kinda unexpected and the queue is a bit backed up.

Working on it.

Thanks. Should be all patched up now. A lot of the user management stuff is a work in progress. After all, didn't have many users before today.

Thanks so much for pointing it out!

Hi. I'm the creator of WhatTheDeploy.

That's certainly on the possible roadmap. Right now, I'm trying to determine the best way of accomplishing that without requiring someone to poke a giant security hole in their application.

It can be accomplished right now if you're OK with a security hole by creating a separate dummy account and enabling Basic Auth through that single account.

Very much open to better suggestions, however.

Better yet, don't send cold recruiting email. Know who you're recruiting and build a relationship so they know who you are.

It's a corollary to what patio11 said elsewhere (https://news.ycombinator.com/item?id=7917255), but more than that, if you build a relationship ahead of time, all of the sudden you don't have to do all the bullshit interview stuff that comes later.

You already know what the candidate's like. You already know their technical skill level.

Then it just becomes about fit.

No whiteboards, no brain teasers, no bullshit.

Send from MMS to email, certainly. It's all just email under the hood.

I use this as an input method on http://montabe.com, for instance.

But going the other way - sending an image via SMS/MMS to a user (which is what that post is about) - is a totally different animal. One in which you'd likely need to format specifically for different carriers and the like (and that's best case).

Actually, my guess is the every-four-weeks bit is to goose revenue.

With monthly, you're getting paid 12 times a year. With every four weeks, you get paid 13 times.

It's a nifty little sales trick. Most people (including me) automatically round four weeks up to a month before thinking about it.

With Ruby, anything you can call from the command line can work via system() (http://ruby-doc.org/core/classes/Kernel.html#M005971).

Alternatively, you can wrap into a gem with a C extension and call it with all the Ruby goodness you should expect (recommended route).

Pseudo-code (wordier than it need be):

class MyModel

  def self.ocr(file)

     result = system("my_ocr_prog", file.path)

     return result

  end

end

A good example of a gem with a C extension might be RMagick (http://github.com/rmagick/rmagick/tree/master/ext/RMagick/)