qsantos / vihn Goto Github PK

Not high priority.

When implementing this, keep in mind that Ctrl/Alt/Meta modifiers are filtered early. That logic might need to be reworked.

See: plibither8/refined-hacker-news#39

Note that older versions of Hacker News might have different structures. In particular, story ages did not have a title attribute in 2020.

This is too inconsistent:

• h: Parent comment (stay in context when changing page)
• p: Parent comment (always go directly to parent)
• l: Open story link/comment permalink
• b: Open story link/comment permalink in background
• c: Open comments
• C: Open comments in background

Because:

• h and p cannot be opened in background
• l and o break and intuitive pattern

Solution:

• think about h in background; maybe g? still inconsistent
• consider adding P to open parent in background
• change binding for l/o; for instance o/O for “open”
• fix documentation in AMO
• fix documentation in Chrome Store

For example, in https://news.ycombinator.com/item?id=32493422, 22 links are annotated, even though only 10 can be used.

When navigating comments, URL changes are not added to the immediate history (navigating back/forward in the browser). This avoids breaking the back button too much.

However, the IRLs are still present in the long term history, cluttering searches.

See plibither8/refined-hacker-news#108

See plibither8/refined-hacker-news#111

Hacker News comment formatting is not complex but trips many users. A simple preview of the comment being edited should be available.

Detect links to some media and allow the user to display them in-page. Similar to RES's “Inline Image Viewer”. Potential candidates:

• YouTube
• Twitter
• Imgur

Navigating comments adds a hash to the URL. Using the back button does not help in removing it.

Things to take into consideration:

• if the page was initially loaded with a hash, it should be kept (what about hash charges)
• it should still be possible to access the URL pointing to the current comment; in particular, coding the browser and reopening it should navigate back to the comment where the user was at

At least in:

• {un,}{fave,flagg}ing
• {un,}collapsing manually
• automatic uncollapsing when using Newest Items

1. Open https://news.ycombinator.com/threads?id=luu#38307861
2. Hit p

This issue is dedicated to listing the features of the Refined Hacker News extension, as a source of ideas. ViHN aims for a tighter scope, so it won't implement most features of Refined Hacker News.

• archive-submission.js
• auto-refresh.js
• backticks-to-monospace.js
• change-dead-comments-color.js
• collapse-root-comment.js
• click-comment-indent-to-toggle.js
• click-rank-to-vote-unvote.js
• comments-ui-tweaks.js
  • Add border to indentation to make to show indent separation between comments.
  • ✅ Highlight item's original poster, displayed as [op] next to username.
  • Custom indent-width (default is 40px), which can be set using the extension popup.
  • Make <pre></pre> tags more visible.
• fetch-submission-title-from-url.js
• hide-read-stories.js
• highlight-unread-comment.js
• input-field-tweaks.js
  • Show how many characters are left in the 'title' field when submitting an item.
  • Increase width of 'title' field dynamically.
  • Increase height of any textareas (even those that are dynamically created), dynamically.
• key-bindings-on-input-fields.js
  • ✅ Ctrl+Enter to submit form
  • Ctrl+I to italicise
• key-bindings-on-items.js
  • stories
    • ✅ Next item (down)
    • ✅ Previous item (up)
    • ✅ Open link and focus tab
    • ✅ Open link in the background
    • Un-highlight item
    • ✅ Upvote item
    • ✅ Favorite item
    • Open item's comments on same tab
    • ✅ Open item's comments on new tab
    • ✅ Flag/unflag item
    • Hide item
  • comments
    • ✅ Next comment (down)
    • ✅ Next direct sibling comment
    • ✅ Previous comment (down)
    • ✅ Previous direct sibling comment
    • ✅ Toggle comment
    • Un-highlight comment
    • ✅ Upvote/unvote comment
    • ✅ Downvote/undown comment
    • ✅ Reply to comment
    • ✅ Favorite comment
    • ✅ Flag/unflag comment
    • Open numbered/index reference link in the comment
• linkify-user-about.js
• list-hn-polls-separately.js
• load-more-links-in-navbar.js
• more-accessible-favorite.js
• more-accessible-flag.js
• on-link-focus-comment.js
• open-story-links-in-new-tab.js
• past-choose-date.js
• prefill-submit-title.js
• preview-and-set-top-bar-color.js
• profile-links-dropdown.js
• reply-without-leaving-page.js
  • ✅ reply
  • ✅ edit
  • ✅ delete-confirm
• show-item-info-on-hover.js
• show-similar-submissions.js
• show-top-leaders-karma.js
• show-user-info-on-hover.js
• site-navigation-key-bindings.js
• sort-stories.js
• toggle-all-comments-and-replies.js

https://www.modernhn.com/

https://news.ycombinator.com/item?id=39559318

https://addons.mozilla.org/en-US/firefox/addon/hnes/

In some cases, the spinning arrow while a vote is being sent can cause reflow. For instance, with https://news.ycombinator.com/item?id=39559318#39559983:

Keep in mind that there can be a black bar: plibither8/refined-hacker-news#72

https://hn.algolia.com/

Long threads are split over several pages. It is currently necessary to manually click on the link at the bottom of the page to navigate to the next page. ViHN should allow navigating to the next page with minimal friction.

As a reference, the Hacker News thread with most comment ever can be used: https://news.ycombinator.com/item?id=25015967.

This is actually a bug of Hacker News, but should be addressed by ViHN

Refined Hacker News highlights new comments, but finding them means scrolling through the whole comment tree. Instead, there should be a simple way to find the newest comments. Maybe something like the upper right popup on SlateStarCodex articles.

• show list of latest comments
• jump to comment from the list
• uncollapse parents if needed
• disclaimer that this only looks at this page comment when there are other pages (previous or next)
• keyboard-based navigation in latest comment list
• make it look proper in smaller windows

• tsc
• biome
• others?

I have not bothered yet with proper handling, favoring fast iterations. However, the submission of a quick reply form could fail when the Internet connection is lost, the user is logged out, or Hacker News is down. The error handling should make sure that the user's content is not swallowed by an error page.

For instance, do not enable it on https://news.ycombinator.com/submit

https://news.ycombinator.com/submit

The l key binding only follows the storie's link. There should be a simply way to always navigate to the comment thread. Maybe using c?

The current workflows are mostly designed to be keyboard-only, albeit without interfering with the existing mouse-only workflows. However, this means that certain features might not work as expected

• focusing the “new comment” form manually does not enable preview
• clicking on a “reply”/“edit”/“delete” link does not enable quick-reply/edit/delete
• clicking on a vote arrow, or an “unvote”/“undown”/“favorite”/“un-favorite”/“flag”/“un-flag” link, or {un,}collapsing comments do not use the 503-safe system

• toggle smooth scrolling
• toggle saving collapsed threads
• toggle Newest Items