I claimed my Hive-Blog channel and my PEAKD channel about a month ago, and I began to transition over from the Steem blockchain to the Hive blockchain. Like many of you, the transition has been somewhat of a memorable event in my life. If you recently claimed your account here on the Hive blockchain and you are trying to pick up where you left off on the Steem blockchain, then you likely know exactly what I was going through once I first began posting here on the Hive blockchain.
It is nice that the Hive blockchain has duplicated all of my articles that I posted on the Steem blockchain up until spring of this year. However, as many of you will likely notice with your Hive-Blog channels and PEAKD channels upon transitioning over from the Steem blockchain, there are some loose ends that always need to be tied up.
The first thing that I had to do was to update all of the articles of mine that the Hive blockchain had duplicated from my Steemit channel and my STEEMPEAK channel. In other words, because I had made corrections on those same articles on the Steem blockchain since spring of this year, I wanted to ensure that their Hive counterparts were completely identical to them. I know that it may sound odd to some of you, because there are going to be those of you who never correct any typographical errors that you find in the articles that have been duplicated from your Steemit channel and STEEMPEAK channel to your Hive-Blog channel and your PEAKD channel; and that is okay. The reason that I make corrections of typographical errors that I spot on old articles of mine is because periodically I like to refer back to them in my new articles and provide a link back to them.
The way that I updated those articles of mine here on the Hive blockchain to mirror their counterparts on the Steem blockchain was that I went through each and every one of them and erased what was there. Then I would go into my Steemd account to copy the contents of each of their counterparts to their Hive counterparts one by one in their HTML format. It may seem tedious, but I thought that it was well worth it inasmuch as I wanted to give my readers the best experience I could do so whenever they viewed my articles here on the Hive blockchain.
Now, some of you are going to ask me the million-dollar question, which is, "How do I address the problem with my links in those duplicated articles here on the Hive blockchain directing my readers to a copy of an article of mine on my Steemit channel or my STEEMPEAK channel in the event that I made reference to any other articles of mine in my same articles?" In other words, if you made reference in one article of yours to another article that you initially published on the Steem blockchain, then, yes, a click on a link that you may have incorporated in that same reference will direct a reader to that same other article of yours on the Steem blockchain rather than on the Hive blockchain, even though you will already have a copy of that other article of yours on the Hive blockchain.
Here is my solution to that same problem. You go into the HTML codes of your Hive-Blog or PEAKD article and you look for something in the address to your other Hive-Blog article or PEAKD article that reads "steemit.com". Then you replace it with "hive.blog" or "peakd.com" so that when one of your readers click onto the link, it will direct them to that same article on the Hive blockchain rather than on the Steem blockchain. It's as simple as that.
Learning all those ins and outs of using the HTML codes makes life easier here on the Hive blockchain than what you may imagine. It is good to read articles here on the Hive blockchain to learn about ins and outs of this nature, although, like me, many of you are probably going to learn these digital skills through osmosis in the proverbial school of hard knocks.
Another valuable practice that I have picked up ever since I transitioned over from the Steem blockchain to the Hive blockchain is that I initially like to compose my articles on my Hive-Blog channel and then upgrade them to a PEAKD article by performing edits on them on my PEAKD channel. This practice makes my composition of each article go much smoother than it would if I tried to compose them on my PEAKD channel. I can also add a description of that article that shows up on my PEAKD channel, and it also allows me to use up to ten different tags on that same article rather than only eight tags. Of course, I will have already have incorporated the first eight tags after initially composing the article in my Hive-Blog channel.
Many of you may prefer to compose your articles directly on your PEAKD channel rather than doing so on your Hive-Blog channel, which is fine. However, I find that my Hive-Blog channel is much more user-friendly in that respect than my PEAKD channel, while my PEAKD channel offers more features to get my articles out there and read by more people. Whatever works for you is what you should do.
This time, however, will be the exception for me, because every time that I try to type in the initial eight tags in the composition screen of my Hive-Blog channel, I either get the following message: "Must end with a letter or number" or I get: "Please use only 8 tags." I don't know what could be going on tonight with my Hive-Blog channel, because I had no trouble using it earlier today. Therefore, I published this article here of mine on my PEAKD channel this one time instead. I guess that I just have to roll with the punches.
This Article Is Copyright-Protected.