@jesta  I like the idea of having unlimited payout cycles . Like you said it make sense, if people on youtube were paid only for 7 days's views they would post a lot of clickbait stuff,repost a lot of video too and would not put the same amount of effort in creating content which will result in lower quality.
My only concern with this feature is that if there is unlimited payout cycles then the daily reward will be shared between more and more posts as time goes by which will reduce payouts for newly created post, not sure if a valid concern but something to think about...

I like it. Couldnt that feature be an arbitrary variable depending in the platform its been created on?

THIS ^^^

It deserves a dedicated post ! Please make a post about it @jesta 
It really deserves more attention!

There are two problems with this:
1. With a limited rewards pool, less and less will be available for 'active' content as more and more starts to go to 'historic' content.
2. It allows users to keep re-voting on the same content over and over by powering down, and then powering up a new account.

I would prefer to add some form of 'easy tipping' to the UI. I feel that this would be an acceptable way of providing rewards to old content. On traditional websites, I would argue that most users would **not** tip - but on a site like Steemit where there are already lots of rewards "flying around" - there is a lot less of a burden to send a few STEEM/SBD coins someone's way if you like their content.

This exemplifies the reason why design-by-committee is doomed to languishing failure.

Engineering is trade-offs, and the best trade-off based on the current engineering constraints is a single payout window.  Everything else (two payout windows, unlimited repeating payout windows, et c) impacts scalability significantly.

There are regular, deep discussions in our engineering organizations about these tradeoffs, and it would be a full-time job for several people just to communicate the minutiae adequately (to people who mostly haven't read the code).

At some point, unless you want to come and sit in our office full time (or understand the c++ consensus code in full), changes like this are going to have to boil down to "trust us, we do this for a living".  I think there about 6-8 people in total on all of Steemit that have qualified opinions about the "how" and the "why" of the engineering decisions of the actual implementation of these changes.

Alternately, go and read the code, and you won't have to trust us.  It's open source for a reason. :)

We are gearing up to support a lot more users and posts, and have identified the scalability chokepoints and have a plan to eliminate most of them.  This is crucial to that plan, at the expense of a tiny dent in UX (it would be lovely to keep 24h payouts, and payout indefinitely, but those implementations simply will not scale as we grow).

Yes, it also would enable FAQ content, Wikipedia stuff, timeless writing or photos, and so forth.

The Op of every comment also from their child comments!

This was actually how it was designed in the whitepaper :)

I'd have to think about it and discuss this more, but offhand it sounds like a really good idea. You even could consider giving community moderators some cut to stimulate engagement also.

thank you... Just comments I'd be okay with as discussions can carry on for a few days but the post, not so much in agreement