zrail

Curious how long you've been sitting on the IP block. I've been nosing around getting an ASN to mess around with the lower level internet bones but a /24 is just way too expensive these days. Even justifying an ASN is hard, since the minimum cost is $275/year through ARIN.

My security update system is straightforward but it took quite a lot of thought to get here.

My self hosted things all run as docker containers inside Alpine VMs running on top of Proxmox. Services are defined with Docker Compose. One of those things is a Forgejo git server along with a runner in a separate VM. I have a single command that will deploy everything along with a Forgejo action that invokes that command on a push to main.

I then have Renovate running periodically set to auto-merge patch-level updates and tag updates.

Thus, Renovate keeps me up to date and git keeps everyone honest.

I like to refer to it as the cooties ownership model. I.e. once you touch it you have cooties.

Chicken and rice is anything but bland. I haven't had Hainanese style but the Thai style khao man gai that Nong's serves in Portland is a flavor that I still remember more than a decade later.

Yep. I treat work computers as hostile entities. They are always on an isolated guest SSID and VLAN and I never use them for personal tasks.

When my kids start bringing school-owned hardware home that's getting the same treatment.

On consumer chips the more memory modules you have the slower they all run. I.e. if you have a single module of DDR5 it might run at 5600MHz but if you have four of them they all get throttled to 3800MHz.

Tailscale has what they call Peer Relays now to help solve this problem:

https://tailscale.com/blog/peer-relays-beta

Nobody who has used Helm in anger will debate this with you.

> Got a link to what you meant? This is pretty hard to search for.

It's part of plan9:

https://en.wikipedia.org/wiki/Acme_(text_editor)

Another pertinent example: (in the US) corporate officers are personally liable unpaid wages and can serve time for willfully neglecting to pay their workers.

Unfortunately not. The RP1 controls the stuff on the 40 pin connector and the firmware is locked down. That said, you do have access to the PIO block, which is a programmable state machine that can talk to (I think?) any GPIO on the connector. Pretty fun stuff, good for real time or things with really tight timing requirements.

https://www.raspberrypi.com/news/piolib-a-userspace-library-...

Heck, the Raspberry Pi 5 does this. GPIO is handled by an MCU that is effectively a Raspberry Pi Pico.

Nice summary. I've been using Ruby both professionally and not for going on 20 years and I just today learned about singleton_class when attempting to build something like Rails' view helpers from first principles.

It's effectively spelled out in the article. The wealth of the last century has been fueled in large part by fossil fuels and it takes an embarrassingly small fraction of that wealth to convince the populace that the competition (I.e. renewables) is a status symbol.

That's a really interesting setup, thanks for the links! I'm pretty deep into Home Assistant but that plugin looks amazing.

I have a Unifi Protect system and am generally pretty happy with it. The biggest problem I have is similar in spirit to the Ring problem: remote access is required to get push alerts from the mobile app.

Unifi had an issue at the end of 2023 where users could access consoles they didn't own through remote access: https://www.theregister.com/2023/12/15/ubiquiti_camera_priva...

If I (or more specifically my spouse) could work the mobile app without SSO I'd be thoroughly satisfied. As it stands I have some regrets.

Sort of.

Go packages have the source baked into the package name. It would be like needing to say `require "github.com/sparklemotion/nokogiri"` rather than what we do today, `require "nokogiri"` and then if you want to change the source wrapping `gem "nokogiri"` in an alternate `source` block.

Go, for some values of "distributed". The vast majority of go packages are hosted on GitHub, but nothing stops anyone from hosting elsewhere and Go has explicit support for indirection such that anyone can use a vanity domain that happens to point at GitHub or wherever.

The only reason someone would need access to the management account would be maintaining child accounts and IAM roles or reviewing logs, none of which should need root.

Retrofitting Go's dependency model into Ruby is not trivial. Go has used full URLs for dependencies from the jump, making a central package repository irrelevant. Ruby doesn't have that. At best you might have a source code URL in the gem source that you can access from a gem server, but that doesn't really anything. Someone still has to provide the index.

Resetting the root password requires proving access to the email address associated with the root account. It also leaves a massive papertrail.

The problem, as with every package manager, is transitive dependencies. It's all well and good to set up direct dependencies to only pull from git repositories, but bundler still needs a way to resolve those gems' dependencies.

You could pre-resolve every dependency in your chain to a git repository, even to a fork under your own control, but that will end up being a maintenance nightmare.

First, sorry for you and your friend. Mental decline is terrifying and I can only imagine how difficult it is to deal with like that.

Could you say more about what your friend did differently than you and what makes it so difficult? Are/were they self hosting but don't remember how it all works?

This sounds interesting. Could you say more? Do you run BGP on the hosts themselves over the Wireguard tunnels? Do you self-manage a Wireguard mesh?

With no insider knowledge whatsoever I can assure you that they do. Large enterprise shops always have these things cached because why take a hard deploy-time external dependency when you can spin up a rubygems (etc) cache backed entirely by your object storage of choice.

late edit: "does _not_ insure weapons of war"

ugh I meant "does _not_" that's what I get for posting while eating breakfast.

Ultimately the US taxpayers will eat the loss in either case. If the government tried to charge it back to Lockheed Martin they'd just raise the price on subsequent programs to compensate.

The government does insure weapons of war. Who would write the policy?

You joke but this is absolutely a thing: https://github.com/skeeto/emacs-web-server

I have run 2x 16GB in my 5070s with the stock bios.