æʃliŋ, medical grab-bag @aescling@cat.family

mornyawn btw . also @clock, what time is it

@amy it’s NEVER filling

@amy real

@The_T @vaporeon_ e926 is just an imageboard fur furries (but with the explicit ones blocked by default—e621 is the explicit, canonical view of the imageboard). not really sure why they have a terms of use blocker tbh

me when i’m deathly hypoglycemic at 3am

i would love to figure out how to solve the terrible latency on my websites without just giving up on my httpd

mornyawn btw . also @clock, what time is it

@vaporeon_ s/qmail, with s6-networking fur networking and TLS, all compiled from source and supurrvised by s6. the setup is your typical qmail install, if that means anything to you. dovecot fur IMAP, just installed from debian. certbot handles ACME; i manually installed it from pip in a virtual environment because the certbot-digitalocean-dns python package isn’t packaged by debian anymore

granted people ignore my shit on gitlab or back when i still used github so maybe i wouldn’t have to worry about it

federation landing in forgejo is what would make running my instance not feel like overkill to me. though i’m not sure i would look furward to the moderation concerns that might entail

@vaporeon_ (if that sounded overengineered to you, i agree lol)

@vaporeon_ @wallhackio veevees using the teletype with the paws

@vaporeon_ i block pushing directly to main and instead pull request small changes to it; i can’t find an actual git hook that runs on “when my forgejo instance merges to main” (post-merge did not trigger when i tried it, but the manpage says that is specifically when you run git pull anyway), but forgejo (and gitlab, fur that matter) DOES trigger a push events on main fur webhooks, so i set up a CGI handler on a port firewalled to only accessible from localhost to run the “git hook”