The cartoon dogs give me a clear signal I am not going to bother reading this page.

You came to this article almost 24 hours after it dropped off the front page to leave this comment saying you aren't going to bother reading it.

Why?

I like your thinking. Deterministic replay with QEMU is supplemental to the larger goal of reproducible builds. The communities concerned with the topic of reproducible software not only expect cohesive human-readable code that runs deterministically to produce binary reproducible results, but their originally stated goals require it.

Deterministic replay with QEMU is a "power tool" in the larger picture of these efforts.

East Taiwan is best Taiwan. West Taiwan is getting out of control. Let's send more weapons to East Taiwan.

"I am morally superior because I have the correct beliefs, as validated by the artificial applause on The Daily Show"

Knockknock was one of my favorite things back in the day. I love Moxie's mindset. Nowadays I put Wireguard in front of everything.

Been wanting to use wireguard but seems like a lot of effort of managing keys and ip addrseses and routing rules etc. Do you have resources that might help me understanding the best setup?

WireGuard is extremely easy to setup. It's difficult to manage if you have hundreds of nodes or dynamic endpoints: that's what Tailscale and Netmaker helps with.

OpenBSD's wg documentation is straightforward. It maps onto wireguard-tools' configuration concepts if you need to use Linux.

1. https://man.openbsd.org/wg.4

2. https://man.openbsd.org/ifconfig.8#WIREGUARD

3. https://git.zx2c4.com/wireguard-tools/about/src/man/wg.8

With OpenBSD you will typically end up with a hostname.wgN config that looks like this:

  inet6 fd00:abcd:efgh:ijkl::1/48
  wgkey <base64-private-key>
  wgport 51820
  wgpeer <base64-peer-pubkey> \
    wgpsk <base64-secret> # optional \
    wgaip fd00:abcd:efgh:mnop::1/64 \
    wgendpoint x.x.y.y 51820
  up

When Wireguard first came out I wrote some scripts for myself. Later on I used SaltStack to configure Wireguard for customers with sets of laptops in the dozens or more.

https://Netbird.io is probably something you may be interested in.

Tailscale is wireguard underneath and does all that managing for you.

I am on a team that provides commercial support for our Linux based user endpoints. We do not deploy endpoints with WiFi cards that require closed-source firmware.

  https://www.thinkpenguin.com/gnu-linux/wireless-n-m2-ngff-card-v2-tpe-m2ncrd2

I'll gladly finance at 4x the cost (so like around $5,000) to purchase an alternative Pixel for a fully open source bootloader with physically compartmentalized chips with open interfaces and a less sleek device.

I don't give a shit about Ai slop.

Sounds a bit like Librem 5.

I wish it was comparable. The Librem 5 is years behind flagship smartphone hardware. I want to switch, but it would be difficult to give up the stability that comes with Android. That said, maybe the Librem has improved in the last year or so.

> The Librem 5 is years behind flagship smartphone hardware.

https://puri.sm/posts/the-danger-of-focusing-on-specs/

> but it would be difficult to give up the stability that comes with Android

This is true: Android had a decade of development with a huge team. However, depending on your usage patterns, it can be good enough today. It works as my daily driver. See also:

https://news.ycombinator.com/item?id=41356567

Thanks for the info. Their comments on hardware treadmills are reasonable. I'm not looking to chase the latest hardware, but I was still scared off by reviews claiming web video playback performance issues. I suppose I was hopping for the bumps to smooth out a bit.

I find it encouraging to hear that it's working for you. I'll probably take another look at making the switch when I have a moment. I'd much rather support an alternative platform if possible.