Skip Navigation

Posts
8
Comments
69
Joined
9 mo. ago

If you're interested in (co-)moderating any of the communities created by me, you're welcome to message me.

I also have the account @[email protected]. Furthermore, I own the account @[email protected], which I hope to make a small bot out of in the future.

  • It's still workable for sure.

    Above all, memorize one thing: When you update, and then reboot, keep an eye on the computer during reboot, especially during the early stages. That's because every month or so, when the drivers have gotten updated, you will be presented with a (often blue) screen about MOK Enrolment, i.e. you need your UEFI that the new drivers are trustworthy. If you miss this screen, you'll boot into a black screen or so without anything telling you what the error is, and to fix it you'll have to enroll those keys manually -- this is not prohibitively difficult, but annoying. (That's if you have UEFI secure boot enabled. If you have it disabled, there is practically no pain at all, ever. You lose a bit of security though. Personally I have it disabled.)

  • I recall these times. As experience grows, one needs to do it less and less often :)

    Also, if your filesystem is Btrfs (which is usually a great choice), check out Snapper. With it, when an update goes wrong, you can often revert your system to a previous state.

    On Fedora, it doesn't come by default, so you'll have to install it. I don't use Fedora, but this guide looks like a decent introduction: https://dustymabe.com/2025/01/07/fedora-btrfs-snapper-the-fedora-41-edition/ Or for something shorter: https://www.andotech.net/installing-snapper-on-fedora-a-comprehensive-guide/

    For its usage, this tutorial from openSUSE should be quite transferrable: https://en.opensuse.org/openSUSE:Snapper_Tutorial

  • If you have an AMD graphics card (or use Intel graphics), one of the biggest pain points is already nonexistent. If on the other hand you have a NVidia card, getting that to run often comes with (recurrent) pains. What is your graphics card?

  • +1 for Wero! We have to get it adopted. If anyone's bank doesn't support it yet, and you need to switch banks for other reasons, best include Wero support among your criteria. ING is among those banks whose support for it is the best.

  • That's a really good idea, I will from now on inspect disused garments for parts that one can use for patches

  • Anyone know some good offers for nice (nerdy) patches? There are nice embroidered patches on Etsy, but at 7 USD per patch they're a bit expensive for everyday repairing (let alone extensive projects like a GNU/Linux-themed biker's vest).

  • It's good to have a Codeberg accout for sure, and to contribute there. One should note though that their services are only for projects under a free (libre) license. They don't really enforce that yet, I think, but it's sure good to know.

    I think gitea (or gitlab) don't have such policies (although I don't know this for sure).

  • While on my laptop I have to use some bluetoothctl (I think) with stupid pin-less setup and cannot use KDE’s own bluetooth applet. We’re both on OpenSUSE Tumbleweed.

    Does rofi-bluetooth help you a little bit with things?

  • I think the general term for this is "domain sniping" or "catching". From this, I also found this paid service, catches.io; can't tell if it or dropcatch is better. They both only charge you when they are successful in catching the domain for you, which is good.

    In general, I second the notion that one probably can't get around paying for a professional, paid service, since one is up against professionalized scoopers (godaddy and the like), who have put a lot of optimization (down to the placing of their servers) into trying to get an edge over legitimate buyers and competing scoopers.

  • Deleted

    Permanently Deleted

    Jump
  • Cool!

  • Deleted

    Permanently Deleted

    Jump
  • Thanks for updating your post with the solution that you found! Best also prepend something like "[Solved]" to the post title.

  • The only thing I disagree with is this:

    This continuing saga shows how important regulation and legislation are to protect consumers, whether it’s individuals like us, or companies that are being bullied into complying with some pretty odious demands.

    This makes it look like anti-repair lawsuits were something that can natuarlly occur, and that the solution were some form of government intervention. By and large, that's not true: It's the existing copyright laws which are the government intervention — what we are calling for is not a restriction of freedoms for the greater good (regulation), but a return of freedoms that were unjustly taken from us.

    (Just so no-one misunderstands me: I'm no opponent of regulations, and am wholly aware that, very often, they actually protect freedom in the greater scheme of things. My point is that terms like "regulation" and even "new legislation" do have a bad ring to many people in the Western hemisphere and beyond, and we needlessly cease discursive territory if we neglect the fact that we are victims of overreaching, oligarch-serving regulation, which we seek to abolish.)

  • If you don't yet have a USB adapter for using NVMe SSDs over USB-3 ports, I'd suggest to buy such a thing first, since they not just make for a simple yet (decently) fast storage expansion solution, but are very useful in all sorts of situations.

  • For an ongoing discusion on Lemmy and a more detailed article see here

  • ffmpeg is usually the tool of choice.

    An example for batch converting of all AVI videos in a folder:

    for i in *.avi; do ffmpeg -i "$i" "${i%.*}.mp4"; done

    Source & further reading here on StackOverflow. The comments to the answer provide examples of how to explicitly tweak the quality level. Inverting what this specific comment suggests, conversion from H264 to H265 could be done by something like this, assuming all your videos' names end on .mkv:

    for f in *.mkv; do ffmpeg -i "$f" -map 0 -movflags faststart -c:v libx265 -c:a copy -c:s copy "${f/x264/x265}"; done

    I wonder: if one wants to make things run in parallel, would that be as easy as adding " & " before the last semicolon here? I suspect this could work as long as there are only a few handful of files, but lead to troubles once there's more.

  • Deleted

    Permanently Deleted

    Jump
  • Like I said: it can be gamed to some degree, but what system can't?

  • Besides finding better ways to positively recognize bots, we also need to invent ways that make it quicker to realize "false alarm, this user is actually legit".

    For example, users should have an option to pin posts and comments to their profile, and I suggest to provide at least two different 'tabs' for this in the public profile: One tab just for the usual "posts and comments you would like the world to see", but another tab for "some recent, complex interactions between you and other (established) users that in your eyes prove quite well you're not a bot". The purpose is simply to save others, worried that you could be a bot, some time of going through your posts in search of signs for humanity. Yes, this can be gamed to some degree (what can't?). However, at a technical level, the feature is little more than a copy of the "pin" feature that would be very nice to have anyways, so we can get an appreciable improvement in our ability to tell users from bots for very little programming effort.