maybe 100% delegate should burn some progress on to the wall of delegate id

[sudo]

I want to bring this thread back up, this would be super useful for seeing what delegates are up to, they could even broadcast a status. There needs to be more transparancy from the delegates on what they are working on, what that specific delegate is for etc. This could of course also be validated against their applicable forum handle to take the discussions off of the blockchain...

[mdj]

I want to bring this thread back up, this would be super useful for seeing what delegates are up to, they could even broadcast a status. There needs to be more transparancy from the delegates on what they are working on, what that specific delegate is for etc. This could of course also be validated against their applicable forum handle to take the discussions off of the blockchain...

[sudo]

upup

[sudo]

any 100% delegate do firsrt?

https://bitsharestalk.org/index.php?topic=14429.msg187703#msg187703

 

[abit]

any 100% delegate do firsrt?

https://bitsharestalk.org/index.php?topic=14429.msg187703#msg187703

[sudo]

any 100% delegate do firsrt?

[sudo]

？？？？

[sudo]

now  2015-2-28

[sudo]

i always give updates to my thread which i find annoying its way better to give updates via wall.

only thing i hate is that mail isnt hooked up and theres no subscriber publisher model for this... It would have been good to use this model when devving the wall so ppl would get notified of an update to a wall u subscribed to

 yes   subscribe fuction  is needed

wall fuction need to be enhanced  as soon as possibile

[sudo]

I am a 100% delegate and I am 100% behind this idea.

I will promote this in future delegate hangout.

I'm just downloading the bitshares 0.6 and I'll burn my first report of my delegate position through burns.

thank you   

[jsidhu]

 i always give updates to my thread which i find annoying its way better to give updates via wall.

only thing i hate is that mail isnt hooked up and theres no subscriber publisher model for this... It would have been good to use this model when devving the wall so ppl would get notified of an update to a wall u subscribed to

[hpenvy2]

I am a 100% delegate and I am 100% behind this idea.

I will promote this in future delegate hangout.

I'm just downloading the bitshares 0.6 and I'll burn my first report of my delegate position through burns.

Thank you.

[rgcrypto]

I am a 100% delegate and I am 100% behind this idea.

I will promote this in future delegate hangout.

I'm just downloading the bitshares 0.6 and I'll burn my first report of my delegate position through burns.

[hpenvy2]

There's enough interest to create a poll. If the community sees a a positive response, we can start requesting delegates giving their official position if they will cooperate. A template could be created and we're making progress.

There is obviously enhancements that could be made to the wall functionality, in the meantime we are off any running. I also like the idea mentioned about delegates proposing how often they plan on updating.

[sudo]

the wall style should be enhanced

来自我的 M812C 上的 Tapatalk

[gamey]

Worth a try, maybe, but don't forget that the walls are meant to be kind of fun, wacky and random. In addition to delegate updates, we've already seen some real crap being hurled up there, so a compendium of updates would have to conduct some sorting. I think it should be just as easy for delegates to update some other page somewhere. To think we can run this whole delegate thing with the client, this forum and the mumbles as the main information sources is not to realize how large and unwieldy things will become.

Well if you can read that a person posts to their own wall, then it can be filtered by that simple criteria.  Although that requires that the delegate use his delegate's key to give the update which isn't so easy for the guys who have a proxy running their delegate.. hrmmmm. Still, I think this might be the best solution shy of someone spending all their time trying to get updates from people.

[donkeypong]

Worth a try, maybe, but don't forget that the walls are meant to be kind of fun, wacky and random. In addition to delegate updates, we've already seen some real crap being hurled up there, so a compendium of updates would have to conduct some sorting. I think it should be just as easy for delegates to update some other page somewhere. To think we can run this whole delegate thing with the client, this forum and the mumbles as the main information sources is not to realize how large and unwieldy things will become.

[gamey]

