Skip Navigation

Posts
4
Comments
217
Joined
2 yr. ago

  • I use NixOS, but before that I was on openSuse. I have not thought about Bluetooth in at all in the last few years. Zero issues. I pair it in KDE's default bluetooth manager and then never really touched it since. Media keys all work, I control it over WiFi from my phone with kdeconnect no problem.

    I think a few months ago I had to turn my headphones off and on again when the quality got really low for a second. Reading this thread I guess I'm extremely lucky? I don't produce music or anything like that, so I might not be taking advantage I'd some its more exotic features.

    EDIT: I am using a basic USB Bluetooth dongle I bought at least 8 years ago for my desktop, and my laptop just uses the built in Bluetooth. If that's any consolation.

  • Is a soft fork, its purpose is to specifically stay in step with the upstream and working on new features the upstream isn't ready/doesn't want. As far as I know, they're the devs working on federation between selfhosted/any other instances.

  • There may be an ARM “takeover” of x86 at some point, but that day is very much not today unless you believe the PC market consists solely of Macs.

    I'd argue that overwhelming majority of people in the world use their phone as their primary computing device. ARM took over years ago.

  • People were uploading, and still are. Uploading a video for my friends, or a school project which needs no return open platforms work perfectly. Irrelevant to my point.

    Companies/Content Creators are on the platform because it pays them. If being on youtube did not pay them, they would go to a platform that did, eg twitch, tiktok.

  • Peertube doesn't give ad revenue sharing, so most content creators can't afford to make content for a platform with no return. If someone was uploading a video for their friends, or a school project, then sure, open platforms are perfect.

  • I know you know, as you already demonstrated your higher understanding. I just wanted to add a little bonus trick for anyone reading that doesn't know, and is learning from your examples.

  • That's wild to me, as I used sed all the time. Quickly and easy changes in configs? Bam sed. Don't even need to open vi when I can grep for what I need, then swap it with sed. Though I imagine more seasoned vi nerds would be able to do this faster.

    1. If you want to split a delimiter separated line and print some field, you need cut. Keep awk for more complicated tasks.

    Depends on the delimiter too! For anyone else reading this, sed accepts many kinds of delimiters. sed "s@thing@thing2@g" file.txt is valid. I use this sometimes when parsing/replacing text with lots of slashes (like directory lists) so I can avoid escaping a ton of stuff.

  • It is AN answer, but also not the only answer. Generating and moving power around is extremely complex and just seeing "Solar cheaper per Watt" and defining it as the best in all cases is silly. If you changed the axis to be size per MWh, then you would draw a totally different conclusion.

  • I appreciate that fun fact. The meme now makes more sense.

  • Feel like this joke would work better with TS | JS. Since that's the point of the former. I don't know how rust and ocaml are related?

  • After years of looking at this and working with x11 forwarding off and on. Honestly, just setup a VNC server and use the plethora of VNC clients for android. In my environment it performs better, and significantly easier to maintain. For my desktop I even find myself just using Steam Remoteplay if I need actual GPU performance over the internet.

    Virtualgl +VNC is excellent if you get it working.

  • When you use your “one password” you’re in effect giving your device permission to access the key storage in your TPM to fetch the private key to present it to the site.

    Very small correction as I understand, but your private key is never presented. The web service should never interact with the private key directly. Your device is signing some bit of data, then the server uses your public key to verify that it was signed by your private key. Its a small distinction, but is one of the principal uses of asymmetric encryption is that the public key can truly be public knowledge and given to anyone, while the private key is 100% always only accessed by you the user.

  • Perfect for your use case, not as much for others. People sharing tools, and all the different ways to solve this type of problem is great for everyone.

  • dust does more than what this script does, its a whole new tool. I find dust more human readable by default.

  • Very cool, reproducible builds are a massive amount of work. Good to see Nixos succeeding in this regard.

  • Security is all about layers. I'm not familiar with the exact process difference, but even without capabilities, its still running as the root user. I believe, I haven't investigated rootless docker that much.

    Podman, for example, can run entirely rootless and daemonless. So it offers one more layer that if something breaks out of its namespace, the user the service is running as can be something without useful permissions adding an extra layer to be able to cause harm.

    Nothing is perfect, but having one more layer approach can be useful, depending in what your threat model is.

  • Exactly. When I say I want a Linux phone all I get are Android options. What I want is a GNU/Linux phone that I can run full Linux distros on.

  • Thank you, unfortunate it is a video but at least there's something. I feel like my requirements of a DE are pretty low, so if it does work, and can open a window with AMD GPU acceleration then cool. I'm not fully aware of how much I actually use specific DE features, so this would be a good way to find out haha. I'd love to give it a shot on NixOS.

  • How do you run it? I admit I haven't dug too deep, but I haven't seen a release post. I've only seen Dev blog posts about the work being done.