RE: RE: Feedback Wanted: “Communities” Design Document
You are viewing a single comment's thread from:

RE: Feedback Wanted: “Communities” Design Document

Words
188
Reading
1 min
Listen
Play
7y

This is really interesting, I do not really see any problems with the current implementation. Although this will require very profound changes to all the frond ends to the point that it may be faster to just recreate one from scratch using components from the old ones.

I tend to disagree on the "mutes are not retroactive" part.

  • It wouldn't be that harder to implement it
  • It would save some amount of bloat on the chain (let's say you get a comment war between bernie and fulltimegeek you're looking at thousands of mutepost operations.
  • If the community owner just doesn't have enough rc to mute them all. he'll be powerless and his community will be wrecked for weeks until he's regenerated got enough rc.

In terms of features that are "nice to have" would be the ability to set your own ads. This way communities can run things where they share ad revenues to their best authors and are incentivized to break the echo chamber and share their page to the outside world for more pageview. They get ad revenue and the frond end earns backlinks, it's a win/win

@howo: This is really | Ecency