715 karma · joined March 7, 2007
I saw something similar on HN a few days ago (http://news.ycombinator.com/item?id=821526), but it didn't have an API. So, I made this one, which is _just_ an API :)
Feel free to use it for your projects. I also open sourced the code (http://github.com/trevorturk/pygments), so you can fork, improve, host your own, etc.
Enjoy!
Nothing personal, but I think there's a lot of trust involved in things like reminders, calendars, to-do lists, etc. Having a bad experience like this with my first try makes it much less likely that I'll give it another go.
"Howdy. Thanks for trying me out. Take a look at http://bit.ly/laterr to use me more effectively. Thanks."
Lately, I've found myself pulling the restful_auth plugin out of my app and seeing what breaks. Then, I'll grab the stuff that's necessary and put it into my lib directory. This helped me figure out exactly what was going on and why. Finally, I trimmed out the stuff that I didn't want. I feel better about knowing what's going on that way, because it is a bit confusing.
I'd certainly say neither solution is perfect, but I still prefer restful_auth approach because it seems more... I don't know... straightforward? Still, the situation could stand for further improvement :)
What really made me decide to drop Authlogic was when I realized it was silently adding validations to my model. I had to dig into the source to find the documentation about that, which really turned me off.
I'm glad people are finding it useful, and I think it's a worthwhile project. I just found that it wasn't my cup of tea. So, I'd encourage people to take some extra time to play with it in a branch before really committing to it. You might consider using the options to make it act like restful_authentication in case you decide to make a change later.
Is there a blog or somewhere to follow development?
I can understand your problem, though. Honestly, I'm not sure that I would pay anything for it, but I'm not a business user or anything - I'm just using it as a slight convenience.
So, for me at least, there's not much value. Maybe I'd pay a one-time fee for some kind of convenience, or to stop ads. I payed $10 for the Instapaper iPhone app, but mostly as a "thanks for the awesome service" kind of thing. I could see doing something similar for this.
Having some kind of ads doesn't seem like a bad idea, and maybe they could be coupons or something? I dunno - maybe something where you got an affiliate deal? I'm not sure how much I would tolerate, but if it was good stuff, maybe a couple a week.
I'm just a joe-average-user guy, though, so I'm not sure how valuable I would be as a way to profit. If there's a way to get after business or heavy users, that might be the trick.
If it's not very expensive to run, perhaps you could open-source it or simply use it as a portfolio piece. I've done some open-source work that ended up benefiting me when I was looking for work. At the very least, that should be somewhat valuable.
Sorry I can't be much more help than that. I think it's a great little utility, but maybe this is a "feature not a product" situation. Perhaps you could try to sell it to Twitter directly...? License it to UPS for exclusive use...?
The way I see it, this has a better business model than a lot of web startups nowadays. At the very least, we've got a slow "burn rate" seeing as how we've spent about 5 hours on the project. As for generating revenue? I think we've got a while before we have to worry about that. We're more focused on scaling the systems than anything right now.
Over 100k clicks on day one? Here's to a successful launch!