The only logic change is that the error reporting is a little cleaner if it fails while loading a profile page

but more importantly, enabling verbose logging now gives a bunch of information about specifically where the error happened in the code if the app explodes

this means that I can more efficiently figure out what went wrong and how to fix it

If you don't feel like redownloading it, that's fine! 0.8.2 will still work, no problem.

This is mainly for new users going forward.

As a side note, I am currently in the process of researching how I could swing a mac port. That may be available in the next update.

I'd need some testing help from a mac user, though.

Out of curiosity - would it be possible at some point in the future to only count the last comment in a series of "reaction comments" (aka blank ones where the icon's expression changes and not much else)? I don't know how feasible that would be, though.

it should be doing that now! multiple consecutive comments from the same journal are counted as one comment.

let me know if it isn't and I'll look into it.

Huzzah, new version!

No worries at all if there just hasn't been time, but you said it might be possible to adjust the search-for-backtags range at some point in the future-- make it so users could select how long ago to check back for new tags instead of it being a default 2 weeks-ish. Is that still in the works?

I'll make that more concrete in a future version, yeah.

Much thanks-- for that, and all your work here. This is fantastic.

obligatory side note, though, that regardless of backtag scan distance, it won't process anything over 90 days old

Oh nice

As a Mac user I would help