Linux on Reddit

https://orionbrowser.com/download/oriongtk.0.3.0.flatpak Orion for Linux Beta 0.3 is Here! This is a big moment for Orion. After months of building, testing, and iterating with a smaller group of early users, we’re opening the doors: Orion for Linux is now in Public Beta – available to everyone. Core browsing is in place, key features are coming together, and Orion is now ready for broader, real-world use and feedback. You can download the Flatpak build of Orion Browser for Linux here: Orion for Linux Beta 0.3 (x86) Orion for Linux Beta 0.3 (ARM) What’s new in this version A more complete browsing experience Since Alpha and the early beta, Orion for Linux has evolved into a much more capable browser: Full tab management Password manager and history tracking Dark Mode and Focus Mode Custom search engines (search directly from the address bar) Early download support (work in progress) Features added in the last release AdBlock support Built-in EasyList and EasyPrivacy Additional filter lists prepared for future expansion Download manager Kagi Search onboarding Try Kagi search even without a paid account Local Sync (initial version) Export/import your profile data (remote sync coming later) Improved bookmark import/export Stability & performance improvements We’ve made significant progress in reliability: Fixed crashes when closing pinned tabs Resolved browser freezes in Website Settings Fixed issues with opening new tabs after installation Addressed tab overview crashes and SQL-related issues Overall, Orion is now noticeably more stable and responsive than in earlier builds. Smaller improvements that make a difference A lot of polish has gone into everyday usability: Standard shortcuts like Ctrl+R and F5 for refresh Ctrl+click to open links in new tabs Improved Settings dialog (especially on smaller screens) Better Tab Groups experience (formerly “Windows”) Context menu improvements and UI fixes across the app Orion for Linux Beta 0.3 screenshot Orion for Linux Beta 0.3 screenshot Orion for Linux Beta 0.3 screenshot What’s next We’re not stopping here. Next steps include: Remote Sync support Continued work on downloads WebExtension compatibility Ongoing stability and performance improvements We’d love your feedback Opening the beta to everyone means your feedback matters more than ever. Tell us what works, what doesn’t, and what you’d like to see next. Browse Beyond ✴︎ The Orion for Linux Team submitted by /u/ucsilahsor [link] [comments]

Good day again. I'm thinking of adding a TCP network stack to this system. Do I need to add anything else? I would be very grateful if you could inform me, or if there's anything else you'd like me to do. submitted by /u/DifficultBarber9439 [link] [comments]

PREEMPT_NONE has previously existed to provide a way to gain more throughput on almost all workloads at the expense of also gaining some more latency, and it was better for most server workloads, which value throughput more than latency. For workloads that spend most of their time in spinlocks, it was actually able to have significantly lower latency than the other preemption options, as well. According to Salvatore Dipietro, some PostgreSQL workloads have approximately half the performance when using PREEMPT_LAZY instead of PREEMPT_NONE. The Linux kernel maintainers have responded that PostgreSQL should add the use of the "RSEQ timeslice extension", which enables a process to ask the kernel to delay preemption for a short period of time. (The default delay is 5 millionths of a second.) However, this solution is not perfect. First of all, it would require PostgreSQL to make changes that would make PostgreSQL unable to work on any machines that do not have an up to date kernel, dropping support for all kernels below version 7. Second of all, it would still reduce throughput and latency on such workloads. It would merely reduce them less. Edit: I suppose that PostgreSQL could check whether the kernel is past version 7 and have two separate versions of each spinlock, one for kernels below 7 and one for kernels above 7, in which case it could still work on kernels below 7. submitted by /u/InfinitesimaInfinity [link] [comments]

