Hey Ryze, now that I think about it. The change that you are shooting for might be more applicable as a condenser change. The condenser or the frontend is the portal whereby you view the hive blockchain content; It is kind of like a web browser is to the internet. Hive is a lot of different things to different people, and the social media aspect is just one of those things. So, for example, if you take a look at 'hive[dot]blog'—you'll notice on the upper right it says: "What is Hive?" The link points to an external link that is hive.io.

I think another or potentially better hyperlink they could have up there is: "What is hive[dot]blog?" Instead of it being an external link to hive.io, it could be an internal link where 'hive[dot]blog' can explain the social media aspect of itself to the visitor. Peakd.com could also link to this page if they wanted. Let me show you an example of what I believe to be a successful condenser level issue that caused a change on peakd.com.

This issue right here, I think this is what led to the creation of collections on peakd.com. I am not 100% certain, but it may be what led to those. And you'll notice that peakd.com picked up that change before hive[dot]blog got around to it. Sorry, I missed this response all those days ago. So instead of where I first directed you, your landing page may be more fit as something that explains the social-media aspect of 'Hive.' More specifically, issues for the hive condenser.

I hope this helps some, please let me know. At its core, issues are a glorified suggestion box for movers, shakers, and idea people. Seeing as how the project is a decentralized and collective effort, this means anyone with the ambition and ability to describe the idea to the coders and the coders can make it happen. I don't know what happens after one creates an issue, if it gets voted on or how exactly that part of the process works.