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.

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.

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

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

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.

Maybe they’re not mammal nipples, but happen to look like it.

To be pedantic, Ford’s threat is to “rearrange [the computer’s] memory banks with an axe”

The countdown is until he starts doing it.

A much better idea than when I tried to organize my restaurant with hashtables.

It was too much for the waitstaff, who had to reindex the floor plan every time they added or removed a plate.

On the plus side, delivering the right food was always O(1).

Surely this could be good, right?

If celebrities need to be accessible to their biggest fans, maybe it would induce them to leave the birdsite? And if this is as big a migration as the article suggests, it has the potential to snowball in network effects, giving other influential users one less reason to feel chained to a dumpster fire.

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.

Yes, OP I highly recommend a GL.iNet device. It’s pocket sized and always does the job.

It’s also great for shitty wifi that tries to limit how many devices you can connect. The router will appear as one MAC and then all your other devices can route traffic through it.

1. Study free materials available online.
2. Take free practice tests.
3. Look for license exams in your area, or take an online one. Exam fees in my experience have been ~$25 and go towards whichever club is proctoring.
4. Pay the $35 FCC licensing fee and get your callsign.

Theoretically, that’s all you need. It’s possible to use certain internet linked amateur transmitters for no cost as long as you have a valid callsign. However, I promise it’s a lot more fun with a real transceiver. You can buy a bare minimum, highly hackable handheld VHF/UHF transceiver for as little as $20.

Or you can slowly give your soul to the moneypit of HF equipment…

In the USA, property taxes are how most towns and cities get the majority of their funding. 200€/year would be crazy low.

In my medium cost of living town (USA), taxes come out to 4, sometimes 5 figures a year. Plus as the area becomes more desirable, property taxes (based on the sale price of a home) go up for recent buyers.

1. Wander around as a group
2. Look at all the different options
3. Split up
4. Get what you want
5. Meet back up
6. Share if you want

Repeat steps 3-6 as needed

As someone who has owned enterprise servers for self-hosting, I agree with the previous comment that you should avoid owning one if you can. They might be cheap, but your longterm ownership costs are going to be higher. That’s because as the server breaks down, you’ll be competing with other people for a dwindling supply of compatible parts. Unlike consumer PCs, server hardware is incredibly vendor locked. Hell, my last Proliant would keep the fans ramped at 100% because I installed a HDD that the BIOS didn’t like. This was after I spent weeks tracking down a disk that would at least be recognized, and the only drives I could find were already heavily used.

My latest server is built with consumer parts fit into a 2U rack case, and I sleep so much easier knowing I can replace any of the parts myself with brand new alternatives.

Plus as others have said, a 1U can be really loud. I don’t care about the sound of my gaming computer, but that poweredge was so obnoxious that despite being in the basement, I had to smother it with blankets just so the fans didn’t annoy me when I was watching TV upstairs. I still have a 1U Dell Poweredge, but I specifically sought out the generation that still let you hack the fan speeds in IPMI. From all my research, no such hack exists for the Proliant line.