Police can’t demand you reveal your phone passcode then tell a jury you refused

Re:Police can’t demand you reveal your phone passcode then t... by hungryforcodes on Friday October 22, 2021 @02:09PM (#28960524)

Sorry-- this is totally unrelated and maybe even inappropriate-- but how do people sort through 300+ comments on HN to consume a topic? I understand that /. introduces bias with its system, but I honestly find myself abandoning alot of deeper HN threads because it's so difficult to parse all the comments. Perhaps I'm missing something.

[ Parent | on HN ]

Re:Police can’t demand you reveal your phone passcode then t... by sixstringtheory on Friday October 22, 2021 @02:22PM (#28960677)

If by “consume” you mean “acquire the contents” of all those comments, well, you’ll have to read them all.

A more interesting question to me for a while has been, how to follow the evolution of a deep thread in which the time it takes to read a larger amount of comments, even more are made. How to know where all the new ones are? It’d be cool to be able to diff a thread based on timestamp.

[ Parent | on HN ]

Re:Police can’t demand you reveal your phone passcode then t... by IPTN on Friday October 22, 2021 @04:00PM (#28961971)

https://github.com/insin/hn-comments-owl does exactly that. Makes following threads so much better.

[ Parent | on HN ]

Re:Police can’t demand you reveal your phone passcode then t... by hungryforcodes on Saturday October 23, 2021 @09:52AM (#28968479)

You and the parent post have both interesting answers -- thanks :)

[ Parent | on HN ]