Good luck getting most wifi and bluetooth hardware working without these firmwares. :)
So your stance is “trust without verification”.
No. The reviewer is going to ask the submitter questions about the code and the submitter needs to be able to answer them in a way the reviewer is comfortable seeing it merged.
I don't know why you are annoyed by this.
You use an automatic tool. It's bound to fail or make a mistake once in a while.
The "uploader" likely knew this, so they had some fun. It's not like what you are doing is legal or anything. "Le me go complain on my blog about someone messing with how I do my illegal activites".
What do you mean?
It's tagged as Coded By Human and there are no obvious hints that this project ius AI slop?
I don't mind people using AI tools to code for them. As long as they understand the code when they submit it and can fix it, if there are errors/faults in it before or after it has been merged.
Thanks. Been so long since I've used vnc that I couldn't remember.
If you want a full complete remote desktop solution, you should probably look at VNC and portforwarding its port. I think it's 3001.
Or if you won't (or can't) mess with port forwards, you could setup something like RustDesk for the TeamViewer experience.
I'm curious. Since you are new to Linux, how did you stumble upon Lemmy and this community? :)
Checks date
Nope, it't not beginning of April...
How much compute does dot-files actually need...? /shrug
As I understand it, it's Microsofts attempt to only allow booting kernels signed by them or their partners. In theory this stops malicious attacks from changing the kernel and have it booted. But Secure Boot is just something you can turn off.
So it's just python scripts??
Maybe ask an AI to create a package for you to test. If it's working fine, edit the PKGBUILD to follow packaging guidelines and upload?
Also, it's made for flatpak. Why not just use that?