Do you mean 12600K, or do you really mean 2600K? These days, I wouldn’t use anything older than 9th gen, especially if you plan on doing any video transcoding with Jellyfin (transcoding means converting the video to a different format while streaming, usually to reduce bandwidth usage when watching videos away from home).

See if there’s any e-waste recyclers in your area. A lot of companies are throwing out systems that don’t officially run Windows 11, so you can sometimes find systems with 8th and 9th gen Intel Core processors for very cheap.

I think sometimes people forget that one of the main features of Git is that it’s decentralized. You don’t need Github; just push your repo to a different remote.

Everyone that clones the repo (usually) has a full copy of it, including all history, and theoretically you can clone the repo directly from their copy. Of course, that’s often not practical, which is how we ended up with these centralized services.

The main issue with losing a Github repo is the auxiliary non-Git-powered features of Github, like issue tracking.

They lose money from it (people that used to pay for an account to get private repos no longer need to) which is why Github didn’t do it when they were independent.

Plenty of open-source projects that I use are happy with them though. I see far fewer projects using Travis CI and AppVeyor these days for example.

Every new feature added to Github has made it more unpleasant to use

Free private repositories, Github Actions, and Github Packages are all pretty useful though. All of those were added under Microsoft’s ownership. Actions got a head start because it was built on top of Azure DevOps infra that Microsoft had already created.

I get the Pro version for free since I’ve worked on a few popular open-source projects. I’m using it in VS Code and it’s helped me write code for systems I’m unfamiliar with. I’ve used it to summarize the architecture of open-source projects so I understand how to contribute new features. The autocompletion can be pretty good too. I also use it to review my code.

We use Claude Code with the Opus 4.5 model at work, and it’s quite a bit better, but I don’t want to pay that much for an AI model for personal projects since I use it so infrequently.

hold hold

Maybe he just needs to rest his arm.

Are you including Github Copilot in that count? Technically that’s a Microsoft product. It’s probably the only Copilot that’s actually useful.

Unfortunately they no longer include elaborate Easter eggs like that, since they adopted a security policy around 20 years ago that forbids them. https://learn.microsoft.com/en-us/archive/blogs/larryosterman/why-no-easter-eggs

I don’t know many people that still call it “Microsoft Office”… They usually refer to the individual apps they use (Word, Excel) rather than the suite as a whole.

Some people just call it “Microsoft” (“please install Microsoft on my computer”), especially if they’re on MacOS where it’s the only Microsoft software they use.

Some people assume it’s part of Windows since they’ve only ever used computers that have had it preinstalled.

Huh, interesting. TIL videos can have non-square pixels.

Both of those documents agree with me? RedHat are just using the terms “client” and “server” to make it easier for people to understand, but they explicitly say that all hosts are “peers”.

Note that all hosts that participate in a WireGuard VPN are peers. This documentation uses the terms client to describe hosts that establish a connection and server to describe the host with the fixed hostname or IP address that the clients connect to and, optionally, route all traffic through this server.

–

Everything else is a client of that server because they can’t independently do much else in this configuration.

All you need to do is add an extra peer to the WireGuard config on any one of the “clients”, and it’s no longer just a client, and can connect directly to that peer without using the “server”.

There’s no such thing as a client or server with Wireguard. All systems with Wireguard installed are “nodes”. Wireguard is peer-to-peer, not client-server.

You can configure nftables rules to route through a particular node, but that doesn’t really make it a server. You could configure all nodes to allow routing traffic through them if you wanted to.

If you run Wireguard on every device, you can configure a mesh VPN, where every device can directly reach any other device, without needing to route through an intermediary node. This is essentially what Tailscale does.

I know of at least one big tech company that uses a self-hosted, self-contained Mattermost instance, hosted with a major cloud provider totally separate from all their infra, for communication in major outages when all their internal tools are down.

You’ll need to use a VPN that supports port forwarding. You could use a cheap VPS instead.

Where I live in California, electricity can be over US$0.60/kWh during peak summer time. Thankfully I have solar panels that offset most of the cost. I’m from Australia which also has high electricity prices.

Depending on the electricity price where you live, a VPS with 8GB RAM might be cheaper than running the laptop. Just something to keep in mind. GreenCloudVPS have some for $45 annually: https://greencloudvps.com/billing/store/budget-kvm-sale (I’m not affiliated with them)

Should I run the server over a VPN

Do you mean for you to access it remotely, or do you mean to expose it publicly via the VPN (so that you can have publicly-exposed services while hiding your home IP)?

For remote access, I’d recommend Tailscale. It mostly “just works”.

Thanks - I forgot about that.

The hostname will be encrypted eventually (ESNI) but you’re right that the IP address is visible.

Destination IP is starting to mean less and less these days, given there’s a large amount of sites that use shared IPs rather than dedicated ones (for example, if they use Cloudflare, Vercel, Netlify, AWS CloudFront, etc.)

1. It encrypts your internet traffic in transit

Note that most sites use TLS these days, so your data is already encrypted in transit.