Recently I started to use Linux more regularly, usually Ubuntu and Alma servers and more recently even a Fedora desktop (KDE) and Ubuntu laptop (Gnome), so a good mixing. For the first time in years I've been able to ditch Windows for real lol But I started to wonder about others: if you are just enjoying Linux as is for your needs like a simple tool, or if you contribute back if feeling like it, or even feel part of a specific "community" that works towards Linux distros or beyond. If yes, why and how did you ended up doing it? And, what project or community would you recommend (or not recommend, if having any constructive criticism)? I feel like I don't have anything to do, considering I'm just a basic user who wouldn't be of any valuable help even to the projects I use (Ubuntu, Fedora..., they're already too well fitted and even supported by the companies behind them), but I'm just curious about other people. submitted by /u/onechroma [link] [comments]

submitted by /u/Gugalcrom123 [link] [comments]

submitted by /u/Unusual_Pride_6480 [link] [comments]

Immer wieder tolle Vorträge, falls ihr was zum hören für unterwegs zb wollt. Auch ältere Jahre sind heute noch gut und aktuell für den rundum Blick oder zum Einstieg. Mods löscht es gerne wenn es nicht hier passt aber in meiner link Sammlung hat es einen festen Platz. https://chemnitzer.linux-tage.de/2026/de submitted by /u/Dani_E2e [link] [comments]

submitted by /u/anh0516 [link] [comments]

obs-kmscap is a display server-agnostic zero-copy screen capture plugin for Linux, which works by directly exporting textures from the screen's framebuffer using native system calls, in favor of double-copy XSHM capture, which is incredibly slow. Depending on your system, it might be potentially more performant than even Wayland Pipewire capture, since it bypasses the double compositing that Pipewire implicates and thus results in lower input lag overall. The idea started from w23's project, which does something very similar in concept, but hasn't received updates or support in years. I am currently trying to test the plugin on a larger scale, and I would highly appreciate it if anyone tried it for themselves and gave me feedback. I am also curious about NVIDIA support, as I don't have an NVIDIA graphics card myself, but seeing as newer drivers have better DRM/KMS support (with nvidia-drm.modeset=1 as a kernel boot parameter) it makes me curious. submitted by /u/thepoke32 [link] [comments]

Repo + install: https://github.com/cushycush/wflow (stars help with discovery on the awesome-lists if it's your kind of thing) I've been building wflow for the last couple of months. It's a desktop automation tool: bind a keyboard chord like ctrl+alt+t, fire a workflow. Workflows are plain-text KDL files you can also build in a Qt GUI. The 1.0 release is what I'm posting today. What it actually does, in one sentence: AutoHotkey-style chord triggers, but on Wayland, where AHK doesn't run and where the existing options stop at "open one app on a global hotkey". The trigger daemon probes for a backend at startup. KDE Plasma 6 and GNOME 46+ get the GlobalShortcuts portal (the consent-dialog one, no sudo, no special groups). Hyprland gets IPC over $XDG_RUNTIME_DIR/hypr/.... Sway gets the i3 IPC bindsym ... exec route. The daemon hot-reloads on workflow file changes via inotify. Compositor IPC mode is fully live; portal mode needs a daemon restart for new bindings (that's a spec limitation, not laziness). A workflow looks like this: ```kdl workflow "Focus mode" { trigger { chord "ctrl+alt+f" } shell "swaync-client -d" shell "pactl set-sink-mute @DEFAULT_SINK@ 1" focus "Editor" notify "head down" body="focus mode on" } ``` That's the whole file. Ten lines. Diffable, shareable, version-control friendly. The GUI is a view onto the file; edit either side, the other catches up. Alongside the desktop release I'm also launching wflows.io, a catalog where people can publish and share workflows. One-click "Open in wflow" from any page, the desktop catches the wflow://import?source=... URL, shows a confirm dialog with title / author / description / step count, drops it in your library if you say yes. Drive-by URLs can't silently install anything. Install: - Arch: paru -S wflow-bin (prebuilt) or paru -S wflow (source build) - Tarball + INSTALL.txt: github.com/cushycush/wflow/releases/latest - Flatpak: manifest is in the repo, Flathub submission is in flight - Catalog + docs: wflows.io What I want feedback on, honestly: - Compositor coverage. I've tested Plasma 6, GNOME 46+, Hyprland, Sway. River, Niri, Cosmic — if you're on one of those and it breaks, the issues page is open. - The KDL format. It's a plain-text file format I built the parser for myself. It's fine. It's also probably going to surface edge cases nobody else has hit yet. Roast it. - The trust prompt. First time you run a workflow you didn't write, wflow shows a categorized step summary and asks you to confirm. Annoying? Necessary? Both? Tell me. Source for the desktop is at github.com/cushycush/wflow (Rust + Qt Quick). Source for the catalog is at github.com/cushycush/wflows (Next.js + Postgres + Drizzle). Both dual MIT/Apache. There's a Discord linked from wflows.io if you want to talk through anything in real time, otherwise the GitHub issues page is the right spot for bugs. submitted by /u/DaCush [link] [comments]

About 2 years ago, I decided to move a few of my servers that contain precious data to some great deal VPSs I picked up during Black Friday from LET. After migrating all the data, I set up Duplicati on one of the servers to handle backups. While configuring it, I came across something pretty concerning. Duplicati can silently corrupt backups over time. So when I actually need to restore data after a disaster, the backups might not even work. Realizing this made me feel like the whole migration was a mistake because those servers were managed and came with backup service. I wanted to move to Restic because it’s rock-solid, but as someone who prefers a UI over managing endless CLI scripts, it just wasn't clicking for me. I wanted a way to easily manage a 3-2-1 backup plan across different cloud providers without the headache. I then found Backrest and gave it a try, but the UI did not make much sense to me as I was not really aware of the restic terminologies back then(this was back in December 2024). Since I’m a developer, I decided to build my own solution. I thought it would take a month or two, but it ended up taking 16 months to get everything perfect. This is quite a long time for me, as I have been building various apps for a long time now, and most took me 3-4 months. Here are the key Features of Pluton: Automated backups with encryption, compression, and retention policies powered by Restic Backup Replication: Auto-backup your content to multiple cloud storage to create 3-2-1 backup plans. Flexible scheduling for automated backup jobs with fine-grained retention policies End-to-end encryption: Backups are totally encrypted from your local machine to your cloud storage. 70+ Storage Support: Store encrypted data to your favorite cloud storage (powered by rclone). Easy Restore & Download: Restore or download backed-up snapshot data easily with just a few clicks. Event Notifications: Receive email, slack & discord notifications for backup start, end, completion, or failure. Auto Retry Logic: Automatically retries backups if they fail with customization options. Intuitive UI: Manage everything from a single, clean interface. Real-time Progress Tracking: Track the progress of backups in real time. Extensive Logging: View app and backup logs right from the UI for better debugging. Run Scripts before/after: Ability to run scripts before and after running backups. 2FA: Secure your dashboard with built-in 2-factor authentication. Pluton can be installed on Linux desktops (AppImage) and servers, and can also be deployed with Docker. Give it a try: https://github.com/plutonhq/pluton Feedbacks appreciated. submitted by /u/towfiqi [link] [comments]

submitted by /u/BrageFuglseth [link] [comments]

submitted by /u/furculture [link] [comments]

submitted by /u/themikeosguy [link] [comments]

submitted by /u/CarlSchwanKDE [link] [comments]

The term “POSIX” seems far more useful, it’s used to talk about OSes that conform to the POSIX standard something that is very specific whilst “unix-like” seems far more subjective and “UNIX” could refer to the OS. submitted by /u/Lopsided-Cost-426 [link] [comments]

submitted by /u/f_r_d [link] [comments]

submitted by /u/Fcking_Chuck [link] [comments]

submitted by /u/anh0516 [link] [comments]

submitted by /u/SpeeQz [link] [comments]

submitted by /u/anh0516 [link] [comments]

submitted by /u/Proper-Lab-2500 [link] [comments]

Hello, I’m someone who enjoys programming as a hobby and has a strong interest in computer science. I build projects using Rust and PHP, and I’ve also been able to introduce various improvements at my workplace thanks to my programming knowledge. Along the way, I’ve been encouraging the use of open-source software whenever possible. I regularly donate to many of the open-source tools I use. However, I’ve been wondering: do these donations actually make a meaningful difference for the developers? For example, I’m considering switching from GitHub to Codeberg and plan to support them financially as well. I even wanted to donate to the Rust programming language, but I couldn’t find a clear way to do that as an individual. So I have two main questions: Do individual donations really make an impact on open-source projects? How can I help promote this culture in my environment? At my workplace, for instance, some open-source tools (like WordPress) are used to generate revenue, yet I rarely see any contributions or donations being made back to those projects. Personally, I believe supporting open-source is important. For example, I use Zorin OS Pro as a way to contribute, and I’m quite happy with it. I’d really appreciate hearing your thoughts. submitted by /u/Jumpy-Win-2973 [link] [comments]

submitted by /u/Fcking_Chuck [link] [comments]

Recently open source subreddits have started seeing a large number of vibecoded personal projects that look novel or useful on the surface, but in reality represent one weekend of prompting by the vibecoder. At best these are benign novelties that maybe get a bunch of unwarranted upvotes but don't really harm anyone. At worst they're unaudited, poorly designed garbage software that looks impressive at a glance, tricking people into installing it on their computers, which will at best lead to some frustration and wasted time and at worst to -DGAPING_SECURITY_HOLE. Because these projects take basically no investment on the author's part, they tend to quickly become abandonware as the author's interest wanes or as they become frustrated with the currently inevitable technical debt reckless vibecoding produces. As a result, projects like this are of negative worth to the open source community. Naturally, these people almost never disclose that they vibecoded their project. The rule proposal The proposal is simple. Expand the current self-promotion rule to forbid all personal projects under 3 months old. The project's age would most easily be proven by a public git repository with 3+ months of commit history. Probably we should also forbid closed-source personal projects, but that's a separate discussion. This works because 90% of problematic slop projects are made by attention-seeking people who want to make something cool and show it to other people, and most importantly don't want to spend a lot of time or effort doing it. If the developer has stuck with the project for three months, it's likely either not vibecoded in the first place (because real projects take time), or the author is dedicated enough that it being vibecoded isn't automatically a massive problem. I've seen rules like this in a few communities and they seem to work pretty well. submitted by /u/turdas [link] [comments]