3 ms·

This is awesome!! :) One tiny thing (though everyone's tiny suggestions sure add up :D ) (aside from the alt-h not working in firefox)... It would be awesome

This is awesome!! :) One tiny thing (though everyone's tiny suggestions sure add up :D ) (aside from the alt-h not working in firefox)... It would be awesome if hitting space or something on a selected post would open it in a iframe (or panel) in the middle of the screen. Then be able to up-arrow/down-array (or PGUP/PGDOWN) through the page and escape out of it. This would mean you can quickly skim an article without leaving the app! But, well done, it's absolutely wicked :D

seFausto 5y ago
I completely agree on the iframe. After opening a link I keep trying to go back by pressing the left arrow. Pressing Ctrl+W is not to bad to close the tab though.
- mrmattyboy 5y ago
  Indeed, not too bad and this is what I did, but certainly not immediately natural, as you have to rely on the browser's tab history (i.e. you closed this tab, redirect user to previous tab), so wouldn't work if I starting viewing a HN post, then continued work (that I should have been originally doing) then go back to the post, close it and then browser redirects me back to the 'work' tab that I came back from..... if you see what I mean. Tab history: * Expected: HN client -> website from post -(ctrl+w)-> HN client vs: * HN Client -> HN post website -(switch tab)-> real work work tab -(switch back)-> HN post website -(ctrl+w)-> real work tab :( )* *Think I opened a bracket somewhere in the comment and haven't closed it
pabue 5y ago
Thank you! I'm definitely not complaining about the amount of feedback. It's really amazing. That really is a great idea. One issue might be that not every site allows being shown in an iframe because they block that functionality. But I'm gonna look into it!
- mrmattyboy 5y ago
  yeh, I can imagine that feature spiralling in complexity (up to pre-checking server-side if they provide CSP/Frame headers, then outright download and proxy the page :P ) Yeh, I could maybe image a 'p' button that would show a preview, that would just be hit-and-miss... I wonder what percentage of submissions on hacker news actively disallow iframes... like actual blog posts and not things like 'new apple product' from Apple's website :wondering:

seFausto 5y ago

I completely agree on the iframe. After opening a link I keep trying to go back by pressing the left arrow. Pressing Ctrl+W is not to bad to close the tab though.

mrmattyboy 5y ago
Indeed, not too bad and this is what I did, but certainly not immediately natural, as you have to rely on the browser's tab history (i.e. you closed this tab, redirect user to previous tab), so wouldn't work if I starting viewing a HN post, then continued work (that I should have been originally doing) then go back to the post, close it and then browser redirects me back to the 'work' tab that I came back from..... if you see what I mean. Tab history: * Expected: HN client -> website from post -(ctrl+w)-> HN client vs: * HN Client -> HN post website -(switch tab)-> real work work tab -(switch back)-> HN post website -(ctrl+w)-> real work tab :( )* *Think I opened a bracket somewhere in the comment and haven't closed it

pabue 5y ago

Thank you! I'm definitely not complaining about the amount of feedback. It's really amazing. That really is a great idea. One issue might be that not every site allows being shown in an iframe because they block that functionality. But I'm gonna look into it!

mrmattyboy 5y ago
yeh, I can imagine that feature spiralling in complexity (up to pre-checking server-side if they provide CSP/Frame headers, then outright download and proxy the page :P ) Yeh, I could maybe image a 'p' button that would show a preview, that would just be hit-and-miss... I wonder what percentage of submissions on hacker news actively disallow iframes... like actual blog posts and not things like 'new apple product' from Apple's website :wondering: