Waivio updates: May 15, 2020

in #waivio4 years ago

User profiles can now be edited using posting keys instead of active keys. Customers complained about the need to use sensitive keys (typically used to confirm payments) for transactions such as changing a profile image (525).

image

Several other Hive sites also support this new standard. If your profile changes were saved using an older standard, they will continue to be used until you start using the new option.

Approve / Reject votes on updates

If you have activated a voting slider in the account settings, it will now also be available for changing the voting power on object updates.

image

This can be a useful tool to adjust the power of your Approve or Reject votes.

Admin roles for objects

Waivio has introduced administrator privileges for object editing. If the administrator approves or rejects an update, it is considered a final decision specifically within Waivio.com (470).

image

At some point, administrator roles will be used for custom websites, which will be built using the Waivio platform. This feature can be used to ensure that the selected objects cannot be easily modified by the community (for example, contact information, legal agreements, affiliate links, etc.).

As we approach the development of a platform for hosting social sites, the roles of administrator and moderator will play even a greater role in ensuring the accuracy of the data within the managed domains.

Other updates and bug fixes:

  1. Object cards - display full address, when possible (312, 520)
  2. Feed - object follow (342)
  3. New posts - remove image credits (360)
  4. Rewards - synch map with the list (429)
  5. Recievables - views for other beneficiaries (443)
  6. Rewards payments - balance tracking (444)
  7. Receivables, payables pages - revised design (446)
  8. Image uploads - display variable sizes (455)
  9. NSFW objects - hide from search, unless enabled (460)
  10. Post beneficiaries - basic management (472)
  11. Image previews - support for embedded formats (483)
  12. Lists - universal approve/reject indexing (494)
  13. Object images - universal approve/reject indexing (496)
  14. Profile pic - support for multiple formats (498)
  15. Rejected name - use original object name if no alts (500)
  16. Slider on updates - allow variations in voting power (502)
  17. Object icon - use parent icon when upspecified (503, 542)
  18. Manage campaigns - include processing fees in the estimates (504)
  19. Campaign activation - specify all secondary objects (506, 509)
  20. Manage campaigns - ability to create duplicates (515)
  21. Rewards / All - display all available campaigns (518)
  22. Object tags - same tag in multiple categories (524)
  23. Profile - update object expertise view (536)
  24. Discover / Users - accurate follow statuses (538)
  25. Profile - number of followers (539)
  26. Approve vote - browser compatibility (541)
  27. Profile - combining data from multiple standards (545)
  28. Creare campaign - specify default values (546)
  29. Guests - rewards campaigns eligibility (547)
  30. Post drafts - saving images (549)
  31. Photo galleries - processing of rejected photos (555)
  32. Updates sorting - recency, approval, vote count (558)
  33. Release note - visibile portion of the comment (560, 562)
  34. Payables, receivables - new front-end code (566)

Waivio is an open source project. If you believe that what we are building is beneficial to the Hive ecosystem, please vote for Waivio proposals on the Decentralized Hive Fund.

GitHub - https://github.com/Waiviogit/waivio
Discord - https://discord.gg/sAkPkFv
Twitter - https://twitter.com/waiviolabs
Hive - https://www.waivio.com/@waivio

Sort:  

what happens if two admins cast opposing votes (approve vs. reject)?

When multiple admins vote on the same update, only the most recent vote is counted.
So, if the last vote by an admin was to reject the update, it will be rejected, regardless of previous votes of other users with admin privileges.