Here to follow content related to Star Trek, Linux, open-source software, and anything else I like that happens to have a substantial Lemmy community for it.

Main fediverse account: @f00fc7c8@woem.space

  • 0 Posts
  • 7 Comments
Joined 1 year ago
cake
Cake day: August 4th, 2023

help-circle
  • Yeah, only thing I can think of is the few banking apps that don’t have web versions.

    I was lucky enough to have all my banking and 2FA apps work perfectly on GrapheneOS. The only app that gave me a significant amount of trouble was iClicker, which my school uses for attendance. That was fixed by enabling Google Play location services, and there was a (fairly expensive) alternative anyway.

    I did have to buy a new phone to use Graphene, because I got my previous one as part of a carrier’s cell plan, and it had a locked BIOS. Though I think the purchase was worth it, and just moving my SIM card from one device to another was enough to get it working.






    1. Create a source control repository containing all your code, and publish it to an online code forge. GitHub’s docs might help with this: https://docs.github.com/en/get-started/start-your-journey
    2. Choose an open-source license and add it to the repository as a LICENSE file. If you want to require any projects that build upon yours to be open-source too, the GNU GPL is a good choice. If you want to allow proprietary programs to include your library without releasing any source code other than that which is directly based on yours, the GNU LGPL is good for that. If you want to allow people to do whatever they want, even use all your code as the basis of a proprietary program without credit, the Unlicense is a good choice. There are a lot of licenses with different degrees of “copyleft” and attribution requirements in between. Technically publishing with a license file is all you need to do, but there are more things you should do.
    3. Create a README text file describing what your program does, and instructing users on how to compile and run it. Consider including more detailed documentation on how to use it, as well.
    4. Clean up your code and file layout so that it’s as easy as is feasible for other programmers to understand.
    5. Promote your project to whoever you think might find it useful!

  • Unfortunately, the state of Android music players is not great. Currently I have two FOSS music players installed: Metro Music Player (the F-Droid version of Retro Music Player) and mucke. mucke has a ton of really cool features that improve the shuffle experience but it’s actually worse than most apps at pulling album art. Retro/Metro has beautiful UI, and has pretty good features for customization, but lacks the cool features mucke has and is less stable. Both have more than one annoying bug, but it took me a while to find music players that had this few dealbreakers.