furikuri

Run info info

Texinfo pages were originally meant to be a longer alternative to manpages that had support for featureful navigation (links, indexes, etc). They're nice and I can see a world where they did catch on, but the standard viewer is always a little bit of a shock to jump in to (being based off Emacs and all)

Remnant of the type of keyboard that Emacs was developed on. Also the same place that the Super, Hyper, and Compose keys originate from

You can map it through your X server/Wayland compositor, but if not Emacs recognizes Alt and Esc as valid meta keys

Guess the Hyper key is due to make a comeback!

For cases where you really just want to jump between different prompts without piping out to another program/file, many terminals also support jumping through prompts as long as your shell marks them with an OSC-133;A escape code (looks like fish does this automatically now). Some terminals that support this are foot, tmux, kitty, and Emac's vterm, but it's undoubtably available in many others.

For example let's say you're using the foot terminal and the zsh shell. Just add the following code to your zshrc and then you can jump through each prompt using CTRL-z and CTRL-x

precmd() {
    print -Pn "\e]133;A\e\\"
}

Lmao. They couldn't even copy code from a random MIT licensed project? Sometimes I think these scammers aren't even trying

You could try making enabling git's rerere functionality, which stands for "reuse recorded resolution"

https://git-scm.com/book/en/v2/Git-Tools-Rerere

https://stackoverflow.com/a/49501436

Arch does tend to keep packages as close to upstream as possible, which can be both a good and bad thing. Sway not binding to graphical-session.target by default is a little strange for example. Other distros also save a first-time user a great deal of configuration for things they probably don't care about as well. Going through Fedora's install and finding out that disk encryption and SELinux were configured OOTB was very nice to see personally. On the other hand Arch's installation (w/o archinstall) has you choosing a bootloader, audio server, display manager, etc. Nothing arduous and I like it, but definitely not for everyone

This is all eliminated by spinoffs of course, but even there users have the option to run random scripts/AUR packages without vetting them. Also doesn't help that the most popular Arch-based distro for a while (Manjaro) was pretty flaky and generally incompatible with the AUR (despite saying otherwise), leading to many people saying "that's just Arch" and swearing off the parent project as well

I switched to (Doom)-Emacs from a ~7yr old homegrown Vim config last week and honestly the configuration is less bad than it seems. If you're mainly writing markdown you'll probably get 99% of the way there by just enabling the dedicated module

Depends

Clannad? Valid

After-Story?

The back end is open source, but sometimes they've lagged years behind releasing the source code.

I think this is the more worrying part if true. The backend is licensed under the AGPL, so this would technically be a ~~violation~~ of their terms

13. Remote Network Interaction; Use with the GNU General Public License.

Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software

Edit: For anyone else reading I looked into it a bit more and looks like the issue came to a head around 3 years ago, with this comment being made after a year of missing source code. The public repo has been pretty active since then, so the issue seems to be resolved

If I had to guess I'd say that their other project, Sponserblock, got a little bit more popular than they were expecting and this is just to help alleviate server costs. Most of the API endpoints don't require any auth at all (the single one that does accepts a random UUID), so any checks must be locally done (maybe system time?). The extension and server back-end are licensed under GPLv3 and AGPL respectively and are also entirely self-hostable, so the code is out there to verify if you wish

Additionally if you're looking for it to start on boot without logging in, you might find the loginctl enable-linger command to be of use. Maybe along with a Restart=on-failure policy in the service file if this is for a headless unit or something