Andrei Rybak <[email protected]> wrote: > Hello, > > First of all, thank you for developing and maintaining public-inbox.
You're welcome :> > I'm a frequent user of accesskeys [1] so I've written a user script [2] > to add them to some links on websites running public-inbox. The user > script is available via Greasy Fork, a website for hosting user scripts: > > https://greasyfork.org/en/scripts/458141-accesskeys-for-public-inbox Cool. I've long intended for the HTML output to be stable enough something like that. Please feel welcome post here if there's new developments or discussion to be had about it. Fwiw, there's also rel=prev / rel=next for paginated pages; but I forgot how browsers use them :x > Any feedback, especially ideas for other uses of accesskey on > public-inbox websites would be appreciated. Do you know if there's commonly-used accesskeys for normal git repo viewers? (cgit/gitweb/etc...) The /$INBOX/$OID/s/ endpoint (linked from @@ diff hunk headers) is being extended to support "normal" git repositories meant for code (WIP: https://80x24.org/lore/pub/scm/git/git.git/ ) and I'd like to avoid conflicts. > P.S. I've looked at source code of public-inbox to try adding support for > accesskeys natively, but my Perl knowledge is very limited, so I > decided against trying to implement it on my own for a patch. No worries. I will consider it if I find time (some other things take priority atm). Do you happen to know what happens if a page defines accesskeys which conflict with userscripts? I prefer avoiding breakage for existing userscript users if implemented in public-inbox itself. I am a bit hesitant to recommend browser extensions in the documentation/help output itself since Stylish was found to be spyware in the past. (that goes for downloading and running anything from the Internet w/o auditing it, first, public-inbox included)
