I think using git in the background is probably overkill. I don’t need to merge/branch/cherrypick/etc on my blog posts—however, now that I say this, git might be the perfect blogging system since it would be awesome to be able to pull-request factual updates to people’s posts, fork and correct posts, etc. That all could be done without git, but git on the backend might be the simplest way to implement it as a feature while having a lot of prebuilt mechanisms baked in for future features.
However, simply showing and highlighting changes with dates would be great. I often write a post and then an hour later re-read it and decide to clarify something or add more context, and I’d like that history of changes to exist for posterity (and to allow comments to hold contextual relevance in case something changed).
Some sort of easy git integration would be very helpful for long-form posts -- something sort of like gist.github.com would be nice. It would also make creating/editing posts offline much easier.
It would be an easy way for people to monetize useful code snippets too. Often I will create a little gist showcasing/demonstrating some code or construct, and it would be great if I could do it on SN so that it at least has a chance to self-monetize.
reply
That's a fascinating idea.
I like how in this thread we've wandered toward some potential monetization models: rewarding long-form writing at a more granular level, for giving / receiving feedback; and for well-articulated bits of useful code -- two things that would have been impossible to hit with monetary incentives in any way other than btc / lightning. How many times on StackOverflow would have gleefully, gratefully given somebody 10k sats for helping you with a conundrum?
Intriguing to think about.
reply