LeoCache is something I've been talking about for a few weeks now. I have mentioned it in various AMAs and a lot of people have been asking what the LeoTeam is up to.
The LeoCache upgrade is a complete restructuring of feeds and content on https://leofinance.io. It adds a lot of features and also opens up a whole new frontier for us.
This is a key upgrade on our path to building the Ultimate Web3 Everything App right here on the Hive blockchain.
One thing that Hive has lacked for quite a while is a really great search feature. Attempts have been made but we were aiming to squash this once-and-for all. I believe LeoCache's new Search Feature works incredibly well.
At launch, you'll be able to full-text search anything on Threads. That's all thread from now to the beginning of the Threads protocol (nearly 1 year ago).
pssst have you seen @leofinance's proposal to double the userbase of Hive? It's time to get ready for the Bitcoin floodgates to open up by positioning Hive to benefit massively from new users. It's officially live and waiting for you to vote and support it getting funded! The proposal outlines our strategy to grow the Hive blockchain by 9,615+ monthly active users using our LeoInfra Lite Account protocol and bring the masses to Hive. We need just 5.2M more HIVE POWER to vote it and reach our goal of 30M backing our proposal. Check it out here -> https://peakd.com/me/proposals/269
This is really exciting for a ton of different reasons. @taskmaster4450le presented an idea as a Thread talking about it and one use case for using it to find other pieces of content to create cross-links - which is valuable for SEO and overall traffic (and of course, Ads revenue).
Check out how I was able to actually find the thread I was thinking about on the closed alpha version of the UI by going to @taskmaster4450le's profile and then searching "Reference" which is a word I remembered from the original thread.
LeoCache has all threads ever created indexed in a rich-text database. This allows you to search the entire Threads database for any word and find Threads that contain it.
By going to his profile and searching this word, it took me less than 15 seconds to find a Thread I wanted to refer to.
Amazing stuff, huh?
LeoCache presents a lot of upgrades to the Threads ecosystem that I am really excited about. Not all of these upgrades are super flashy new features like Search. Some of them are a bit less flashy but HUGELY important for us to scale in the future.
Our mission is to onboard new users to Hive using Threads as their entry point. Threads are super easy to use and a familiar experience for all X users - who are our primary target market.
No More Indexing Issues
Here's an exciting one. I was talking to Task this morning and he mentioned that the indexing problem on LeoFinance.io is kind of annoying - especially for his #playlist idea that he's been doing.
ICYMI: Taskmaster and some other users have been building Playlist Thread Containers on Threads. These containers have anywhere from 10-100 threads containing a link to a song that they want in the playlist.
It's a super cool idea but one problem? After 2 or so days, they start to show as "not indexed". I'm sure you all have seen this message before:
It's super annoying but LeoCache is coming to the rescue. This is a scaling issue for us. It has to do with containers and the way that Threads is built.
LeoCache fixes this. It brings a whole new backend infrastructure to the table that eradicates this issue and for people like Taskmaster who build these awesome containers, it's going to be a godsend.
You can see this in action here where I have the Current Production UI booted on the left and the Closed Alpha version on the right.
Closed Alpha has LeoCache implemented and Production does not. Without LeoCache, the thread is 1 month old and therefore, shows as not indexed. You can't go beyond a few days in time because of scaling issues.
With LeoCache, you can now see Threads that were created 1 year ago, 5 years ago or 20 years ago (whenever Threads becomes that old, as we're only 1 year old rn).
So you see the power of LeoCache applied in this use case.
There are dozens more use cases for LeoCache including a scaling issue that we saw during the Zealy campaign when over 20,000 threads were created in a single day.
With LeoCache, I believe we'll be able to do 100,000+ threads a day right at launch and it introduces as scalable stack that will allow us to scale to millions and possibly tens of millions of threads per day.
As we continue to grow, we'll need the ability to scale. LeoCache is the answer to our future.
Another key use case is the notifications tab.
I'm sure you've seen this issue if you use Threads a lot. Sometimes you get a reply from 1 or 2 days ago and click to reply back from the notifications tab.
What do you see?
On LeoCache, you will no longer have this problem.
I didn't even dive into the algorithms for Trending and Following that we're introducing. Those are gonna be a whole new post on their own.
And a For You page? LeoCache will introduce it.
LeoCache enables us to build complex algorithms for content sorting.
What can't LeoCache do? Idk, fly? But maybe soon™️ we'll crack that too.
LeoCache is a game changer and I am really excited about it. This isn't an official dev post which is why I put it here and not on @leofinance but I just wanted to share in the excitement. We're doing some final tests and will likely push the closed alpha to Production by Friday of this week once some final bugs & tweaks get rolled out.
pssst have you seen @leofinance's proposal to double the userbase of Hive? It's officially live and waiting for you to vote and support it getting funded! The proposal outlines our strategy to grow the Hive blockchain by 9,615+ monthly active users using our LeoInfra Lite Account protocol and bring the masses to Hive.
- Vote the Proposal on PeakD ▶️ https://peakd.com/me/proposals/269
- Vote the Proposal on Ecency ▶️ https://ecency.com/me/proposals/269
- Vote the Proposal on Hivesigner ▶️ https://hivesigner.com/sign/update-proposal-votes?proposal_ids=%5B269%5D&approve=true