| A lot of space is wasted on the "cards" style scroll design. Which means I rapidly lose interest scrolling at all, I did it once, won't scroll down again. The header with the "recommended based on people you follow" message is obtuse information i don't need to know. There would be more magic if the algorithm didn't say why this item was chosen for the feed. And the header style wastes space. Invoking the soul of git is always the most conceptually pure design inspiration. therefore, git-relevant facts are always more effective than social-relevant facts. // example <User> in <Repository>:
2 commits:
Removed unused code
Refactored x function // example <Repository> Released <Tag>:
Xth release since <LaunchDate> //example <User> branched <Repository.MostRecentlyWorkedOnBranch> to a new branch <BranchName>. //end examples This would be a dense view of chronologically-relevant feed information that can be digested quickly. The only other information that i find useful other than standard git data based information is 1. when readme.md is updated, and 2. when media is added to the readme of starred, watched, and algorithm-discovered repos. When a commit of readme.md occurs, extract the markdown of the commit, render the markdown in a feed post with a link to the repo/readme, so i can read it in context. |