top | item 47092559

(no title)

big_toast | 9 days ago

ya, thank you, I recognize the history! The extension just seemed isolated from another identity. So I was wondering the thinking. I wish chrome let you scope the manifest/permissions on the user side more.

discuss

order

latchkey|9 days ago

i've done my best to keep it as minimal as possible. i wish i didn't even need squeeze, but there was some block that required it and it was easier to just do it as a few lines of code. i figured as long as it is all built by CI, GPL and OSS, I'll get a pass. it is the best we can do today.

try it out, let me know what you think. i promise not to hack your hackernews.

latchkey|9 days ago

one other thing. the best thing you can do is just run it in a separate profile than the rest of your browsing. i don't do that myself, but it would be slightly more secure that way.

big_toast|9 days ago

Separate profiles is perfect. Not sure why I haven't been doing this. The keyboard shortcuts are wonderful and enter to open the article is so optimistic! Thank you for dragging me across the finish line. Your extension is glorious.

Edit: I liked the j and noticed it even worked elsewhere (bestcomments is when I ran into it)! None of this is requests, just reflections. Still warming up to the keyboard navigating collapsed comments behavior. Also I think I remember the original HNMarkAllRead 'hide stories' checkbox hid stories after visiting comments. (And there was a hide comments checkbox that when marked only revealed new comments since the last visit) There are lots of workflow permutations to hn!