I’ve been looking for a good self-hosted media server, and after trying out a few, I landed on Jellyfin. It’s free, open-source, and doesn’t nag you with subscriptions or locked features. Exactly what I needed.

Instead of going the traditional apt install route, I decided to install Jellyfin using Flatpak — it keeps things clean and isolated, which I prefer on my Debian setup. Here’s how I got it up and running, including setting up access to my media folder.

Step 1: Installing Flatpak (if you don’t have it)

Flatpak wasn’t installed on my machine by default, so I ran:

sudo apt update
sudo apt install flatpak -y

After that, I added the Flathub repo:

flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo

Quick tip: After setting up Flatpak, it’s best to log out and log back in — or just reboot — to make sure everything works smoothly.

Step 2: Installing Jellyfin Server via Flatpak

The Flatpak version of Jellyfin is available on Flathub, and installing it was simple:

flatpak install flathub org.jellyfin.JellyfinServer -y

To start the server, I ran:

flatpak run org.jellyfin.JellyfinServer

You’ll see some logs in the terminal, which means Jellyfin is doing its thing. Keep this terminal open for now — or later you can make it run in the background.

Step 3: Open It in Your Browser

Once it’s running, just go to:

http://localhost:8096

That’ll open the setup wizard where you pick a language, create your user, and set up your libraries.

If you’re running this on a different machine, just replace localhost with that machine’s IP.

Step 4: Giving Jellyfin Access to Your Media

Here’s where I got stuck for a minute: Jellyfin (via Flatpak) can’t see my media folders by default because of Flatpak’s sandboxing. Took me a second to figure this out.

Let’s say your movies are in /mnt/media/movies. You’ll need to give Jellyfin permission to see that folder:

flatpak override org.jellyfin.JellyfinServer --filesystem=/mnt/media:ro

The :ro part means read-only — safe if you don’t want Jellyfin messing with your files.

If you want it to write metadata, subtitles, etc., drop the :ro:

flatpak override org.jellyfin.JellyfinServer --filesystem=/mnt/media

Then just restart Jellyfin:

flatpak run org.jellyfin.JellyfinServer

Step 5: Add Media Libraries

Back in the web interface:

• Go to Dashboard > Libraries
• Click Add Media Library
• Pick what kind of content it is (Movies, TV, Music…)
• Point it to your folder, e.g., /mnt/media/movies
• Save and let Jellyfin do its magic

It’ll start scanning and building up your media library.

That’s It!

Jellyfin’s now up and running on my Debian system via Flatpak, and it’s happily indexing my media. The Flatpak approach keeps everything tidy, and it works great so far.

If you’re like me and prefer simple, no-nonsense tools that respect your setup, Jellyfin’s worth a try. And Flatpak makes it dead simple to install without touching your system packages.

The post How I Installed Jellyfin on Debian Using Flatpak appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

What Is OpenRA?

OpenRA is a community-driven initiative that reimagines classic RTS games for contemporary platforms. It’s not just a remake; it’s a complete overhaul that introduces:

• Modernized Interfaces: Updated sidebars and controls for improved usability.
• Enhanced Gameplay Mechanics: Features like fog of war, unit veterancy, and attack-move commands.
• Cross-Platform Support: Runs seamlessly on Linux, Windows, macOS, and *BSD systems.
• Modding Capabilities: A built-in SDK allows for the creation of custom mods and maps.

These improvements ensure that both veterans and newcomers can enjoy a refined RTS experience.

Latest Features and Updates

The March 2025 release brought significant enhancements:

• New Missions: Two additional Red Alert missions with improved objectives.
• Persistent Skirmish Options: Settings now carry over between matches.
• Balance Tweaks: Refinements for Red Alert and Dune 2000 to ensure fair play.
• Asset Support: Compatibility with The Ultimate Collection and C&C Remastered Collection.
• Language Support: Progress towards multilingual capabilities.

These updates demonstrate OpenRA’s commitment to evolving and enhancing the RTS genre.

Installation on Linux

Installing OpenRA on Linux is straightforward:

1. Download AppImages: Visit the official download page to get the AppImage for your desired mod.
2. Make Executable: Right-click the AppImage, select ‘Properties,’ and enable execution permissions.
3. Launch: Double-click the AppImage to start the game.

Alternatively, you can install OpenRA via:

• Snap: sudo snap install openra
• Flatpak: flatpak install flathub net.openra.OpenRA

