Bitfeed

Is there a reason a second HTTP request is needed to get the rawtx vs. including the raw tx in the bitfeed as a field?

Should there be a protocol for redactions? e.g. removing items from a bitfeed? Would that be more appropriate for a "second layer" protocol?

This might be a little bit off in the weeds, but Bitfeed seems like it'd be a great way to manage a bitcoin-hosted webpage. The biggest issue with hosting a site completely on-chain at the moment is the fact that changing a page would require updating DNS records (or some equivalent). With Bitfeed, you could just point your DNS at a server which renders the html file published by a certain Bitfeed, and then any updates pushed to the feed could be rendered on the new version of the site in realti

As for powpress, really want to use it particularly for the rich editing not found on other platforms atm. But I feel it needs a monetization strategy for authors. Medium has changed theirs a couple times, but still relies on "reads" and how they interpret reads (formerly claps but that got out of hand obviously bc the claps have no cost-- something BitCoin solves inherently). Hate to say it, but paywalls have been working for a long time. New York Times, even bit.sv and yours.org worked in

The "Bible" of investing is "Security Analysis" by Graham & Dodd, but it has MANY versions. Some prefer the original 1930s version. Some prefer the newest version updated for modern stocks and companies and times. But it's nice to be able to see the iterations, with their respective time-stamps in one place, to make that decision. Same goes for articles. For my articles, I want to do revisions, but don't want to lose control of the original. It allows both myself AND the reader to see where

Bitfeed and 21e8/Boost are going to be a match made in heaven

Very very interested in helping you moving this forward my friend!

This is nice. Thank you. Here's something to mull over. If a post can have many versions, with each version being a separate tx with unique txid, how is the best way to represent that in a bitfeed?

Interesting! Design question - why not make it compatible with the existing RSS protocol?

The Bitfeed spec is intentionally minimal and unopinionated. Hoping a lot of different use cases arise. Please share your ideas on Bitfeed channel.