Ah, yes, just over five attempts for every human alive. I assume they took the reply addresses at face value and have forwarded 45 billion cease & desist letters to Microsoft’s Redmond office?
Inbred: chaorace’s family has been a bit too familiar. (Can be inherited)
Ah, yes, just over five attempts for every human alive. I assume they took the reply addresses at face value and have forwarded 45 billion cease & desist letters to Microsoft’s Redmond office?
Could have been MMANAA 😔
If you hate job boards then you need to find individual company “Careers” pages and go from there.
How you go about this varies a lot by skillset and industry, but I’ll just throw out a random example: lots of Linux jobs exist in the DevOps space (think Kubernetes, Ansible, Chef, NixOps). It just so happens that lots of medium-sized software companies need DevOps people, so you can pretty easily find companies looking for DevOps hires just by browsing Y Combinator’s Startup Directory
With that being said, I get the impression from the way your post is worded that you’re looking to break into a new career without having yet established a concrete plan. My advice would be to step back and consider specific options first. Almost all jobs like these require industry-specific certifications (e.g.: CompTIA, ITIL, AWS, Azure, Cisco, etc.). You need to look at your options, pick a certification, earn it, then go job hunting. Certifications are great for securing entry level jobs and the standards body issuing these will often provide an online directory of partner companies who are currently hiring.
You’ll understand when you’re older, son
Ugh… they got Plasma everywhere!
Try Satty? It’s inspired by flameshot, Wayland native, and written in Rust.
I am of two minds:
It’s a mess, but honestly so are a lot of critical FOSS projects (e.g.: OpenSSH, GNUPG, sudo). Curmudgeons gonna curmudgeon. There was a point of no return and that was years ago – now that Wayland’s finally becoming useable despite itself it’s probably time to come to terms with the fact that better alternatives would have arisen had anyone thought they could truly manage it.
No, I am not contradicting myself. Let me say it again with the ambiguity removed:
I’m sure you still believe this is a load of apologia and frankly you can think what you want, but you should probably know that I’d already read about the Cox story when it first broke and specifically chose my words with that knowledge in mind.
Read the document:
The growing ability to access microphone data on devices like smartphones and tablets enables our technology partner to aggregate and analyze voice data during pre-purchase conversations.
Key word is “technology partner”. They’re buying voice transcripts ripped from someone else’s spyware and selling the service of scraping it for keywords and maybe somehow tying that back to an individual by cross-referencing the hit against data from traditional above-board ad platforms.
Google isn’t buying transcripts, Facebook isn’t buying transcripts. It’s Cox Media buying shady recordings stolen from spyware-compromised devices and then trying to whitewash it into something sellable with their (unverifiable) cross-analytics middleware.
Hmm… what’s the purpose of loading amdgpu at all if you’re using an NVIDIA card? Optimus?
we still have people that do not believe that the phones are always listening when seemingly any website or app you use gives you advertisements about what you were just talking about in the other room with the phone locked.
Oh come on. Don’t bring this into conspiracy territory. Yes, eavesdropping does happen, but it’s not something an uncompromised Android phone will do when locked. Even when it does happen in the case of spyware, the people doing it aren’t selling your transcriptions to advertisers.
People should still opt out of as many of GAPS’s spyware-like features as possible, as you suggest, but not because it’s a special anti-listening-device warding spell.
Your best bet is probably figuring out why the graphical session isn’t working and then going from there. Since you’re on NixOS odds are all the logs you need are right there in journald.
Worst case scenario: you might need to pin your system nixpkgs to ~January 2021 until the issue sorts itself out. You can still install newer userland packages if you separately manage them as a flake (this is a common and well-supported pattern in home-manager
)
EDIT: found a discussion with good configuration.nix
examples for pinning the system nixpkgs. Once you find a workable pin you could also try inching it up to get a better idea of what broke (January 2021 is a good starting point because it’s the last month before 5.11 released, a newer pin is very likely possible)
I’d say that’s already becoming the case in a few places. Hyprland isn’t just “Wayland good”, it’s “You should use Wayland good”.
Yes, I know the devs behind it act like pissants. That’s bad and I’m sorry for liking their software. I use Emacs too and RMS was kind of an asshole. Hell, I use Lemmy even though one of the devs has slighted me on more than one occasion.
More importantly: did you know the “monopoly man” does not in fact wear a monocle? We live in trying times.
Wayland is Wayland. If you use a Wayland compositor, you’re getting a lot of security by virtue of design alone. Things like keyloggers and screenrecorders will not be able to intrude on your session barring vulnerability exploits. I’m not going to touch on the relative vulnerability risk of each environment since a) they’re all relatively new & b) I’ve never implemented Wayland myself
With that being said, here’s what’s not protected by Wayland regardless of the chosen compositor: microphones, webcams, keyrings, and files.
For microphones & webcams, any distro which rolls Pipewire in combination with Wayland will be sufficient to secure these. Pretty much all Wayland environments roll Pipewire so this is only important to consider if you’re running your own customized environment (be sure to disable any pre-existing PulseAudio daemon after setting up Pipewire to close this security hole)
For keyrings, these are handled by your environment’s polkit implementation. Much like Wayland, there are several implementations of polkit and they’re all just about equally secure barring any potential vulnerabilities… Just make sure that you’re using an encrypted database (usually on by default) and that you have it configured to always relock & properly prompt for the unlock key.
For file access, this is actually a core probelm with Linux as a whole – any unsandboxed application you run will be able to read any file that you can read. The solution is to use sandboxed applications whenever possible. The easiest way to achieve this is through using flathub/flatpak applications, since they will always list out and enforce their required permissions on a per-application basis. For non-flatkpak applications, you’ll need to use “jail” environments (e.g.: bubblejail, firejail) in order to artificially restrict application permissions by hand.
It could probably be argued that the board didn’t do what was best for the investors, which is what they exist to do.
Incorrect. OpenAI LLC (the traded company) does not have a board of directors. The board of directors actually belong to the parent company, simply “OpenAI”, which is a nonprofit organization – the only thing that they’re beholden to is the OpenAI company charter.
Here’s a simplified breakdown:
Board of Directors =[controls]=> OpenAI (non-profit) =[controls]=> OpenAI LLC =[employs]=> OpenAI CEO
OpenAI LLC is obligated to act in the best financial interest of their shareholders, but OpenAI LLC does not actually have control over who sits in the CEO chair. That power goes to the non-profit “OpenAI” parent company – a company beholden to their board, not shareholders.
In the Steam Link app, you have the option to select “Start Streaming” without picking a specific game. This will stream the screen as it is without binding to a specific window.
The main caveats here are as follows:
Honest answer? Steam RemotePlay
What I’ve done instead is configured a desktop hotkey that toggles the system-level microphone mute. Two birds with one stone: foolproof PTT and on the same hotkey regardless of Zoom/Meet/Teams/Slack/Discord (consulting is fun)
You may be interested in reading this post about the process of packaging Steam.
tl;dr: It’s mostly an annoyance reserved for packagers to deal with. Dynamically linked executables can be patched in a fairly universal fashion to work without FHS, so that’s the go-to approach. If the executable is statically linked, the package may have to ship a source patch instead. If the executable is statically linked & close-source, the packagers are forced to resort to simulating an FHS environment via chroot.