These methods ensure that OpenRA integrates smoothly with your system.

Why Choose OpenRA?

OpenRA stands out in the Linux gaming landscape due to:

• Community Engagement: Regular updates and active forums foster a vibrant player base.
• Modding Scene: A robust SDK encourages creativity and customization.
• Cross-Platform Play: Enjoy multiplayer matches with friends on different operating systems.
• Educational Value: An in-game encyclopedia provides insights into units and strategies.

These features make OpenRA not just a game but a platform for learning and community interaction.

See OpenRA in Action

For a visual overview, check out this review:

Other Notable Strategy Games for Linux

If you’re exploring more strategy titles, consider:

• 0 A.D.: A historical RTS focusing on ancient civilizations.
• The Battle for Wesnoth: A turn-based strategy game with a rich fantasy setting.
• Freeciv: A free Civilization-inspired game with extensive customization.

Each offers unique gameplay experiences and is well-supported on Linux platforms.

OpenRA exemplifies how classic games can be revitalized for modern audiences. Its blend of nostalgia and innovation makes it a standout choice for strategy enthusiasts on Linux.

The post Rediscover Classic RTS with OpenRA on Linux appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

In the ever-evolving world of amateur radio, digital voice modes have revolutionized how we communicate. Among the various software options available, DroidStar stands out as a versatile and powerful solution for digital voice communication. This comprehensive guide will walk you through everything you need to know about DroidStar, from its features to installation and configuration.

What is DroidStar?

DroidStar is an open-source application that connects to various digital voice systems including:

• M17 (with open-source Codec2 vocoder)
• Fusion (YSF/FCS, supporting both DN and VW modes)
• DMR (Digital Mobile Radio)
• P25 (Project 25)
• NXDN (Next Generation Digital Narrowband)
• D-STAR (REF/XRF/DCS reflectors)
• AllStar nodes (as an IAX2 client or using Web Transceiver mode)

Originally developed as two separate projects (DudeStar using Qt Widgets UI and DroidStar using Qt Quick UI), they have now been merged into a single entity under the DroidStar name.

Key Features

Cross-Platform Compatibility

Built with the Qt C++ library, DroidStar runs on multiple platforms:

• Linux
• Windows
• macOS
• Android
• iOS (without USB device support)
• Other POSIX platforms with Qt availability

Hardware Support

DroidStar is compatible with:

• AMBE USB devices (ThumbDV, DVstick 30, DVSI, etc.)
• MMDVM modems for hotspot functionality
• MMDVM_HS (hotspot) modems

MMDVM Support

DroidStar can function as:

• A hotspot/repeater when connecting to a digital mode reflector/DMR server with an MMDVM device
• A stand-alone transceiver when using ‘MMDVM Direct’ mode (currently M17 only)

Optional Features

• Flite Text-to-Speech: For testing without speaking (requires building with Flite TTS support)
• Software vocoder plugin API: For loading vocoder software (proper licensing required)

Installing DroidStar on Linux Using Flatpak

Flatpak makes it easy to install DroidStar on any Linux distribution. Here’s how:

Step 1: Install Flatpak (If Not Already Installed)

For Debian/Ubuntu-based distributions:

sudo apt update && sudo apt install flatpak -y

For Fedora:

sudo dnf install flatpak -y

For Arch Linux:

sudo pacman -S flatpak

Enable Flathub repository:

flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo

Step 2: Install DroidStar

Search for DroidStar:

flatpak search droidstar

You should see something like:

Name             Description                   Application ID                    Version          Branch        Remotes
DroidStar        A digital voice client        io.github.nostar.DroidStar        1.0.1-git        stable        flathub

Install DroidStar using:

flatpak install droidstar

When prompted with “Use this ref?”, type Y and press Enter.

Launch DroidStar with:

flatpak run io.github.nostar.DroidStar

Step 3: USB Device Permissions (Linux Users)

Linux users with USB AMBE and/or MMDVM dongles need to:

1. Add your user to the ‘dialout’ group
2. Disable the ModemManager service: sudo systemctl disable ModemManager.service
3. Reboot your system

Configuration Guide

Basic Setup

1. Enter Your Callsign: A valid amateur radio license is required
2. Choose Digital Mode: Select from DMR, D-STAR, YSF, NXDN, P25, or M17
3. Select Host/Module: Choose the desired reflector or server
4. Configure Mode-Specific Settings:
   • For DMR: Enter your DMR ID, latitude/longitude, location, and description
   • For D-STAR: Configure MYCALL, URCALL, RPTR1, and RPTR2 fields
   • For AllStar: Set up IAX client parameters or Web Transceiver details

