• 0 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: July 12th, 2023

help-circle



  • I love that these extensions exist and in theory they sound awesome. Unfortunately for a few reasons I’ve never been able to get in the habit of using Tridactyl (or any vim browser addon):

    • it doesn’t play nice with Google drive apps (which my company uses extensively), so if I use the vim shortcuts to cycle between tabs and open a Google doc, the next time I try to cycle tabs it will instead start typing in the document. (Alternatively I would never be able to interact with Google docs without manually enabling ignore mode)

    • hint mode works really well for some sites but a lot of sites have multiple anchors close together (eg one for an icon, one for text and one behind both) which leads to longer hints and difficulty figuring out which hint to actually use

    • Firefox doesn’t allow you to rebund the default “/” search (quick find) cycle keys. The default is c-G for next (not sure about previous); I would like to use n/N

    On simple and well-designed “dumb” webpages it works amazing. I wish more sites were designed that way, but unfortunately a lot are made with the assumption of a mouse/touchscreen :(


  • I think neovim with kickstart has out-of-the-box support for go, or if not, should be configurable with two added lines (add the treesitter parser and LSP). Unlike nvchad and lunarvim and stuff, this is not a “distribution” of neovim but a good starting point for a config that makes it easy to slowly learn how to add stuff and change stuff as you see fit.

    At the beginning, you can add languages that you need support for pretty easily by adding to a list of LSPs and Treesitter parsers that should be installed; later on you can start adding and configuring plugins as you wish.

    I’d say it sets you up about the same level as Helix or a little less than VSCode.





  • Since this issue is most prevalent while browsing new, you could temporarily store (a hash of) the titles and contents of each post during a given browsing session, and if a post matches another post on the same page (e.g. one set of posts from Everything/new), hide it and allow the user to see comments from each instance of the post when they view the canonical (earliest, or most active, or returned first) post.

    If another duplicate post is later loaded (through scrolling) the post could be hidden and replaced with a smaller indicator telling the user a duplicate post has been detected, and they can click it to view the comments.