Look, I get it – a lot of people hate Justin Sun and they want to screw them over however they can. Effectively stealing links from Steemit.com and redirecting them elsewhere, specifically to Hive-oriented front ends, is one way to do that. I get it.
What do you talking about?
I wrote the post Howto to use beempy for cold transaction signing
on the Hive network using peakd.com. busy.org is now serving HIVE content alone, therefore I included the site.
According to the open standard from 2016 Improving SEO:
Most frontends have been specifying the originating app on each post for some time, but now we have an open standard for signalling to Google and other indexers the authoritative (canonical) URL of any Steem post. This will help give “link juice” to the originating apps.
the canonical URL should point to the homepage of the originating app according to this open standard which is also valid on Hive.
As I wrote my post with peakd.com, the canonical URL should point to peakd.com and according to the open standard, busy.org and leofinance.io should use the same canonical URL. Of course, they can decide not to follow the open standard ...
I see that there is a problem with duplicate content for posts, which were written before the fork. All these posts are now available through the Hive and the Steem APIs. I propose that each content creator deals with this situation as he likes.
RE: Canonical links of Hive posts and duplicate content