SteemWorld Update ~ SPS / Holy Shitness Proxy
Update
Sometimes there is a hidden button that reveals what is about to come next...
If you don't want to click hidden buttons, you can also just visit:
https://steemworld.org/proposals
And you will reach the new Worker Proposals Overview:
The overview shows all active (votable) proposals. The LED-like image on the left of each row shows, if the proposal has reached the minimal required amount of voted SP to receive a part of the available SPS Fund on an hourly basis.
As some of you might have noticed, the Currently Available amount is being calculated simply by:
Total SPS Fund / 100
The red status means that the start date of the proposal is not yet reached. Even if the amount of voted SP for those proposals will be displayed as '0.000 M', it does not mean that they didn't receive votes already. It's just so that (currently) the total amount is not being calculated by the Steem nodes for not yet started proposals.
When you click on a row itself (not on the links), the content (post) of the proposal will be displayed:
To close the Post Viewer, just hit Esc on your keyboard or click on the X button.
When you click on the voted SP amount of a proposal, the Proposal Votes Overview will show up:
The rows are sortable by clicking on the desired column header. In this case it is sorted by 'Influence -> descending'. I added a few extras to make it all more self-explanatory.
I guess this will come as a surprise to many of you:
Your witness proxy decides, which projects you are able to support!
As shown above, some of the numbers are being displayed striked through. This is the case, when a voter has defined a witness proxy in his account and that proxy didn't vote the same proposal.
Don't ask me, why that is and if it makes sense at all, but it is how it is. So, in my opinion it does no longer make much sense to set a witness proxy as long as one wants to support proposals that the proxy does not want to support. Do you see the problem?
If you have multiple accounts and want to vote for all of them at once, that feature could be of use, of course. Otherwise I would recommend to reset your witness proxy.
As I know that many people would have asked me later, I added a context hint for those cases:
There is another case that I want to explain here:
Here the voter has set a proxy and the final proxy has also voted the same proposal. So, the voter's influence is not lost in this case, but of course, it could be in future, if one of the proxies should decide to set a different proxy or remove his vote for the proposal.
As some of you may not know, you can set a witness proxy and that proxy can also set a different witness proxy. The maximum length of what I call a proxy chain is 4. Don't ask me, how I managed to still make the data load quite fast. It was really fun for sure to build this, I tell you.
In the meantime I added a small summary in the dialog:
If all of the following voters of my proposal would reset their witness proxy, I would already earn with the SPS:
@likwid, @exyle, @nextcolony, @mattclarke, @slider2990, @bdvoter, @ash, @preparedwombat, @freiheit50, @ericet, @backinblackdevil, @scrooger, @masterthematrix, @alucian, @chrisrice, @ankapolo, @zelenicic, @georgeknowsall, @artemisa7, @dunsky, @jonknight
Let's do it!
Voting for proposals is not yet possible on SteemWorld, but this will be added in the next few days.
More to discover soon ;)
If you think that I bring value to Steem,
please vote for my proposal:
Thank you for supporting my work!
Lieber @steemchiller,
ich hatte gerade meinen Proxy geändert und ein paar Sekunden später erst daran gedacht, dass das eventuell Auswirkungen auf deine SPS-Finanzierung haben könnte.
Ich habe es sofort wieder rückgängig gemacht.
Bitte, hat es Auswirkungen auf deine SPS-Finanzierung, wenn ich einen anderen Proxy als dich wähle?
Und wenn ja, wie soll ich bitte vorgehen, damit ich dir für deine SPS-Finanzierung erhalten bleibe, wenn ich den Proxy ändere.
Lieben Gruß, @double-u
Moin @double-u, solange dein neuer Proxy mein SPS-Proposal auch unterstützt, wird es keine Auswirkungen haben.
LG, Chiller
Hi @steemchiller,
das tut er im Moment noch nicht.
Kann ich nicht unabhängig vom Proxy für dich beim SPS stimmen?
Ist im Moment durch mein Rückgängig-Machen wieder alles wie vorher für dich?
Edit:
Der Proxy forum.orcinorum ist gerade dabei, für dich zu stimmen beim SPS.
Sagst du bitte kurz bescheid, ob das geklappt hat.
Danach setze ich diesen Proxy wieder.
Wenn noch mehr Leute jetzt den Proxy wählen und der mich nicht wählt, verliere ich diese Stimmen. Also ~ 300000 SP habe ich heute irgendwie verloren...
Wenn man auf https://steemworld.org/proposals auf die Gesamt-SP klickt, sieht man ja die Details, welche Votes zählen usw. Die Gesamt-Summe in der Übersicht wird in der Blockchain nur stündlich aktualisiert, aber in der Vote-Übersicht kann man immer die aktuellen Werte sehen.
Die durchgestrichenen Accounts haben mich zwar gewählt aber der Proxy nicht und daher zählt deren Vote dann auch nicht. Kann man da alles genau sehen ;)
Edit:
Musste nochmal editieren, da der Steemit-Editor meinen Kommentar mit dem alten überschrieben hat. Ich hoffe, das wird bald behoben.
Die müssten jetzt gleich wieder da sein von forum.orcinorum.
Super! Hat geklappt und ich habe jetzt mehr Unterstützung als vorher :)
Ja, du müsstest 1.085.836 SP von forum.orcinorum erhalten haben.
Jetzt kommen gleich noch meine 102.000 SP hinzu ;-) PROST! mein Lieber!
Edit:
@steemchiller: So, meine 102.000 müssten jetzt auch noch hinzu gekommen sein.
Edit:
Wenn ich das richtig sehe, bist du nun noch eine Position nach oben gerutscht ;-)
The linking of Witness Proxy and Proposal voting was not explained and it doesn't make sense.
It took me months here to understand what voting for a Witness means. Proposals are much easier to understand. There is no need to couple these distinct actions.
Posted using Partiko iOS
I agree, would be better to have a distinct SPS proxy setting for that and a
set_sps_proxyoperation for the RPC nodes. This would require to add an additional field likesps_proxyin theget_accountsresult and thelist_accountsmethod would need to be updated to be able to search for accounts ordered bysps_proxy.I hope something like this is planned for a future hardfork.
At least we (all) now know how it works.
Well, probably not surprising, but I disagree, and I would be opposed to such a change. The original spec for SPS stated that voting for proposals would work like voting for witnesses. And it was not an accident that we didn't create a separate proxy process for proposals. Adding the need to set multiple proxies for two very similar kinds of voting just means more things for a user to manage. In practice, I don't think most users should be proxying their vote anyways. The two main cases where I think it makes sense to proxy your vote is 1) when you have multiple accounts (this applies to a number of large stakeholders) and 2) when you're no longer actively involved in steem and are just holding a passive investment. In both of these cases, you're probably going to want both to proxy to the same place.
No hard feelings, you guys did a great job with planning, developing and testing the SPS. So far I didn't see any major issue coming up and it seems to work stable.
Maybe my wording was a bit rough, but I still think that it would be better to have a separate proxy setting for that. An alternative solution could be to prioritize the direct votes, so that there is a way to vote for proposals, which the proxy doesn't want to support.
I agree. Some witnesses had something like 'set us as witness proxy, if you trust our work and you don't want to keep on track what all the other witnesses do' in their post signature. I guess many people don't know that they cannot support any SPS worker as long as they are proxying their vote. You know that most people don't read the technical details as carefully as developers do.
In this case, I think the better and simpler thing to do is to drop their proxying and cast their own votes.
That is one of the positive effects of the current logic. More people with proxies set will begin to inform themselves about how it all works and they may want to make use of the new possibilities too, which is only possible by resetting the proxy... :)
Hmm, I wasn't aware of it, but that "set us as witnes proxy, if you trust our work and don't want to keep track what all the other witnesses do" sounds like a particularly terrible suggestion. To me, there's a big potential conflict of interest in having witnesses also being proxies. It's almost a shame I can't downvote witnesses for that :-)
HUmm.... the down voting witness is indeed interesting. After all, I may want to prevent more a "problem" that "promote" a good thing.
I desagree absolutely.
Having witness proxy linked to SPS voting has broken some of my other accounts proposal voting to a non desired direction(sorted now ofc). That’s not good at all, at least to me.
I don’t think setting a witness proxy implies not being active on the community.
I’m fortunately monitoring the proposals stats regularly and spotted something was wrong, then read this post and noticed the issue...it’s not a light one, it’s actually a mess in the proposals votes and have affected the stats of my chosen ones.
This is not one would spect although it may appear reasonable.
I stick on a separate behaviour or at least a massive communication to users how this works for the proposals system. It caught me unaware, I have not enough time to read deeply the tech info and I think I’m the average user here.
Cheers
My suggestion is that the UI's (e.g. steemit, busy, steampeak, etc) should just warn a user if they try to vote with a proxied account that their vote will not count until their proxy is canceled.
That would be awesome...I would include it in the steemproposals site as well.
Steemit has opened an issue to make this change in their UI: https://github.com/steemit/wallet/issues/103
That’s a cool start to sort this out. 👍
So as a user (example) that does not want to vote, but wants two types of "profiles" of proxy to vote, that user is doomed to choose either one or the other?
I am pretty certain that users that vote for witnesses like me, have a completely way of voting for proposals, again, like me! For me it does not make sense that proxies fill the same bucket. Even if that means less participation. For me, a different problem.
In regards to the work involved. I am fine with the current strategy as long the separation of the proxies is planned and will be carried over in the next HF or soft.
Oh je, das mit dem Proxy war mir gar nicht bewusst. Aber ich denke das es bei mir wohl keine Rolle spielt, da meine Zweitaccounts ja auch für Dich stimmen. Eventuell werde ich heute Abend diese Stimmen zurück nehmen.
@mattclarke proxies to me. I'm now supporting the proposal. Thank you for all that you do on steemworld.
Thank you!
@steemchiller, is there a best manner to receive help in using features on the steemworld website? I've made comments on your posts in the past, and I usually get a courteous response, so here goes.
I have been trying out various avenues suggested to me to create an account, many of which send me an error without explanation for the reason. Recently I paid 3 steem to create an account using steemworld, and it was also unsuccessful. Was able to sign the transaction using keychain and received this error message: "KeyChain returned no error text."
Not able to sign the transaction with steemconnect.
Still have 1 account tickets available I wish to utilize.
Thank you to anyone who responds with assistance. Been a fan of steemworld since the beginning, and I would like to support it by using the account creation feature.
It looks like SteemConnect does not support the operation
create_claimed_account(a 'new' operation that came with HF20). This has been the case for KeyChain too, but it worked in my last test. I just needed to update the extension. Do you use the newest version? Chrome/Brave or Firefox?When I'm done with my current stuff, I will try to create 2 accounts with KeyChain (one with a Chromium based browser and one with Firefox, because in the past there have been big differences regarding Steem API support in KC between those two).
I will come back to you later ;)
Okay thanks.
I'm using Chrome for my KeyChain extension. There was a Chrome update today I just ran.
I got it to work with KeyChain in Firefox and Brave, but I needed to change something on my side. Normally the
requestBroadcastmethod accepts the operation data in the same format as the SteemJS API does, but this is not the case for the fieldjson_metadata. I guess they changed something in their serializer.Anyway, after refreshing the page it should finally work now :)
Bingo!
Thank you. This is a great service.
Lieber @steemchiller,
irgendwo habe ich gelesen, dass du die SPS-Kriterien geschafft hast.
Wenn dem so ist ... Herzlichen Glückwunsch!
Ich möchte noch mal auf einen Kommentar von mir zurück kommen, da ich annehme, dass die Sache eine Kleinigkeit ist, die du sehr schnell ändern könntest. Ich hoffe, ich vermute richtig.
Hier war meine Frage:
https://steemit.com/steemworld/@double-u/pxklbi
Lieben Gruß, @double-u
Hi @double-u!
Ja, ich habe es geschafft und ich freue mich sehr darüber. Um ehrlich zu sein (wie ich ja schon erzählte), kann mein Konto auch unbedingt etwas Unterstützung gebrauchen... Die ersten Einnahmen werde ich also auf jeden Fall direkt auszahlen, aber in ein paar Wochen kann ich dann auch einen Teil davon aufpowern und die Community damit unterstützen.
Die Sache mit dem Aufklappen der Operationen wird erstmal so bleiben. Eventuell werde ich dafür noch eine Option in den Einstellungen hinzufügen (oder per Strg + Klick), aber bei vielen geladenen Daten führte das Zuklappen zu merkwürdigen Phänomenen (blinkte mehr als gewollt), daher muss ich das bei Zeit nochmal prüfen. Vielleicht hatte es auch mit meinem Browser zu tun. An sich gefällt es mir so, wie es jetzt ist, sogar besser.
Ich bin noch nicht dazu gekommen, dir im Chat zu antworten. Du weißt ja sicher, dass einige Menschen länger brauchen, um zu verstehen, wie man mit anderen umgeht. Mach dir da mal nicht zu sehr 'nen Kopf wegen denen. Wir sitzen ja alle im selben Boot und das ist es, was am Ende zählt und uns alle für immer vereinen wird.
Wenn man mit Dingen beschäftigt ist, die man liebt, kann einem sowieso nichts etwas anhaben und das Gute kann dabei nur wachsen. Versuch mal ein paar Tage alles Negative zu ignorieren und du wirst sehen, wie sich deine Realität zum Positiven verändern wird ;)
LG, Chiller
Hi @steemchiller,
Meinst du, du könntest eine Option in den Einstellungen hinzufügen?
"Per Strg + Klick" fände ich nicht gut.
Danke! Und liebe Grüße, @double-u
Ok, @double-u :) Nach näherer Betrachtung komme ich zu dem Ergebnis, dass es doch vorher besser gelöst war. Ich habe nun eine neue Option unter
Settings -> View -> Maximize Multiple Operationshinzugefügt.Die Standard-Einstellung ist jetzt wieder
No. Als kleines Bonus-Feature habe ich es jetzt so gebaut, dass man mit gedrückter Steuerungstaste (also Strg + Klick) trotzdem mehrere gleichzeitig maximieren kann. Die Option wird in dem Fall einfach temporär ignoriert.Danke für den Denkanstoß! Hast mich im richtigen Moment erwischt ;)
LG, Chiller
Super! Funktioniert alles ganz toll!
Herzlichen Dank!
Und lieben Gruß, @double-u
Voted in favor of your proposal soon after your initial post @steemchiller!
Glad to see you are getting some support, and getting closer!
Your campaign (which is being supported by a large number of people in the community) seems to be showing at least one "bug" in the system: On the SteemProposals web site, a project (evidently) can't display more that 300 supporters... so even though the actual support is far ahead of this, what is SHOWN to voters is this:
This was as of a few minutes ago. In reality, I think you are only missing about 800K's worth of votes...
I think @dmitrydao needs a ping for to be let known of this bug.
Fixed. Thanks for catching this.
Sorry, supporting a closed-source project without any concrete deliverables or QA/QC with community funds is a non-starter for me. It's a great project, but you are drastically changing your funding model by drawing from this well. Your operations should reflect that.
As I mentioned earlier in a few comments, SteemWorld will be open source next year, but I need some time to prepare for that.
I added the following to my proposal post, so that no one will miss it:
It's not really clear to me why you can't publish it now, if your plan is to open-source it. Is there some proprietary code that needs to be removed first? Or are you just concerned that the code is "messy" now? If the latter, I don't think this should stop the process. In any case, as an aside, if you do open-source it, I'll add my vote to the proposal (note that this isn't a promise of long term support, that would depend on future progress).
It's the latter and I really have a problem with publishing imperfect code. It all started with a small toolbox, but it grew quickly to a big codebase, which I'm still cleaning up over the time. It took me weeks already and I know that many developers won't bother to do this, but I want to complete it, before publishing the whole thing. So far I made good progress and I think that in a few months I'm done with it.
Of course, this kind of work is important but not highest priority for me and I don't do it the whole day, because there are many other things that also need to be done.
On the client-side I didn't work with arrow functions in JS from start on and I mainly used simple {} objects instead of classes, statics and inheritance. A few years ago there was not much browser support for all the things we now can use in JS, but that's no excuse for me. I don't want to keep the code in kind of a deprecated state. Publishing it now would cost me more time than cleaning it up prior to that.
For the server-side I developed a blockchain parser in PHP, which is still being used (until I can switch to my planned SDS). It parses the chain, stores blocks (for later replays) in compressed SQLite databases and builds the dbs for the mentions, incoming delegations, delegation history, witness stats, transfers search etc. It also contains a request handler class that handles the requests coming from the clients on SteemWorld and a simple ticker API that caches the market prices for currencies and many cryptos.
I assure you I'm sitting here more than 12 hours a day 7 days a week to get all this done. That's no problem for me, because I did this for many years already and I have always been kind of a creative freak. I developed my first stuff when I was ~ 14 years old. I am now 34. I worked for 8 years as software developer in a medium-sized logistics company, collected a good amount of money for my dream of being self-employed and lost it all shortly after I started my business, because of a huge mistake with highly leveraged gold trades.
So, that's a part of my life story. I won't give up on this one, because then nothing else would make sense anymore.
The organic community obviously loves and respects all the hard work you have put into this invaluable tool, thank you for all your hard work, and no mind to the gatekeeping trolls.
Great. Please come back with another proposal then. Until them, I'm reluctant to support spending limited community funds on closed source development (which does not mean I will never support it, but its a serious obstacle).
Done and done! I set it to @qurator who is also supporting you all the way! Good luck and thank you for Steemworld!