shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

243
active users

#archwiki

0 posts0 participants0 posts today
TECC :archlinux:<p>What I love about <a href="https://social.tchncs.de/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> – especially <a href="https://social.tchncs.de/tags/ArchLinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ArchLinux</span></a> – is the full control it gives you. It's lightweight, highly customizable, and you only install what you really need. The rolling release model keeps everything up to date, and the <a href="https://social.tchncs.de/tags/ArchWiki" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ArchWiki</span></a> is an amazing resource. It’s not always easy, but you learn a lot and really understand your system.</p><p>"example image"</p><p><a href="https://social.tchncs.de/tags/FOSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FOSS</span></a> <a href="https://social.tchncs.de/tags/LinuxLife" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LinuxLife</span></a> <a href="https://social.tchncs.de/tags/ArchBTW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ArchBTW</span></a> <a href="https://social.tchncs.de/tags/OpenSource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenSource</span></a></p>
Mika<p><a href="https://sakurajima.social/tags/Linux" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> audio is bizarrely confusing to a regular user lol - if I were to configure a <a href="https://sakurajima.social/tags/PulseAudio" rel="nofollow noopener noreferrer" target="_blank">#PulseAudio</a> setting (i.e. <code>clock.force-quantum</code>) but obviously most systems now have moved to using <a href="https://sakurajima.social/tags/PipeWire" rel="nofollow noopener noreferrer" target="_blank">#PipeWire</a>, but from what I can tell or think to understand is that systems use PipeWire via something called <a href="https://sakurajima.social/tags/WirePlumber" rel="nofollow noopener noreferrer" target="_blank">#WirePlumber</a>, should this (user-specific) configuration be done in a WirePlumber config, or PipeWire? I normally could learn these things easily through the <a href="https://sakurajima.social/tags/ArchWiki" rel="nofollow noopener noreferrer" target="_blank">#ArchWiki</a>, but so far, this topic is completely lost on me lol.</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://meow.social/@RayuDW" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>RayuDW</span></a></span> good question...</p><p>Normally it's set to your locale once but depending on OS &amp; implementation and chipset it may need to be set by the OS based off localization settings...</p><p><a href="https://infosec.space/tags/ArchWiki" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ArchWiki</span></a> to the rescue: <a href="https://wiki.archlinux.org/title/Network_configuration/Wireless#Respecting_the_regulatory_domain" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">wiki.archlinux.org/title/Netwo</span><span class="invisible">rk_configuration/Wireless#Respecting_the_regulatory_domain</span></a></p>