You don’t understand, the problem isn’t the people who put in no effort.
It’s those evil LLMs, they are to blame.
You don’t understand, the problem isn’t the people who put in no effort.
It’s those evil LLMs, they are to blame.
New tip just dropped
everything
You’re in the right place, most social media users can’t properly formulate their thoughts into sentences, lol.
That’s not a pipewire problem, that’s a systemctl problem.
Failed to connect to user scope bus via local transport: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined
The error means systemctl --user can’t reach your user’s D-Bus session because the required environment variables aren’t set. This typically happens when you’ve switched users via su or sudo rather than logging in directly, because htose don’t initialize a full systemd/PAM session. It could also be that your session wasn’t properly initialized by systemd-logind or a number of other things. Try spawning a proper user session:
sudo machinectl shell your_username@
and try the systemctl command again.
My pipewire seems to have issues with crackling audio and severely dampening my mic and I have no clue why.
Pipewire’s default quantum (buffer size, effectively) is incredibly low, this is good for low latency audio but anytime your system is too busy to keep the buffers filled you get crackling.
If you look at pw-top you’ll see all of your devices and nodes. The quant column is probably 1 or a very small number for the devices.
You can increase the quantum with this command. This only lasts until pipewire restarts:
pw-metadata -n settings 0 clock.min-quantum 512
At a sample rate of 48000, this is roughly a 10ms buffer. 1024 is 20ms, etc. You want it as low as possible without getting crackling. Start with 512 and adjust from there (you don’t have to use a power of 2, a quantum of 1234 works just as well).
severely dampening my mic and I have no clue why.
By default pipewire doesn’t do any ‘mic boost’, as Windows calls it. You can get the same effect by raising the maximum volume.
In your sound control panel you should be able to turn the mic up higher than 100%. In KDE Plasma, you can do this in System Settings -> Sound -> Configure Volume Controls… [top right button] -> Raise maximum volume.
Alternatively, you can use EasyEffects to add a compressor. This will boost your mic volume and also prevent it from getting too loud
Compressors basically reduce the dynamic range of an audio signal by attenuating loud sounds and boosting quieter ones, this would provide a better mix.
Other useful plug-ins are noise canceling, (kills background noise) and echo canceling (lets you play sound out of your speakers which won’t get picked up by your mic). Sometimes apps, like Discord, will do this signal processing for you while others, like Signal, do no signal processing.


I went into my bathroom and it was full of electromagnetic radiation and 5G. Checkmate, atheists


Anyone who does that will find themselves quickly out of business and bankrupt from lawsuits.
The headline is a fantasy, it’s a tool that augments professionals in some situations. It doesn’t replace them.


Popular is supposed to be the highest activity subreddits. If you keep scrolling you’ll only see older posts from the same set of subreddits. r/all is all the subreddits sorted by popularity, if you keep scrolling you see lower and lower upvote counts.
Your home feed is your subscribed subreddits.


My question exactly: The computers should be purpose-built, including the operating system.
They are, mission critical systems are typically on a Unix/Linux base or completely custom built.
The systems that use Windows are the ones related to office work, like updating the crew’s bank information and distributing pay.


The article leaves out that this was on Commander Wiseman’s personal tablet, a Microsoft Surface Pro and not any device associated with the mission.
He sought tech support for internet connectivity issues on a PCD (personal computing device), which is a Microsoft Surface Pro.
The ‘Two Microsoft Outlooks’ was a description of the issue he was having. The headline is implying that there are two machines running Outlook that don’t work.
NASA detected that the PCD was actually on a network. It asked the commander for permission to connect to the tablet remotely so it could look into a problem with the Optimus software. “I also see that I have two Microsoft Outlooks and neither one of those are working,” Wiseman responded, per a clip shared by Niki Grayson on Bluesky. “If you wanna remote in and check Optimus and those two Outlooks, that would be awesome.”
The source of the quotes and a better article:


He’s going to be in for a big surprise when he’s on the far side of the moon and discovers that all of his ‘local’ files are on OneDrive.


The whole point of the ‘Real Name’ and ‘Location’ fields was so that people could physically locate you.
They’ve been part of Linux since the 1960s without any horrible outcomes. birthDate is even less identifying than ‘Real Name’ and even less dangerous than ‘Location’.
Not that it matters because they are all optional fields that nobody uses unless they want to.


How does systemd having an optional birthDate field prevent children from having a computer?
It also has fields for ‘Real Name’ and ‘Location’ (and has since the 1960s) without any problems. Most people don’t even know that they exist because they’re optional.
Tuesday is war crimes day