I was happy to find a significant number of #inxi bugs along the way, hiding in all kinds of corners, and getting those squashed was an unexpected bonus, since every squashed bug is one less future issue.
Objectively, I'd really like to see the userbase take on a more proactive stance, and get involved more, at least in terms of finding specific parts of inxi that interest them, and contributing energy to those.
On another front, #xfce 4.19 is ready for testing, #wayland support is near!
I am starting to feel that the time of refactoring the initial #inxi sections post > #Perl translation is winding down, and I increasingly want to see what the community itself does, or doesn't do in regards to how they use or perceive #inxi in terms of actual real time/energy put out on their part.
I'd say the lack of this effort actively is rapidly growing into the most serious problem I'm seeing, so it's tempting to just sit back and watch what happens, without trying to interject too much.
The recent big #slackware repos/package tools upgrade in #inxi 3.3.27 kind of closed up the last significant repo/package gap, including adding pkgtools support to --recommends as the final supported package manager type (that makes 4, and that's it, there won't be any more, other pm inxi packagers are free to follow the docs on how to create an inxi that supports their pm.).
This was also useful to see what is out there and going on in the Slackware package/repo space.