Not sure about fidesmo, but you can check if your device is apatch-eable, as it reportedly can fool safetynet.

Ah, okay, thanks for clarification

Yeah, but dudes there are kinda pissed off about semantics, IMO. Like, unless there’s a PR from tuxedo using the same v3, I don’t think it should concern them in the slightest… And instead of saying “keep in mind it’s not upstreamable” they go out of their way to mark tuxedo’s patches as proprietary 🤨

So, gpl3 is apparently not GPL and is somehow proprietary. Sure, makes perfect sense. Idk where they even find those geniuses.

Cosmic-comp is my second favorite after hyprland so far due to their tiling being quite well thought-out. The problem is, it’s part of a DE and is somewhat cumbersome to configure as a standalone compositor (can be fixed by patching libcosmic, tho), and also it’s quite bare-bones when it comes to features.

Then there’s pinnacle which looks promising, but I haven’t yet tried to daily-drive it.

Also, maybe qtile, which has a Wayland back-end.

So, the whole xz backdoor saga was merely a figment of my imagination?

We have minecrafts on linux. One useful-ish thing that I can think of (and currently use waidroid for) is myscript’s nebo, a handwritten note-taking app with quite good OCR. Since myscript don’t build their SDK for Linux, let alone apps, it’s somewhat the only way currently, I guess… Unless you can run wpf-s via wine somehow?

I guess it’s the case of аксиома Эскобара, tbh

Looks like here may be your issue: https://github.com/apognu/tuigreet/issues/140

Stable Tuigreet is 0.9.0, which is affected, so if using that, makes sense to pull it from unstable otherwise just update, I guess

Android translation layer is interesting. Well, at least I personally like this approach more than that of waydroid. Also would be nice to see the performance of that with binfmt compared to that of waydroid + libhoudini

Huh, nice to see my initial judgment was incorrect

I’m wondering if syncthing in gplay can show some kind of warning that the app is discontinued pointing to use the fork version on f-droid, or, if that’s prohibited by play’s EUFOA (end-user fuckover agreement), discussion on the forums mentioning the existence of said fork… [addit: So, kinda like what termux folks did, but less covertly]

I’m not sure you can classify this as a failure, as explicitly prohibiting interfacing with non-agpl stuff would greatly limit the amount of stuff you can license under it, perhaps up to the point of making it generally unusable. As for “not like that”… Well, yeah. But you can’t deny it’s misleading, right? Free software kinda implies you can modify it whatever you want, and if it’s a free ui relying on a source-available middleware… Turns out, not so much.

Although, a posdible solution would be require explicitly mentioning if you’re basically a front-end for something; but I’m not sure if it can be legally distinguished from the rest of use-cases.

I doubt it. What’ll probably happen is them moving more and more of the logic into the SDK (or adding the back-end of new features there), and leaving the original app to be more or less an agpl-licensed ui, while the actual logic becomes source-available. Soo, somewhat red-hat-esque vibes: no-no, we don’t violate no stupid licenses, we just completely go against their spirit.

I mean, I see a usecase for that, given you make a separate community for that, and not, say, spam c/technology with everything posted on XDA. So, kinda like RSS with comments. I personally follow hackaday both here and via RSS.

Alternatively, one can mirror someone who publishes rarely and only cool stuff. I remember mr.d0x being such a guy (now I don’t really follow security-related things much, so mb it’s changed, but I doubt it)

Thanks for sharing your concerns here. We have been progressing use of our SDK in more use cases for our clients. However, our goal is to make sure that the SDK is used in a way that maintains GPL compatibility.

• the SDK and the client are two separate programs
• code for each program is in separate repositories
• the fact that the two programs communicate using standard protocols does not mean they are one program for purposes of GPLv3

Being able to build the app as you are trying to do here is an issue we plan to resolve and is merely a bug.

I.e. “fuck you and your foss”

Wait, you can compile coreboot without google’s vboot support. If it’s the only problem, why drop motherboards?

Well, I guess nixos itself isn’t too overcomplicated, but fun begins when you start layering abstractions over abstractions 😁

deleted by creator

What exactly happens when you try to switch ttys? Literally nothing likely means you’re on tty2 already, and should try going to the 3rd one, and do on. If you’re getting a new installer session, they may’ve made it autostart on all ttys, but I don’t see the point in that