f00f/eris

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.

Handbrake will probably still work if you compile it from source, but it seems like upstream isn’t paying much attention to libdvdcss support.

The version in Debian’s repo still works for me, anyway.

I’ve never used these, but I’ve come across them while scrolling through F-Droid and they seem to fit this use case:

Kotatsu
Kinoko

I’ll probably use Codeberg or another Forgejo server for my next programming project, if/when I have one that is far enough along to publish (motivating myself to get that far is a tall task). Until then, everything I’d consider contributing to is either on GitHub, or is self-hosting some other software, so I don’t have a reason to create an account yet.

https://github.com/TeamNewPipe/NewPipe/issues/11139

I’ve switched to FreeTube for now, it still works using the Invidious API. This is happening because YouTube is testing forced login to watch videos or use the API. There is a workaround it seems, but we’ll have to wait for all the major clients to roll it out.

Debian! It’s stable, elegant, and doesn’t impede customization. I distro-hopped a lot over the years - some that I ended up disliking included KaOS (severely limited software repository), Clear Linux (only way to get ffmpeg was to compile it from source) and Fedora (very slow); most I liked, and just decided to move on at some point. But I kept coming back to Debian, and eventually got to a point where instead of trying a different distro when Debian broke, I would just reinstall Debian.

I’d be interested to try VanillaOS or another “immutable” distro at some point in the future. See if they’ve matured enough for my day-to-day use.

I’ve had great experience with QKSMS on GrapheneOS. Thanks for directing me to the fork, I’m switching to it right away.

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!

I have to borrow a school laptop just to do proctored exams, because their “lockdown browser” doesn’t support Linux, and even if it did, it seems to do some things in kernel mode, so I don’t want it on my system.

Surprisingly, most classes at my university are entirely FOSS based, aside from that one piece of software, an obscure scientific program that only one assignment used, and MATLAB (which is easily replaced by GNU Octave.)

https://framatube.org/w/9dRFC6Ya11NCVeYKn8ZhiD

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.

I really liked the simplicity of GNOME To Do when it was around. The successor seems to be GNOME Endeavor, which I haven’t tried extensively.

oh it is still being updated! great.

I’m aware of FreeTube and PlasmaTube, which IIRC both require an Invidious instance. There was something called SMTube in the past, not sure if it still exists.

Nothing I’m aware of has both desktop and mobile version, but if anything there are more options for mobile YouTube clients; try NewPipe or Clipious.

Edit: SMTube does still exist. It does not require Invidious, but it does use tonvid.com.

Revolt is the most Discord-like FOSS chat app; it’s very easy to use and customizable. Rocket.chat and Mattermost do similar things and are more oriented toward organizations (the Slack/Teams Classic use case).

What makes this extra confusing to me, is that this doesn’t seem to happen to the same extent for Invidious instances. I’ve only needed to swap between two instances on Clipious, whereas on LibreTube I was hopping across their entire instance list and sometimes not finding even one working instance.

I know Okular can do at least most of that. Don’t think it’s available for Mac OS X, though.

Depends on a few factors, AFAIK as a non-lawyer. If the license allows closed-source derivatives (i.e. is permissive rather than copyleft), then anyone can create a closed-source version with all of the contributors’ changes, including the original maintainer. And anyone can choose to keep it open-source. The community contributions still to some extent belong to the contributors, though the license waives most of their rights.

Some projects are copyleft, but contributors are required to sign a license agreement (a CLA) which allows a single entity to change the license as they desire, including to closed-source - this is a good reason to avoid such projects. The contributors don’t own their work in such a case, but they can still fork the old project as it was before being taken closed source.

In a copyleft (e.g. GPL) project with no CLA, it’s illegal for anyone to make a closed-source version, and a major contributor could sue even the maintainer for doing so.

In all such cases, the change to a closed-source model does not erase the existence of the open-source code with community contributions. A fork is always possible.

You mean one that allows logging in and posting to Twitter aka X, without a significant fee? Not to my knowledge. Lately Elon and co. have been working to make third party clients completely impossible to develop, so it’s either use the official app, use the website, or quit Twitter.

If you just want to browse Twitter, I don’t know of any options for that either, but keep an eye on Nitter; currently it does not work, but they’re apparently working on a way to work around Twitter’s latest changes.