You may have heard the term "canonical links" or "canonical URLs" as they relate to SEO (search engine optimization). In a nut-shell, this is the standard for where an article is originally published.
Fortunately, the charging one has been solved now that we've all standardized on mini-USB. Or is it micro-USB?
It's considered good practice to avoid reposting content all over the web. Search engines typically encounter such a situation and have to figure out where the content was originally posted, in order to optimize results.
But on Hive, it's possible for duplicated content to legitimately show up in multiple places. Either because there are multiple frontends (like hive.blog or peakd.com) or because of blockchain explorers (like hiveblocks.com or hive-db.com).
Even without a blockchain, syndicated content is a valid reason for duplicated content. For this reason, search engines have agreed to accept the idea that duplicate content exists and have provided guidelines to help optimize.
The guideline includes the use of special non-UI tags that appear (hidden) in the page in order to clue the search engine in on this situation.
If you go to a post without these special tags, the page is asserting that they are the origin of the content (correctly or incorrectly). If the search engine determines that this is untrue, it could potentially have a negative impact on page ranking, especially if it's an ongoing pattern of behavior by the domain.
To demonstrate this, I operate a domain called hivedocs.info where I host hand-picked content related to development of Hive tools. For example:
https://hivedocs.info/news/2020/03/17/announcing-the-launch-of-hive-blockchain.html
In the above page, you will find a post that was originally published to:
https://steempeak.com/communityfork/@hiveio/announcing-the-launch-of-hive-blockchain
The content is identical. But I have provided a non-UI element in my version that points to the original version:
If a search engine encounters hivedocs.info, it will see that I am "mirroring" these posts in order to highlight them, but I'm not asserting that these posts originated on my domain.
In theory, there could also be sites out there that do not take these steps to ensure proper canonical links. Sometimes, it's because they don't know about these optimizations. And some of them are trying to pull a fast one, claiming that they originated the content (for plagiarism or other nefarious reasons).
There are tools to help identify if content is properly tagged with canonical links. The one I tend to use is called Inspect Canonical. If you'd like more information about how Hive approaches these concerns under the hood, check out Hivescript for canonical links and SEO by @good-karma.
This is pretty interesting and surely didn't know that you can do that and use hidden elements and still preserve the source of a piece of information. While there is a long road ahead but considering that blogging is one of the HIVE core function, I think is great to inspire and use such approaches.
While you don't necessarily need SEO on HIVE, you need it on other web pages to have good ranks.
What we don't want is for anyone to think Hive is just a content racket trying to game the system. Paying close attention to SEO guidelines reduces the chance of being perceived as a "copypasta ring."