AnnouncementsMatrixEventsFunnyVideosMusicAncapsTechnologyEconomicsPrivacyGIFSCringeAnarchyFilmPicsThemesIdeas4MatrixAskMatrixHelpTop Subs
3
IdeasForMatrix - - (+2|-0)
Viewed, Not viewed comments.(self)
5 commentsbyHighQulaityDickPics

When someone makes a comment on a post, that post goes to the top of the feed. If i then click on that post to see what the comment is, i have to remember what was there and try to find the new comment.

What would the approach be to give use users a way to either check of seen comments or an option in the settings to allow it to automatically check all seen comments, and then put those on the bottom of the comment section unless a a new comment is a child of the parent comment?

Comment preview
[-]x0x7
1(+1|0)

I'd think it would be easier to mark unread comments visually. If I did that I'm storing the data for that on the front end. Larry won't like that because his browser never persists anything. I've yet to think about how I'd want to model the data on the back end. Maybe something similar to what I'm using for voting. That will probably become the single largest record source for the site. But I guess it's lowish value data so I can just purge the table if it gets crazy.

Either way I'd do it on the front end first.

parentlinkreply
[-]JasonCarswell
1(+1|0)

If I'm understanding the discussion, this seems to be about "freshness". Why not just make it all expire from the database after a month. I can't imagine many conversations lasting more than a month nor anyone needing to save this sorting presentation.

parentlinkreply
[-]HighQulaityDickPics1(+1|0)

Yeah, then you dont have to mess with a comment list that reorders itself based on views.
What about having a dead link get generated next to each comment you want to tick off, that way the browser can store that info in the history of the users browser. use like █ or something?

parentlinkreply
[-]x0x7
1(+1|0)

I see what you are saying. I'd more likely just use 

localStorage.set(`commentview.${commentid}`,true);
//or
localStorage.set(`commentviews`,JSON.stringify(commentviewobject));
//or
localStorage.set(`commentviews.${postid}`,JSON.stringify(thispostcommentviewobject));
//or
indexDB('insert into commentview values I forget the rest because I havn't used indexDB in like 6 years but I know it exists)';

First options will load an absurd number of entries into your localStorage. When and how that breaks I have no clue. Might as well abuse it and find out.

The second one would build a huge object that would get parsed and stringified every time you visit a page. How that one breaks I know a bit more. Not a good idea.

The third one is in between. Stores a reasonable amount of data per record and reduces the total number of entries in localStorage by an order of magnitude.

Last one I think browsers stopped persisting that even more than localStorage because they mostly want to phase that out of existence. A features browsers regret supporting but they did so now they keep it -ish. Full of inconsistent nerfing across browsers as a way to poison the pill for anyone trying to use it.

parentlinkreply
[-]HighQulaityDickPics1(+1|0)

oh yeah. that is a good point i didn't consider, different browsers work differently. Thats weird. :-) Thank you for the suggested approaches and why they would break down.

parentlinkreply