Actually, Celeste is originally a 8-bit game. It was developed on PICO-8, and then was ported to PC.

There are some code updates to refactor API call two months ago on Codeberg.

OpenWiFi implemented a WiFi 6 (802.11ax) network card with FPGA, and its driver. Currently only available for subscription, but will be open source in future.

I think that most of usefulness of swap has passed now that we have systems with noodles of ram.

Please read this article authored by maintainer of Linux kernel memory management subsystem and cgroup subsystem, Chris Down.

https://chrisdown.name/2018/01/02/in-defence-of-swap.html

And there is another article with some additional informations about swap authored by @farseerfc@sn.angry.im who tranlated the article above to Chinese.

https://farseerfc.me/followup-about-swap.html (only Chinese version available)

No. It's not random. SLAAC uses EUI-64 by default, it generate fixed /64 suffix from MAC. And with suffix match of nftables you can still do device specific income firewall rules. For random privacy address, it's only used for outcome so just block all other income of IPv6 addresses except EUI-64 is enough.

ESPHome has supported Thread since 2025.6.0b1. But Matter support still need more time.

https://github.com/esphome/esphome/releases/tag/2025.6.0b1

https://github.com/esphome/feature-requests/issues/1430

I don't want each client to have a globally unique address as that just allows insane tracking.

Just for this issue, SLAAC has a privacy extension to generate temporary random IPv6 address for outcome traffic. It's untrackable as well, but in different way to NAT (one device has many addresses instead of many devices have one address).

For example, something like epub is going to be hard because the format is really just a zip file with a specific internal file structure. So, it's not really the .epub file you want to grep, but one of the files within that zip file you want to grep through.

ePub is a zip file contains a batch of HTML file for contents and some XML files for metadata. So you can extract it and do grep as you do for HTML files.

I suppose displayport over thunderbolt plus embedded USB hubs in computer monitors gets close, but the display settings controllers usually require proprietary drivers and are vendor specific.

DisplayPort have DDC to control display settings. But I don't know how much settings was standardized and implemented by vendor. But at least, the backlight was implement by most vendors, many users use it.

It's difficult to have. The members of HDMI Forum are almost the TV manufacturers and the members of VESA (the maintainer of DisplayPort) are PC and GPU munafacturers. So TV almost uses HDMI and monitor almost uses DisplayPort.

The green PCB on left-bottom corner breaks the consistence of design...