A lot of this is Fuzz's idea.. but if Delegates can burn publicly and not anonymously then svk's site could read these transactions from the blockchain and update a page with what everyone is doing.  Then it is easily sortable by last update etc.  When someone doesn't update it becomes apparent. I think this would work well without setting expectations of frequent updates.  People can complain publicly if there aren't enough etc.. but we can also just go to the one most obvious spot and see the latest updates.

Then we can put a twitter button on there and people can tweet their delegate updates.

All integrated into a nice little package at the biggest goto site for delegate info and we leverage twitter with it.

[sudo]

Very sad to see that not even one delegate would like to respond. I hope they are as active as when they are asking for votes...

When a working client comes out, I will gladly do it.  It takes hours of wrestling with the client to do anything at all.

Just get an SSD, they're not that expensive.. Unless you're happy to just use the light client you'll probably be unsatisfied for a long time..

My wallet works fine with a standard HDD... It's like 5 years old too

4k read&write of HDD is terribly
lag offen happen
ssd gain much better user experience

[svk]

Very sad to see that not even one delegate would like to respond. I hope they are as active as when they are asking for votes...

When a working client comes out, I will gladly do it.  It takes hours of wrestling with the client to do anything at all.

Just get an SSD, they're not that expensive.. Unless you're happy to just use the light client you'll probably be unsatisfied for a long time..

My wallet works fine with a standard HDD... It's like 5 years old too

Dang, there goes my theory about it being HDD related!

[lil_jay890]

Very sad to see that not even one delegate would like to respond. I hope they are as active as when they are asking for votes...

When a working client comes out, I will gladly do it.  It takes hours of wrestling with the client to do anything at all.

Just get an SSD, they're not that expensive.. Unless you're happy to just use the light client you'll probably be unsatisfied for a long time..

My wallet works fine with a standard HDD... It's like 5 years old too

[sudo]

wall edit GUI can  learn the bbs style
such as  Discuz!   A good layout

[sudo]

any  blockchain employee respond &action first?

[Empirical1.1]

I like this idea. Forum reports would be fine as well, we just need more transparency from our delegates across the board.

  The community is clearly asking repeatedly  for frequent updates and transparency yet few delegates are currently providing them.

Maybe someone should make a template. One where they show the dollar equivalent earned say 'Jan 1st to Feb 1st' and then a breakdown of salary, expenses and future projects etc.

[svk]

Very sad to see that not even one delegate would like to respond. I hope they are as active as when they are asking for votes...

When a working client comes out, I will gladly do it.  It takes hours of wrestling with the client to do anything at all.

Just get an SSD, they're not that expensive.. Unless you're happy to just use the light client you'll probably be unsatisfied for a long time..

But it used to work fine, then on a new release it broke and never worked again.  How can it be a hardware problem if a few months ago it was working?

Most likely because globally there are more blocks and more transactions, and maybe your wallet has more accounts and more transactions as well.

[matt608]

Very sad to see that not even one delegate would like to respond. I hope they are as active as when they are asking for votes...

When a working client comes out, I will gladly do it.  It takes hours of wrestling with the client to do anything at all.

Just get an SSD, they're not that expensive.. Unless you're happy to just use the light client you'll probably be unsatisfied for a long time..

But it used to work fine, then on a new release it broke and never worked again.  How can it be a hardware problem if a few months ago it was working?

[svk]

Very sad to see that not even one delegate would like to respond. I hope they are as active as when they are asking for votes...

When a working client comes out, I will gladly do it.  It takes hours of wrestling with the client to do anything at all.

Just get an SSD, they're not that expensive.. Unless you're happy to just use the light client you'll probably be unsatisfied for a long time..

[lovejoy]

I like this idea.

Just a few things to consider... transparency is a no brainer.. efficiently executing on how that is delivered without overburdening will take some finesse.

 
Yes, we are still evolving the best mechanisms for efficient transparency.  crypto_prometheus is spearheading the next newsletter, out on the 1st with a whole range of delegate updates included.  So stay tuned for that and let's continue discussing the preferred methods for keeping our community informed!

