• 2 Posts
  • 20 Comments
Joined 8 months ago
cake
Cake day: September 7th, 2024

help-circle

  • TL;DR: Do not sell the app, sell the service

    After reading all the comments, I am a bit confused.

    Based on my understanding, this a self-hostable, privacy friendly app, that does not contain a libre license, as you plan on monetizing it.

    First of all, the primary reasons of opting for libre software are privacy and freedom. So, the lack of such license can be considered a red flag.

    Second, a lot of privacy conscious Android users download their apps from services like F-Droid, that have strict rules against closed-source. So, trying to sell a privacy solution on Play Store does not sound like a good business model.

    Tips for monetizing a libre service:

    1. The client should have a libre license. You code running on the user’s device should be verifiable.
    2. Charge for your STUN/TURN server.
    3. Sell the server blob. Sandboxing apps on a Linux system is far easier (to prevent them from accessing the internet and potentially leak data).

    There are apps that are even available on F-Droid, and are similarly monetized. Some examples, that I use, are: Bitwarden, Mullvad, Telegram and Tailscale.






  • Talking about desktops, there may be some issues with Radeon RX 7000.

    If your hardware is that new, please stick to a distro with the newest kernel, like Fedora. There is a gaming oriented distro based on Fedora, called Bazzite, but I don’t know how big its community is, and how much it differs from vanilla Fedora.

    There are also a lot of choices in the Arch family, like Garuda, Endeavour, and Manjaro. However, please stay away of those since you probably don’t have any experience on Linux. Manjaro is not really Arch, and can face issues with AUR packages, and the rest may break during updates.

    Try the distro of choice in live mode. If you have enough RAM (like 16GB+), you can try to download Steam and some small game to see how it works. Keep in mind that, while in live mode, all files are stored in RAM.








  • I don’t understand this mindset.

    In open source, both malicious actors and contributors will try to find problems.

    In closed source, the development team is paid by hour (and probably don’t care about the product quality) and the only motivated people to find real issues are malicious actors.

    But people still consider closed source safer.



  • That smokescreen argument makes a lot of sense. Both the company and our clients, tend to opt for ready out-of-the-box proprietary solutions, instead of taking responsibility of the maintenance.

    It doesn’t matter how bad or limiting that proprietary option is. As long as it somewhat fits our scenario and requires less code, it’s fine.