We need to make threads a media epicenter.
For this to happen, 2 things need to be done 1st:
- Make 🦁🧵 more stable than what it has been (look at today); and
- Display all threads content regardless of front-end used to generate it.
You are viewing a single comment's thread from:
1/ Without a doubt
2/ That is up to the front-ends. They have to tie into the Leo containers through Leoinfra. At some point, it will be open source but still up to the apps.
We will see what happens.
Regarding 2/, Ecency.Waves already treats D.Buzz & LeoThreads as nodes; it can display feeds from all 3 platforms at the same time, without restrictions. If we reply to a thread using Ecency/PeakD/Hive.Blog, LeoThreads won't display it.
The cache system is what is allowing scaling.
That's true; that's not issue for 2/. Once in a while, we make the mistake of replying 2 a thread using something "not Leo"; LeoThreads won't display that reply. I understand why this was done, but I think in the long run this is a mistake.
Again, that is because it doesnt go through leoinfra so it isnt going to read them.
That is why the features we are getting like reversing the comment order and fast load times even with 500 comments is taking place.