• 4 Posts
  • 119 Comments
Joined 2 years ago
Cake day: September 1st, 2023
  • onlinepersona@programming.devtoOpen Source@lemmy.ml•A federated bittorrent trackerEnglish
    211·
    12 days ago

    @jonny@neuromatch.social I want to like this, but the repo and website do not convey this fundamental information about the project

    • what it is
    • what is does
    • why it does it
    • how it does it

    The repository only has deployment notes.

    The webpage has:

    • The name
    • A quote
    • What SciOp belongs to
    • A call to action addressed at… somebody
    • Some random stats

    It doesn’t mention “tracker” anywhere and only mentions “bittorrent” once.

    Please consider people who:

    • know nothing about the project
    • don’t care about who you are
    • have under 5 minutes (most likely 1 minute) to be intrigued
    • are not necessarily technically inclined

    Ask yourselves who the target audience is and maybe even state it on your webpage.

    Lastly, it’s probably too late to change the name and it’s a matter of taste, but making it a homonym to PsyOp make me immediately think that this has a connection to anti-vaxxers, chemtrail believers, flat-earthers, illuminati freaks, and just conspiracy theorists in general.

    Maybe I’m the only one thinking this, but as it currently exists, the project feels very much like the old-school C projects that assumed you were “in the know” before even arriving at the website or project. It does not make it inviting - at least not to me. It may be a completely false impression, but it is my impression nonetheless.

    Anti Commercial-AI license

  • onlinepersona@programming.devtoOpen Source@lemmy.ml•Open source maintenance feeEnglish
    341·
    1 month ago

    This is the text is suggested to be added

    ## Open Source Maintenance Fee

This project requires an [Open Source Maintenance
Fee](https://opensourcemaintenancefee.org/). While the source code is
freely available under the terms of the LICENSE, all other aspects of
the project--including opening or commenting on issues, participating in
discussions and downloading releases--require [adherence to the
Maintenance Fee](./OSMFEULA.txt).

In short, if you use this project to generate revenue, the [Maintenance
Fee is required](./OSMFEULA.txt).

To pay the Maintenance Fee, [become a Sponsor](https://github.com/sponsors/<YOURORGNAME>).

    The EULA template can be found here. This is the part I find important

    1. Conflicts with OSI License

    To the extent any term of this Agreement conflicts with User’s rights under the OSI License regarding the Software, the OSI License shall govern. This Agreement applies only to the Binary Release and does not limit User’s ability to access, modify, or distribute the Software’s source code or self-compiled binaries. User may independently compile binaries from the Software’s source code without this Agreement, subject to OSI License terms. User may redistribute the Binary Release received under this Agreement, provided such redistribution complies with the OSI License (e.g., including copyright and permission notices). This Agreement imposes no additional restrictions on such rights.

    I think it’s a good attempt, but I’m not sure how it can be enforced. It would also need to be applicable to different jurisdictions. The project maintainer would have to know that somebody requesting a feature, commenting or participating in discussions is doing so in the name of the company 🤔

    Thank you for sharing this. It’s food for thought.

    Anti Commercial-AI license

  • onlinepersona@programming.devtoLinux@lemmy.ml•Can I ignore flatpak indefinitely?English
    6·
    2 months ago

    I wasn’t being very serious about nix. IMO, it’s quite the time investment due to its poor documentation and it has a lot of gotcha’s if you aren’t on NixOS e.g one example is that it’s great for terminal applications, but horrendous for GUI applications as it’ll be hit or miss. Again, this is if you’re not on NixOS. So, it can feel like an “all or nothing” approach.

    If you have the time and will, then it can be very rewarding. But if you just "want something that works ™ " side by side in your current system, personally, I wouldn’t recommend it - unless it’s hidden by some other tool like devenv (which is a great tool for reproducible developer environments).

    Anti Commercial-AI license

  • onlinepersona@programming.devtoLinux@lemmy.ml•Can I ignore flatpak indefinitely?English
    132·
    2 months ago

    Adopt nix and you will be able to ignore it forever! 😉

    Seriously though, as others have said, use whatever fits you best. I avoided snaps and flatpaks due to the increased size requirements. So many things were duplicated for no apparent benefit (to me). However, with their introduction of permissions and portals, it does seem like a safer option. Although, we’re in a phase right now where not everything is flatpakked and applications trying to talk to each other is a pain (keepassxc unable to talk to flatpak firefox librewolf, chromium, etc.).

    Now that I use nix, I have a whole bunch of other problems, but at least getting packages is quite low on the list.

    Anti Commercial-AI license