microG: Android (almost) without Google – our interview with the developer

The use of microG means that on smartphones, you can enjoy the comfort of Android without being spied on from front to back. It’s a sort of „castrated“ Android, where hardly any data are transferred to the Google servers. How does Google manage to enforce control over the mobile operating system Android with all its might? What does it take to stand up against Google? That and much more, we will find out in our interview with the inventor of microG, Marvin Wißfeld.

👉🏼 👉🏼 Read more:
https://tarnkappe.info/microg-android-almost-without-google-our-interview-with-the-developer/

#interview #microG #android #google #DeleteGoogle #Marvin
📡@cRyPtHoN_INFOSEC_DE
📡@cRyPtHoN_INFOSEC_EN
📡@BlackBox_Archiv

microG developer will be back in 1-2 weeks

https://gist.github.com/mar-v-in/c8254168c63361c5094de13a7afea344

Hello everyone,

As many of you have noticed there had been very little involvement of me with microG over the last months.

tl;dr: I'll be back for microG work in 1-2 weeks.

I am mostly unemployed since beginning this year. There are several reasons for that and things not working out as expected, but I am not completely unhappy about that.

Another open-source project I am maintaining had it's first release. This was originally planned to happen by end of last year, but that didn't work out as expected and thus took most of my time in January.

As I need to have some income, I worked intensely for two weeks in early February as a freelancer. This worked, but turned out to be more exhausting than expected, so the fourthcoming week I wasn't actually productive.

Due to reasons™ (not to be named or speculated on) I wasn't able to work productively in most of March.

I did work on several smaller and mostly independant things. For example I contributed to the advancement of OMEMO protocol (the end-to-end-encryption protocol of XMPP), including the first implementation of the new version.

These things were collaborative efforts and often long planned in advanced, so I handled them with priority.

Another open-source project I am maintaining is preparing for it's first release. This didn't happen yet, but hopefully will happen very soon.

I do have several things done for microG that never made it into any repository:

Major changes in UnifiedNlp (planned to become a 2.0 release).
Major refactor of GMS repositories (#859)
Various fixes for applications crashing.

As there is potential for these changes to conflict with pending PRs, I didn't felt comfortable with merging them just now to reduce the overall workload.

Now I heard that several people are working on forks of microG. That's great to see. But please do create pull requests and/or document in any other way what you changed, so I can merge/catch up as soon as I have the time to do so.

I'd also like to mention again that I am very open to grant contributor rights to the main microG repository to more people. "Requirements" are you are willing to contribute more than once, review and merge pull requests and fix issues arised through the changes you introduced. Please let me know through any means if you fit in here.

Marvin



Here are some ways to support microg development economically:
https://t.me/NoGoolag/2479


📡@NoGoolag
#microg #developer #marvin