This is great feedback. Honestly I’ve been primarily focused on integrating features so far. In the next couple of releases I plan to go through and focus on refining the UI making it more readable, reactive, and customizable.
I hadn’t really considered adding a jump button, but I can absolutely look into that as an option. I might even see if I can fit that in the next release, as it should be quite simple to implement.
As for open sourcing, I have not decided just yet. I would prefer open source, but I need to put some more thought into it before I make a decision.
Alright so I’ve reworked the mod log a bit, and the readability has improved. I’ve also added more details and collapsible content so it’s not quite so overwhelming. I included some , and an undo option for all the mod actions (still working on undo for admin level actions). There is still some UI work to be done, but it is definitely an improvement already.
I think I’d like to work on some admin tools next, but I don’t want to try and tackle all of them at once. I’ve had a busy schedule lately, so I don’t want to prolong releases anymore than they already are. I was thinking to add support for reviewing user applications first, but if you have any suggestions on frequently used admin tools that I may want to start with, just let me know.
As for adding/removing/transferring mods, I’m not sure what limitations are due to the api, and what may be just UI limitations, but I will look into it. I know one limitation is that a community can’t be transferred to a user on a different instance than the community.
The parent peek option should be very easy to implement, I should be able to add this in the next release no problem. Most of this is already implemented for viewing context when replying, so I just need to add an option to preview it. This also gives me an idea for the comment compose view, where you could view multiple parent comments for context while composing.
I’ll hopefully have the next release pushed out on Tuesday evening this week.