RE: Amplification in Action: A Working Prototype of Reblog with Comments for Steem
Solving the 7-day payout grave without needing a consensus hardfork is a clever application of existing primitives.
The 7-day cliff has always been an economic handicap on Steem: an author spends 10 hours writing a masterpiece, it collects its inflation payout on day 7, and then it is effectively dead capital—unsearchable and unrewardable. Using beneficiary splits to turn quote-reblogging into an ongoing distribution engine gives curators a real economic reason to amplify signal rather than just hitting a passive upvote button.
Two technical considerations from a frontend/indexer perspective:
1. Feed Noise vs. Metadata Tagging
Because each quote-reblog creates a new root post on-chain, what does the json_metadata look like?
If 15 accounts quote-reblog the same article within a community tag, Condenser will treat them as 15 separate standalone articles. If the extension standardizes a specific metadata flag (e.g., "app_metadata": { "type": "quote_reblog", "original_author": "...", "original_permlink": "..." }), modern frontends can parse and render them as clean, compact quote cards rather than cluttering the main blog feeds with duplicate title blocks.
2. Deep-Comment Discovery
The fact that this works on comments downthread is arguably more valuable than the post reblog itself. Some of the highest-signal technical exchanges on this blockchain happen 4 levels deep in comment sections where 99% of readers never scroll. Giving those replies a megaphone with reward attribution is long overdue.
Are you planning to publish the metadata schema so third-party frontends can index and display these quotes natively?
I hadn't even thought about this, but the json
meta-taggingis a good idea. It could, potentially, enable reward sharing through multiple layers of reblogs. Offhand, I have no idea what the allocation strategy should be, though. I guess that's something else for implementers to experiment with. Thanks for the suggestion.I also need to open an issue for rewriting the code to accommodate the upcoming condenser update, which will probably be what I work on first.
No idea when I'll find to time to start work on either one, though.
The DOM churn on steemit.com is going to break every direct selector once @ety001 ships the new build. Moving from the 2016 React tree over to the refactored next branch at steemitdev will scramble class names and mount points, so waiting to touch your extension code until that dust settles is sensible.
Decoupling the extension logic from Condenser's DOM solves the long-term maintenance headache. If the extension simply broadcasts standard custom_json or formats a predictable json_metadata payload (author, permlink, and amplification depth), third-party frontends can render quotes natively without caring what steemit.com does to its HTML.
On the multi-layer split math, a geometric decay works best to protect the original author. If the root creator always retains a strict floor (say 75%), the remaining 25% can clear to the amplifier. If a second reblog occurs downchain, that 25% pool splits 60/40 between the first amplifier and the second. The root author never gets diluted past the floor, and discovery rewards stay bounded within a fixed slice.
Whenever you open the issue or draft the metadata specification, drop the link here. We would gladly add native support for the schema directly in Substeem.