How to INCREASE HIVE-blogging/LEO-threads USAGE TREMENDOUSLY without Marketing - integrate Music platform(s)
Now you think: "edje is crazy"
Maybe I am, but I am pretty sure we can achieve massive exposure to people in and foremost outside the crypto space without the need to use the marketing instrument. Through that massive exposure, we will - likely - gain substantial amounts of new active users.
In the comment section of this blog post, I touched on a few examples that came to mind when I got into a conversation with the author who voiced the idea of filling LeoGlossary with Film and Music content.
One of these ideas I'll bring forward below. An integrated HIVE comment and token system into a well-established platform in the music industry: DISCOGS.
Interested to learn more?
Keep reading 🙃
First I describe the idea and high-level concept after which I address possible questions you may have. Add yours in the comment section in case I didn't address those.
The IDEA
Integrate the HIVE blogging system into a well-established music platform with a large audience. It may not be an easy task to convince such a platform/company to play ball with blockchains in general and the HIVE blockchain in particular. But what if such a company isn't a regular fiat-based business seeking tons of profit? What if such a company was started in a decentralised fashion way before Bitcoin was invented? What if such a platform allows most of their content to be used by others, for free? And what if such a service already has a social element?
DISCOGS x HIVE
I believe, for DISCOGS (website), the answer is YES to all questions I put forward in the previous paragraph above. The 'about' page tells us the content is "A user-generated database: Open source and crowdsourced". The same page tells us they have 602k community contributors and have been around since 2000. I remember very well when they launched. Discovered them just a few weeks (or was it months?) after they went live.
Discogs is a platform that has the most extensive database of artists and their works. It also facilitates a (second hand p2p) marketplace for music media, from vinyl to CDs and whatnot. Last but not least, a Forum is part of the platform as well.
Both sides of Discogs, the artist and their discography as well as the marketplace already have a comment section. The marketplace allows for different currencies.
Are you connecting the dots already?
The CONCEPT
It is plain and simple.
- Add the HIVE comment system to Discogs (for direct monetisation by Discogs user)
- Optionally: Add crypto tokens and the HIVE/HBD token to the marketplace payment section
The concept includes the usage of Discogs as it is today. With that I mean, any Discogs user commenting to albums, artists and whatnot, can continue to do so in exactly the same way, with the same tools, with the same accounts, as the user is using today.
Basically, the concept of adding the HIVE commenting system to the Discogs one is that it adds, but doesn't replace.
Obviously, we shall be open to replacing the existing commenting system with a 100% HIVE-based one, but this isn't the pitch to them. The goal is to lower the barriers for Discogs to play ball, as much as possible.
Essentially I see in front of me a comment section (see also the image below for an impression of what I visualise) in which the HIVE-based comments are within the Disocgs comment section. The HIVE-based comments may show slightly different to the current Discogs comments, preferably by an additional icon, or perhaps the HIVE brand. The monetary rewards may not be visible at Discogs, but if Discogs allows, why not show the monetary item? This could simply be the HIVE token, or LEO, or both. Orrrrr a new Discogs token. Albeit the latter isn't required.
Clicking the HIVE logo can do many things, one of which would be to open a page in which the HIVE side of Discogs is explained with actional items, like subscribing to the HIVE side of things.
Sooo ... What is in it for Discogs?
That's a good question. And not too difficult to answer.
With the HIVE commenting system integration, Discogs not only provides something new to their audience but also a possibility for all these 600k+ contributors and 700k+ daily visitors to earn extra, whether this be in a direct currency with a dollar value or points that may bring them some extra benefits (eg Discogs tokens for some kind of loyalty program).
In addition, integrating HIVE commenting system may also provide an additional revenue stream for Discogs. More about this further down this article.
What when Discogs isn't Interested?
Obviously, I have a plan B in mind. Well I even have a plan A2 in mind as well.
Plan A2
When Discogs is interested in integrating HIVE in one or the other way (eg the commenting system) but doesn't have time to make this happen, the HIVE community can step up and fill the gaps, whatever those gaps are.
Note: in Plan A Discogs does the work, we at HIVE sell the idea to Discogs, help them to understand HIVE, train their developers, show them what they need to know, answer their questions and all that. But essentially HIVE isn't developing major parts of the integration, this is handled by Discogs development team(s).
Preferably our contributions we do free-of-charge with direct out-of-pocket costs paid for by Discogs, or by the proposal system. In the end, we do this for the benefit of HIVE, which will be reflected in increased HIVE token value 😉 in case Discogs is willing to pay, obviously, that is allowed. Such income will be somehow distributed to those contributing.
Plan B
Create and launch the next generation of Discogs using all the information from Discogs but with its own branding. This could just be the discography side of Discogs, but could also be extended with the marketplace including the crypto payment side of things. My suggestion for such Discogs 2.0 service is to also allow a full end2end web2 experience to not be limited to the tech-savvy crypto users and - mostly - money-hunting bloggers. Making use of web2 - and its user experience (UX) - is the name of the game here.
Plan B is far from optimal though and requires a lot of time, effort and money to create, establish and gain traction. Though the core of the service is free of charge, the service itself needs to be architected, developed, coded, marketed and operated through B2B and B2C approaches and channels.
the OPPORTUNITY
To me, the opportunity for HIVE is clear since I truly believe we can find solid web2 platforms that can be convinced to add the HIVE commenting system in one or the other way. Through such integration, HIVE is suddenly exposed to a much larger audience (700k daily visitors source), whilst the UX for the existing user base isn't changed one bit. At the same time, the collaboration of Discogs with the HIVE blockchain can be used as a reference towards other platforms and the entire market. And when Discogs doesn't want to play ball, we can try a gazillion other services, networks, and platforms.
At the same time, the HIVE integration could also add to the business model for Discogs. For instance, a percentage of the rewards goes to Discogs, set per comment. Perhaps these rewards do not directly flow into Discogs' own HIVE wallet but into an intermediate wallet. A wallet that pays out to Discogs when certain conditions are met so that some control mechanism is in place for Discogs to continue to support HIVE. Perhaps some bonuses can be given to Discogs when they achieve certain marks like a minimum of new active users onboarded to HIVE and/or other achievements that are good for HIVE.
The marketplace is very interesting as well. Supposedly more than 17 Million items were sold through the Discogs marketplace in 2021. This averages to about 50k items sold per day! Perhaps adding crypto tokens including HIVE/HBD isn't giving a direct monetary reward for the HIVE ecosystem, but for sure it'll bring another opportunity for increased brand awareness of HIVE. Think of: "powered by HIVE" when integrating a set of crypto tokens, including the mother of all tokens, BTC and others. Essentially am thinking of a payment module that is delivered by and branded with HIVE.
Commitment, Skills & Leadership
Plan A doesn't necessarily require a centralised company setup with some solid entrepreneurs taking on the adventure. Within the HIVE community, we must have plenty of peeps with the skills that are required for such a startup adventure. We just need to group these individuals. We need to be willing to commit to the tasks agreed upon. In the worst-case scenario, our time is not being compensated through financial means, directly. But perhaps indirectly by a better-known HIVE token and a higher value of the HIVE token on the exchanges?
Plan A2 may need a legal entity. Well, likely it needs a legal entity since I don't see how software and such can be built for Discogs platform without going through legal hoops. I mean, almost none of the services in the fiat space allows for non-legalised contributions. Though Discogs may be different since they have community contributions at heart.
Plan B: not gonna talk about what is required for Plan B since either Plan A or A2 will work out 🙃 for sure 🙇
the Tech Stuff
From the tech side of things, bringing in the HIVE commenting system requires development. Not only the HIVE commenting integration into the UI of Discogs but also a web2-like UX to get an HIVE account for those Discogs users wanting to start participating in Discogs through the HIVE blockchain. In essence, the user who likes to be onboarded shall not have to install plugins, or software, to sign up and sign in. A wallet needs to be created by the service. And perhaps Discogs requires an inbuild (yes, centralised) wallet for all the users executing actions for which rewards are given, regardless if they already have a HIVE wallet or not. Perhaps the user needs to subscribe to the reward system to receive an HIVE wallet and the ability to claim the tokens already earned in the past. Resource Credits shall be delegated so that a user using the HIVE system through Discogs doesn't have to buy HIVE tokens and stake them. Temporary RC delegation is maybe necessary for this to not run into the situation of too much unused RC delegation.
Much is possible, but in the end, Discogs decides what will be on the table regarding HIVE services. We shall help them to define what this is. Perhaps even drive this when Discogs allows.
I am pretty sure next to a good story on collaboration, demonstrating sound knowledge in every aspect in the sales cycle, we need to show what is possible in terms of a Proof-of-Concept (PoC). Such PoC is more about features than anything else. But also a PoC (including showcasing our expertise) shall take away any concerns from Discogs. This could be anything to do with UX (eg speed of the system accepting a comment, which should be instant if you ask me, not waiting for a few seconds after confirmation of the HIVE blockchain), load on their systems, quality of integration, uptime of HIVE chain and whatnot. I can't tell exactly what they will find important just yet.
We will find out when we start talking with them, but I do know we need to be prepared for a lot. This essentially means we need to identify all the skills required, find the peeps, get commitments from them and be ready for what is coming our way. And all that BEFORE we start reaching out to and talking with Discogs. We don't have time to find all the expertise and willingness of peeps in our community when we progress from the first to the second meeting with Discogs. And am 100% sure we need more expertise than I can provide for the second meeting. Even for the first meeting, I very likely don't have all the expertise myself.
So yah, we need to organise BEFORE we can reach out.
Please check this API Discogs provides, you'll notice I am not telling BS. Plenty of content is available through the API. Plan B can be facilitated through this. However, we go for plan A or when that fails, plan A2 making the API a bit less relevant 😉
certainly NOT the last words
If it was for me - a decade ago I would've considered starting this whole thing up myself in the role of an entrepreneur and would've established a company of some sort. Though my age is tik tak -ing forward. Today I see myself in a place with plenty of ideas, with a lot of passion for those ideas, but not the energy anymore the actually take on the role of an entrepreneur, a manager, or a leader.
Although I am ready to support others who do want to take up such business, aiming to onboard professional companies, with the goal of benefiting HIVE and crypto in general.
Not saying that I won't do any of that myself, but no promises on those fronts 😉 Time will tell. That said, with this blog post I already took some form of leadership, although at this stage just open-sourcing the concept of onboarding Discogs to the HIVE ecosystem. Am more than willing to work with others in the community (or outside for that matter), like-minded peeps, to make something happening that makes much sense for your HIVE ecosystem.
As Eminem would say "My Ed´s Gone Crazy"
But the good kind of crazy, the mad scientist kind. The thing is that your post is even longer than your comments and I have been cooking up a scary story all morning so I got lost at The Concept and picked it Back Up at the Tech stuff.
Hence it will require another read to fully understand but I love what I think I understand so far!
hahahaha the scary bits and the concrete concept bits: I understand why it isn't easy to switch. or I think I do. let me attend to your scary contribution just now, to see if I can make that switch, or not. likely I can, knowing myself a little, but that aside 😉
This idea has potential. I don't use Discogs, but if some big site used Hive for their commenting system then it could bring in a lot of users. If someone could provide an easy way to integrate Hive comments into an existing site then it could be attractive. The site owners would not have to worry about storing the comments as they would be on the blockchain.
I hope you can find people to move this forward.
What would be most preferable, is for the HIVE community to build an integration framework through which not only the integration itself is made easy for external parties, but it also holds all the necessary features incl HIVE wallet, statistics and monitoring stuff a professional company needs. I believe we are missing this. I even think such an integration framework could even have a business model, like a subscription service or something. An honest commercial business can be created around such an integration platform.
I also think we need a go-to webpage for such companies in case of questions about and around the HIVE chain. The latter could possibly be the reason why we need at least a part of plan A2. My experience is that any professional company wants a telephone number they can call, in case of issues.
Let's see if I can get some traction. I do hope so as well!
This post has been manually curated by @steemflow from Indiaunited community. Join us on our Discord Server.
Do you know that you can earn a passive income by delegating to @indiaunited. We share more than 100 % of the curation rewards with the delegators in the form of IUC tokens. HP delegators and IUC token holders also get upto 20% additional vote weight.
Here are some handy links for delegations: 100HP, 250HP, 500HP, 1000HP.
100% of the rewards from this comment goes to the curator for their manual curation efforts. Please encourage the curator @steemflow by upvoting this comment and support the community by voting the posts made by @indiaunited.
thank you so much 🙇
Wao! This is so good and will add more value to us all. I haven't heard of this app though but it's Indeed a good for to use. Thanks for sharing.
It is just an idea at the moment, with a high-level concept. There is no market verification yet, not in general, nor from Discogs.
We need to create a team before we reach out to Discogs.
It could be the case Discogs isn't interested at all which torpedoes Plan A and A2 instantly. The question is then: How to move forward? My idea is to go to the next music platform and offer the same, Plan A and perhaps Plan A2 (targets for instance are: Resident Advisor, Beatport, SoundCloud and tons more). Perhaps even Viberate which is a service that started out in crypto space, but is in fact a web2 service at the moment.
We give us eg 6 months (or 12?) to materialise a launching customer.
When nothing is materialised, draw up a new idea/concept for the same market segment, or for a new market segment. Also here I have a suggestion, go for a similar concept but then Movie segment.
After that (or parallel to): Forum, Product review and Service review segments.
And what about the Travel segment?
For certain segments, it may be the case the small players are more the prospective customers instead of the large players. For instance, I don't see Booking dot com or Agoda going for direct monetised comments and reviews, as well as I don't see these players onboarding a crypto payment system provided by HIVE. These parties will have their plans and will execute accordingly.
Although in travel space plenty of small players around. They may be interested in adding something novel to their own website/service: monetised Blogging, perhaps with their own token as a loyalty token. Thinking of it, this may be something Booking dot com and Agoda could have a match with, but still, even when they like something like that, it'll be hard to get them to use HIVE chain for the token. Although, the free-to-use aspect of HIVE (no tx fees, well, not directly, indirectly HIVE has fees, such service just needs enough RC to pay for the users' transactions) is very beneficial for a loyalty system. That said, perhaps no reason for Booking/Agoda to use a blockchain-based loyalty system. Although I can think of some benefits that may be of interest to these parties to start focussing on.
Anyway, I am zooming too much into the unknown and therefore deviating from the purpose of the post and this comment.
We need to identify the peeps with their skill sets and try and form a team to start this idea of B2B play to bring HIVE features and integrations to the (fiat) market.
You have a nice foresight and then I think if these things you have listed here can be met,it would be in favour of hive and will help it grow more. But now, the question is connecting with those that are really needed to make this thing work out as fast as it should and getting better resource credits to help. Good one champ
Yes indeed 😉 Thanks for you nice comment.
You are welcome brother
I didn't hear about Discogs before your post, but that's probably my fault... 🙂 I like the idea of adding an "HIVE comment section" at other Web 2.0 websites for the simple reason that you stated, more eyes on HIVE and free exposure... If it is presented well to the "other side" with clearly stated benefits, it is a perfect match for a healthy collaboration...
Btw. I remember that we had one dapp while we were on the legacy chain where you could do movie reviews, but you had to stick to the "specific rules"... Rules were there for practical reasons, as they were the tool for "formatting" the data into the dapp connected to HIVE... It was a kind of IMDB copy but with originally written content by Hivians... No copy-paste BS... Unfortunately, when we had our hard fork adventure, the idea died, but that doesn't mean that it wasn't good...
It is important to take our brains out of the box and ideas will come... Like this one... I hope that it will find traction!
Now you mentioned it, I vaguely remember something, though can't seem to recollect anything anymore regarding what it really did.
In general, I have an 'issue' with the idea of: "Let's create our own knowledge database for movies and music"... or for whatever other data type that is already out in the field and publicly available.
In essence, this is not a problem, the idea may be nice, but the question is: "Who will make use of the data held by such a database when IMDB and Roten Tomatoes are out there for movies? When Discogs, Spotify, TIDAL, Apple Music etc are out there for music?"
Hardly any user is interested in using services with incomplete data when services with more or less complete data are around, and free of charge. One needs to have a well-thought-out plan to fill a new database with the same/similar information for users to actually start using the data and/or the services around such data.
When such a plan isn't there, just trying to fill a database with data, data that is already available in other publicly accessible databases, is a useless exercise and millions of hours of wasted human time. I've seen too many attempts already which all failed after peeps already spent tons of time.
And even when we get a great setup for a new music or movie service, with its own database filled with enough data to be relevant for a large audience, the challenge still remains: "How to attract such an audience?"
Anyway, I think you already got my point before I wrote this comment 😉 Rendering this comment into the category of useless human time spent 😂😂😂
Ah... Now you killed the whole conversation... 😃
So, in your theory, if we have McDonald's, there is no point in opening Burger King? 😜
I do agree that there is no point in copying/pasting things, but there are still some valid ideas out there that are worth doing... On the other side, I do like your idea of "slow integration" and adding small bits of Web3 to traditional Web3 platforms... The first step is to go under their skin and slowly take over... :)
😃
Hahahaha I knew it, I needed to write even longer comments than I already do.
For sure there is room for Burger King next to McDonalds. There is even room for 10+ others. However, each new burger chain (App, dApp, Service) has to do something the others don't do, more or less (even true copycats can become successful but eg undercutting price with the direct result margins under pressure with the direct need to capture a larger part of the market quickly t be able to survive). Plus, and this is the most important part, when (more or less) copy/pasting, one needs to have DEEP pockets to rollout. The DEEP pockets are what none of the HIVE-based dev teams have. None. Well, in the entire crypto space, only a few have deep pockets, the rest doesn't.
I took the liberty to change the second web3 in the sentence to web2, since that is what I think you meant. My reaction to your comment: You understand what I am trying to say indeed! 🙇
pretty complex for my old tired brain.... I popped over to Discogs .... and it seems very well established . Do you not think that collaboration with another Web3 project would attract more attention? Such as for example AUDIUS ? I know they have their own token but swop mechanisms are not that challenging these days.... just a thought.
Any service that is relevant can be considered. My suggestion is to go for those services that have massive daily usage. I doubt AUDIUS can outnumber DISCOGS. Also, when somehow we can get well-established Web2 services sing HIVE features, this will be a major reference for other web2 services. But as said, DISCOGS is just an example. I think a good example to start with, but in the end just one of the many platforms that we can target.
Also, when dealing with Web2 services, we will need to fill in some gaps which we may not have to fill in the Web3 services world (AUDIUS is Web3 more or less). Going after these Web2 services/companies will therefore upgrade the HIVE ecosystem with a more organised setup to deal with the Web2 services/companies world. In the end, the growth for HIVE will come from integrating the Web2 world. It is about time we (the HIVE ecosystem) start filling those gaps to position ourselves much better for growth 😉
I hear you ..... but I retired now so I leave the deep thought to you brilliant youngsters .... {grin}
Hahahahaha feeling very very young at this side, but the world has a different opinion regarding that 😂
Cool, Cool.... Very Nices !!!!!!!
I Like and share this Idea
I hope to contribute a grain of sand to this idea... in Venezuela I am a broadcaster and promoter of national rock bands from Venezuela, Spanish and Latin America, I interview bands, I cover reviews of rock concerts, as a digital medium specialized in rock and metal.
Nice! And you also posted a bit about your work already. Cool.
In what way do you think you can contribute to the idea/concept?
I hope I don't spam you, but... since 2013, I have been interviewing rock bands, reviewing the rock concerts I attend, for all this dedication, I earned the opportunity to have been interviewed by an important hard rock and heavy artist Venezuelan metal with 46 years of artistic career, this is Paul Gillman (former vocalist of Arkangel, current band Gillman and Power Age 2.0) on the television program Kultura Rock TV, you can see a photo of the interview on my facebook profile.
I have interaction with some colleagues from the press specialized in rock and metal music and one of them has been sharing my PeakD and 3speak content.
Also what, I told a friend of mine about hive who is a journalist at a radio station that has a program about rock and metal called La Diseño, he is Gillman's right hand man at the Corazón Rockero Foundation (the foundation that is responsible for organizing the festival of national and international rock Gillmanfest, 100% Venezuelan rock concert, Kultura Rock en Vivo and rescued the Festival de las Flores, a concert where the great legends of Venezuelan rock are honored).
I also contribute as press for the underground Christian rock movement La Rocka where I have a friend who wants to form a heavy metal band with me and is going to help me propose to the leader of the movement so I can give a talk about Hive,
a movement where various bands want to play there
In that sense, there could be possible contributions that I could propose locally, I am not a celebrity and I don't even think about being one, I am just a rock and metal lover who has decided to organize to contribute a grain of sand to the Venezuelan national scene and aspires to establish itself in the Spanish scene (in fact, I will soon publish an interview with a heavy metal legend from Spain and Latin America
Regarding Discogs, I don't even have an account there, although there are albums by Venezuelan rock bands, but locally, I have certain possibilities.
ah jah cool! nooo you are not spamming. thanks for showing your passion and all your connections. its cool. its cool if we can win more HIVE users in the music side of things, telling stories and whatnot, writers, like you. though I always feel not many peeps like to be with HIVE, I suppose mainly because of the community being so tiny in comparison. the idea in my post counts for every blog out there. in the past, and perhaps still today, someone in the community made a little plugin available to connect wordpress websites to hive, essentially doing what I articulated in my post, more or less. I think with that plugin it was possible to use the HIVE blockchain to store the blog and comments. am not sure of only the comment section could be in HIVE with that plugin, I think not. anyways, not many used it. also, those who used it never turned to the HIVE UIs, so I think those who had this integration done, stopped at some point in time. since this is how HIEV works, when users post, and perhaps comment on comments of other on their own post, but never go to other users' post, usually such user is not gaining any traction on HIVE. anyways, ling story short, I believe one of the few ways to grow HIVE is by a concept like in my post. not an easy route, but an essential route. I do hope some developers agree with it as well since they are required for such adventure, the materials whatever needs to be created to get some of those bigger web2 services playing with HIVE.
Oh, ok...thank you very much!! I have a friend and press colleague who is a graphic designer, in September I covered an event of the Christian Rock Movement, La Rocka and my friend's digital media, whose project is called "takemyhand" and he shared my review using the PeakD link. .. with small movements, little by little you manage, in a non-invasive way, to generate interest in Hive, I like it because I can support my journalistic works on Rock and Metal and the idea of integrating Hive comments into Blogs designed in WordPress
some baby steps are also good, when plenty of users do the same towards their friends, acquaintances and colleagues, HIVE will grow for sure 🙃
That's right, you start small, taking small steps.=)
Congratulations @edje! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)
Your next target is to reach 54000 upvotes.
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOPCheck out our last posts:
I don't know if you @edje or anyone in charge will read this, but in my honest and (of course) respectful opinion, what this community needs is more passion and content related to point of views about the art of music in our lives. We see a few of this things right now but not quite a lot. It will be just fine a bit more.
100% agree. amongst others the reason why I launched Spread the Vibes thingy years ago. ah well, its not very busy this part of the bear market in many segments on HIVE.
Funny we were thinking the same but with Audius, although they don't seem that interested lol We would be happy to help you on this project if you want to give it a go!
Audius is certainly a service that can be targeted. They don't have a comment system at this moment I think, or did I miss something? How best to reach you? Through Discord? My handle is: edje42
EDIT: we were already connected I just found out, did send you a short DM on Discord 😉
😽
Topic: Integrating a HIVE commenting system into the Discogs music platform
Format: Traditional debate format with two teams - the Affirmative team arguing in favor of the integration and the Negative team arguing against it.
Affirmative Team Arguments:
Increased Exposure: Integrating HIVE into Discogs will expose the HIVE ecosystem to a much larger audience, including the 700k daily visitors to the platform. This increased exposure can lead to a significant influx of new active users to HIVE.
Monetization Opportunities: The integration of the HIVE commenting system can provide a new revenue stream for Discogs. By allowing users to earn rewards for their comments, Discogs can incentivize engagement and loyalty among its 600k+ contributors. Additionally, Discogs can potentially earn a percentage of the rewards generated through the commenting system.
Collaborative Development: The HIVE community can collaborate with Discogs to integrate the HIVE commenting system. This collaborative approach allows for shared expertise and resources, reducing the development burden on Discogs and fostering a positive relationship between the two platforms.
Negative Team Arguments:
Lack of Interest: It is possible that Discogs may not be interested in integrating the HIVE commenting system. Convincing a well-established platform like Discogs to adopt blockchain technology and a new commenting system may be a challenging task. Without the buy-in from Discogs, the integration cannot proceed.
Technical Challenges: Integrating the HIVE commenting system into Discogs requires significant development work. Ensuring seamless integration, user experience, and system stability can be complex and time-consuming. It may not be feasible for Discogs to allocate the necessary resources and prioritize this integration.
Alternative Solutions: Instead of relying on Discogs, the HIVE community can explore other platforms and services that may be more open to integrating blockchain technology. Pursuing alternative partnerships and collaborations can be a more efficient and effective approach to achieve increased exposure and adoption of HIVE.
Conclusion:
The integration of the HIVE commenting system into the Discogs music platform presents both opportunities and challenges. While it has the potential to increase exposure and provide monetization opportunities, there are also obstacles such as potential lack of interest from Discogs and technical complexities. The debate encourages critical thinking and exploration of alternative solutions for increasing HIVE adoption.
The author @tonybad runs a petition against illegal homelessness https://www.ScamBuster.TV
Nice summary. Not sure why you've added this summary though; AI-generated and all.
Yep. Trying out the AI. If I did nothing, would that be better ?
I am against using copy/paste from AI, well against AI on HIVE in general when not combined with something straight from the human brains and fingers.
HiveWatchers downvotes posts/comments generated by AI, especially when the source isn't mentioned.
I respect your opinion. Obviously, whoever built the AI facility, saw a demand to keep up with the competition 🙄
Perhaps to read a summary of a post, rather than to create a summary and post? 🙃
Hi Edje, thanks for your post. How difficult would it be for developers to create a 'Share to Hive' button on platforms like Spotify, Discogs, SoundCloud, Audius, etc.? Perhaps Hive could also serve as a platform for discussions and reviews of albums, songs, videos, and more. Once that's in place, we could approach those websites. Simply adding the Hive logo could attract many new users, including record labels, journalists, and photographers.
The integration itself, on the HIVE side should not be that difficult. However, the services need to play ball, ie allow the integration, and execute the integration (with or without help from the HIVE peeps). Ultimately, it changes the UX for the Spotify user, the Soundcloud user, or whatever 3rd party music platform we are trying to integrate. I suspect a serious sales effort is required. A reason why I focussed on Discogs in the article, since they are used to open source with a community play. Spotify and Soundcloud are not. Audius is perhaps another target indeed, though the 'effect' on usage may be limited due to limited use of that service. I suppose a frontend can be build for all services, but that in itself will be more difficult to get users on' Most users like the native apps.