You are viewing a single comment's thread from:
RE: Steem Developer Update (Graphene 2.0)
Few questions:
@ned mentioned on steemspeak, that steemit team is using/is going to use Scrum. Are you going to use new feature of github - scrumboards which in github are now called projects. I already noticed test board created: https://github.com/steemit/steemit.com/projects/1
What is ETA for migration to Graphene 2.0, how you are going to split this huge task to smaller stories?
Currently the Steem nodes that power steemit.com consume over 14 GB of RAM and this number is growing at a rapid rate.
I heard that 2nd voting period (30 days) is not longer because of memory. I guess that with Memory Mapped File size of those data should not be so big problem... so is it possible that third voting period (like.. 1 year) will be introduced?
I feel its very important for the real quality of steemit posts to flourish that there needs to be a long term incentive for continual value of posts.
ITs important to design incentive for people to uproot "old" content and still have the author get compensated for that. This will inspire much more in depth content and bigger scope projects of development and discourage the quick post to keep active and get more quick votes.
the 30days issue will solve definitly many problems i see like in @pharesim project pevo, and other content ...
funny... yesterday I read whitepaper of his project ;) It's a small world :)