This week in our forums…
Key Stats
In the past week, our Linux forums had the following activity and key statistics:
- Total New Posts: 195
- Total New Topics: 16
Top Contributors
- @Brian_Masinick: 17 posts, 73 likes received
- @ericmarceau: 16 posts, 71 likes received
- @Itachixkurosaki: 11 posts, 44 likes received
- @andreas: 10 posts, 40 likes received
- @rogerp: 10 posts, 37 likes received
- @tkn: 8 posts, 35 likes received
- @taki_at_gamma_linux: 14 posts, 35 likes received
- @J_J_Sloan: 8 posts, 31 likes received
- @benowe1717: 6 posts, 26 likes received
- @Bombilla: 10 posts, 11 likes received
Interesting Topics
In General Discussions, @J_J_Sloan kicked off a lively language discussion in Programming languages. Members compared Bash, C, Perl, Python, Prolog, Crystal, Rust, and even Julia for sysadmin work and scripting. @tkn and @ericmarceau shared real world Bash and C tooling, while @andreas described moving personal projects to Codeberg and using Python and Prolog in research, giving the thread a great mix of practical and academic perspectives.
Also in General Discussions, @taki_at_gamma_linux asked a thoughtful licensing and architecture question in Why can we make Linux distros, but not really Windows or macOS distros? 
. Replies from @pavlos, @ugnvs, @tkn and others broke down how open source licenses, modular design, and “share alike” terms make Linux highly remixable. The thread also explored how commercial licensing restricts Windows/macOS derivatives and even dug into Intel’s use of MINIX in firmware as a contrasting example.
In Showcase, @Itachixkurosaki opened Just asking for a little feedback on what I can do better to get concrete critique on a self hosted portfolio and résumé aimed at breaking into IT. Detailed feedback from @ericmarceau, @andreas, @rogerp and @ugnvs covered résumé gaps, font size, content density, portfolio structure, voice authenticity, and even OPSEC concerns. The conversation evolved into an in depth look at how to present homelab projects professionally while protecting personal data.
Over in #linux-support, @ericmarceau raised a subtle but important data integrity concern in Writing to USB stick - (Caja) non-sync’ed?. After observing that Caja reported copies as finished while the system was still flushing buffers, they asked how to make completion reflect real writes. @Jymm, @taki_at_gamma_linux, @pavlos, @mrtoo, @andreas and @tkn unpacked the buffering layers, sync behaviour, udev options, user expectations, and even filing an upstream issue. It is a useful thread if you rely on USB storage for backups.
In General Discussions, @taki_at_gamma_linux started a reflective meta thread, Do Linux users overcomplicate simple things? . The question contrasted graphical installers with elaborate terminal workflows and asked where “control” ends and “overengineering” begins. Responses by @ugnvs, @tkn and @ericmarceau argued that complexity often reflects exposed options rather than unnecessary complication, and that scripting is both convenience and a form of play for many users.
In Showcase, @Halano presented a lightweight Arch tooling project in Archpkg Browser. The FLTK based GUI makes browsing Arch repositories quick and visually simple. @taki_at_gamma_linux provided feedback and a pull request, and @hydn dropped in encouragement, while @Halano outlined plans for a more distribution friendly file manager to complement the current GPU heavy RaymothFM.
Also in Showcase, nostalgia met X11 in Windows 2000 for X11, where @Halano shared a project that directly draws on X11/Xft to recreate classic Windows 98/2000 era shells. Screenshots and comments from @andreas, @jaymo_chicago, @ericmarceau and @ClaudioDC highlighted both the authenticity of the retro design and the potential to ease transitions for users moving from older versions of Windows to Linux.
In #linux-support, @ericmarceau opened Bluetooth connectivity issue to investigate why only a single Bluetooth speaker worked correctly on Ubuntu MATE while others refused to take over audio. @Itachixkurosaki responded with a detailed walkthrough of PulseAudio/PipeWire profiles, pavucontrol, and A2DP vs HSP/HFP, and later added a follow up on auto switching via WirePlumber once @Norm24 reported a partial workaround through MATE’s sound preferences.
In #community-picks, @benowe1717 documented a substantial homelab milestone in How I Chose to Ready my Homelab for the Upcoming SSL Certificate Changes. The article explains the coming reduction in TLS certificate lifetimes, then walks through automation strategies for lab services. @hydn added a long reply comparing CA signed and self signed certificates, arguing that for purely internal labs, trust distribution matters more than who signs the cert, and the two exchanged thoughts on usability, browser warnings, and when external CA trust really adds value.
In #help-support, @taki_at_gamma_linux published a tutorial style guide, 
How to Set Up a VNC Server with x11vnc — From LAN to Remote Access. The post walked readers from basic LAN VNC to firewalls, SSH tunneling and CGNAT. @Itachixkurosaki then contributed a substantial reply comparing that “classic” approach with modern remote access patterns using tunnels and out of band consoles, followed by @taki_at_gamma_linux revisiting their recommendations in light of CGNAT and security considerations. The exchange turned the thread into a layered look at how to design remote access today.
Finally in Debian, @J_J_Sloan highlighted how widely Debian is used in Debian runs in some important spaces. The topic notes Debian’s role at Google, HP, global NTP servers, cloud infrastructure and CERN’s migration from RHEL to Debian Trixie. @andreas chimed in that this reach really lives up to Debian’s “universal operating system” slogan, underscoring why Debian discussions remain central on the forum.
Activity by the @staff Group
In #our-community, @hydn provided an operations update in Scheduled maintenance—September 20th, 2026. They announced a brief period of downtime for urgent OS livepatching and a Discourse security update, clarified that the larger scheduled upgrade for September 20 remains on track, and confirmed completion once both kernel and forum patches were applied.
Within server, @hydn shared a new article integration in Master Linux Bash History with historyctl, HISTFILE, and Shortcuts, outlining how to enhance Bash history beyond simple arrow key recall. @tmick followed up to say they had learned new techniques from the piece, hinting at members adopting more advanced shell workflows.
In #desktop-apps, @hydn added a practical configuration tip to How to Set Up Hibernation on Linux (Swap Done Right). They described switching an XFCE system to hybrid sleep, documented the tradeoffs between suspend, hibernate, and hybrid, and shared how to extend XFCE’s idle timeout beyond the GUI limit by editing xfce4-power-manager.xml directly.
Across General Discussions and Debian, @andreas and @system helped keep ongoing discussions moving. @system compiled a new Saturday Showcase: Built & Shared by Members This Week recap that pointed readers toward member projects such as @Itachixkurosaki’s portfolio, @Halano’s Archpkg Browser, and the Windows 2000 for X11 shell. This automated highlight post amplifies member work and guides weekend browsing.
Staff also stayed active in welcoming and supporting newcomers. In long running community threads like Welcome! Introduce yourself, @Bombilla and @hydn greeted many first time posters, helping them settle into the forum. In What’s everyone working on? 2026 edition 
, @Bombilla welcomed @mr_mcbride while staff and regulars encouraged deeper project sharing in Showcase.
Finally, curation work continued behind the scenes. @hydn featured @benowe1717’s TLS automation write up by moving How I Chose to Ready my Homelab for the Upcoming SSL Certificate Changes into #community-picks, signaling it as a high value reference for others planning for shorter certificate lifetimes.
Best Reply or Topic of the Week
The standout contribution this week is @Itachixkurosaki’s in depth response in How to Set Up a VNC Server with x11vnc — From LAN to Remote Access.
In that reply, they:
- Broke down what port forwarding actually does, using clear analogies that are accessible to less experienced readers.
- Compared “classic” VNC over exposed ports with more modern, layered remote access patterns that rely on SSH, VPNs, zero trust tools and out of band consoles.
- Emphasized realistic constraints like CGNAT and ISP restrictions, then mapped those constraints to practical alternatives for homelab and small server setups.
The post builds directly on the original guide rather than contradicting it, and the resulting conversation provides a nuanced, up to date view of how to think about remote desktop access in 2026.
Top Contributor
Congratulations to @taki_at_gamma_linux on earning this week’s Top Contributor badge! 
Thanks for reading. See you again next week! 
Our community remains free of banner ads thanks to our partnership with Better Stack.
Better Stack offers infrastructure observability services, uptime monitoring, logging, incident management, and a free tier worth checking out. Visit Better Stack
Important: Avoid replying to this topic. Instead, reply to the topics linked within. Or, if you have questions or comments related to this weekly summary, please post them in the #site-help or Our Community forum category.