I set up a very straightforward Godot dev environment yesterday using toolbox which is built on top of rootless Podman.

• Create a new fedora toolbox
• Enter toolbox
• Install DotNet dependencies, git, etc with dnf
• Install Godot binary from release page
• Turns out there were other dependencies I needed
• Godot wanted a few Wayland libs on the container, so I installed Weston (maybe overkill)
• Godot wanted libxrandr so I added that too
• Godot just works ™

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’s a JTAG port in the base of the cortex for pushing firmware updates. Problem is, we lost the signing keys back in the neolithic. Thag got crushed by a mammoth before we had a chance to invent written language and write documentation.

Sometimes the freeze might be in the display manager. Eg xorg or your wayland compositor has crashed.

In that case, you can use keyboard controls to change tty and fall back to a text interface. I think it’s ctrl + alt + Fn$number, where $number will correspond to the tty you want. Most graphical sessions launch on tty2, so you would use crtl + alt + F1 to switch to tty1.

From there you can log in and use terminal commands to launch a new gui session, or to try and debug what went wrong. Generally, I’ve only had freezing issues on Linux when my GPU is dying. There was also a period where my work computer didn’t have enough swap space. It would freeze whenever I tried to compile code during a video call.

I used to browse certain subreddits for negativity bait. Eventually I decided that I didn’t want to immerse myself in a negative mindset so often.

The trick for me was to recognize those moments when I was on auto-pilot and navigating to those spaces because I was bored and it was a reflex. I would remind myself that I know it’s bad for me, and then force myself to do literally anything else. Go to some other website. Vacuum the floor. Put on some music and go for a walk. Eventually I lost that reflexive instinct, and now I have no desire to go back to those places.

I’m not going to pretend that what worked for me will work for anyone else, nor will I say that I’m now a better person for avoiding those spaces. I’ve probably replaced that habit with an equally pointless one, it’s just nice to not always view things from the context of tearing others down.

Eh, maybe. Back during feudalism, emancipation of serfs was also considered theft from the nobles who owned the land (and thus the serfs who worked it).

Sometimes governments implemented programs to reimburse the nobles for losing “their” serfs, and sometimes not. Now that we’re a couple centuries removed from that drama, we generally accept that the destruction of feudalism was a good thing, regardless of whether it was theft.

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.

Programmable condoms which make the user look like a bad dragon dildo.

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 /

Me getting my identity verified by Nigel the porno photographer because he’s an upstanding gentleman

“Yeah, I’d know that asshole anywhere”

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.

Also, what is “Harry” short for?

Harold?

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.