Feedback Thread: Discussion (>'.')> <('.'<)

Ha! That one had a NEW flag attached to it for me.

And I think I know how it happened. Two of the tabs in my browser have an A2K page open. I posted the new post in one and refreshed "My Posts" in the other. Maybe that's it.

Of course!

Weird, not something I've seen so far. Must be a bug if it's inconsistent.

I updated my post while you were responding to it. Did you catch the update?

I have seen the "new" tag for my own replies, but it happens intermittently and infrequently. Usually, a thread to which I've replied is below all of the new stuff.

Perhaps someone else is replying to the thread in close proximity? Someone else replied and then deleted their response?

I did not catch the update. That makes sense.

Testing that theory.

Nope. Other tab displayed it correctly.

On a different note, I have two points about the companion poll thread:

1) Re-design: Is there a screenshot based on which we can vote it up or down?

2) Improved PMs: The basic PM design works for me. I wouldn't suggest any more than an incremental fix: make the new-PM editor the same as the new-Post editor, so that it includes a BBCode editor and a preview. I suspect that for that purpose, you could just reuse code you're already using anyway. Other than that, I'm fine with the status quo.

Hmmm ... differences in our browsers' caching?

Could be. I'm running Firefox 3.6.6.

Firefox 3.5.10 on Fedora Linux 12

I just had a post show up as NEW when I was the last poster. I have no idea what I did differently on this post vs any other post I made this morning.

FIrefox 3.6.6

OK, I just replicated it by replying to a thread, and then immediately hitting "new posts".

Probably just an artifact of how Robert wrote the software.

Ooh screenshot! Awesome.

By "immediately hitting 'new posts'" do you mean that you don't even wait for your response to load? As in, do you see your response in the thread before you hit "new posts"?

Edit: a-ha. I made the "new" appear if I didn't let the post load/ I never saw it on the thread, I just hit "new posts" IMMEDIATELY" after "submit." That seems to make sense though. (Even though I wrote it I haven't read it.)

Actually, I let my reply load first, then scrolled up and clicked "New Posts".

Doesn't happen every time, just sometimes.

Huh. Sure sounds buggy then.

Maybe not buggy, just engineering trade-offs for performance/usability vs. processing power, database size, physical disk access, etc.

I've seen the my own post new issue only once, I'm not sure what causes it (we may actually need to slow the program down to fix it, I wonder if the thread is being marked read at the very same timestamp of the post sometimes) but it's very rare.

As for including ignore into the read tracking I am not sure if this is desirable. They may be ignored but the topic is still new, and others may want the new to be what it says on the tin. Also, what if the last post was a user ignored but the previous ones (also new) weren't? That becomes a very expensive calculation, no longer allowing us to use our db indexes and well, put it this way: it's an unlikely feature because it's very non-trivial and has high potential for confusion.

Fair enough, it was just an idea. I had a feeling it might be expensive in runtime.

No, the project is to develop the design.



Well there are some serious issues for heavy users, related to pruning and their inability to manage that at all (e.g. they are having messages they want pruned and have no ability to delete the ones they don't want) so we'll at least need to do that.