Anti-dilution will help increase BTS price, support! It's good for all of you who are holding BTS, I don't understand why you are against alt

The reason some say not to vote for this proxy is because that it has today 139,535,652 proxied votes, which makes this the most powerful proxy of the community. It votes for both refund400k and refund100k making a lot of projects not getting funded, some that has greatly helped to advance the community during the past year. This does nothing good for the community. If any time is important to spend and support development it's during down trends, when the support may otherwise be lost and users go elsewhere.

Just like Customminer writes....
 

Don't vote against worker proposals blindly, spending on WPs during downtrends ensures we're productive whilst others are stagnant, by cutting off worker proposals you intentionally stagnate Bitshares.

Anyone is free to vote for whatever reason they may have, I'm not against that. But delegating votes blindly to proxies is foolish. Those that support this proxy doesn't undertand how it hurts the development and progress of the community.

Of course, development is always happening, even if the community doesn't spend money or support them, but progress like this is usually neither fast nor coherent. Supporting developers is one good way to ensure quicker and coherent progress.

Yes, these two issues have been fixed recently. The misspelling was merged a few days ago and the market fee will be in the next release.
https://github.com/bitshares/bitshares-ui/issues/2375

As @xeroc mentions, a change in API node could help your problem. Your internet connection would have little impact on this, it's rather how overloaded the node you're connected to have.

You can change API node by opening the menu on the right top corner -> Settings -> Nodes. Try with running a "Ping Nodes" command, and select one node that is relatively close to you with a good ping time.

Hope this helps.

Thanks to few individuals going around and promoting this worker, believe that since this early AM, BitShares UI Worker is Active and just ~2M votes above refund400k.

Please keep giving in Your votes. [/center]

Chee®s

Indeed appreciate these that help us promote this worker. At the moment the worker have passed the refund100k worker as well.
Looking forward to a great 2019 with great progress and development for Bitshares!

Happy holidays everyone.

@iamredbar thank you for your continued trust.

It has been a crazy few months, and we've had MUCH work to do on the UI. Thanks to the funding from the community we've been able to have plenty of community support by react developers in various stages of exprience. The main team have had plenty to do and learned alot along the way. Remember that we've all started in the middle of the project at some time or another, none of us was in the start of this.

Just during the last month of the year we had plenty to do to add functionallity for globally settled assets that was added to the core a while ago. Since bitUSD, and plenty of other assets, suffered this from the fall of BTS price. The whole team enganged in added new functions and test them to make sure they worked as intended.

Despite comprehensive testing tries, we do sometimes have issues coming up afterwards. One of the biggest changes we did was also to change the release schedule to also have a 'Release Candidate' before the actual release. We do our best to catch issues before they get out to the main release, but since the team is still not a large one, we rely heavily on othes to help us test. Once an issue is identified in a release candidate that is major we will make a fix for it before we do another standard release. This has been a big change, and something we've had to grow into and find good ways to work with.

To visualize how much issues that have been created, addressed and closed by the team since the community started funding the worker of Bitshares-UI.
We appreciate the support from the community to be able to do this work, and to continue enhancing the UI.



Repository activity for the last month.




Sources:
- https://github.com/bitshares/bitshares-ui/pulse/monthly
- https://repohealth.info/report/bitshares/bitshares-ui

I support this BSIP. It tackles the issue of ancient voting power that is used and forgotten.
A vote for something should decay of time, and actively recast to remain. This would make a more active/engaging community and would give ancient whale votes less of an impact when they start to decay.

I'm interested in seeing the discussion on this and a good way to implement it.

Bitshares UI supports Beet in long-term development


A recent addition to the family of Bitshares applications is the Bitshares Companion application, now called Beet. The app was initially drafted and by clockwork, which handed over the source for the Beet application to the community.

The goal of Beet is to make it easier for third party applications to work on the bitshares network, without having to worry about handling the private keys on these applications. Beet will be the handler for signing the transactions, while the application using it can focus on usability and functionality.

The bitshares teams believes that Beet fits nicely under the current UI worker in long-term development. Beet development will for the moment be supported by the UI worker and agreed to compensate for the initial development as source was released to the community. The project manager of the UI worker will handle issues, assignments, compensations in the same way as the current UI repo works today.

We see great potential of development for Bitshares applications with the addition of Beet. While Beet is still in very early alpha, having it compensated under the current UI worker will make development speed up, improving the ecosystem.

Beet Gihub Repo, https://github.com/bitshares/beet

The UI team also wants to inform that it will receive some extra support by Stefan Schießl during the month of August as Sigve is on a well-earned holiday.

Thanks for your support and your feedback.

@oxarbitrage:
I'm happy that you've noticed the changes we've worked on during the last worker. Happy to see your support of our continued work.

@kimchi-king:
I'm glad you've taken the time to have a conversation about the worker with Stefan Schiessel and that you've decieded to give your support to it for now, and I hope I can help with making you able to comfortably continue to do so over the comming period as well.

Reading your response makes me understand that one concern is clear updates on what is going on, what has been done and what the future plans are. As new Project Manager of the team I can promise that this will change from now on and I will start to write at least monthly updates on this, making sure that everyone understands what is happening, and why something may not be happning. I've previously posted updates about releases of the client on Steemit, something I'll also do as part of my new assignment.

I believe that while the current github setup, with issue and hour tracking, have been thought to be transparent enough we can definetly find ways to be even more clear. We are paid by the bitshares community after all, and should provide some details on what is happening.

Reading that you have potential UX designers that could help out with designs to be worked on is a really good thing, as we've so far had to few people with this skill on the team. We've started to recruit some new people, but we're always interested in having a buffer for now.

Right now we need to coordinate the team with enough work and UX designs to be worked on that we can see the  improvements that the community wants and deserves.