andreashappe / narcissism
- Source
- Commits
- Network (1)
- Issues (0)
- Downloads (0)
- Wiki (1)
- Graphs
-
Tree:
c7ca522
commit c7ca5227e6e562935d70580a9e09faa8fb985f59
tree 70555c5331193b8ae19c112afa9d4007a4139458
parent 6aa1d220b36580080d43b1ad1654ef6b00acdb15
tree 70555c5331193b8ae19c112afa9d4007a4139458
parent 6aa1d220b36580080d43b1ad1654ef6b00acdb15
| name | age | message | |
|---|---|---|---|
| |
.gitmodules | ||
| |
README | ||
| |
Rakefile | Thu Oct 22 13:19:43 -0700 2009 | |
| |
app/ | ||
| |
config/ | ||
| |
db/ | Thu Oct 22 14:05:59 -0700 2009 | |
| |
doc/ | Thu Oct 22 13:19:43 -0700 2009 | |
| |
public/ | ||
| |
script/ | Thu Oct 22 13:19:43 -0700 2009 | |
| |
test/ |
README
== Introduction So you had a blog and stopped to update it regulary. Then twitter started to attract you and the blog finally died, still you cannot bring yourself to kill the thing off as you are thinking "maybe I'll write some pages that somebody might actually find useful and I'd need some sort of wiki/blog to publish it". May I present you.. Narcissism. It is a simple Rails website that captures a twitter stream and presents it in a blog-like fashion. In addition simple wiki sites (through Textile) can be entered to the system and are integrated into the user's timeline. == Getting Started 1. get the software from github 2. install rails and all needed gems 3. if you're thinking about installing this on a production system: STOP! 4. otherwise configure config/twitter.yml 5. setup some periodic thingy (ie. through cron) that triggers twitter updates So far there is no public access control and there are no captchas. This makes this software totally unsuitable for public deployment (which might change soonish). == Features * twitter account leecher * add wiki pages through textile * erm.. yeah, that's it for now == TODO In no particual order, patcher are welcome :) : * user management/prevent the public from entering stuff * captchas * comment support * tags/categories? * support blog posts (ie. convert from wordpress) * actually provide a REST resource that triggers twitter upgrades * allow two-way communication -- ie. update twitter from narcassism * full-text search for everything (wiki, blog, tweets) * move twitter config into configuration file * export sitefeed * export RSS feed * blockify subsequent tweets into one bubble (to minimize space usage) * convert rest to HAML (and do some serious code restructuring) * make it less ugly October 2009, Andreas Happe