Installing the Vocoder Plugin

DroidStar supports software vocoder plugins through its API. To install a vocoder:

Method 1: URL Download (Works on All Platforms)

1. Go to Settings tab
2. Enter the vocoder URL in the “Vocoder URL” field
3. Click “Download vocoder”

Method 2: Manual Installation (Linux/macOS/Windows)

1. Download the appropriate vocoder plugin matching your platform and architecture
2. Place the plugin in the system settings file location:
   • Linux: ~/.config/dudetronics/
   • Name format: vocoder_plugin.platform.arch
   • Example: vocoder_plugin.linux.x86_64

Note: The platform and architecture for your device are shown on the About tab. Remember that any vocoder plugin should be properly licensed by you if copyright patents apply.

Using DroidStar

For DMR Mode

1. Enter your DMR ID
2. Input the talkgroup ID number (e.g., 91 for Brandmeister Worldwide)
3. For DMR+ hosts, create your options string and check “Send DMR+ options on connect”

For D-STAR Mode

Enter the correct values for MYCALL, URCALL, RPTR1, and RPTR2 before transmitting.

For AllStar

DroidStar supports two methods for AllStar connectivity:

IAX Client Mode

1. Define IAX nodes on the Hosts tab
2. Select the node when IAX mode is chosen from the Main tab
3. Send DTMF commands like *3node, *1node, *70 in the IAX DTMF box

Web Transceiver Mode

1. Add a line in the Host tab with format: IAX 12345 wt 4569 allstar-public allstar
2. Add your ASL web portal password to “ASL password” under settings

Final Thoughts

DroidStar is a powerful tool for amateur radio enthusiasts looking to explore digital voice modes. Its cross-platform compatibility and support for various digital protocols make it a versatile option for both beginners and experienced operators.

While this software is provided as-is without official support, it benefits from the work of many open-source projects including MMDVMHost, MMDVM_CM, mvoice, and others. The vibrant amateur radio community continues to improve and expand DroidStar’s capabilities.

Whether you’re experimenting with digital modes or using it for emergency communications, DroidStar offers a flexible and accessible platform for digital voice communication.

Visit:

https://github.com/nostar/DroidStar

https://github.com/rohithzmoi/Droidstar-DMR

http://kapihan.net/connect/resources/files/droidstar-vocoders.php

The post DroidStar: The Ultimate Digital Voice Communication Tool for Amateur Radio appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.

When it comes to Linux software installation, Snap and Flatpak have become popular options for packaging and distributing applications. Both formats aim to simplify the process by providing a universal way of distributing applications across different distributions. However, despite their common goal, they have distinct differences, histories, and ecosystems. In this post, we’ll dive deep into the origins of Snap and Flatpak, compare their features, advantages, and disadvantages, and help you decide which one to use.

The Origins and History of Snap and Flatpak

Snap:

Snap was introduced by Canonical, the creators of Ubuntu, in 2016. Canonical wanted a solution to address the limitations of traditional Linux package managers like APT or YUM, especially when it came to distributing applications across multiple distributions. Snaps are designed to be distribution-agnostic and include all the dependencies an application needs, thus avoiding the problem of missing libraries or dependencies. They’re containerized, making them more secure and easier to manage.

Flatpak:

Flatpak has its roots in the Fedora project and was developed by Alex Larsson in 2015. Similar to Snap, Flatpak provides a way to bundle applications with their dependencies. The idea behind Flatpak was to allow applications to run consistently on different Linux distributions while maintaining a high level of security. While Fedora and Red Hat were the early adopters of Flatpak, it has since gained support from a wide range of distributions, including Ubuntu, Debian, and Arch Linux.

Key Differences Between Snap and Flatpak

1. Repositories:
   • Snap: Snap applications are hosted in the Snap Store, maintained by Canonical. The Snap Store is centralized, meaning Canonical manages the publishing, updating, and distribution of all snaps. This can make the process easier for developers, but it also means that there’s less diversity in where and how applications are hosted.
   • Flatpak: Flatpak uses a decentralized approach with multiple repositories available. The primary repository is called Flathub, which serves as a hub for most Flatpak applications. However, developers and organizations can host their own Flatpak repositories, giving them more control over their distribution. This decentralized model gives users more freedom in choosing their source of applications.
