nativeforks

I've been using 1.1.1.1 for performance rather than privacy. Maybe I should revisit that decision after reading this.

The browser-first approach is a bigger deal than it sounds. Every time I've looked at reverse engineering, I got stuck somewhere between "install this ancient compiler" and "patch this SDK". Being able to just open a tab and start experimenting removes a huge amount of friction.

Exactly, you got it

>Maybe look into dual licensing.

No, no, not at all as a FOSS developer.

> I’m planning a non-intrusive in-app prompt to remind users about donations something subtle, because many users forget once they start using the app, rather than only seeing the donation info in the README.

As I mentioned previously, the above approach seems to be well enough and good.

Thanks! I feel the same there’s a lot of room for small, focused utility apps that do one thing well without ads, trackers, or dark patterns. That’s largely the motivation behind this project too. Competing on care, simplicity, and respect for users really feels like a worthwhile direction.

Thanks for the suggestion, that’s a fair point. I currently rely on a couple of mainstream platforms mainly to keep things simple, but I do see the value in more open and permissionless options like Bitcoin/Lightning or Monero.

I’ll definitely consider adding at least one of them going forward. Really appreciate the willingness to support.

Yep, if it were close to the power line, it might cause accuracy loss, but you can obviously easily find the compass accuracy in the top app bar, and if it goes 'very low', the alert dialog automatically popsup to notify you to recalibrate it.

The reason I included that note is that, as an open-source developer, I’ve seen many projects that weren’t actively maintained get picked up by bad actors as they modify the code and publish it on Google Play with ads or IAPs. I wanted to discourage that.

Other than this notice, MBCompass is fully licensed under GPLv3 or later.

Yep, I’m aware that many FOSS projects use in-app payments, but for MBCompass, I want to keep it free on every platform, regardless of the audience. Without funding or community contributions, it’s hard to maintain a FOSS project with meaningful features and improvements, rather than just vague “bug fixes/version bumps.”

As a FOSS advocate, I started this project as a community contribution to address the gap between user needs and available apps.

I can maintain it long-term without major contributions, but support really helps (especially maintaining in different apps stores). I’m planning a non-intrusive in-app prompt to remind users about donations something subtle, because many users forget once they start using the app, rather than only seeing the donation info in the README.