I think you have a solid idea, but your implementation is wack. If you can code, why would you use some platform that has absolutely nothing to do with your service? Its just going to create problems down the line. Ex. URLs.
I honestly suggest, you spend about a week implementing this yourself. Its trivial.
samataro: I'm working full time and using laconica was simply the quickest way to get from the idea stage to up and running. If imgfave take off I'll most likely rewrite it from scratch.
You should be sure that "rewriting from scratch" is going to give your users some concrete benefit that will make them like your site even more, and you should be sure that "rewriting from scratch" is the easiest way to give your users those benefits.
I would understand if this was something big and untested. But IMHO, when a project is as simple as yours is, there is no reason to do it right (not perfect) form the start. There are things you will regret if you start to gain traction.
Comments
I think you have a solid idea, but your implementation is wack. If you can code, why would you use some platform that has absolutely nothing to do with your service? Its just going to create problems down the line. Ex. URLs.
I honestly suggest, you spend about a week implementing this yourself. Its trivial.
samataro: I'm working full time and using laconica was simply the quickest way to get from the idea stage to up and running. If imgfave take off I'll most likely rewrite it from scratch.
Why?
You should be sure that "rewriting from scratch" is going to give your users some concrete benefit that will make them like your site even more, and you should be sure that "rewriting from scratch" is the easiest way to give your users those benefits.
I would understand if this was something big and untested. But IMHO, when a project is as simple as yours is, there is no reason to do it right (not perfect) form the start. There are things you will regret if you start to gain traction.