Top

A Fresh Cup is Mike Gunderloy's software development weblog, covering Ruby on Rails and whatever else I find interesting in the universe of software. I'm a full-time Rails developer and contributor, available for long- or short-term consulting, with solid experience in working as part of a distributed team. If you'd like to hire me, drop me a line. I'm also the author of Rails Rescue Handbook and Rails Freelancing Handbook.


Navigation
« Double Shot #348 | Main | Bug Trackers I Have Known »
Monday
08Dec2008

Double Shot #347

DateMonday, December 8, 2008 at 1:00AM
It's another new week, full of hope.

  • simplepay - Rails interface to Amazon Simple Pay payment service.

  • Using Google App Engine as Your Own Content Delivery Networkm - A useful idea if your traffic isn't too huge.

  • TortoiseGit Challenge - The GitHub folks want to see better Windows client software, and are offering a bounty for it.

  • CSV Mapper - Library to simplify importing CSV to Ruby apps. I may have a use for this soon.

  • Ruby on Rails Hosting Round-up - Always a popular (and mildly controversial) subject.

  • RPX in Action - If I ever have to implement OpenID, this looks like a good way to go about it. I'm hoping I never have to, though.

  • KnockKnock - Google authentication API for Ruby. As far as I'm concerned a better bet than OpenID.

  • Compass - A Sass-Based CSS Meta-Framework. Looks interesting, but I think that might be just a bit too much abstraction layer over something I barely understand anyhow.
    • AuthorMike Gunderloy | Comment2 Comments |
    in

    Reader Comments (2)

    I'm curious, Why don't you like OpenID?

    The knock-knock project looks useful, but requires one to type in their Google password. Google has an authentication API that is safer and more secure. I wonder why Knock-knock didn't use that....

    December 8, 2008 | Unregistered CommenterBenjamin Thomas

    I wrote about OpenID issues at http://webworkerdaily.com/2008/05/21/openid-a-contrarian-view/

    And I'd assumed (silly me) that KnockKnock was using the authentication API. If not, they're part of the problem, not part of the solution.

    December 8, 2008 | Unregistered CommenterMike Gunderloy

    PostPost a New Comment

    Enter your information below to add a new comment.

    My response is on my own website »
    Author Email (optional):
    Author URL (optional):
    Post:
     
    Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>