The LeoThreads feature on Leofinance is a very interesting one. It was the ultimate implementation to achieve more engagement on Leofinance, and introduce a proper short-form content system on the Leofinance blockchain. Leofinance is one of the greatest projects on the Hive blockchain.
However, I tried to figure out the inner workings of @Leothreads, even if I am nothing close to being a developer, I just felt, I needed to look deeper into the inner workings of LeoThreads, and that is for a very good reason. Let's take a look!

LeoThreads Figure Out (Or Sort of)

I didn't look at any strings of codes; all I had to do was start a thread on #LeoThreads and track it on the Hive Blockchain Explorer.Here is what I found:

Looking at the above transaction tells you a lot about how Leothreads is implemented. A Hive account @Leothreads has been created, within which a "Multi-container Thread Post" is created occasionally to house the Leothreads' contents, that is your microblogs. All your threads are basically replies to each other's created multi-container thread posts.

This seemingly simple implementation is really a nice implementation. It makes the best use of the blockchain rather than trying to re-write the scripts. And it also inspires confidence in LeoThreads, at least we know for now that all the bugs experienced are just an outcome of its implementation and not an issue with its foundation. It is also reassuring to know that your threads will not clutter your blog.
While I have tried explaining the workings of LeoThreads in some simple form, trust me, it is way more than that. You can think of the job done to impose a 240 word limit, integrating LeoThreads smoothly with @leofinance, and much more. It is undoubtedly a neat job. Kudos to the team behind this.

Stats

How has LeoThreads done so far? The reception has been great, I must say! For the past 48 hours (as at the time of this writing), 2,224 threads have been created in LeoThreads. The reception is encouraging. We just hope the fire keeps burning.

Early Feedback on LeoThreads

LeoThreads will mature quickly. As I've said earlier, it is built on a solid implementation, and most improvements should now be on the UI/UX levels. Here are a few recommendations:

1. Good use of dividers: Currently, it is till when you hover over a post that a highlight divides the post, but a proper divider showing where one post starts and ends will go a long way. Here is a graphic aid:
   
2. Use "New Thread" instead of "Threads": The Threads on the top of the page require a little bit of figuring out. They hardly indicate any action. Replacing it with "New Thread" could be nicer. See an example:
   
3. Proper Presentation of Ads: The ads on LeoThreads seems to be given first priority over threads, this is because they usually load first before threads, which slows down the page, as it seems the entire ads position must be loaded first before putting threads in between them. I feel, a better way to do this will be to:
   i. Use simpler and shorter ad banners and well-optimized banners.
   ii. Putting ads by the side of the page
   iii. Automating ads as threads itself instead of having it heavily implemented on the threads page

Breaking LeoThreads

But I tried something more. Can I break LeoThreads word limit of 240 words per thread?
I went to the back end, using PeakD, and visited the LeoThreads' Multi Thread 0.3, which was currently being run on LeoThreads as at the time of writing. Thereafter, I created a thread by pasting a huge amount of text, which was obviously accepted, but wasn't displayed on the LeoThreads frontend. So, it seems you simply cannot exceed the word limit.
Moreover, any threads made outside of the LeoThreads frontend seem to be ignored entirely by the system.
The developers really did a lot of work on the backend, and their efforts are quite commendable.

@ifarmgirl reportedly observed this that someone keeps breaking the Thread:

I also did observe the above few moments after making the above attempt to exceed the word limit, but I cannot say for sure if it was my attempt, but I strongly believe that it wasn't!

Nonetheless, I may be guilty and culpable for overstepping the boundaries, but the fact remains that Leothreads is undoubtedly in its early stages of development, in fact, its current state is a public beta, so we may not have the best of it till after a few refinements, and trust me the devs are already working round the clock...