Feed is a social media feed on top of a GitHub repo. It expects the repo to be in a particular format, then renders it. Here's an example:
https://wideopenweb.github.io/feed/index.html?owner=benofben&repo=benlackey-feed
An author creates a post by commiting to their GitHub repo. There is a particular format they must follow. All posts go in a folder called posts. Each post has its own folder. A README.md in that folder contains the post body and may link other content in that same folder.
A consumer reads a post by accessing an feed server. That server interacts with the GitHub repo the user passes as an argument. The server renders that content as HTML. The feed server is open source and available on GitHub. Anyone can run their own.
- GitHub Login - Does it have to be token or can it be that web UI one?
- WOWA (Wide Open Web Auth) - Perhaps built on OAuth. Open meta layer over social providers.
- Comments - likely auth'd with GitHub. I keep wondering if this can be done cleverly with forks and PRs, though that's very GH dependent.
- Intermingle multiple feeds
- Better date handling -- maybe show created and updated but sort by updated?
- Improve Preview -- right now it just says feed. Could have information on the feed or show the title and image from a particular post if one is being linked.
- Batch import from Facebook
- Sync with Facebook
- Evaluate GitHub lock in - perhaps move to plain old git and/or consider portability to GitLab
