A few ideas for developing for Blurt

in blurt •  4 years ago 

Hello. These ideas are based on the use of other blockchains, as well as on dreams that they will be implemented at least somewhere.

1. Multilinguality

I'm not talking about specifying the language in tags. This, of course, is good, but it leads to the fact that absolutely all posts are located on the same tag.

Suggestions:

  1. Or language selection functionality: ru, en, de, fr, cn, etc.when creating a post with the ability to filter feeds by language.
    Naturally, each language has its own tags.
  2. Or a block with a list of popular tags (categories) in the selected language. We need UTF-8 support in tags so that you can write them in any language, not just English.
    In the api, such a block can be created using a method that passes the language tag to. The tags that are most often used with the selected language tag are returned.

2. Returning part of the delegation

Let's say you found a curator who supports cool posts. If you delegate to it, it gets all curation rewards (its blurt power + yours).
The idea is that when delegating, you can specify the percentage of curation returns: 0% - this is nothing for you, 100% - everything for you.

In the Golos blockchain (https://github.com/Golos-blockchain/golos) this functionality is already implemented.
But for some reason, they passed the restriction setting to delegates, although the minimum and maximum percentages should be set by those who accept delegation, i.e. curators. To do this, you can create an operation like this:
" `
["config_return_curation_rewards_percent",{"min_percent": 1000, "max_percent": 8000}]

This will make the project even more interesting for those who want to buy tokens for curating content, including through delegation to interesting participants.

## 3. Linear distribution of votes for delegates
Currently, 1 vote = the amount of blurt Power. It turns out that if a user has 1 MILLION Blurt Power and he voted for 10 delegates, this is like 10 MILLION (1 delegate is the entire amount).
the
Essence of my proposal is that the amount of Blurt Power should be divided by the number of votes. For example, if a user with 1 MILLION BP votes for 10 delegates, each will get 100,000 BP.

Even better, if you can vote for each delegate with a different percentage: someone will give 15% of their BP, someone-25, and someone the remaining 60%.

This will increase decentralization and allow new investors to influence delegates.

You can also borrow a vote with a split stack by the number of selected delegates from Golos blockchain.

## 4. Polls, voting system.
This question arises in one way or another for users who run blogs.

I propose to implement a system for creating surveys and voting on them at the blockchain level. And that the result depends on the amount of Blurt Power. This will create another reason to invest BLURT in BP.

## Whole
Thank you for your attention. The blind developer and author @denis-skripnik was with you. See you in new posts.

Next, I will share one or more videos from my life.

PS unfortunately, I don't know much English, so I use automatic translation. If you have any questions, or something turns out to be incomprehensible, ask: I will try to explain it in other words.
Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE BLURT!
Sort Order:  

I think they are good suggestions, personally I very much support the idea of being able to translate the interface and facilitate its use in different languages, since I have seen that certain communities are very active and their native languages are not necessarily English, such as are the bloggers in Korean, Chinese, Bengali and Spanish that I follow and who write interesting posts.

In fact, my native language is Spanish and here in blurt one of the friends with whom I comment the most writes in Chinese, so it would be more comfortable for both of us to have the possibility of publishing both in a common exchange language as well as in our languages natal.

Yes. I hope they implement this functionality.