Cross posting on (Hives)

Communities or «hives» are still something very new for all of us and we must understand how they work. The option we have is to look for all the information that has been published about it and the classic «trial and error».

For this new stage,, which is an extraordinary and beautiful dApp, presents some different alternatives to those offered by

There is one of them, called «cross post» I found interesting, because it raises the possibility that you post the same content in several communities. This implies greater exposure and being able to cover different audiences.

There is a complicated point to understand in this new modality, because if the new communities (understand that now when I talk about communities, I am referring to these hives) are too «wide content», such as Cervantes or OCD, it would not be fulfilling the purpose of being thematic communities. But, if on the contrary, they are too specific or specialized, the content will be limited to a minimum number of users, that is, those who are subscribed to that community.

Therefore, a tool that allows publishing in several communities at the same time would come in handy. But…

One of the most complacted aspects I discovered when using it, is that it is a tool that points easily to abuse.

At this time it has an additional limitation, that the result of “republishing” the content in the given community is only seen from

The procedure to do “cross post”, is that from the Steempeak dApp, you click on the three points that open the dialog window for editing, etc. and there appears the option «Cross post in …». There you choose the community where you want to share the content and you must write a review of a maximum of 100 characters, where you explain why you are sharing it.

This will generate a new post (it’s not like resteem), which will generate new rewards. In this post the user who is doing the cross post will appear as the author, with an indication that indicates who the original author is (in the case of content produced by someone else).

The full view of the review, along with the full content of the original post, will only be seen on, because on the other platforms you will only see the review that was written and the link to the original post.

The system places from the moment of posting, the original author as beneficiary of 90% of the reward. In other words, the main beneficiary is the original author. 5% is intended for the community in which it was published and 5% for the person who performed the operation (if it is someone other than the author).

The person who performs this operation is the author, therefore the post will receive the automatic votes that are scheduled to vote for this author. That is to say, if author «A» is in the fanbase of 100 people, that is to say, when he posts, he receives 100 automatic votes, at the time that «A» makes a cross-post of a post by author «B», that post will receive all automatic upvotes. that usually receives «A» and the beneficiary of 90% of that reward will be «B». This can be an extraordinary tool to support other authors who do not have a fan base, while giving them greater exposure.

However, the same tool can be used by the same author to publish the same content in different communities and receive the automatic vote many times on the same content, which can become an abuse or missuse of the rewards pool.

To avoid this abuse, the indicated thing would be to renounce the income generated by that publication. That is a process that I have not found out how to do it.

In conclusion, I think that the idea of sharing content in several communities at the same time is important, for the reasons explained above. But I think the way this tool is developed right now is not the best.

We will have to continue testing and think about the improvements that are needed.