I take my shitposts very seriously.
It’s mostly a joke, although people from regions with lacking or misleading sex ed might not be aware of its importance. Or existence.
It’s also possible that the issue is with the technique. Proper stimulation might be difficult to achieve during intercourse if one or both participants are inexperienced or selfish.
English is a horrible language full of ambiguity. F/LOSS is libre, but not necessarily gratis.
Right at this moment, I’m rebuilding my homelab after a double HDD failure earlier this year.
The previous build had a RAID 5 array of three 1TB Seagate Barracudas that I picked out of the scrap pile at work. I knew what I was getting into and only kept replaceable files on it. When one of the drives started doing the death rattle, I decided to yank some harder-to-acquire files to my 3TB desktop HDD before trying to resilver the entire array. Guess which device was the next to fail. I could mount and read it, but every operation took 2-5 minutes. SMART showed a reallocation count in the thousands. That drive contained some important files that I couldn’t replace, which were backed up to the (now dead) server. Fortunately ddrescue managed to recover damn near everything and I only lost 80 kilobytes out of the entire disk. That was a very expensive lesson that I’ve learned very cheaply.
The new setup has a RAIDz1 pool of 3x 4TB Ironwolf disks (constrained by the available SATA sockets on the motherboard), plus a new SSD for the OS and 16GB RAM (upgraded from literally the first SSD I ever bought and 10GB mis-matched DDR3).
Mounting it was a bit of a dilemma. The previous array was simply mounted to the filesystem from fstab and bind-mounted to the containers. I definitely wanted the storage to be managed from Proxmox’s web UI and to be able to create VDs and LXC volumes on it. Some community members helped me choose ZFS over LVM-on-RAID5. Setting up the correct permissions wasn’t as much of a headache as last time. I’ve just managed to get a Samba+NFS+HTTP file server and Jellyfin running and talking to each other. Forgejo and Nextcloud will be next.
Then don’t bring that shit to other communities. I don’t care what happened in other places; from my perspective, from what I’ve seen, you’re the one creating conflict.
At any rate, this is a meme community: sharing and remixing other people’s things for fake internet points is the cornerstone of internet meme culture. If you think this is immoral, you should contact the artist rather than intervene on their behalf.
Why is it so fucking hard to just report, block, and move on?
ZFS uses the RAM intensively for caching operations. Way more than traditional filesystems. The recommended cache size is 2 GB plus 1 GB per terabyte of capacity. For my server, that would be three quarters of the RAM dedicated entirely to the filesystem.
Read my comment again, it has the answer. Most VPN services do not provide end-to-end tunnelling. If the exit node is located outside Russia, then what enters the Russian internet will be simple HTTPS traffic.
Been running it from Russia where stock WireGuard stopped working mid-2025.
Sounds like the issue is ISPs within Russia blocking outgoing Wireguard traffic from customers.
If the traffic exits the tunnel without hitting a Russian ISP (e.g. a Mullvad exit node in Sweden that routes the unencrypted traffic to the destination), you won’t be affected. If the exit node is behind a Russian ISP, it might get filtered by DPI depending on which direction is subject to the filter.
In one word: no. In more words: some addressing methods can lead to privacy and security issues, but those aren’t widely used anymore.
IPv6 addresses can be assigned to interfaces by several systems. One of those is SLAAC, or stateless address auto-configuration (comparable to APIPA and the 169.254.0.0/16 address space for IPv4). One method by which it generates globally unique routable addresses is by inserting the interface’s MAC address into the IPv6 address. Since IPv6 generally doesn’t use network address translation (and thus no masquerading), this would advertise your computer’s MAC address to the whole internet. More recently, SLAAC uses pseudorandom temporary (or “privacy”) addresses for interfaces, together with a unique network prefix assigned to the customer (analogous to the single public IPv4 address).
It’s also possible to assign IPv6 addresses statically or by using DHCPv6.
It’s better to delay it and release an immediately usable product than to break the desktop when an unexpected bug is encountered and make the computer unusable. I’ve never transitioned a desktop environment and framework to an entirely different display system, but I don’t imagine it’s as simple as flipping a switch.
Mint is not a bleeding edge distro. Reliability should come first, always.
It’s the objectively correct choice, but it might draw the ire of Fedora stans.
Try this thread: https://community.home-assistant.io/t/kiosk-mode-for-raspberry-pi-with-touch-display/821196
We use PiSignage at work for the overhead displays. It’s basically Debian stable with the Labwc compositor and a single Chromium kiosk mode window that opens automatically to a local web server.
I take ONE DAY away from this gods-forsaken website…
It’s problematic, but possible: https://jamesguthrie.ch/blog/multi-tailnet-unlocking-access-to-multiple-tailscale-networks/
If the other person has a Tailscale account, it sounds like the most expedient method is to simply invite them to the tailnet as a non-admin user with strict access control.
You could share a node with an outside user, but I don’t know how much the quarantine would affect its functionality. You could also use Funnel to expose the node to the internet (essentially like a reverse proxy), but there are obvious vital security considerations with that approach.
trash-cli is your friend.
No leaving before you git push, you’d better start working on those merge conflicts!
The treekie in me wants BookData.
(edit) This made me remember The Measure Of A Man and now I’m fucking depressed. They had such high hopes for the future.
https://tailscale.com/docs/how-to/set-up-https-certificates#machine-names-in-the-public-ledger
Your machine names and tailnet domain name will be added to a list that is publicly accessible when a new certificate is issued to one of your machines. CT is meant to verify, through one or multiple third parties, that a certificate was issued to a particular DNS name. This isn’t unique to Tailscale – all other CAs do this, and modern browsers will refuse to connect to websites if they can’t verify the certificate through at least one CT ledger.
This doesn’t expose your systems any more than getting a DNS entry and a certificate from other sources. If you don’t want your tailnet and machine names out in the public, you’ll have to use self-signed certs and self-hosted HTTPS-capable servers or proxies.