Alicornutopia

Throne3d wrote:@Pedro: that doesn't help us come to a solution for this particular item, though. Do you actively prefer that hidden posts not be marked in any way on other post lists? Would it inconvenience you (1) not at all really, (2) a bit, (3) quite a bit or (4) very much a lot?

Does too, if all I want is what I said then that implies I don't care whether it's marked hidden from unread elsewhere as long as that doesn't affect post behaviour.

(1.5), making that a user setting would work, but I don't care enough to really ask for it.

I would not like this (all post links show) enabled by default because of eg room of requirement. (Yes, I know that particular problem is going away, but in general we should handle those sorts of situation. Also it'd still be cluttered on posts with 1000+ replies.)

@Unbitwise, currently for that use case I just use incognito mode (and hence am logged out and hence it doesn't mess with my read position).
Reply count is a good place to put the link (hadn't occurred to me).
Links at the end of the stats page should be doable but I'm not sure of the UI. (I guess it could literally be unstyled links in a row specifically for that?)
I will poke at my hacked up UI some more. (It currently has edge cases where long author metadata bits are handled in a very non-responsive way.) I personally like timestamps but the text could be more obscured if people don't care for it (currently is smaller, I think? Could try making it even smaller but that sounds maybe inconvenient.).
Loading pages is totally fine with NoScript. Looking at the first post when not on the first page is problematic (the expando needs JavaScript). The post dropdown is broken. You cannot hide warnings. You cannot preview. You'll have issues with icon selection (add existing to gallery, set character default icon) and with making posts (cannot open dialog to swap characters or alias, cannot change icons, RTF editor will be broken, privacy list won't open if you set that privacy) and you can't create a new template from a character's page (can still manually make it elsewhere). I think there are other things that are problematic. I've heard of progressive enhancement and it sounds like a good idea but would be kinda hard to fix everything up like that - long term goal?

@Pedro okay so we can just implement that thing.

Thanks!

My main feedback about the report continues to be: I do not like that a thread disappears from yesterday if it's been updated today. I do want to know how many tags a thread got yesterday even if it then also got new tags today, and right now that information is completely lost to the waves of time.

Also marking a thread you owe tags in as unread continues to cause the arrow to be purple rather than green.

I think the daily report on the constellation should be labeled differently; having the button for it be named 'report' is a little confusing. I had a brief moment of 'oh, there's a feature where I can report bad activity?' And then clicked it and realized what it was. I think a new user would have trouble understanding it.

Throne already has a pending change to "Daily Report" for when Marri has time to review it.

pedromvilar wrote:My main feedback about the report continues to be: I do not like that a thread disappears from yesterday if it's been updated today. I do want to know how many tags a thread got yesterday even if it then also got new tags today, and right now that information is completely lost to the waves of time.

It's actually kinda aggravating to do this cause I can't use the last tagged at date stored on the posts and have to go calculate from the actual replies. And then handle the top post specially for new threads. Doable eventually, just extremely not copy paste.

Marri has been busy irl and Throne has been VERY prolific and this meshes poorly but hopefully these will clear up nicely soon.

Alternative: retain yesterday's report and use that rather than recalculate?

Also it actually displays differently in different timezones, so it's not just "one report". Meaning using the data from the day before could be reasonably inconvenient.

Why not just generate it with a count (distinct) where date_tz = that day?