3 ms·
I've always liked this idea. However I am not sure about "perma-shortlinks", for discovery on other sites as the means of networking and discovering content. I
by tomaytotomato 7mo ago
I've always liked this idea.
However I am not sure about "perma-shortlinks", for discovery on other sites as the means of networking and discovering content. It seems clunky to maintain as it requires a human or some automation to curate/maintain the links. If a blog removes a link to another blog, then that pathway is closed.
It would be cool if we could solve that with a "DNS for tags/topics" a - Domain Content Server (DCS) e.g.
1. tomaytotomato.com ==> publishes to the DCS of topics (tech, java, travel)
2. DCS adds domain to those topics
3. Rating or evaluating of the content on website based on those tags (not sure the mechanics here, but it could be exploited or gamed)
You could have several DCS for topics servers run by organisations or individuals.
e.g. the Lobsters DNS for topics server would be really fussy about #tech or #computerscience blog posts, and would self select for more high brow stuff
Meanwhile a more casual tech group would score content higher for Youtube content or Toms Hardware articles.
This is just spit balling.
- Pooge 7mo agoDidn't you just describe a social media feed? The whole point of syndication is that it's curated by humans (you, if it's your own feed).
- tomaytotomato 7mo agoYes and no A social media feed implies 1(n) curated by 1 algorithm hosted on Facebook/Twitter/Instagram What I was thinking is: - foo.social - bar.social (tech curations) - java.bar.social (sub curated Java list) All these DCS (domain content servers) would be polled by your own local client Your client can then aggregate or organise how it shows this feed e.g. I could have a trending aggregator for situations where a blog post is shown on multiple domains (sort of shows virality)