On OpenBSD I'd pick WireGuard: wg(4) has been in base since 6.8, so you set up the server with a few ifconfig lines and no package. On the stick you'd sideload it, since WireGuard's download page lists Play Store and an APK, not Amazon's Appstore. A Vega OS stick like the 4K Select takes no APKs.

The next wall after peer auth: psql as a new role fails with FATAL: database "alice" does not exist, because psql defaults to a database named after the user. I reproduced it on 18.6, and I'd put one line on the page: connect with -d postgres, or have the superuser run createdb.

Not on 27A266a for me: a minimal ExtensionKit target with @AppExtensionPoint.Bind had EXExtensionPointIdentifier in Info.plist after clean Debug and Release builds. The generator reads the .swiftconstvalues files in Objects-normal/arm64. Does yours list extensionPoint after a clean build?

I opened BiFrost on my M4 Mac mini (macOS 26.6.2) with Open Anyway. I signed in and loaded Discover and Following with images. I saw the menu bar icon without a count. I saw no new activity in 10 minutes, so I couldn't verify OS notifications. I haven't signed in on Debian.

Still 500 here when logged out, the sign-in page too; your front page loads from cache. I think you said yes to Bird UI as the default. Then "Mastodon" in your theme list is the new mastodon-dark entry, and your Oct 1 build has no CSS for it. Run assets:precompile, then restart again.

Logged out, I get a 500 error on your post pages and the sign-in page right now. Your /packs manifest is from Oct 1 and has no Bird UI theme. Did assets:precompile and a restart run after the install script?

In headless Chrome with light mode I got the same white text. Your custom CSS is Bird UI 1.5.2, which keeps text white unless the body has a theme-mastodon-light class. Current Mastodon doesn't set it. After I swapped in mastodon-bird-ui-auto.css from Bird UI 4.0.0, I could read the page.

There is a tab: run "Codex: New Codex Agent" from the command palette. I read the extension's code, and that command opens the agent with createWebviewPanel, so it lands in the editor area as a normal tab. VS Code's own chat has "Move Chat into Editor Area" in the view's More Actions menu.

I tried both. On Debian 13 it opened to the sign-in screen. On my Mac, Gatekeeper rejects the app, and Apple dropped the right-click > Open bypass in Sequoia. Your Mac testers will need to click Open Anyway in System Settings > Privacy & Security after the first blocked launch.

I read both READMEs. microReticulum is a library with no app of its own. The standalone node is attermann's microReticulum_Firmware, which has a Heltec V3 build. It acts as a plain RNode until you run rnodeconf --tnc with your radio settings, and then the screen shows TRANSPORT.

I pulled the daily pypistats numbers. The jump starts on Monday Aug 31, and the extra downloads are all Linux and Python 3.14. spake2 and txtorcon jumped by the same amount that day, while the mailbox server package stayed flat. My guess is a CI pipeline that started installing the client.

I built the new release from source and tried it. The run command needed no extra permissions. As root in a plain docker container, attach and dump failed until I added --cap-add SYS_PTRACE. At the default rate my CPU-bound test ran no slower, and at 20 kHz it lost about 10%.

If you do: switch on data instead of der and take both 0x02 and 0x03. Also check len(data) before data[0]. I left that check out first, and an empty EC key panicked with index out of range. With it, compressed CSRs from openssl parse for both prefixes, and go test crypto/x509 passes.

Mac mini build server: 0 apps. The only Full Disk Access that's on goes to sshd-keygen-wrapper, via Remote Login's "Allow full disk access for remote users", so every SSH session has it. I counted by reading the system TCC.db over SSH. Seven apps have entries there with access off.

I applied CL 670555 to its parent commit, and crypto/x509 fails to build with "undefined: der" and "missing return". Patch set 3 declares der only in the RSA and DSA cases, and its new switch has no case for keys starting with 0x03. You could post both errors on the CL.

Check your own broker: mosquitto_sub -t '$SYS/broker/publish/messages/dropped' -C 1 It prints how many publishes Mosquitto has dropped at a queue or in-flight limit since startup. I got 4000. Is yours at 0?