Author Topic: Feeds without delegates....maybe a better solution?  (Read 4149 times)

0 Members and 1 Guest are viewing this topic.

Offline ozvic

  • Jr. Member
  • **
  • Posts: 44
    • View Profile
  • BitShares: trev

They own the stake and that's how the game works. I'm cool with that.


Check! Good to see we're on the same page.

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG

If inits were publishing feeds that might cause significant centralisation. Inits were voted in because there were not enough delegates updated to current version.
Unless there are enough serious delegates willing to do their job - inits cannot be removed (without hurting the network).
Even now there are people (including me) running multiple delegates and still there aren't enough people willing and able to be decent delegates.

Yes and no. I've only noticed the 're-rise' of the init's to the top 101 in the last day or three. I can see a good number of standby delegates below the 101 threshold that are advertising 0.4.18.

If whoever's responsible wants to make more btsx, that's fine. They own the stake and that's how the game works. I'm cool with that.

No need to make version excuses though. Active delegates have to upgrade or they'll be on a fork before they know it.

I find the truth ... cool. ;)

prob due to timezones, I was (one of) the first to make it to 0.4.18 RC1 according to bitsharesblocks.com.

Init delegates were voted in just before v0.4.17 hardfork started. There weren't enough delegates that upgraded to 0.4.17 on time. Perhaps some of the delegates updated to 0.4.18 were slow/unreliable previously and that is why they weren't voted in. Its a free system - anyone can vote.

Offline ozvic

  • Jr. Member
  • **
  • Posts: 44
    • View Profile
  • BitShares: trev

If inits were publishing feeds that might cause significant centralisation. Inits were voted in because there were not enough delegates updated to current version.
Unless there are enough serious delegates willing to do their job - inits cannot be removed (without hurting the network).
Even now there are people (including me) running multiple delegates and still there aren't enough people willing and able to be decent delegates.

Yes and no. I've only noticed the 're-rise' of the init's to the top 101 in the last day or three. I can see a good number of standby delegates below the 101 threshold that are advertising 0.4.18.

If whoever's responsible wants to make more btsx, that's fine. They own the stake and that's how the game works. I'm cool with that.

No need to make version excuses though. Active delegates have to upgrade or they'll be on a fork before they know it.

I find the truth ... cool. ;)

prob due to timezones, I was (one of) the first to make it to 0.4.18 RC1 according to bitsharesblocks.com.

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
They not publishing.. I assumed they were in control of i3 or dacsun. Not a good example... :O
*agreed*

If inits were publishing feeds that might cause significant centralisation. Inits were voted in because there were not enough delegates updated to current version.
Unless there are enough serious delegates willing to do their job - inits cannot be removed (without hurting the network).
Even now there are people (including me) running multiple delegates and still there aren't enough people willing and able to be decent delegates.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
They not publishing.. I assumed they were in control of i3 or dacsun. Not a good example... :O
*agreed*

Offline ozvic

  • Jr. Member
  • **
  • Posts: 44
    • View Profile
  • BitShares: trev
They not publishing.. I assumed they were in control of i3 or dacsun. Not a good example... :O

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc

Offline ozvic

  • Jr. Member
  • **
  • Posts: 44
    • View Profile
  • BitShares: trev
So who's voting for all the init's?

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
I thought you couldn't downvote due to the "emski attack"?
you still cannot downvote .. it's a feature that comes with slate voting .. If you were to vote as recommended by a delegate you can exclude some of his recommendations

http://wiki.bitshares.org/index.php/ApprovalVoting

Offline Method-X

  • Hero Member
  • *****
  • Posts: 1131
  • VIRAL
    • View Profile
    • Learn to code
  • BitShares: methodx
I thought you couldn't downvote due to the "emski attack"? I went through all my votes and "unvoted" delegates who were not publishing BitGLD feeds. I no longer care about the pay rate, I just vote for delegates who maintain their feeds.

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani


Tell me what is the difference from just hard coding the feed into the program?

the difference is that some delegates (like me) are publishing feeds manually.



Sent from my ALCATEL ONE TOUCH 997D


Offline bytemaster

Any delegates not publishing a feed will be voted out when I get back from Vegas. 

For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
I think we should first start down voting delegates that don't do there job properly

I mentioned already that some delegates seem to be too lazy while standby delegates most certainly are not.

As a standby delegate, I tried to put in a feed but encountered error.  So no go.  Standby delegate cannot publish feeds.

I believe there are other standby delegates like me who are eager and capable to perform this role, and are waiting for the opportunity to be given.  :)
« Last Edit: September 28, 2014, 08:36:39 pm by cube »
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline yellowecho

I'm going to start downvoting all delegates that dont maintain a feed by the end of the week.. giving them a bit more time to get their shit together
696c6f766562726f776e696573

Ggozzo

  • Guest
we already have TWO different scripts which take DIFFERENT sources and do different operations on them ..
plus .. they are "simple" python scripts that can be modified to your needs/policies

If all delegates employ the same scripts, there will be no difference from the case that wallet embeds the price feed internally.

Exactly.