BitShares Forum
Main => Stakeholder Proposals => Topic started by: clayop on December 16, 2014, 08:55:02 pm
-
I have been running delegate campaign for over two months and still have to get more votes to become an active delegate.
Honestly, it is disappointing when I see many non-active delegates are on the 101 list, not publishing price feed nor actively communicate within the community. I do not want to blame them, just want to say we have better delegates on our standby list.
In my opinion, almost all of delegates posting here deserve to become 101 delegates, at least they are better than init delegates. They stay up to date with versions, contribute to community, and communicate with other members.
However, our community is still redundant to vote for good delegates. Interestingly, this problem is similar to what we have in democratic society, low turnout rate and inefficient vote.
So what should we do?
I think delegates are already put much effort on campaigning their bid and encouraging vote. This is not the problem.
Then, delegates should build up trust network. We should support other trusted delegates and be supported by them.
We already have a good tool for this purpose, "slate".
If possible, please show your support for other delegates and encourage your voters to refresh their vote as "vote as my delegate recommended". This will bring more good delegates into the 101 list and benefit our Bitshares community.
Delegates, unite!
PS. can someone translate it into Chinese if you think it's valuable?
-
I've repeated over and over that most people are not voting to keep their funds safe.
Next version will have voter keys and we will start making voting a much bigger part of the culture.
-
I've repeated over and over that most people are not voting to keep their funds safe.
Next version will have voter keys and we will start making voting a much bigger part of the culture.
Great. Thanks Toast!
-
What frustrates me the most is seeing the _11_ init delegates not publishing feeds, pulling 3% fees.
-
that's really sad, i feel with you!
I've repeated over and over that most people are not voting to keep their funds safe.
Next version will have voter keys and we will start making voting a much bigger part of the culture.
+5%
-
I've repeated over and over that most people are not voting to keep their funds safe.
Next version will have voter keys and we will start making voting a much bigger part of the culture.
+5%
-
What frustrates me the most is seeing the _11_ init delegates not publishing feeds, pulling 3% fees.
You gave me an idea...
They should implement a future that stop's paying delegates if they don't publish at least x feeds per day... (independent of their payrate)
-
I for example can not install / run .26 because
Large memory requirements during re-indexing and resyncing. At least 4GB RAM is recommended (swap file is not sufficient). Less RAM can cause freezing and crashes
since my client with my funds is on a vm with max. 2gb ram. source: https://github.com/BitShares/bitshares/releases/tag/v0.4.26
I didn't attempt to update it therefore.
If it is all easier and faster voting participation will also go up I think.
-
I for example can not install / run .26 because Large memory requirements during re-indexing and resyncing. At least 4GB RAM is recommended (swap file is not sufficient). Less RAM can cause freezing and crashes
since my client with my funds is on a vm with max. 2gb ram. source: https://github.com/BitShares/bitshares/releases/tag/v0.4.26
I didn't attempt to update it therefore.
If it is all easier and faster voting participation will also go up I think.
That wasn't actually true, you can re-index and sync just fine with 512mb RAM and a swap. Compiling is another matter though.
-
You gave me an idea...
They should implement a future that stop's paying delegates if they don't publish at least x feeds per day... (independent of their payrate)
Good idea. If delegates don't publish feeds, BTS earned should be burned as dividends maybe?
-
I voted for you!
For community votes you need time, because all people need a feeling about you.
@toast a reminder pls publish feeds. I don't get it why you don't do it!
-
We really need 1 website where we can browse delegates, click their names and have...
- The mission of that delegate
- Weekly, biweekly, monthly, etc. updates/results
- Other delegate info such as pay rate, produce, missed etc.
It could easily be added to this.
http://www.bitsharesblocks.com/delegates (http://www.bitsharesblocks.com/delegates)
Hopefully svk would consider adding this. The forum is a great place to get elected but we need a place where we can see what the 101 delegates are up to.
^^^We need this. It's hard to keep track of all the people and what they are doing if you are not super active on the forums. Having everything organised in one place will help with voting.
Also a nice feature would be a delegate having the ability to recommend another delegate. So say on toast's or BM's delegate page they could have a list of other delegates they recommend.
-
I for example can not install / run .26 because Large memory requirements during re-indexing and resyncing. At least 4GB RAM is recommended (swap file is not sufficient). Less RAM can cause freezing and crashes
since my client with my funds is on a vm with max. 2gb ram. source: https://github.com/BitShares/bitshares/releases/tag/v0.4.26
I didn't attempt to update it therefore.
If it is all easier and faster voting participation will also go up I think.
That wasn't actually true, you can re-index and sync just fine with 512mb RAM and a swap. Compiling is another matter though.
I have .24 atm. So the only way to update is compile newly right? So won't work?
-
The voting is badly broken. Apparently, they're working on making it better.
-
Allowing collateral to vote would increase my weight quite a bit :)
I heard it's going to be included soon.
-
I for example can not install / run .26 because Large memory requirements during re-indexing and resyncing. At least 4GB RAM is recommended (swap file is not sufficient). Less RAM can cause freezing and crashes
since my client with my funds is on a vm with max. 2gb ram. source: https://github.com/BitShares/bitshares/releases/tag/v0.4.26
I didn't attempt to update it therefore.
If it is all easier and faster voting participation will also go up I think.
That wasn't actually true, you can re-index and sync just fine with 512mb RAM and a swap. Compiling is another matter though.
I have .24 atm. So the only way to update is compile newly right? So won't work?
You can always compile on another computer with sufficient RAM and then copy the executable to your VPS, that's what I do.
-
I for example can not install / run .26 because Large memory requirements during re-indexing and resyncing. At least 4GB RAM is recommended (swap file is not sufficient). Less RAM can cause freezing and crashes
since my client with my funds is on a vm with max. 2gb ram. source: https://github.com/BitShares/bitshares/releases/tag/v0.4.26
I didn't attempt to update it therefore.
If it is all easier and faster voting participation will also go up I think.
That wasn't actually true, you can re-index and sync just fine with 512mb RAM and a swap. Compiling is another matter though.
I have .24 atm. So the only way to update is compile newly right? So won't work?
You can always compile on another computer with sufficient RAM and then copy the executable to your VPS, that's what I do.
I have done the same thing with the chain to prevent issues with syncing and re indexing. Open updated client on computer with more RAM, let chain sync, close client, and copy over the chain folder. It takes a little while but seems to be working fine on VPS with 1 gb RAM.
I agree with the original post. It is currently very hard to get a new delegate voted in. With the number of feeds published, there should be plenty of room for good healthy competition. I'm excited to see how the new voting password helps.
-
I for example can not install / run .26 because Large memory requirements during re-indexing and resyncing. At least 4GB RAM is recommended (swap file is not sufficient). Less RAM can cause freezing and crashes
since my client with my funds is on a vm with max. 2gb ram. source: https://github.com/BitShares/bitshares/releases/tag/v0.4.26
I didn't attempt to update it therefore.
If it is all easier and faster voting participation will also go up I think.
That wasn't actually true, you can re-index and sync just fine with 512mb RAM and a swap. Compiling is another matter though.
I have .24 atm. So the only way to update is compile newly right? So won't work?
You can always compile on another computer with sufficient RAM and then copy the executable to your VPS, that's what I do.
Copying files from an insecure computer to a secure one sounds risky to me. The whole purpose of using a VM is to do only one thing per VM (trading, BTS storage, etc).
-
I've repeated over and over that most people are not voting to keep their funds safe.
Next version will have voter keys and we will start making voting a much bigger part of the culture.
I am looking forward to this feature rolling out. And yes, delegates unite! +5%