lnk.to Brainstorming
lnk.to has to relocate, like, this week.
What is lnk.to, you might ask? Well, lnk.to will take a long link, and make a very short link to it. If you have to give someone a URL, it is handier to give them a shorter URL. Have you ever tried to send someone a link to Yahoo Maps? Then, you know what I mean.
Phase 0: Classic lnk.to
So, my think is to re-implement lnk.to, and duplicate the current functionality — you can add a link, see the recent links, see, perhaps, the most popular links, which are all just porn anyway … but this time there’s an option for “private” link.
It’ll be re-written in this format, from scratch, with a proper, clean Perl Object back-end to a MySQL database.
Phase 1: my.lnk.to
Next, we’ll use mod_rewrite to get even a bit more cleverer. If you go, say, to dman.lnk.to, you’ll go to dman‘s lnk.to. This will be a chain of like 25 links maintained by the user dman. dman will have his own RSS export and other neat things that could facilitate export to people’s blogrolls. dman can share his account with friends, if he likes, basically sharing links around.
Phase 2: my.lnk.to/friends
The user model will be extended to allow users to add RSS feeds from which to populate links. “Virtual” RSS-only users will be creatable, and users will be allowed to list out who their friends are. Using that “friends” interface, a handy aggregator can be fashioned.
Behind the scenes, we see code extension — I write a “link chain” interface for Phase 0. Phase 1 requires a “user interface” and management extensions to the “link chain” interface. Phase 2 then sees extensions to the “user interface” …
I have a few other cute ideas to toss in there, which might crank up the fun a bit … dang this day job! Dang this lack of infinitely-flexible server resources! Ah, well, it forces me to think a great deal, measure several times, and make, I hope, one awesome cut!
