Post by twetch#2275

1Eyk15…d43C Key · twetch

Feature request for Twetch...

Compress branched twetches down into a single instance on my feed. I don't want to see the same post ten times on my feed! I want to see more content for the same time input.

Signal:noise.

1AE48v…F1NS Key · twetch

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

What the chain says
Block
623 760
Time
2020-02-26T15:35:41Z
Signer
1AE48vXR3aXUzEtmhRDVomrymGvETqF1NS
App
twetch
Type
post
Content type
text/plain
Name in tx
twetch#2275

Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.

Signed by 1AE48vXR3aXUzEtmhRDVomrymGvETqF1NS Verified

Replies (5)

1LkKZd…J96j Key · twetch
Replying to@1AE48v…F1NS

Single branch instance != single users branch instance

1AE48v…F1NS Key · twetch
Replying to@1LkKZd…J96j

still not right

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

1Eyk15…d43C Key · twetch
Replying to@1AE48v…F1NS

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.

1Eyk15…d43C Key · twetch
Replying to@1Eyk15…d43C

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.

1Eyk15…d43C Key · twetch
Replying to@1AE48v…F1NS

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...