At that time Lemmy didn’t support instance blocking at the user level. After the devs released that update it still took time for world to upgrade. Updates were coming out every couple of weeks and world likes to wait for about 6 weeks of stability on a release.

Lemmy World announced the block about 10 months ago: https://lemmy.world/post/2498330

The larger instances usually setup a community just for announcements. For world it’s !lemmyworld@lemmy.world

That depends. Are you looking at preserving the music without loss of information? Then you need to use a lossless format like flac. Formats like aac, mp3, opus can throw away information you’re less likely to hear to achieve better compression ratios. Flac can’t, so it needs more storage space to preserve the exact waveform.

You can use a lossy format if you want. On most consumer level equipment, you probably won’t notice a difference. However, if you start to notice artifacting in songs, you’ll need to go back to the originals to re-rip and encode.

Bad bot. Bad summary.

There’s talk on the Linux kernel mailing list. The same person made recent contributions there.

Andrew (and anyone else), please do not take this code right now.

Until the backdooring of upstream xz[1] is fully understood, we should not accept any code from Jia Tan, Lasse Collin, or any other folks associated with tukaani.org. It appears the domain, or at least credentials associated with Jia Tan, have been used to create an obfuscated ssh server backdoor via the xz upstream releases since at least 5.6.0. Without extensive analysis, we should not take any associated code. It may be worth doing some retrospective analysis of past contributions as well…

Yet another example of why we need privacy laws with real teeth.

Do you mean Computer Fraud and Abuse Act (CFAA)?

They’re using AI to generate summaries of chat logs.

I don’t believe they’ve had an IPO yet, but it wouldn’t surprise me if they start selling that data to hit profitability.

Forums do it better, can be indexed by a search engine, can be bookmarked, and can be archived using the wayback machine or a similar service. Important information shouldn’t be buried in chat logs. And discord’s forum feature was an idea they tacked on and is a poor substitute for the real thing.

Try editing a file in /etc as a regular user. It happens sometimes and you really want that warning that the write failed.

Anyway, :x is superior. It only writes if there are changes. So, your mtime doesn’t change unnecessarily.

Been there. Done that.

That sounds pretty niche. You may have to check AUR.