Why would you call closed source client apps “open”?
while(true){💩};
Why would you call closed source client apps “open”?
Do note though that MeshCore is proprietary and has a licensing cost to unlock all of its features whereas Meshtastic is open source and free as in freedom.
Sometimes. Most times they buy them to gut them for their patents. Fitbit and Pebble both probably had some patents that Google really wanted.


This happens to me when I run games sometimes in 4k at max settings, with a 7900XTX. So far I have not found anything that prevents it, and I’m starting to suspect my power supply or my house’s wiring might be the issue. It almost seems like a voltage sag.


I dunno if you know this but SMS support got removed from Signal a few years ago


Its still better than any new chat protocol thats been made in the last decade. You’ll have to pry my family XMPP server out of my cold dead hands.


Great! Now I can listen to my PinePods on my PineBuds which I store in my PinePod that they came with.


Browser+jellyfin is easy then, but again you need to make sure you’re not using google play services. That shit calls home like crazy.


With how KDE treats Plasma and their whole dev philosophy of “If we don’t use/like something, than neither will you”
How does anyone confuse the KDE team for the Gnome foundation? How did you manage to pull that off?


Lol. Lmao even.
If it has google play services on it, at all, there is absolutely no privacy.
If you can manage to stick to an F-droid+Aurora+Obtainium setup (maybe with IzzyOndroid enabled in F-droid), you can probably pull off privacy, but in my experience there are at least three major streaming services ive encountered that refuse to run if Google Play Services aren’t running and you can’t pass the SafetyNet authenticity/security check thing (which raspberry pi is missing the firmware and hardware to be able to support.) Netflix being the biggest of them, I think Disney Plus has issues, and it’s been a while since I tried but either crunchyroll or hbo Max gave me a hard time.


That’s what I do. I have a bunch of .desktop files that just open Firefox in kiosk mode to whichever website I want, and a bunch of .PNG files to make them look like apps. I installed them system-wide.
I’m a pretty big KDE Stan but I decided to give Gnome a go since Plasma Bigscreen is virtually impossible to install for a normal user at the moment. Its not perfect but it gets the job done, and I love the basic parental controls it has. Still absolutely awful in terms of settings though.


An Airmouse is a gamechanger.
Its a TV-remote-style device that works like a Wii remote to control the mouse, usually has a keyboard on the backside, and connects to a USB 2.4ghz or Bluetooth receiver depending on the model you get.
I got a $20 Rii and a $10 other brand one to try out. Both are fine. I like the buttons on the Rii better but it has no backlight which sucks because I’m usually watching TV in bed at 9pm. The $10 one’s keyboard also responds faster so I can actually speed type.


I wish we would all start switching over to JSON for configuration files. It’s so much easier to parse, and you can’t screw it up with too many spaces or not enough.


I don’t like how the manjaro team does it specifically. A lot of the time i’ve seen packages break in Manjaro that work fine in Arch, then Manjaro users come into Arch forums acting like its an Arch problem when it isn’t.
Also, their driver install helper causes more problems than it solves, which was especially highlighted in the transition to open source official nvidia drivers. Couldn’t install the open source ones for the longest time, and couldn’t install the right ones from the repo with pacman directly. Caused some major issues for a friend I was helping.
Helped him switch to proper Arch and all the issues went away.
Valve on the other hand puts extreme effort into maintaining stability. I use it regularly and have zero issues, though I use it as-is out of the box.


Workflows are different, configuration files can be different, and package names (not just management) can be different.
Additionally, release cadence (how fast you get new stuff, even when considering fixed releases), stability, performance (how were the packages compiled), and custom patches that aren’t part of the original code (*shakes fist angrily at Manjaro*)


I don’t like flatpaks or snaps or anything like it either, but I think they help a lot in situations like the Steam Deck or PinePhone where you want the base to be able to move slowly and be stable, while letting the apps on top move quickly.
The problems with flatpaks and similar is that it allows and even encourages developers to stick with horrendously outdated libraries, and your system is only as safe as the container’s isolation defenses.
They also make it more difficult to go in and directly modify or tweak the program as the user.
And many developers are no longer offering bare-metal options.


Well, in the case of the liberux and the 9 pro, you get a lot more storage space built in (very fast storage), way more RAM, etc.
Its up to you whether that’s all worth it. To me it is, I max out sub-$400 phones very quickly. The pinephone feels very choppy to use too by comparison.


Wow, that’s quite the difference. What’s more shocking to me though is the fact that the rockchip somehow is built to handle a higher resolution than the tensor despite being weaker (8k@60fps vs 4k@60fps), and has AV1 support where the tensor doesn’t.


That’s a good callout. I’m not super familiar with it, do you know how it might bench against the Tensor G4?
Non-open source devs suck by virtue of being closed source, period. It doesn’t matter how good their project is, if it’s closed it goes in the trash.