“3.3 Use Limitation” section of their licence file is not compatible with open source definition.

That’s vibe coding.

If you use iOS Strongbox does support passkeys.

We should support our fediverse admins and instances 💪 Support by sending money (for people who can), moderating content, submitting issues or helping the team and project ✌️

So abandon open source and move to “post open source” or ethical source might be a (sad) solution.

Anticipate technical debt and follow what Google recommends. In few words, use Kotlin and Compose.

However you should really have a look on Google guidelines. In more worlds:

• by default Kotlin and Compose
• if some logic to share between other projects in other environments: Kotlin Multi Platform (KMP)
• if shared UI: Flutter (but Google reduced Flutter teams and KMP is being better and better, so we can suppose Flutter will join the Google Graveyard

I do not know if the solutions I listed below are open source ; however as an open source contributor I am used to work with some tools depending to choice of the projects:

• Crowdin
• Weblate
• Loco

About credits, I don’t think these tools exposes in some automated way the contributors identities. However, nothing prevents you to use these web UI tools to find who contributed and list people for example in your CONTRIBUTORS files. Another way could be to edit the automated commits these tools submit to your Git repos by adding credits to the translators (with for example Co-authored-by field).

Yep, it seems it is, but it can manage KDBX files. Just wanted to share 😄

Edit: sorry, didn’t see this thread is in Android community, my comment is not relevant for this platform.

You can use also for example Strongbox (https://github.com/strongbox-password-safe)

Edit: sorry, didn’t see this thread is in Android community, my comment is not relevant for this platform. For Android I am used to Keepass2Android (https://github.com/PhilippC/keepass2android). Simple, still maintained, under libre licence GPL 3.0.

Not sure of that, maybe we need some case law or update on existing copyleft licenses. Source code generated with GenAI tool, even if their model have been trained with corpora of copyleft sources, are not (yet) considered as derivative works. What a pitty.

Could be interesting. Non-free and current GenAI tools violate copyright, we may consider some evolutions of copyfarleft licenses to forbid such use of source code in these types of tools.

And nice comment spotted there: https://fosstodon.org/@geraldew/113849843708286036

Just wanted to share for the common knowledge and the debate as I already saw here some “post open source” and content about rubbish licenses like SSPL or BSL 😉

Be sure also the issues you have in your project have the suitable labels to help future contributors to pick easily some of them, i.e. labels like “help wanted” or “good first issue”.

You can also refer to best practices listed and explained for example in Advent of Open Source so as to have a nice and user-friendly repo: https://adventofopensource.com/

Wow, you mean that Flock 😅

https://en.m.wikipedia.org/wiki/Flock_(web_browser)

BTW I hope any project won’t increase the Z version only by including Dependabot commits, it would be insane. Release must be documented, tested, with CHANGELOG updated. If some maintainers just accept Dependabot commits without checking, move away. That’s just simple crappy auto-merge.

Nice idea 👍

The project here is not under an open source license as defined by the 10 criteria of the Open Source Initiative. There is the only acceptable definition of what is open source today, and you can refer to it by clicking on this hyperlink: https://opensource.org/osd

The publication will be deleted as out of topic.

Please explain and answer the concerns as voiced by the community ; without more detail man can think your are a troll, a bot, or someone generated this answer using GentAI tools.

Your answer is not accurate as it does not bring useful details to the community which have legitimate concerns.

In addition the mentioned GitHub repository in a first sight does not contain mandatory files like CONTRIBUTING or SECURITY which does not help user be confident and have less concerns. Moreover, as the reproducibility of builds is not easy to prove event for FLOSS projects, you cannot rely on that point about open source approach. It does not seem that you are using either Dependabot, Renovate or Snyk to ensure the security of the software.

You should really bring details and make the community less worried and more confident instead of bringing that type of answers.

Next ones of that type might be removed ; the community is not dedicated to open source washing.

I agree but the solution used for the blog hosting does not expose anything to have a nice rendering of the commands. In addition, using the time to write the command helps to understand and remember. But I agree it could be upsetting.