AtomHeartFather

I’m just an old guy with a lot of opinions. I am a sysadmin by trade. I like Linux, cool gadgets, Sci-Fi, DC comics, bass guitar, prog rock/metal, and annoying my kids with dumb dad jokes.

  • 13 Posts
  • 46 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle
  • Polaris strikes me as the retelling of a fever dream. I did enjoy The White Ship more than Polaris because it seemed to be a little more cohesive. Either story could easily be the basis for a concept album by Rush or an epic song by Iron Maiden.

    I have to admit that I don’t much care for these early writings. They are brief and somewhat disjointed, a little too dreamlike to hold my interest. I do hold them in some regard since they show the beginnings of his Dreamlands ideas that take on fuller form in his later writings.


  • The Doom That Came To Sarnath was my first introduction to the writings of HPL many many years ago. I enjoy re-reading it as much as I did the first time. This time I opted to listen to it on HorrorBabble, the narrater was very good.

    I always find myself thinking about little side stories in the same setting. What did the “people” of Ib ever do to deserve the hate of Sarnath? The beings that inhabited Ib seemed to just keep to themselves. They are described as having “bulging eyes, pouting, flabby lips, and curious ears, and were without voices”. Is it just simple pure xenophobia that drove the people of Sarnath to kill them all, or were there unstated incursions into Sarnath? The story does does not describe the denizens of Ib as anything other than ugly, and maybe that was enough for the people of Sarnath.

    In the end the people of Sarnath got what they deserve, which is a somewhat surprising result considering how deeply xenophobic HPL was at the time of the writing. One would expect a Sarnath apologist viewpoint.

    I always feel like Doom has an almost cinematic feel to it. Even though the story is brief the setting is lush and very interesting.






  • I don’t hate it. It makes room to tell new “old” stories without just completely dismissing canon. The idea of a “fixed point in time” is a concept that I think originated with Doctor Who. The Strange New Worlds concept is similar, but instead of a fixed point its a fixed event or fixed outcome.

    I do wonder though, how much of this “time pushing back” is actually that? Or is it actually just the “Federation Time Cops” from the far future making sure things happen even if someone successfully meddles with history. I actually kind of hate the concept of time travel being a thing in Star Trek. Leave it to shows like Doctor Who.










  • I do appreciate your feedback, but I think at a minimum that anyone trying to run a Lemmy instance in Docker should know how to install docker and docker compose and how to run basic commands like docker compose up -d. There are many tutorials out there for doing just that and I’m not trying to reinvent the wheel. Once you have gotten that part done my document kicks in and picks up where the official documentation is currently lacking (in my opinion).

    I do explain a lot, but I did my best to explain it in terms that most anyone could understand.

    I will take your feedback to heart and maybe try to write a step by step tutorial for people who are completely new to Docker as well.



  • Thanks for your comment, but I don’t see much value in pulling a new copy of the docker-compose.yml from the Lemmy GitHub. The only things I would be updating when Lemmy updates is the tag/version. If they added new environment variables some time in the future I could certainly take a look at their updated compose file to see the changes but I wouldn’t want to pull it down and replace my custom compose.

    I specifically don’t care for their (Lemmy devs) choices for logging, docker networking, and the built in nginx, so removing and simplifying all that was my main goal. Everyone has their own way of doing things, and this is mine.

    I will probably take a look at your Traefik configs and add them as a separate document for those that don’t want to use NPM. My goal is to add a subsection for most of the current revproxy choices.


  • I do not recommend using Ansible. It adds additional requirements and complexities that are unnecessary. Ansible is a great tool for managing multiple servers and software installs, in my opinion it is not the right tool to install Lemmy on a single instance. My install instructions require only that you have docker and docker compose installed.

    That said, you could easily replace the docker-compose.yml that Ansible set up for you with the one I am providing. Just don’t run Ansible against your server again or it will wipe out your changes.









  • Community discovery that spans all federated instances should be one of the top things that development should be working on. And it should be integrated into Lemmy, not as a separate website people have to go to and search.

    Peoples are lazy. They don’t want to have to go to some separate website and then search for something. And lets not even get started on the difficulties of adding a remote community if your instance doesn’t know it exists, its wonky at best.

    If a user cant type “Stephen King community” in the search bar on their instance and then get results, they are either going to assume it doesn’t exist and give up OR they are going to be hitting that “Create Community” button.