Feature request for Twetch... Compress branched twetches d…

this is not as easy as it sounds

if we did this some users wouldn't get their branch pushed to the feed or seen

we don't want to be curating content for people

Single branch instance != single users branch instance

still not right

you would then be paying every brancher for the next branch in line

What?

I thought because I said it, it would already be done!! :)

Even if you employ a different solution, I'd appreciate the higher signal:noise ratio.

Perhaps raise the cost of branching...

The solution probably lies in the incentive model, then.

Too much branching compared to new content creation. Leads to too much noise just because it's repeated so many times. It's not that the content itself is bad.

Actually, here's a thought... There are two types of branches. One adds value, the other merely shares the same content with no additional content.

Treat them differently.

Spread the payment over some, but not others. Incentivizes adding content.

YES! And so if it is branched (xx) times it will always remain top of feed.

"quoting" as already exists creates new content. So I definitely agree branching could be like x+x+x+x person branched this and quoting always remains a seperate twetch

I like that.

It's not Twetch curating. It's users either adding value, or bumping it to the top of your feed.

The more who branch it, the less money each will make, but that's ok because it still spreads the content, while rewarding all who branch.

And if the division of payments for branching is done based on your following list rather than a global variable, it will pay based on reaching new people more than just reaching many people.

Those who spread content benefit most.