3 ms·

So double entry accounting records each entry as a debit and credit which enables all sorts of new possibilities in accounting. Triple entry blogging is just ha

by TimPC 4y ago

So double entry accounting records each entry as a debit and credit which enables all sorts of new possibilities in accounting. Triple entry blogging is just having two backups for everything with completely different technology from those backups enabling some other things? I don’t get it. I don’t see having two backups as being any sort of secret sauce the way double entry was.

cxr 4y ago
I think this blog post is the result of coming up with a headline that sounded cool, but doesn't really have, as followthrough, the kind of "punch" you're expecting to be behind it. He ends up shifting gears midway through and talking about something perhaps completely unexpected to the reader if the reader were to begin forming their own conclusions about what the piece is truly about based on what's written at the start. To be fair, I recognize that this is a rough (but enthusiastic) sketch of a lot of not-fully-formed ideas. I also recognize what he's talking about. I spent a lot of time during COVID lockdowns refining similar thoughts. It's weird, though, the continual references to platforms like Replit. The real point of "Triple Entry Blogging", if I understand the decision to lead with that, is that it operates on inert data. Just plain, dead media—like RSS/Atom (or JSON blobs). It even uses as an example the same use case that I point to here—Mastodon. What he really wants is something less demanding of compute on the backend. Again, though, nothing that relies on Replit- or Glitch-level powers makes for a good example of this principle put into practice. Moar/previously: <https://news.ycombinator.com/item?id=30862781 https://news.ycombinator.com/item?id=30862781>
- TimPC 4y ago
  I could see that if triple entry blogging included saving and exposing a raw text version of the blog. But it doesn't.

by TimPC 4y ago

cxr 4y ago

I think this blog post is the result of coming up with a headline that sounded cool, but doesn't really have, as followthrough, the kind of "punch" you're expecting to be behind it. He ends up shifting gears midway through and talking about something perhaps completely unexpected to the reader if the reader were to begin forming their own conclusions about what the piece is truly about based on what's written at the start. To be fair, I recognize that this is a rough (but enthusiastic) sketch of a lot of not-fully-formed ideas. I also recognize what he's talking about. I spent a lot of time during COVID lockdowns refining similar thoughts. It's weird, though, the continual references to platforms like Replit. The real point of "Triple Entry Blogging", if I understand the decision to lead with that, is that it operates on inert data. Just plain, dead media—like RSS/Atom (or JSON blobs). It even uses as an example the same use case that I point to here—Mastodon. What he really wants is something less demanding of compute on the backend. Again, though, nothing that relies on Replit- or Glitch-level powers makes for a good example of this principle put into practice. Moar/previously: <https://news.ycombinator.com/item?id=30862781 https://news.ycombinator.com/item?id=30862781>

TimPC 4y ago
I could see that if triple entry blogging included saving and exposing a raw text version of the blog. But it doesn't.