Hey guys.
Well, here I am again - closing on a launch of a new big project.
Been debating the name with myself for a long time. The functionality is almost done, the database is filling up, the template is designed and coded. It's time to pick a name. What do you think of this:
feedest.com/.net/.org
Looking for first impression BEFORE you hear the concept, and AFTER.
The concept:
The site is a database driven feed resource. Wait, hold the "Yeah... another one" comments. Yes, there are plenty RSS/feed directories out there, but here's the twist. I realized that attempting to categorize the plethora of feeds is really awkward - you end up with DMOZ-type tree branching deep into sub-sub-sub-sub-categories.
So, in a true Web2.0 spirit I leave it up to the users - tagging, social bookmarking, rating, commenting, searching... Everything is custom and fully automated - the feeds are harvested by a spider (closing on 30000 validated entries) from the web or submitted by users. The feeds are automatically validated, determined whether it's RSS/RDF/Atom/Podcast, added to a database. Then re-crawled regularly to prune dead feeds (three strike rule with automatic alert to everyone bookmarked that feed). All bells and whistles - AJAX, tags, clouds, aggregator, validator, RSS/Atom converter, tools, etc, etc... The template is very simple and clean - very web2.0
Now... Is this FEEDEST or what?
Satellite dev blog taglined "Survival of the feedest"
What do you think?
I've been sitting on a RSS.sc/RSSsource.com pair, but decided to ditch it for many reasons, including "it's not just about RSS", and ".sc = source" notion being derailed by whois.sc backing into whoistools.com. Right decision?
Leo.
Well, here I am again - closing on a launch of a new big project.
Been debating the name with myself for a long time. The functionality is almost done, the database is filling up, the template is designed and coded. It's time to pick a name. What do you think of this:
feedest.com/.net/.org
Looking for first impression BEFORE you hear the concept, and AFTER.
The concept:
The site is a database driven feed resource. Wait, hold the "Yeah... another one" comments. Yes, there are plenty RSS/feed directories out there, but here's the twist. I realized that attempting to categorize the plethora of feeds is really awkward - you end up with DMOZ-type tree branching deep into sub-sub-sub-sub-categories.
So, in a true Web2.0 spirit I leave it up to the users - tagging, social bookmarking, rating, commenting, searching... Everything is custom and fully automated - the feeds are harvested by a spider (closing on 30000 validated entries) from the web or submitted by users. The feeds are automatically validated, determined whether it's RSS/RDF/Atom/Podcast, added to a database. Then re-crawled regularly to prune dead feeds (three strike rule with automatic alert to everyone bookmarked that feed). All bells and whistles - AJAX, tags, clouds, aggregator, validator, RSS/Atom converter, tools, etc, etc... The template is very simple and clean - very web2.0
Now... Is this FEEDEST or what?
Satellite dev blog taglined "Survival of the feedest"
What do you think?
I've been sitting on a RSS.sc/RSSsource.com pair, but decided to ditch it for many reasons, including "it's not just about RSS", and ".sc = source" notion being derailed by whois.sc backing into whoistools.com. Right decision?
Leo.
Last edited:









