

Nonce is used extensively in the context of cryptography to mean “used exactly one time”. Usually this refers to a random number that a server shares with a client to establish secure communications.


Nonce is used extensively in the context of cryptography to mean “used exactly one time”. Usually this refers to a random number that a server shares with a client to establish secure communications.


I set up a very straightforward Godot dev environment yesterday using toolbox which is built on top of rootless Podman.
The nice thing about toolbox is that it uses my native host Wayland compositor. So whatever I have running in the toolbox can be interacted normally through sway (my host WM).
You can either distribute a container image with your given toolbox configured, or just document the setup steps.


You can host docker volumes over NFS, but the actual container images need to exist on a filesystem that supports overlay (which NFS does not) unless you want things to be slow as shit. And I really do mean miserably slow. A container image shared over NFS will take forever to spin up because it has to duplicate the entire container filesystem instead of using overlays, and then it’ll blow up your disk usage by copying all these files around instead of overlaying them. It’s truly unusable.


From that same discussion thread:
We plan on supporting any token/nft/coin for tipping, awards, curating, less captchas, etc. Each subplebbit owner should be able to create their own tokens or nfts to monetize their effort and incentivize their users to participate. Avatars will also be curated NFTs.
The protocol does not use blockchain for data, but the web service itself looks like it would use crypto and NFT to manage aspects of user identity, spam prevention, and monetary incentive.


There used to be a similar bug in the Roku jellyfin app.
If you can recreate the subtitle issue using test file 5 from this repo, it might be worth submitting a bug report. https://github.com/ietf-wg-cellar/matroska-test-files


No. 404 media is written by people. I’ve personally been impressed by their reporting over the last year.


I once had a directory in /tmp called etc which contained subdirectories for something I was migrating.
I thought that I was in /tmp when I ran rm -rf etc… I was actually in /
I think this is probably more a copy of various East Asian social media services than anything Reddit-like. Pretty sure TikTok and a bunch of Chinese video streaming services already do this. I think the whole Money -> Gifts -> Rubies -> Money chain is intended to dance around money laundering legislation. The same way that Pachinko machines aren’t technically considered gambling in Japan.


The problem isn’t just that people are making AI slop: It’s also a problem that Zuck has seen the engagement that this trash generates and realized that it’s good for Meta’s metrics. They’re never going to do anything to stop it if the alternative is that investors might realize that Facebook is a rotten log.


Look up the GPU on these charts to find out what codecs it will support: https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new
NVENC support will tell you what codecs your GPU can generate for client devices, and NVDEC support determines the codecs your GPU can read.
Then compare it with the list of codecs that your Intel can handle natively.


If you want to move your containers to a different location, look into configuring docker’s data-root: https://stackoverflow.com/questions/24309526/how-to-change-the-docker-image-installation-directory
You copy /var/lib/docker to a new location and update /etc/docker/daemon.json
I will say: Moving data-root to an NFS mount isn’t going to work well. I’ve tried it, and docker containers rely on filesystem features to run their overlays. On an NFS, this feature isn’t present, so your services will duplicate the container’s entire filesystem. This will tank your performance and is basically unusable for anything but trivial examples. Docker data-root basically needs to be a “physical” disk.
I’ve had no issues using NFS shares mounted as docker volumes. It’s just the data-root where it’ll fail.


If you’re doing it from scratch, I’d recommend starting with a filesystem that has parity checks and filesystem scrubs built in: eg BTRFS or ZFS.
The benefit of something like BRTFS is that you can always add disks down the line and turn it into a RAID cluster with a couple commands.


Yep, the problem was that docker started before the NFS mount. Adding the dependency to my systemd docker unit did the trick!


isn’t it an annoyance having to connect to your home network all the time?
It’s less annoying than the gnawing fear that my network might be an easy target for attackers.


Proliant G9 is an EoL server that hasn’t been sold since 2018. Meanwhile, Debian bookworm released last year. I’d be surprised if the problem were that your installer gave you a kernel that’s too old.
What is the output of ip addr show?


It might also be worth ruling out low-level issues:
Actually, amateur TV broadcast was something that interested me. I had the opportunity to buy an SDR with wider bandwidth, but I wasn’t sure how much I’d get into it, so I kept things cheap.
Another thing I’m looking into is ADS-B flight tracking. My house is within range of a sports arena where there are all manner of overhead banners get flown. Might be fun to follow them around on a map.
If you post on !amateur_radio@sh.itjust.works, I’d read.
I bought a cheap RTL-SDR to help solve a CTF challenge at DEFCON. The 2m/70cm antenna on my roof is begging for a fun project that’s not just talking to other hams.


I worked on a product that was only allowed to return 200 OK, no matter what.
Apparently some early and wealthy customer was too lazy to check error codes in the response, so we had to return 200 or else their site broke. Then we’d get emails from other customers complaining that our response codes were wrong.
Calibre is an ebook library manager with a reader built-in. Koreader is purely reader software, and it works particularly well on touch and eink screens.