did we cover Manifesto 2025: the freedom to communicate belongs to us yet?
. https://jami.net/jami-survival-kit-your-backup-solution-in-case-of-internet-failure/ .
did we cover Manifesto 2025: the freedom to communicate belongs to us yet?
. https://jami.net/jami-survival-kit-your-backup-solution-in-case-of-internet-failure/ .
Kotasu:
In light of recent challenges — including threating actions from Kakao Entertainment Corp and upcoming Google’s new sideloading policy — we’ve made the difficult decision to shut down Kotatsu and end its support. We’re deeply grateful to everyone who contributed and to the amazing community that grew around this project.
Butterfly 2.4.1 is here with the biggest set of bug fixes and improvements in a long time.
Highlights:
Delayed autosave
Thumbnail capture improvements
Template import and export improvements
Improved PDF handling
Drawing improvements
File view and UI improvements
Multi-input and tools improvements
Stability and performance for large files
Read more here: Butterfly 2.4.1 released
This week there was Droidcon Kampala happening on the 10th to the 11th of November. I had the opportunity to talk about F-droid and how users can distribute their own apps using F-droid and Repomaker. The talk was aimed at college students interested in Android development.
The slides are here: Copy of Distribute your own Apps with F-Droid - Google Presentaties
Many thanks to the Droidcon Uganda team and the F-droid team for making an amazing project. \o/
. Releases · jurihock/voicesmith · GitHub An update after 11 years.
Mensa new maintainer. GitHub - famoser/Mensa: eth & uzh mensas in zurich .
. status · Issue #16 · researchxxl/syncthing-android · GitHub Syncthing fork is transferred to other devs.
## Reproducing and testing together
In the process of doing all this development work, we ran mass rebuilds of the whole collection of apps, killing two birds with one stone. First, it served to test our new build automation with the existing apps, and second, it showed us with apps are reproducible. For the apps that were not reproducible, we have looked into fixes in our stack, in upstream build tools, and in the app themselves. and what kinds of issues
We mapped out all the issues we have encountered caused by running builds in VMs versus containers. There are two classes:
Those that are sensitive to CPU/RAM configurations, since VMs and containers present CPU and RAM limits differently.
Builds needing privileged calls that containers normally do not normally support in production setups (direct writes to sysctl or /sys/devices/system/cpu/)
The method for presenting CPU and RAM limits are implemented differently between virtualization (e.g. libvirt) and containerization (e.g. Podman) are different, and are not interchangeable. This can lead to build differences. We currently know of no workaround or fix for this.
we’re up to 68% reproducible builds now too
. Roland Horsch Horsch / Dib2Qm · GitLab Deprecated.
Some great f-droid.org fixes from @ray2c .
. The Fight for Android's Open Ecosystem (F-Droid Interview) - Techlore.TV - Digital Rights For All .
can you link to which text you want highlighted?