5 ms·
Well, it could enable a few things: - Fetching the latest updates from a network of your peers selectively, a bit like RSS feeds - Merging histories from your
by jka 5y ago
Well, it could enable a few things:
- Fetching the latest updates from a network of your peers selectively, a bit like RSS feeds
- Merging histories from your peer network into a linear format (straightforward since there shouldn't be any merge conflicts between empty commits)
- Construction of branches arranged by topic by cherry-picking relevant commits
- Bisection of content would be available in order to navigate conversation history
Also it'd federate fairly naturally, and is quite network-safe because it'd only require the presence of hosted git repositories (in other words: few network services and installation dependencies required).
Only an idea - wrangling and herding the commits could be the tricky part, in practice (the per-topic branches in particular are a half-baked idea).
- Minor49er 5y agoFor your first points, why not just use RSS feeds? Otherwise many blogging platforms support multiple authors for a single blog and categories/tagging which can also achieve something similar
- jka 5y agoWell, in comparison to RSS: git's fairly good at negotiating and transferring a subset of relevant commits over the wire, whereas RSS feeds (naively, as I understand it, and without really considering ETags or other magic) tend to be rendered server-side as a list of posts, regardless of whether client(s) are already up-to-date on the latest content.
- Minor49er 5y agoSome RSS feed generators have ways to filter posts on whichever criteria is allowed (category, tags, etc). Some sites will even provide these separately. Couldn't a client pull these all of these together and combine them to achieve the same sort of thing, or even perform filtering itself?