• Posts
  • RSS
  • ◂◂RSS
  • Contact

  • Mark New Comments

    August 31st, 2014
    tech, comments  [html]
    Online discussion spaces tend to use either linear or threaded comments. With linear comments there's just one long series of responses while with threads each comment is attached to the one it's replying to. In general I really like threads: the clarity they give you is very powerful, allowing a large number of people to have a coherent discussion by all breaking off into their own overlapping mini-discussions around individual posts. A downside to threads, however, is it's very hard to come back to a discussion and see what's changed. If you just have a linear discussion you find the last comment you remember and read from there, but with threads you're kind of lost.

    One solution is for the page to keep track of when you last visited, and highlight any comments that have been posted since then. I first saw this on lesswrong, more recently it's been added to slate star codex, and now I've added it to the comments here:

    See how there's a little black line to the left of Alex's comment? That means it was posted more recently than the last time I visited the page.

    Warning: boring technical details follow.

    While you could do this sort of thing with local storage, I wanted this to work on as many browsers as possible, so I used cookies. The key bit of javascript is this:

    var last_visit = document.cookie.replace(
       /(?:(?:^|.*;\s*)jtk_last_visit\s*\=\s*([^;]*).*$)|^.*$/, "$1");
    var current_time = new Date().getTime();
    var one_year_gmt_str =
       new Date(current_time + 31536000000).toGMTString();
    document.cookie = "jtk_last_visit=" + current_time +
                              "; path=" + window.location.pathname +
                           "; expires=" + one_year_gmt_str;
    
    What does this do? The first line reads the cookie jtk_last_visit if the browser sent it. If no value was sent it will just be "". (The crazy regex comes from an MDN post.) The next three lines set the jtk_last_visit cookie to the current time, make it expire one year later, and restrict the path to be for this page only. That's important: otherwise visiting any page on the site would clear your highlighted comments.

    Now you have some javascript that does:

    var comment_is_new = last_visit.length > 0 &&
                         comment_epoch_ts > last_visit/1000;
    
    And you mark up the comments based on comment_is_new.

    Comment via: google plus, facebook

    Recent posts on blogs I like:

    What should we do about network-effect monopolies?

    Many large companies today are software monopolies that give their product away for free to get monopoly status, then do horrible things. Can we do anything about this?

    via benkuhn.net July 5, 2020

    More on the Deutschlandtakt

    The Deutschlandtakt plans are out now. They cover investment through 2040, but even beforehand, there’s a plan for something like a national integrated timetable by 2030, with trains connecting the major cities every 30 minutes rather than hourly. But the…

    via Pedestrian Observations July 1, 2020

    How do cars fare in crash tests they're not specifically optimized for?

    Any time you have a benchmark that gets taken seriously, some people will start gaming the benchmark. Some famous examples in computing are the CPU benchmark specfp and video game benchmarks. With specfp, Sun managed to increase its score on 179.art (a su…

    via Posts on Dan Luu June 30, 2020

    more     (via openring)


  • Posts
  • RSS
  • ◂◂RSS
  • Contact