You and I are both using Lemmy via the Lemmy.ml instance. If Lemmy.ml blocks (aka “defederates from”) another Lemmy instance, you and I won’t be able to interract with people on that blocked instance.

You can seen the block list here: https://lemmy.ml/instances

Removed by mod

I’m setting my homepage to stronk.bond

I’ve been using restic as well, but with Backblaze B2. So technically this issue doesn’t affect me, but they’re on thin ice so I might switch to another S3 provider. What made you go with Wasabi?

This person’s probably right but I still resent everything being designed for the lowest common denominator

This, plus the fact if they don’t overcommunicate and send you 10 transactional emails (eg. “your order is still on its way!”) they’ll have people filing credit card disputes and BBB complaints, blasting support screaming this-site-is-a-scam-where-is-my-order!?? over a two day shipping delay.

This HN thread reads like a fun Chesterton’s fence exercise.

New engineer shows up the first week on the job: “10 emails? You guys are all stupid this only needs to be 3 emails…receipt, shipped, and feedback!”

Whole team groans, having to explain yet again the many years of scar tissue behind exactly why every one of the 10 emails exists.

I haven’t personally tried it, but Owncast might be an option if your friend knows someone who would be willing to host it. (I’m not sure if that would be considered technically demanding)

I currently push to a private GitHub repository (planning on moving to a self-hosted Forgejo instance soon).

Although making my nix configuration public would be safe anyway since I use sops-nix which encrypts all my passwords in the repo using a key derived from my SSH key. During nixos-rebuild it decrypts them and puts them each in their own text file at /run/secrets, with permissions set so you need sudo to view them. (The permissions can be tweaked as needed)

It was a pain in the neck to get started with initially (like NixOS itself), but it was very much worth it. (Basically a necessity since putting secrets even in a private repo is considered bad practice)

I got it working, thanks! I think I found a minor bug though. I could only get the --template flag to work when the file is in the current working directory. Subdirectories and absolute directories didn’t work. I worked around this by simply cding into where my template was stored before running tinyfeed.

Even tinyfeed -i feeds.txt -o index.html -t ./template.html (with ./) results in:

fail to output HTML: fail to render HTML template: template: "./template.html" is an incomplete or empty template

This guy Zuckerberg’d way too close to the sun

Check the demo: https://feed.lovergne.dev/demo

It links out to the source webpage, so this might not be what you’re looking for.

Although this might inspire me to build a single page app generator using Astro that does that.

This looks awesome, definitely gonna try this out! Any plans to add images/thumbnails? Looks like gofeed already returns them.

Their website doesn’t load for me thanks to my firewall (they’re a spyware company)

I’m never listening to music ever again

Do you use git? That basically forces you to do some documentation as you go. Multi-line commit messages are often helpful too. (When I first learned git, I only committed using git commit -m which is a bit restrictive in terms of how much you can fit in commit messages)

All my computers (including servers) share the same NixOS Flake. So my documentation consists of:

1. The Nix code itself
2. The commit messages for each change I make
3. Inline comments in the Nix code
4. A few readme.md files to explain the contents of certain directories

I know how to fix that

You can’t make this stuff up!

AMC made a documentary series about it in 2008

I think copyparty would accomplish that pretty well