We recently saw this inquiry on Leo Snaps:
@senorcoconut/re-senorcoconut-ps3nqmxa

For those using a translation software:

How possible would it be to create a sort of Hive Basic Income type thing but for Leo on our threads??? With an obvious limit to how many threads get the payout per account.

Hive SBI Response

Our entire software stack is open source, so it could be spun up by anybody for threads, with some modifications to narrow it to that app/community.
Our preferred alternative - anybody could contribute a pull request with the requisite changes. Hive SBI already has a small amount of LEO on Hive account@sbi-tokens and would review and approve pull requests that accurately enable users to delegate LEO to Hive account@sbi-tokens for bonus Hive SBI units. Hive SBI would also commit a fair value of bonus units to developers that contribute to our project.

The real implications are around the economic implications of automated comment voting. Threads and Snaps are considered by some to be lower effort than full-form posts, and in the past automated voting on comments and short-form content has been problematic. This is easily mitigated for a particular community if the pull request above includes the following features:

1. An oracle that calculates the HIVE value of LEO votes.
2. The capability to upvote LEO threads with Hive account@sbi-tokens only instead of primary SBI accounts.
3. The capability to check threads for the voted value and remove it from member's accumulated balance.

At present Hive SBI members get their LEO and other token votes as tiny 'bonuses' that are relatively immaterial compared to their regular upvote value, since less than 1% of program assets are in tokens. The value of these token votes is not removed from member pending balances. The listed changes would enable members to receive pending balance specifically from their Threads contribution, while drawing minimally from the Hive Rewards pool (enabling Threads to decline Hive Rewards payment and earn exclusively from LEO votes). This would reduce the likelihood of downvotes from the broader Hive community, but does not preclude the possibility of downvotes originating within the LEO community when content is considered not good enough to merit the automated votes received.

The above-mentioned changes would enable members to take value directly in Threads instead of long-form content. If implemented, Hive SBI would commit to ramping up their current staking pattern for LEO (and once implemented for LEO, similar could easily be implemented for other communities.)

While these capabilities are officially on the Hive SBI roadmap, there is not currently an active full time developer in the Hive SBI project. Development has usually been done by community members willing to work for bonus units and then get paid over time via their upvote value. If any developer would like to tackle the project, we're happy to get into more detail either in formal proposals on github or in the Hive SBI discord. We do think it would be easier to deploy code updates to the existing Hive SBI stack than it would be to fork the project and start from scratch.

You can learn more about Hive SBI on our website.