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.
You are viewing a single comment's thread from:
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.