[sudo]

upup

[wuyanren]

必须这么做

[matt608]

Very sad to see that not even one delegate would like to respond. I hope they are as active as when they are asking for votes...

When a working client comes out, I will gladly do it.  It takes hours of wrestling with the client to do anything at all.

[BunkerChainLabs-DataSecurityNode]

Very sad to see that not even one delegate would like to respond. I hope they are as active as when they are asking for votes...

I saw two respond in the thread and suggested there needed to be improvements for the burn to ensure proper identification. You might have missed them, but they are there.

Besides this, during the last Beyond Bitcoin meeting Friday this was discussed with BM. It was suggested a possible framework for reporting could be created to standardize it. Makes sense.

However, every project is different in the frequency of their updates. Do you really want daily updates that basically say.. debuged this, 50 lines of code today, did this, did that each day? For some progress might be measured in strategic meetings and events that span months. So while the framework would make total sense so that we can index and keep track of it all, the frequency would really depend on what it requires. I think it is fair to have the delegate from the start declare their planned update frequency. If this is found deficient then it can be brought up. If still not satisfactory then they start to lose votes obviously.

Just a few things to consider... transparency is a no brainer.. efficiently executing on how that is delivered without overburdening will take some finesse.

[sudo]

visit bitsharestalk.org is so slow  make me mad.



at least  delegate can  paste  the URL of their topic  on the wall

[ripplexiaoshan]

Very sad to see that not even one delegate would like to respond. I hope they are as active as when they are asking for votes...

[sudo]

who first?

make the wall  served its turn

[Rune]

I like this idea. Forum reports would be fine as well, we just need more transparency from our delegates across the board.

[xiahui135]

good idea.
and we have these delegates. it is reasonable to measure what they are doing. And hope some delegate will lead to do that, to compete some delegates out.

[sudo]

This can be achieved once non-TITAN transactions are used and the owner of the balance_id that acutally spends the burn can be linked to an account (read: is the BTS address of the owner/signing key of a delegate)

blockchain_get_account_wall can show the signer
but GUI can't

maybe  GUI can  list two part or three column

the id owner himself
the  Non-anonymous
the Anonymous


>> help blockchain_get_account_wall

Usage:
blockchain_get_account_wall [account_name]                                                            returns all burn records associated with an account
returns all burn records associated with an account

Parameters:
  account_name (account_name, optional, defaults to ""): the name of the account to fetch the burn records for

Returns:
  burn_records

aliases: wall

[xeroc]

This can be achieved once non-TITAN transactions are used and the owner of the balance_id that acutally spends the burn can be linked to an account (read: is the BTS address of the owner/signing key of a delegate)

[liondani]

very good idea!!!
that ensures that these updates will never get lost (blockchain) and anybody can review them at any point in time very easy!
Simultaneously  anybody should copy/paste it to a personal progress/report thread on this forum for max exposure...

I like that idea too ..

That way wall messages also function as a kind of contract

but how can we ensure that a message (about progress etc.) is not burned from a third-party/spammer instead the real owner of the delegate id?
I propose a future/option that allows us to make public the id that burned the message (example when we burn to our own account)...

[xeroc]

very good idea!!!
that ensures that these updates will never get lost (blockchain) and anybody can review them at any point in time very easy!
Simultaneously  anybody should copy/paste it to a personal progress/report thread on this forum for max exposure...

I like that idea too ..

That way wall messages also function as a kind of contract

[liondani]

 

very good idea!!!
that ensures that these updates will never get lost (blockchain) and anybody can review them at any point in time very easy!
Simultaneously  anybody should copy/paste it to a personal progress/report thread on this forum for max exposure...

[sudo]

cost just 1bts one burn

来自我的 M812C 上的 Tapatalk

[天籁]

 

[cgafeng]

good idea.

[sudo]

daily or at least weekly
progress  plan  promise etc.
burn on to the wall of delegate id