If we can't bring Hivebeepedia to life, can we at least bring online a topic-specific Hive-powered almanac or database?
Cover Image made using HTML and CSS, with light edits made using MS Paint.
It's amazing how much we can learn from a database such as IMDB.com:
- Jack Nicholson and Elton John both appeared in Tommy (1969);
- Samuel L. Jackson had a bit part in Coming to America (1989);
- William Shatner starred in The Incubus (1966), an art house Esperanto-language movie, before he took on the role which defined the rest of his life. As an added bonus, this movie even had a brief scene in The Matrix (1999).
Sadly, Amazon.com acquired IMDB.com, so I don't use it as often as I had in the past.
Wikipedia is the most widely used wiki on the planet, but it's not the only game in town. Years after it launched, it had become a victim of its own success. In recent years, it came to be lumped with Big Tech, and you know what that means.
Just as sadly, I do my best to avoid Wikipedia.
So what's out there in Web3 that we can use? If it's not on Hive, where in Web3 do we go to earn crypto, or at least support decentralized services?
Last week @taskmaster4450le touched on how Wikipedia is anti-crypto and what a wiki powered by Hive blockchain would be like. It's safe to say that the mechanical aspects of the wiki would be easy while the compensation and governance aspects would be more difficult. While it will be a happy day when something like "Hivebeepedia" launches, but that won't be any time soon.
So this post is partly my comment to my fellow Leos and partly some points for my fellow Hivers across various communities to consider.
One Example We Can Use: LeoPedia
Just as CoinGecko and CoinmarketCap have educational sections, so does LeoFinance: LeoPedia
AN OPEN RESOURCE FOR CRYPTO EDUCATION
Your Guide to Crypto
Explore, learn and educate yourself about one of the most revolutionary movements in our lifetime.
LeoPedia is meant to be a factual source of crypto which we can consume, consult, and to which we can add content. It has useful content, but it's also limited. LeoPedia is good at what it does, but it can do more.
While LeoPedia would be a major milestone when it's fleshed out and maintained regularly, something more limited yet much easier could be made available.
"Hivebeepedia"? One Day, But Not Today (or Tomorrow)
There are many concerns we need to address before we can proceed with something I call "Hivebeepedia"; how do we
- authenticate content?
- handle disputes?
- reward authors and content validators?
- keep Hivebeepedia decentralized?
- fund it?
The coding aspect of "Hivebeepedia" is trivial compared to those issues and other concerns.
Funding via tokenomics or proposals will always be a concern, but we can at least minimize the other issues if we focus on more limited resources we had been used to accessing before we became Hivers.
So What Can We Make for Ourselves?
Almanacs contain time-related or geographic information which can be looked up quickly, or at least consulted for review. Facts and figures beyond dispute is the main characteristic of an almanac.
- Who else shares your birthday?
- What happened on some date throughtout the years?
- What were certain dates like before they were captured by historical events?
- How many Hoboken-sized cities take up the area occupied by Canada or Kazakhstan?
Would the Hive-powered almanac be one you would use yourself as your go-to resource? What needs to happen to make it one?
References are what you would expect them to be: Stores of data to be consulted for necessary data that's not commonly used. As with almanacs, there should be no question as to their authenticity, although they need to be checked for accuracy.
- How many grams are in one troy ounce of gold, platinum, or palladium?
- What formulas let us convert among Fahrenheit degrees, Celsius degrees, and Kelvins?
- When was Pluto last considered a planet?
- At what age did Pelé join the New York Cosmos?
- For which team did Reggie Jackson play before he became known as "Mr. October"?
- What f/stop or ISO do you need to use for a panoramic photo?
- What are the flags for the provinces of Spain or Nigeria?
- Is mead a lager or a stout? (Trick question: it's neither.)
- How in the world do we make home-made holiday fruitcake??
(They should also be easily accessible in case issues of financial concern arise such as who is going to pay for dinner or the car service ride home.)
Dictionaries and Glossaries
This should be a no-brainer in terms of validation and confirmation. Both are still needed, but what's there to be disputed? As for rewards, that can be decided by community vote or a proposal: reward per term? per quantity? per container such as topic or letter?
Dictionaries can be made for each language, either stand-alone or paired with another. They can also be made along the lines of Urbandictionary.com and other slang or vocabularies.
More limited dictionaries, glossaries, can be made for jargon and other terms of the trade.
Dictionaries and glossaries could be made for finance (including crypto), film and television, sports, arts and crafts, medicine, law, education, mathematics, botany, cooking, computing-- anything activity involving people. Which is everything.
Who Can Make These Limited References?
Many topic-specific communities can oversee the creation and mantainance of references which make sense for them. Some of these references could even be collaborations between communities. Along with providing a resource for the communitiy and for Hive, it would generate buzz around an activity which would benefit everyone. If this brings more members and more content, it should be a matter of time before token values increase. This is what we want for the tribes where we're contributors, and along the way this helps the value of HIVE rise.
They may be dedicated teams responsible for overseeing these projects (especially if funding comes via proposals), but any community member should be free to contribute to the references. Over time some Hivers will be known as contributors or even funders, and this may be enough to attract even more contributors or funders. This is the kind of feedback loop we want.
In the event of drama becoming part of the project environment, the project will suffer and token value will drop; if we wanted that kind of drama, we would go with Big Tech and Web 2.0 resources instead.
Where Do We Find Content?
It could be crypto-related, but it could also be something focused like an almanac for movies, sports, photography, recipes, etc. Something easy for anyone to contribute to, and something easy enough to govern and to authenticate with minimal effort.
We could even mine content from Hive blockchain and give credit where credit is due. Not only would this be awesome for the author or the post which contained the content being used by the reference, but it would also help with SEO (Search Engine Optimization) when people outside Hive searrch for content and encounter our Hive postings.
Why Make These References?
Not everyone can set up nodes or code, but anyone can add content and data. Some of us may not know much about crypto or finance or trading, but we can make up for that in other areas where a reference is needed. While the amount of data to add to one of these reference projects is staggering, it's not that bad if everyone added a little to it each day.
No matter which token we buy, there is one ultimate concern for us: we believe the value of the token will rise. If people see that we continually develop, people will want to be associated with what we offer, and that helps a token rise in value. If people see nothing happening, that will kill the price of the token. Many of us have seen this for ourselves either as participants or as observers.
For a community whose token value is not what it had been in the past, working on these references could be a way to revive interest in the community, and therefore the token associated with it. Even if the token doesn't return to its ATH in the short term, the activity may be enough to ensure an upward trajectory for the token price. After all, if others see that we care about our token, perhaps they should care too?
Fine Print Considerations
So as to avoid any legal difficulties, the content we would provide would need to come from public domain content. If it's not public domain content, at the very leasy it needs to be properly sourced and documented. In this respect, we would follow rules or protocols used by the more widely known wiki applications. This is especially important if we're dealing with data from professional sports, music, and cinema.
Just My Two Sats
While it would be ideal for Hive blockchain to power "Hivebeepedia," there's more involved in bringing it online than coding and technical specifications. On top of things which Wikipedia does for itself, there is the tokenization of the content. Add to that the Hive ethos of keeping things decentralized as much as possible. It can be done, but it may be a while before we see something like "Hivebeepedia."
Until then, we may be able to bring to life lesser-scale references such as almanacs, references, and dictionaries. Each type of reference would feature content more concerned with accuracy since authenticity would be essentially a given. This would make tokenization easier.
Anyone should be able to make a contribution to any of these references, whether its LeoPedia or a reference for Natural Medicine or CineTV. In practice, certain people will gravitate to these projects as be known as contributors or funders, and if the project makes enough buzz then it can attract more people to it as contributors or funders. Even if a formal group of contributors and funders takes shape, there will always be room for informal contributors and funders.
There are communities which began with much promise, but for whatever reasons find themselves in a holding pattern. Today it's these, but tomorrow it could be ours. Regardless, a project such as bringing online a reference which is updated constantly could be a way to revitalize interest in a community, and alone the way add value to the token price.
To avoid trouble with content which may be protected by some sort of legal status (especially market data for indices or other financial instruments), we should focus on data which is in the public domain. Should we need to use data not in the public domain (for example, for movies and television), we need to source the data properly.
While it's true that all we do on Hive is on blockchain and blockchain is forever (at least until that asteroid with Earth's name on it arrives), a better way to ensure our legacy on Hive is to contribute to a project such as one of these references. If our contributions to such a project help make life better for someone else-- even a no-coiner-- then we added value to that person's life. If our contributions add value to both the lives of others as well as to our communities on Hive, then we all win.
|What's Better Than Earning 20% on HBD Savings?||Short Post: Can't Deposit ETH Using DEXs? Visit wleo.io||Short Post: Putin's Price Hike? 5 Dates Show It Isn't
|Links in image||URLs|
|Daily Crypto Markets Live Blog||https://leofinance.io/@leomarkettalk|
|Links in image||URLs|
|"...to make up for..."||https://leofinance.io/hive-167922/@magnacarta/who-is-magnacarta-and-why-is-he-sending-me-pizza|
|Proof of Brain||https://proofofbrain.blog/@magnacarta|