2. System Integration and Isolation:
   • Snap: Snaps are more integrated with the system, but they also come with some isolation features. They’re sandboxed, meaning that they run in a container with limited access to the system. However, they tend to be more “system” oriented, as Canonical has more control over the underlying system’s interaction with the apps.
   • Flatpak: Flatpak applications are more isolated and run in a more strict sandboxed environment. This isolation improves security, but it can sometimes cause issues with system integration, especially for applications that need to interact closely with the host OS. Flatpak uses a runtime system, meaning that Flatpak apps rely on a shared runtime for common dependencies.
3. Update Mechanism:
   • Snap: Snaps update automatically in the background, which can be both a blessing and a curse. Users don’t have to worry about manually updating their apps, but some users find automatic updates to be intrusive, especially if they’re not in control of the timing.
   • Flatpak: Flatpak also has an update system, but it’s more user-controlled. While Flatpak apps can update automatically, it depends on how the user configures their system. Flatpak updates tend to be more flexible and less frequent compared to Snap.
4. Size and Performance:
   • Snap: Since Snaps bundle all dependencies, they tend to be larger in size. While this guarantees that the app will work across different distributions, it also results in applications being bulkier and consuming more storage.
   • Flatpak: Flatpak applications tend to be smaller than Snap packages since they share common dependencies through the runtime. However, if an app requires multiple runtimes, it can still lead to a significant size overhead. Despite this, Flatpak apps generally perform better because they use shared runtimes, avoiding unnecessary redundancy.
5. Security and Sandboxing:
   • Snap: Snaps are sandboxed by design, and Canonical uses AppArmor for additional security. While this offers a good level of protection, some users feel that it’s not as strict as the Flatpak model, as Canonical’s more centralized control can mean less transparency.
   • Flatpak: Flatpak uses SELinux (Security-Enhanced Linux) or other similar security mechanisms for sandboxing. Flatpak has a more strict isolation model, meaning that Flatpak apps are more restricted in terms of what they can access on the host system.

Command Lists

Let’s take a quick look at the basic commands for using Snap and Flatpak.

Snap:

• Install a Snap package: sudo snap install <package-name>
• Search for Snap packages: snap find <package-name>
• List installed Snaps: snap list
• Remove a Snap package: sudo snap remove <package-name>
• Update Snap packages: sudo snap refresh

Flatpak:

• Install a Flatpak package: flatpak install flathub <package-name>
• Search for Flatpak packages: flatpak search <package-name>
• List installed Flatpak applications: flatpak list
• Remove a Flatpak package: flatpak uninstall <package-name>
• Update Flatpak packages: flatpak update

Advantages and Disadvantages

Snap Advantages:

• Centralized Snap Store simplifies distribution and management.
• Automatic updates reduce the need for user intervention.
• Works across many Linux distributions with minimal setup.
• Strong integration with Ubuntu and other Canonical-based systems.

Snap Disadvantages:

• Larger file sizes due to bundling all dependencies.
• Automatic updates can be intrusive for some users.
• More centralized control, meaning less transparency.
• Slower start-up times compared to native packages.

Flatpak Advantages:

• Strong security features with strict sandboxing.
• Smaller file sizes thanks to shared runtimes.
• Decentralized model gives more freedom and flexibility.
• Better integration with GNOME-based systems and other desktop environments.

Flatpak Disadvantages:

• Slightly more complex to set up due to multiple repositories.
• May require more storage if multiple runtimes are installed.
• Some apps may face compatibility issues in terms of system integration.
• Less integration with Ubuntu-based systems compared to Snap.

Which One to Choose?

Snap is a great choice if you’re using Ubuntu or a distribution based on it, as it is tightly integrated into the ecosystem. If you prefer a more centralized system with automatic updates and easy management, Snap might be the way to go. It’s also ideal if you need a quick and straightforward installation process across various distributions.

Flatpak is a better choice if you value security and sandboxing, or if you want to use a decentralized system with the freedom to pick your repository. Flatpak is more suited to users who appreciate flexibility and want smaller file sizes by leveraging shared runtimes.

Ultimately, the choice comes down to your preferences and your distribution. Both Snap and Flatpak have their strengths, and as Linux continues to evolve, the adoption of both formats will likely grow.

The post Snap vs Flatpak: A Detailed Comparison appeared on Hamradio.my - Amateur Radio, Tech Insights and Product Reviews by 9M2PJU.