OneCardboardBox

joined 1 year ago
[–] [email protected] 19 points 2 days ago

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.

[–] [email protected] 8 points 3 days ago* (last edited 3 days ago)

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.

[–] [email protected] 6 points 1 week ago* (last edited 1 week ago) (1 children)

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.

[–] [email protected] 5 points 1 week ago* (last edited 1 week ago) (1 children)

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.

[–] [email protected] 2 points 1 week ago (1 children)

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.

[–] [email protected] 2 points 2 weeks ago (1 children)

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

[–] [email protected] 15 points 2 weeks ago

The unfinished basement is the only interior photo with warm, inviting colors

[–] [email protected] 21 points 2 weeks ago

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.

 

I generally let my server do its thing, but I run into an issue consistently when I install system updates and then reboot: Some docker containers come online, while others need to be started manually. All containers were running before the system shut down.

  • My containers are managed with docker compose.
  • Their compose files have restart: always
  • It's not always the same containers that fail to come online
  • Some of them depend on an NFS mount point being ready on the host, but not all

Host is running Ubuntu Noble

Most of these containers were migrated from my previous server, and this issue never manifested.

I wonder if anyone has ideas for what to look for?

SOLVED

The issue was that docker was starting before my NFS mount point was ready, and the containers which depended on it were crashing.

Symptoms: journalctl -b0 -u docker showed the following log lines (-b0 means to limit logs to the most recent boot):

level=error msg="failed to start container" container=fe98f37d1bc3debb204a52eddd0c9448e8f0562aea533c5dc80d7abbbb969ea3 error="error while creating mount source path '/mnt/nas/REDACTED': mkdir /mnt/nas/REDACTED: operation not permitted"
...
level=warning msg="ShouldRestart failed, container will not be restarted" container=fe98f37d1bc3debb204a52eddd0c9448e8f0562aea533c5dc80d7abbbb969ea3 daemonShuttingDown=true error="restart canceled" execDuration=5m8.349967675s exitStatus="{0 2024-10-29 00:07:32.878574627 +0000 UTC}" hasBeenManuallyStopped=false restartCount=0

I had previously set my mount directory to be un-writable if the NFS were not ready, so this lined up with my expectations.

I couldn't remember how systemd names mount points, but the following command helped me find it: systemctl list-units -t mount | grep /mnt/nas

It gave me mnt-nas.mount as the name of the mount unit, so then I just added it to the After= and Requires= lines in my /etc/systemd/system/docker.service file:

[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
After=network-online.target docker.socket firewalld.service containerd.service time-set.target mnt-nas.mount
Wants=network-online.target containerd.service
Requires=docker.socket mnt-nas.mount
...
[–] [email protected] 28 points 4 weeks ago (1 children)

Maybe not for the plot (since it's never referenced or brought up ever again in the film) but I think it does work thematically:

This would be the one real miraculous event in Brian's life. If anything, you would expect that a man who fell from a tower, got picked up by a flaming ball, and returned safely to the ground would be hailed as a holy person by all witnesses.

Instead, nobody gives a fuck and in the next couple of scenes Brian becomes a holy figure through entirely unrelated and mundane means.

[–] [email protected] 4 points 4 weeks ago

Especially gardening tools.

Why does every fucking house in our neighborhood need its own lawnmower, weedwacker, and hedge trimmer? You only need it for an hour or two every month.

[–] [email protected] 6 points 1 month ago

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.

[–] [email protected] 8 points 1 month ago

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).

32
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

I have a .ch domain name, but I am not a resident, citizen, or business of Switzerland. For now, this is not a problem, but it's always possible that the rules change and I am ineligible to renew it down the line.

Is there such thing as a domain holding company? I'm thinking of someone in Switzerland who will be the registered owner while I have a legal contract defining my rights to use the domain?

This is all very hypothetical, and I'm happy to just wing it for now (it's mostly hobby/personal stuff). More just curious.

Just for fun, I looked into what it would take to register a business in Switzerland. I'd need a Swiss work permit to file for a sole proprietorship, and then I'd still have to pay ~60 CHF a month for a virtual business address.

view more: next ›