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.

This has the vibe of being on a party boat and waving at random people on another party boat passing by

Just found OOP on Mastodon: @goldstein@im-in.space (Does this notify them?)

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)

This is what Torvalds himself recommends to all real Linux fans

I’ve been using NixOS for my laptop and servers for over a year and I’m totally obsessed with it. While I upvoted you for visibility, I wouldn’t really call NixOS obscure anymore. I’m constantly seeing it randomly mentioned in various distro-agnostic Linux spaces online lately.

Although it’s been seeing a lot of hype lately, I agree it’s still sort of niche and definitely not for everyone.

Hannah Montana Linux

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