The Pillars Of LeoGlossary
This is an evolving project that keeps expanding as we move forward.
For the moment, there are a few main pillars that we are focusing up. They are:
- movies
- music
- glossary
All of these are intertwined as explained in the video. Over the next year, this will serve as the foundation for a review site that will emerge from the data.
▶️ 3Speak
0
0
0.000
I thought the Leo Glossary was all about cryptocurrency only this is great that the Leo glossary is expanding to more subject matters as well thank you so much for the update.
It was originally crypto, finance and other business related terms. But with the shift in Leo focus this expanded.
Sorry, but I have to play the devil's advocate. Why would someone not go to IMDB or Rotten Tomatoes for film information? And why would someone not go to Discogs and Resident Advisor for music information? Those databases weren't built in a day, but years to decades. The user is interested in completeness as well as UX, similar to why Spotify has such an enormous amount of users, while the artists are shitting on Spotify due to low payments. But that aside. Spotify shows the power of completeness and how peeps want to listen to music (a stream, playlists, auto-selection of next track/album, favourites and all that).
I fail to see why 200 or 1000 movies in LeoGlossery will benefit the HIVE chain or Leo service. When building something like this, a complete team/company, tailored services and business cases are required IMHO to attract new people to Leo because of this type of content in Leo Glossary. A flaw regarding YT links is that the YT videos may be taken down, which happens regularly. This results in bad UX for those posts for which that happens.
Don't get me wrong, I like the idea, especially since I played around with the idea of a decentralised Wikipedia myself, years ago. However, though the idea is great, it is darn hard to compete with the existing services that are as complete as it can get, household names in the industry, and the goto platforms by content producers, production houses and labels.
IMHO, the only way to make a Leo-based movie database or music database successful, is to create a compelling service and find the partners to fill in the content. These are production houses in movieland and labels in music land. They own the databases with content. They can support in bulk uploads.
Did anybody talk with IMDB, Rotten Tomatoes, Discogs, or Resident Advisor? Trying to onboard them? Bringing eg monetary rewards to contributions, comments and whatnot? These services may be interested in this since all these first movers have difficulties in finding business models. When just 1 of these services starts to use HVE/Leo in one or the other way, THAT will be MAJOR.
EDIT
Discogs has an API that can be used to create a service using the entire Discogs database. Add the Leo/HIVE comments system and market the whole thing in cooperation with Discogs. The most extensive Music database in the whole Universe is onboarded to the HIVE chain by simply creating a service and reusing the content - While comments are monetised. Any link can be added, eg YT videos, Spotify, TIDAL, Soundcloud and whatnot. It all depends on the dApp builder and the users of such dApp.
Owww don't forget for the dApp owners to open wallets for users and pay for the transaction by RC delegation. Some investment is needed by the dApp to allow all Discogs peeps to collect HIVE/LEO without them having to open an account or know how to handle such an account.
No need to create all the content which costs millions of hours to be on par with Discogs.
ps Likely the other services in Music and Movie segments have similar APIs, or can be enticed to integrate with HIVE with a bit of support from the tech peeps at HIVE.
https://www.discogs.com/developers
EDIT2
Same for IMDB. API available. https://developer.imdb.com/
Thanks for your feedback and what you say is true. Of course, we start with the premise of what is on those sites is owned by the corporations. This brings into question the results. Also, they have a monopoly on the all the responses tied to the reviews.
We certainly are dealing with something evolving. Of course, we have to start somewhere. And you are right, incorporating data from elsewhere is helpful although brings up the same issue you mentioned with YT, they can change the API.
So we keep coming back to the control of the data.
I agree that we have to try things.
I disagree with you regarding the matter of content being under the control of a central organisation and therefore is under threat to be deleted. YT is known to take down copyrighted materials. IMDB and Discogs are known for their community-build databases and sourcing of copyright materials by the owners. They know what the community is worth. Heck, back before WWW was made available to us when I had to use Gopher and Lynx, I was contributing to IMDB already. Anyway, I really think it's much more valuable time to try and onboard Discogs, IMDB and other services for eg monetised comments than spending time to create all the content ourselves. As mentioned, this will cost millions of hours for the content alone. And what about the reach for such content? And even with eg Discogs, a marketplace for vinyl, CDs and whatnot is available as well. When these services don't want to integrate with HIVE, create a new service, using some to more of the content from their database, add their marketplace and add HIVE/LEO token as a payment form, including a hot-swap from these tokens to whatever fiat currency, or crypto, and voila. A much more compelling service. Similar style to what Travala does. Use the big-ass content databases out there to benefit crypto. In cases of IMDB en Discogs, to benefit LEO/HIVE 😉
EDIT
I'll create a post describing a concept for IMDB as well as Discogs sourced material and how it can benefit HIVE without copyright infringement, and perhaps even reach the entire audience of said services. Even with a new service based on their content 😉
I look forward to the post. Should be very educational.
am not sure if you'll see this post in your timeline or somewhere else, therefore I am providing you with the link here 😉 https://peakd.com/hive-192806/@edje/how-to-increase-hive-bloggingleo-threads-usage-tremendously-without-marketing-integrate-music-platforms
looking forward to read what you think of this, the idea, the concept and also like to read from you how you would go about the materialization of this idea/concept. perhaps the LEO team can take this onboard? perhaps with the support of others in the community?
note that where I wrote HIVE, can also be LEO, or any other team or future team to be created 😉
Summary:
In this video, Task discusses the main pillars of Leo Glossary, emphasizing the project's ongoing evolution and the addition of new ideas. The pillars include movies, music, and the glossary itself. Task elaborates on the structure of movie pages within Leo Glossary, the addition of music albums and playlists, and the importance of internal linking within the glossary to interconnect related content. He also highlights the community-driven nature of the project and the goal of providing useful content for users to engage with. Task expresses his commitment to expanding the project further and emphasizes the long-term vision behind Leo Glossary.
Detailed Article:
Task delves into the main pillars of Leo Glossary, beginning with the movies section. He explains that pages are being added to create a database resembling IMDB and Rotten Tomatoes. These movie pages include a plot summary, cast information, and images, with room for comments and eventually polling. The second part of this pillar involves embedding streams for users to watch movies directly on the Leo website, enhancing the user experience.
Moving on to the music section, Task mentions the work being done by Wealth West on albums and playlists. Each album page features a write-up, details about the album, and embedded songs for direct listening. Playlists offer a curated collection of songs, categorized by genre, band, or era. Task also integrates music posts through threads to engage the community and potentially introduce decentralized polling for user interaction and ranking.
Task then transitions to discussing the glossary, emphasizing the importance of linking terms across different Leo Glossary pages to create a cohesive network of interconnected content. This linking strategy aims to enhance user experience and facilitate navigation within the platform. Task acknowledges the project's focus on utility over SEO concerns, highlighting the goal of providing valuable content for users to consume, interact with, and engage in discussions.
In conclusion, Task underlines the community-driven nature of Leo Glossary and his dedication to expanding the project by setting ambitious goals, such as increasing the number of movie pages. He stresses the project's uniqueness, novelty, and long-term vision, reinforcing his commitment to delivering a platform that offers a diverse range of content and opportunities for user participation.
Notice: This is an AI-generated summary based on a transcript of the video. The summarization of the videos in this channel was requested/approved by the channel owner.