The prohibitions against copying and pasting are driven by Googlebot and other programs that monitor the origins of content.
If a person copies and pastes from SteemIt to Hive or visa-versa, Googlebot will penalize both sites for the duplicate content. (This does not happen with esteem.app and peakd because sites accessing the Hive Blockchain have an established system for identifying the source of the content.)
People who drop the same content in both platforms are hurting both platforms.
So, it seems to me that both Hive and SteemIt should discourage people from dropping the same post in both platforms.
I hope that @cheetah and members of the Hive Cleaner team start downvoting content copied and pasted from SteemIt as they would from any other source. I've been tempted to do that myself.
PS: I am still participating in both platforms; however, I put different content on both blogs.
For this post on PeakD, the HTML contains:
<link rel="canonical" href="https://hive.blog/hive-174578/@condra/hive-etiquette-and-conventions-are-we-approaching-some-clarity" />So yeah it seems like PeakD is pointing to hive.blog as the canonical location for the post. But there really should be a post-level option for which URL to use as the canonical link. This would allow content posted on Steem or Hive to pick one location as canonical to avoid being penalized by search engines.
Thanks for reporting. I did some improvements to better handle this in the next release ;)
Since STEEM and HIVE are different blockchains, I would not expect there to be any coordination between the two.
As for the rel=canonical links, I believe that they are trying to handle that at a programmatic level. The canonical is set to the platform that generated the post.
The comments are a complete mess because comments can come from a number of different sources. IMHO, comments should be treated as extensions of the parent. The blockchain seems to treat them as separate posts.
Things that appear on the same blockchain can be handled programmatically. Stuff that appears on two different blockchains cannot.
Rather than creating a complex system to accommodate people who want to post the same stuff on both forums, it would be better to discourage the practice.
What if I want to use Hive to cross-post content from my personal blog, as a way of permanently archiving the content? I think it's shortsighted to think that all text posted to the blockchain should exist solely on the Hive blockchain.
I agree here, comments can inherent the parents canonical URL provider.
Sorry about taking so long to reply. I decided to a answer the question by creating an example.
IMHO, one should design the work flow so that one's personal site is recognized as the canonical source.
So, what I did was write an article on my personal web site. I then wrote a post using PeakD which links to my personal web site.
Although the PeakD post and my site say essentially the same thing, I simply used different wording for both posts.
I want to use different wording on my post to prevent Googlebot from demoting my personal site for having copy and pasted text.
Because the PeakD article has a link to my article, Googlebot will recognize my site as the canonical source.
Another way to do this is to create a stub article on your personal site. Write the HIVE post with a link to the stub, then finishing the stub article. Regardless of the work flow, you want the text to be different so that Google does not demote your site for duplicate content.
I will now go to an unnamed social media platform that shares some similarities with HIVE. I will quickly type out a post with a link to my article.
I will end up with three articles pointing to my article. Each article has different text and Googlebot will love me.
The problem with using a personal site as an archive is that HIVE has a higher PR rank than your personal site. So, when Google sees that you copied a bunch of text from HIVE, it will ding your personal site. If you want an archive on your personal web site, you should block googlebot from reading the archive in robots.txt.
Take a loock at the actual comment from
f83e92172197bdf3b88556740feedd68034a868dto see the codeblock content.@steempeak @peakd, you have a bug where you're messing with text in code blocks. Preformatted text should be left alone!
cc @asgarth
Perhaps a bot to leave a comment on the hive post.
"We've found similar content on the Steem blockchain. Posting the same content to both chains reduces search engine rankings for all posts on both chains."
Actually the peakd team could add it to their front end, instead.
@jarvie, is this worth considering?
When I wrote my reply I was thinking about written words in the comment.
So, I started thinking about images.
It would be interesting to have a shared image repository for both blockchains.
Quite frankly, I don't think Googlebot tosses out penalties for shared images.