![](https://pawb.social/pictrs/image/e29fdaeb-39c1-4ed6-aedb-8bd3a05e8d1c.png)
![](https://pawb.social/pictrs/image/c539447a-2bba-40d7-bf1e-499739972903.png)
One place it shows up is "Send Secure Message" on a user's profile that has a Matrix handle filled out, right next to the normal "Send Message" button.
professional software developer, amateur coyote 🏳️🌈
One place it shows up is "Send Secure Message" on a user's profile that has a Matrix handle filled out, right next to the normal "Send Message" button.
Voksi (Empress): I am not Empress
Empress (Voksi): I am not Voksi
Realistically this is exactly what they would say if they're lying too, so the only real outcome is don't harass people without better evidence.
Very cool, thanks for posting. I was recently looking for something like this and I'll probably be using it shortly.
Looks like Mullvad is not really affected: https://mullvad.net/en/blog/2023/8/9/response-to-tunnelcrack-vulnerability-disclosure/
Transparent compression, snapshots, copy-on-write, deduplication, and data checksumming (and healing via read or scrub) are the main things you might notice as an end-user. BTRFS is mostly on par or slightly slower than other simpler filesystems for speed (can be faster on HDDs due to compression), so if you're using it you probably want to be taking advantage of the features it offers, not because it's going to be faster.
Copy on write is likely to introduce significant performance decreases in cases where large or medium size files have a couple bytes changed. It’s usually recommended to turn CoW off on those files
Do you happen to have a source or benchmark for this? My understanding of CoW is that the size of the file does not matter, as BTRFS works with blocks and not files. When a block is changed, it's written to a new location. All the old blocks that are not changed are not written again - this wouldn't even make sense in the context of how BTRFS deduplicates blocks anyway.
So:
10 kB base file
modify 1kB of the content
== 11kB total "used" space, and 1kB of new written blocks.
that old 1kB that is no longer part of the file will eventually be cleaned up if needed, but there's no reason to delete it early.
We're running out of places for techbros to put AI. They'll be putting AI in our pancakes next.
Couldn't find it originally, updated now: https://twitter.com/kawaiiberpunk/status/1352037036560101377
I may be biased because I already know how, but to me defeating DRM using the community tools is really trivial and I tend to use Steam copies of games because I like the Steamworks features that I can emulate with Goldberg. Even when given a choice between a GOG copy and Steam copy, I usually pick Steam. It's sort of a weird decision for me to make for permanent archival because I really hate DRM but the DRM versions have more features (achievements, auto-LAN, etc) and are negated with a local DLL so is it really DRM at that point?
I deny network on all my games unless I have a good reason to allow it - almost never have problems with them being mad about it as long as their DRM is emulated/defeated. I use bubblewrap's bwrap --unshare-net --dev-bind / /
as a command prefix in Lutris to do so.
Most game cracks work just fine through WINE. You just need to get the game extracted into the WINE prefix and have the crack applied, then point Lutris at it and it will work fine. If you find a specific crack isn't working, you can probably find another that does, or crack it yourself using simple tools that are always Linux-compatible. I wrote a guide on using these tools for reference.
There's no way $3k/month is an accurate number to run a single community. Lemmy.world (and mastodon.world etc) combined takes ~1k/month to run, and they're far larger and more active.
Also, anyone who goes back to Reddit doesn't belong with the 196 community. No bootlickers allowed.
Lapce is an alternative that you can try, though it's self-described as "pre-alpha".
I use them for an online copy of my backup. They're very cheap and I've got nothing bad to say about them. I use rclone to sync a local borgbackup repo to it, which gives me a couple copies for redundancy.