Recent submissions

Comment · 1 year ago
I enjoy:

- seamless container logs (journalctl), no weird separate logger

- service start/stop/enable-at-boot no weird separate command

- integration with system/user slices, triggers, cronjobs (timers), exposing containers as first class commands overall!

Basically it's worth seeing container services work with non-container services.

If you don't like systemd, or have no stake in it, sure, have fun without it, but it's definitely added value when you're running services, and want to start containerizing some of them without abandoning all the good tools you are using in favour of docker logs docker run etc.

Comment · 1 year ago
Comment · 1 year ago
Yes-anding this to say:

For per-user gitignore, one can set the following config in ~/.gitconfig:

    # System-wide gitignore file
    # To avoid in-repo repetition for system-specifc garbage files
    [core]
        excludesfile = ~/.config/git/gitignore

Then your file at ~/.config/git/gitignore can be a normal format, and not need to be stored in repo. Perfect for system files (.DS_Store...) or editor swap files etc.
Comment · 1 year ago
Not an expert, but it seems NASA holds a few magazine publications for just that, it must come up often.

One VERY on topic is "ISS Benefits for Humanity", which shows why the ISS benefits everyone.

See edition 2022: https://www.nasa.gov/wp-content/uploads/2022/09/iss_benefits...

Seems from the table of contents, it breaks down to: earth observation, microbiology in microgravity, human health research, inspiring younglings, new physics, and "growing the low-earth economy".

Then broader there's a yearly one called Spinoff that points to the technology transfers, but that's not just from human flight, but from all NASA-funded work.

See last few years' edition: https://spinoff.nasa.gov/spinoff/archives

Comment · 1 year ago
I really want to love uv: It's a hair away from being perfect, they just have to find a solution to the "poetry version" (bump) problem = https://github.com/astral-sh/uv/issues/6298 (Work in progress, last I heard!).

Once we have a way to get package version bumps, I can finally leave poetry for the speed of uv!

Of particular interest to me, uv has "workspaces", perfect for monorepo-like sub-packages: useful for plugin-based workflows where you may want to keep a few independent plugins in one repo.

Comment · 1 year ago
Yeah I'm confused why none of the solutions presented deploy the same TF across the environments: Surely if you have dev vs prod, 90% of dev infra is also needed in prod?

Then sure sprinkle a few per-env-toggles `count: 1 if env == dev else 0` (or whatever the latest nicest way to do that is today), but it feels weird to have to set up an artificial TF module around our entire codebase to be able to share the bulk of the code?

Comment · 1 year ago
Comment · 2 years ago
Note that the specific naming of hurl.dev is not random: hurl is a wrapper for curl, where the requests are stored in a plaintext file.

So hurl.dev didn't roll dice and got hurl, but consciously got a close sounding word.

In that sense, that makes one claim over the other a little more valid, in my mind, though you're right that clashes will have to occur.

I did get confused extra hard by the url = hurl.wtf, when hurl.dev is so close yet about different topic.

Comment · 2 years ago
Comment · 2 years ago
Comment · 2 years ago
Comment · 2 years ago
NNCP, from http://www.nncpgo.org/

It's a protocol/tool for async file transfer, built for disconnected/intermittent connectivity amongst known parties (trusted friends as p2p), allowing even for sneakernet-based file transfer.

It's started as a modern take on usenet, but it boggles my mind how cool it is:

Want to send a TV Series to your friend? send it via nncp, and it will make it through either via line-based file transfer (when connection allows, pull or push, cronjob, etc), or even via sneakernet if there is "someone going that way".

Comms priority system lets you hi-prio message-checking via expensive network link vs bulk file transfer using trunk lines later.

It even can be configured to run arbitrary commands on message receive, to allow indexing/processing of files (like a ZFS-receive hook, mail/matrix ingestion...)

See all the usecases: http://www.nncpgo.org/Use-cases.html

As with many of these cool techs, I just wish I had a good reason to use it =D

Comment · 3 years ago
Comment · 3 years ago
Rome ... Virginia, USA.
Comment · 3 years ago
I'll note that France has a slight variant on that, where it's assumed that any identifiable marker of the ballot could reveal a voter's identity, bad in case of blackmail like "vote for X, and show it by having a stripe at at the top, or I [do bad things to family], I'll be checking the ballots").

To avoid this, no markers, but all possible votes are pieces of paper with printed text, grab N>2, go in the booth, put in one in an envelope.

This way your vote and any other vote look identical, and vote is voided in case of any identifying mark (even weirdly bent paper etc). No stamp needed, just number of votes/envelopes.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton