Following = mesh Branching = small world The only problem:…
Following = mesh
Branching = small world
The only problem:
Twetch is a network where not everyone wants everything. So, we need filters.
Then, more connections won't increase noise, only signal.
Filtering is the most important next step for Twetch.
Replies
Good Point! And maybe displaying your current balance instead/additional to the amount you earned. I keep switching back and forth to moneybutton to check how much cash I have left.
I think that's more of a wallet based thing than a Twetch thing.
I'm not sure I want a service to be able to access my balance, either... That's my own information, not theirs.
So, hashtags then?
Agreed. It's easy to construe Money Button as being a part of Twetch, but they're actually separate, interoperable pieces. MB has an API though, and it might be cool to develop a desktop widget or browser extension that always displays your balance.
Possibly, but I bet there are better ways... More reliable, valuable ways.
Yup. I've always wanted to be able to build deep if/then rulesets using hashtags.
Though we'd need an incentives structure that rewards post originators for accurately tagging their posts with relevant info.
That's where I'm going with it, too, except... Why does it have to be only the post originators who are tagging it?
There's a solution here, and I don't think it'll actually look like tagging/hashtags, or anything else we currently recognize.
Not sure how others tagging could be incentivized unless they were earning part of the subsequent like/branch revenue, which seems strange to divide up as a post gains popularity.
Interested in other perspectives on this too.
I've got ideas... Haven't worked it out completely yet.
It all has to do with how networks manage disparate valuations. Need to find the appropriate ways to abstract, while creating identifying, meaningful qualitative assertions about things.
Maybe as an opt-in option like dark mode. Functionality is theoretically also already there: https://docs.moneybutton.com/docs/api-rest-user-balance.html
Perhaps. I don't like the idea of it though, and I think there may be better ways to go about it. Too many potential privacy issues, in my opinion.