Needs a name (smoke-signals?)
This is an open source, hosted, bi-directional bridge of Tent and RSS. It would be hosted somewhere, and installed as an app against your tent server.
Using Python, because it doesn't make us claw our eyes out. Likely with the Flask framework.
- a screen to enter your entity
- server does v0.3 tent app registration
- needs access to status posts, and perhaps essay posts.
- dashboard lets us add in an RSS feed url
- app needs to fetch it and parse it regularly (30mins? hour?)
- feedparser is pretty good at this: https://pypi.python.org/pypi/feedparser
- needs to keep track of last seen item (by item guid? many feeds suck at guids...)
- on new items, create a new post on the users feed
- for microblogging, it could be a status post with the feed item title and link
- it could create an essay, with the feed item content as the essay content
- it could create a new rss-archive post (pick a name), if the user didn't want to publicly share it.
- dashboard should let a user generate a feed from his status (and essay?) posts
- optionally allow filtering
- ex: only create feed of posts with the word "#feed" in it
- not needed at first, but cool idea: Feeds based on tag posts. tent/tent.io#183
@BenjBouv If we have to choose between the two, I would choose the Public Mode option, simply because it seems to me to be the most useful. I doubt that 99% of users will be using this for "firehose" style RSS feeds, mostly for their personal blogs or favourite writers. So it shouldn't be much of an issue to just automatically post them publicly without user intervention.
Though one could always implement both then give the end user the option :) The latter idea of notifying if a feed is already in use is certainly a good idea, though I'm not sure how it is technically possible with a decentralized service like Tent, unless you can find a way to crawl Skate.io when the API opens up.