After a bit of bait, and closed beta, we are finally rolling out our "yourFrontend" Hive-as-a-service offering for any user whether they are familiar with HIVE or not.
HIVE supposedly is a great place for everyone, but be sure to have your own front end if you think its important to control how your content is displayed, who is visible, what is visible, and other such things. It is not professional to show a disagreement about rewards, or let some rando whale decide that your biggest investor is unworthy to have his comments seen for unrelated reasons.
But the solution is here! And before long, will even be open source. But one step at a time - I think its working!
Okay, let's start slow, because I know that no matter how many posts I write about this stuff, its still dense for distracted minds, and someone will be saying - wait, what is this again?
You can have your own frontend, its not hard, and many have done it before in a bespoke manner. This is the first (that I know of) comprehensive "HIVE-as-a-service" version of this simple and "old as HIVE" idea that everyone can have their own frontend, since all the data is stored on the blockchain.
No votes shown! neener neener 😜
Once you purchase the microservice (currently set at 2.9 hive per montha, read more here), we have to update our settings. Subdomain is used for display, we are happy to host it on our own domain, but even so users will be able to see and adjust before moving to their own domain or even to hosting their own based on our open source code (coming soon, its almost viable for release).
This produces a configuration file in line with the open source use of the product, and you can see it on the page:
Once this is set up, we will need to do some manual work, which we are happy to do at our manual pace, 2-3 times a week most likely. Our admin interface is all set up for this, and there are a few things to be said about this:
First time set up is always going to be like this. We have worked hard (so hard) to make this as streamlined as possible, but there is nothing we can do to avoid this one manual click on our end the first time. Our system is set up to rebate/add days to the expiration date equal to the time between registration of the service config and our delay in deployment. For example, if its 2 days, you will get those 2 days added on to your service expiration date.
But once its set up - you can edit it as often as you like - live and integrated with our api service. Just log in, adjust the settings, and boom. This is simple and easy, just for you dear user.
Your instance information is viewable by you, and the configurations are also completely yours, again, you will be able to use this to test, and then deploy yourself if you like.
Next on our to-do list is to allow custom domain forwarding, so that once you are happy you can get us to point to a domain or subdomain you control. This has some interesting follow-ons for all of HIVE, related to backlinks, but we have plenty of time to talk about secondary uses after we get our main user set - the "corporate" account.
We are working hard - we never stop. Feel free to participate in this process, try it out or even request features on our latest is this worth money post. You can ask for features for free at any time as well, but we will always prioritize those who go through the steps to get on "My Radar", as explained in these posts.
And give our 
