There is [email protected] and [email protected].
I mean... "who needs features in 2022" is onto something. But I use both, for various Nvidia and laziness related reasons, and have a dim idea what they do inside, as probably most flamers on the topic.
Feedback: to see an example one has to click through to another file in the repo.
Is it a subset of Markdown or YAML? It is a type of decision that it would be good to be upfront with to the users. It also gives you a framework for further thinking and development, and some out of the box parsability.
YouTube recommendations are often 30-60% decent and you can always fall back to that. Anything that has tags and similar artist functionality: Last.fm (still technically exists), everynoise.com, more specialized sites like Encyclopedia Metallum. I like to get some recommendations out of band even if I use streaming, otherwise it's too easy to phase out and make your memory dependent on their algo.
Some (even) more niche and involved methods:
Obvious things I don't see mentioned:
history | grep whatever (or other useful piping), though your older commands are forgotten eventually. You can mess with the values of HISTSIZE and HISTFILESIZE environment variables in your system.I don't know if you're talking in the long campaign, same players context, but I often find that for one shots around half of players, at best, skim the rulebook of the particular system. Myself sometimes I do, sometimes I don't find time. Some people, like it or not, come to a session mainly to chill and even let the others do most of the adventuring. Others engage with the adventure but don't feel like engaging with the rules beyond what the GM requires.
I'm also assuming the GM will explain the rules, and I think they are the ultimate authority. So stuff from the rulebook may not even be relevant (thrown out, replaced), and GM is the interface for the rules. I would call it OSR mentality, though some may call it glorified player laziness. But as a GM it may give you more room for your ideas actually.
I think the situation is a problem if players don't know the rules and get mad when their plans are impossible. I suppose this can happen more often with rules-heavy systems.
Anyway, I think keeping the rulebooks close to the players (either as putting them on the table or sharing PDFs) is good advice.
Context just before that quote:
As we understand it, this contract clearly states that the terms do not intend to contradict any rights to copy, modify, redistribute and/or reinstall the software as many times and as many places as the customer likes (see §1.4). Additionally, though, the contract indicates that if the customer engages in these activities, that Red Hat reserves the right to cancel that contract and make no further contracts with the customer for support and update services.
This is rich, don't know how many people are aware of that.
I was looking into Arch-based environment and wondered if there is an option for a scenario where you don't have to update for a few weeks for example, because you don't use that computer or whatever. But you still want to try the Arch configurability and wiki docs for it.
From what you're saying, it's still actually all rolling release. From my (flawed? correct me) understanding it is different from Ubuntu or Fedora, where you can update an outdated OS state and it isn't supposed to break. Possibly barring changing OS versions.
Thankfully regardless of trends in new gaming material, OSR is there to provide some sort of shared ground and quasi-compatibility back to the seventies. And a rough framework with an excuse for shameless homebrewing as well. I hope it will also continue to be a term you can use to attract people to play in the style.
They may not expose the actual PDF to you at all, just some software rendering of it. In that case I'd focus on making screenshotting efficient. Find a program that lets you save the whole screen to file automatically at once (one button press), or use Firefox ctrl+shift+s -> click on the page area -> save -> enter.
Any relatively sprawling historical place can do. (Image-search for "X plans" and "X photos" where X is your place) You can annotate them with whatever theme you want, look also at real life photos for inspiration. I mean to run something like this at some point. Real life cave systems, on the other hand, are mind boggling.
Agreed, I think hosting it on localhost not exposed to the internet is a great idea if this satisfies your needs for now. Do double-check the docs for your system if firewall disallows web server connections by default (Manjaro and Endeavour are based on Arch which is supposed to have good wiki).
Then, if you want to go online, you can export the database and put it into a server install.
There's a case to be made, realistically speaking, that using a well-known framework or even a CMS like Wordpress means less complexity specific to your website to understand for the next person. FTP cough SFTP or Markdown/HTML is definitely not beyond non-technical people to understand and use, but sadly there could be some resistance nowadays I imagine.
I would look into static website generators. Sadly I'm not sure what is most reliable nowadays, but I would prioritize easy of use and installation, as speed is probably meaningless on your scale. Here's a random article.