Thanks user, the feedback helps a lot!
Would love to, but where? Right now it's just narrow enough to fit on one half of the screen.
My shell lets me click the URL in the lizard l output. And there's lizard oa if you don't want to click all of them. oa does update the "last seen" status.
You still think it's necessary to have more open commands?
I'll think about this. Hopefully I can come up with a good syntax.
Yeah, I've been thinking of this also. But that would be the first step into full-fledged client territory rather than monitoring tool, which is why I've been hesitating.
What criteria do you think make sense? (I currently copy and paste it into a text editor/spreadsheet and filter that way)
I've deliberately made it stateless so that scripting is idiot proof, but I also feel like it would be a convenient feature. The concern is that it will make development confusing (since now every function can be done in two ways). Maybe I can hold off a bit until all the major features are complete and then start working on the interactive.
This was a wontfix for me, since it seemed more logical to just set a cronjob to call lizard r periodically. Thoughts on this?
What's your reasoning for this? I feel like text mode would be very infrequently used and "I changed my mind I want the images too now" would be a common issue.
I think this goes into the search/filter, but how about I just dump a csv and your own software can deal with the filtering?
Actually a "list only threads with activity" feature has been priority for me recently.
This is gonna involve a lot of learning for me, since I have no clue about such things, but definitely mandatory for v1.0.
My two confusions:
1) What syntax? Just dumping a flat JSON dictionary is easy but is that
2) What options do you think need to be configurable?
Definitely will implement this soon. Although you can kind of tell from lizard r output.
Right now it works by looking at the anchored reply associated with the thread, and tries to scan for them. So it's not really "You" detection, more like "replies to this post" detection.
It's pretty buggy, which is why I'm considering tracking replies, threads and board separately. If you can reproduce it on /test/ that would be really helpful.
Sounds like a bug, I'll look into it. Used to be c, but I changed to create since it's such a rare command.