Pierre-Yves Lapersonne

Software crafter and digital punker keen on open source, iOS and Android apps. Interested in software ecodesign, privacy and accessibility too. pylapersonne.info

  • 18 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: November 4th, 2023

help-circle
  • It is always the same issues in fact. You should consider your threat model before all. Then, consider the Signal app, then your iPhone supposed to be updated, trusted, with ADP enabled, biometric lock with erasure after 10 failures, etc. Then consider your ISP, then your country. Etc, etc. You should also compare the contexts. Is an iPhone “better” than a low or middle ranges Android-powered smartphones? For sure, yes. Is it better than high-range expansive smartphones with Android ? Or Pixel ones? Not that sure. And compared to GrapheneOS or /e/? Pretty sure not that much. You can also compare messaging solutions. Is Signal better than WhatApp? Of course yes. But what about XMPP and Matrix for example?

    And what are your use cases? Remember your threat model. If you are an activist, a journalist or a whistleblower your needs may be different than a “commons citizen worried about its privacy.

    In few words, the only pain point I see is the fact than iOS is proprietary and runs non libre source code and Apple devices than APN. But Android devices are not so much different. It does not mean the solution is not private or efficient, if we succeed in defining a definition of “private or efficient”.

    In a nutshell, it could be considered as good. But not perfect.



















  • It depends of the project in fact. You should reach the community and maintainers by joining them in their Discord / Slack / Matrix / whatever. They may be able to help you.

    You can create first an issue, asking for improvements and create a discussion airy the maintainers so as to know which languages are not managed yet and if they are interested in new support. Explains also why you can bring good translations (e.g. native speaker, teacher, etc). It sill help to bring confidence.

    Then create a pull / merge request with the updated files. For example, strings.xml ob Android, .strings in iOS, etc. But beware, localisation is not only a matter of translations. You may have also to support new languages and formats for figures, currencies, or dates for example.

    Do not use translations services. Project maintainers are able to use them, and in plenty of cases the translations are not good at all or loose details.





  • Very interesting topic in fact, I am not sure a unique and perfect solution exists.

    In fact, it depends to how much you earn, how matter does for you the project, how big it is, etc. It is a question of feelings after all.

    For example you may want to donate $20 one time to a useful tool you use, but for an app you enjoy using which match your own values you may want to send each year $50. But for some people it is complicated to give money, they need to satisfy their own needs before and people don’t have all the same incomes.

    FMPOV, if the project is “just a tool” it can be a $20 one shot. If I use the software daily, it can be $50 per year. Maybe more if I feel it will help.

    About the transaction medium, it depends. Projects can use Liberapay, others PayPal or Open Collective, or also in-app purchases. I don’t use cryptocurrencies because of the transactions fees.

    Hope it helps!