- 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.

It lets you define a systemd job with some custom syntax and run it as a systemd service, and even stretches to allow some form of kubernetes YAML to be run as local (single node, rootless) containers!

Real nice.

See previous presentation on HN: https://news.ycombinator.com/item?id=43456934

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

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

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.

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?

See https://jiby.tech/post/my-git-worfklow/

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.

I made an entire presentation about this[1], trying to sell it to work mates.

[1]: https://jiby.tech/presentation/makefiles/makefiles.html

See the europython video intro: [2], or as slides[3]

[1] https://smarie.github.io/python-pytest-cases/ [2]: https://www.youtube.com/watch?v=QTyfr2UNR98 [3]: https://ep2021.europython.eu/talks/649sqwq-powerful-tests-an...

Or framed differently: "What category of software would you describe Github as?"

For all of this, the answer the community came together to find is ... Code Forge.

One extra resource on it: ForgeFed[1], which describes itself as:

> ForgeFed is a federation protocol for software forges and code collaboration tools for the software development lifecycle and ecosystem. This includes repository hosting websites, issue trackers, code review applications, and more. ForgeFed provides a common substrate for people to create interoperable code collaboration websites and applications.

[1]: https://forgefed.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

[1]: https://newpipe.net/FAQ/tutorials/install-add-fdroid-repo/

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.

The repos can be fed as list on CLI, via file, or via a "source" type plugin (allows github search or custom API calls), the PR creation works via a "Forge" plugin.

Resulting PR list can be fetched to review status:

> Of 113 given PRs, 73 merged, 30 closed not merged, 5 ready to merge (no conflict), 5 with conflicts.

I've created hundreds of PRs with it via github app integration, see the plugins repo[2].

[1]: https://jiby.tech/mass-driver/usage.html [2]: https://github.com/OverkillGuy/mass-driver-plugins.html

Kind of like the sysadmins removing any scripting languages and compilers from servers to avoid giving rogue processes any leg up. It's legitimately making it harder for baddies to exploit a way in. ...Though it's never been easier to package your own interpreter (micropython or equivalent), so I don't expect it slows people down much.

In the mindset of MS: legit devs should package their own tooling, and baddies shouldn't get the freebies.

Here's a diagram from the Memacs repo:

   emails              -> memacs-maildir.py  \
   firefox history     -> memacs-firefox.py   |
   SMS                 -> memacs-sms.py       |
   RSS-feeds           -> memacs_rss.py       |
   bank statements     -> memacs-easybank.py  |>  Memacs
   postings            -> memacs-slrn.org     |
   git repository logs -> memacs_git.py       |
   svn repository logs -> memacs_svn.py      /
   |_________________|   |_________________|     |______|
   your personal data      Memacs modules        Org mode

See the whitepaper, called "What really happened on September 15th 2008? Getting The Most from Your Personal Information with Memacs"[2].

This project is now a little bit dead, but the concept of private data fusion was fantastic, and transformed my view of calendars.

Agree that calendars are a little underused in that way, and would love to see more work towards that private calendar data usage.

[1]: https://github.com/novoid/Memacs [2]: https://arxiv.org/abs/1304.1332

Granted I haven't used it, on toy project or in anger, but it sounds really neat.

I'm a software dev turned devops, and I try to write down opinions I haven't seen written anywhere before.

Lots of Unix shell, TDD/BDD, automation, project management, and most recently SDLC ramblings.

Sample articles:

- https://jiby.tech/post/literate-wordle/

- https://jiby.tech/post/my-git-worfklow/