1 reason it’s wrong to me: https://nosystemd.org/

Under “Notable bugs and security issues” there is a big list of issues which were all (afaict) fixed many years ago.

There have been reasonable philosophical objections to systemd, some of which are still relevant, and as that site shows there are still many distros without it, but for the vast majority of desktop users who want something that JustWorks… using a mainstream distro with systemd is the way to go.

This blog post from pmOS covers some of the pain of trying to use KDE or GNOME without it.

Would be easier to know how old a kernel release is without looking it up.

I concur, but it would be much easier to make the major version the current year (as many projects do, and Linux should imo) rather than the whole project’s age at the time of a release.

Linux is only 34 years old, btw.

no transcoding quality loss

is jellyfin actually transcoding when people don’t want it to?!

otherwise, “no transcoding” doesn’t sound like a feature. transcoding is very useful when you actually need it, eg watching something remotely which is stored at a higher bitrate than your network connection can stream. one way to do it with mpv is ffmpegfs, btw.

(fellow mpv user here; i’ve only used other people’s jellyfin instances… but i’d be very surprised if they’re always unnecessarily transcoding everything they watch.)

nope.

I have to ask: what’s with all the obsession with immutable distro?

I guess the promise of having updates JustWork™? I don’t currently use one but I see the appeal.

However FWIW, unlike its namesake ChromeOS, the “Nixbook OS” this post is about is not actually an immutable distro: the instructions are to install NixOS normally and then clone the nixbook repo into /etc/nixbook and run its install.sh. Among other things it installs an update service which runs git pull on that repo as well as running nixos-rebuild boot --upgrade and flatpak update --noninteractive --assumeyes etc.

Cheers to this guy for what he’s doing, but the name is a little confusing. This approach works but it is not nearly as robust as the immutable distro paradigm implied by the name.

i haven’t used it myself but https://jmp.chat/ looks good if you’re OK with a US or Canadian number.

there is a lemmy community about it here: !sopranica@lemmy.ml.

cc @singpolyma@lemmy.ml

Bespoke is a synthesizer first but “like a DAW in some ways, but with less of a focus on a global timeline. Instead, it has a design more optimized for jamming and exploration.” (youtube trailer, wiki, wikipedia)

“But you can’t copy with Ctrl+C, it’s…” - You can. When something is selected It copies selection to clipboard, otherwise it sends SIGINT.

What terminal emulator are you using where ctrl-c copies instead of sending SIGINT when text is selected? In every one I’ve ever used, ctrl-c still sends SIGINT even with text selected (and one must must use ctrl-shift-C/ctrl-shift-V to copy/paste).

I don’t have any suggestion for getting the behavior you’re asking for, but besides the normal ctrl-(shift)-C/V clipboard FYI you also have two other types of clipboard-like things: one which works anywhere (not only in the terminal) and is actually always automatically copying anything you select and lets you paste from it with middle click (this originated with X Windows but i think most Wayland compositors have also implemented it by now), and another which is found in GNU Readline (used by bash and numerous other REPLs) called the “kill buffer” which can be pasted (or “yanked”) from and cut (or “killed”) to using Emacs keyboard shortcuts (which also include various cursor movement controls).

Notes:

• the kill buffer is local to a given readline context, it’s not shared across different shell windows.
• the list of emacs keybindings in that wikipedia article i linked is currently confusingly referring to the kill buffer as “the clipboard”
• you can drastically reconfigure your readline keybindings and other behavior by editing your .inputrc file, but you cannot achieve what you were originally asking for because there is no concept of text selection in readline.

HTH!

I suppose it runs on an Arm-Processor

It would be odd if a device labeled “Wintel Pro” had an arm CPU.

Wintel means Windows on Intel, or more broadly Windows on any x86 or x86_64 processor.

the info line contains the answer:

Info: applications using this runtime: io.github.Hexchat

You need to remove Hexchat if you want to remove the end-of-life runtimes it requires.

I regret to inform you that the maintainer wrote in February 2024: This will be the last release I make of HexChat. The project has largely been unmaintained for years now and nobody else stepped up to do that work.

My computer uses both system and user remotes.

Because my .var directory is almost full, […]

If you’re low on disk space you probably want to have everything installed as either user or system, to avoid having some runtimes installed in both.

it’s “open core”.

slop 👎

Gitea has gone open core; it is still free software but its development is controlled by a for-profit company which is developing non-free features. So, Forgejo is the community-run fork of it which people outside the Gitea company are contributing to instead now. You can read more about their divergence here.

Python does have a year option that they are not using.

No, it doesn’t:

Help on class timedelta in module datetime:

class timedelta(builtins.object)
 |  Difference between two datetime values.
 |
 |  timedelta(days=0, seconds=0, microseconds=0, milliseconds=0, minutes=0, hours=0, weeks=0)
 |
 |  All arguments are optional and default to 0.
 |  Arguments may be integers or floats, and may be positive or negative.

Authorities don’t need to ask Signal for metadata; Signal promises they don’t log any themselves and that is probably true.

But, they outsource their server operation to Jeff Bezos, and then they do some absurd security theater to pretend that cryptography makes it so that the server (Amazon) couldn’t possibly log metadata - which is obviously false.

in the computing context, “lock-in” is shorthand for vendor lock-in.

How exactly do they hope to lock devs in github??? That’s absurd, there’s no way they can achieve that. I can always take my projects elsewhere and there’s nothing they can do to stop me.

I can’t tell if you’re joking? If not, what do you think “lock-in” actually means?

It doesn’t mean that it is impossible to leave, it means that there is substantial switching cost. And, that is certainly the case for github-hosted projects: all active contributors need to make a new account somewhere else, issues and discussions need to be migrated, CI workflows typically need to be rewritten, and good luck finding something that gives as much free compute for CI as github does. Yes, it’s easy to mirror a git repo onto another service, but github is much much more than just git repo hosting and each of their features have their own switching cost.

Also, OP actually said “lock devs in” rather than “lock projects in” - I actually am forced to have a github account if i want to contribute to projects which refuse to move their issues off of it 😢 … and the difficulty in creating new accounts anonymously these days prevents me from contributing to several things (lemmy, for instance) which i otherwise would.

if they do something, it’s not in your interest

this is often true, but sometimes (like in this case) they are actually doing things that are in (almost) everyone’s interest: making browsers more secure 🙄

(see my other comment in this thread for details)

deleted by creator