How would encryption even make sense here? Up to the server, everything is protected via TLS. And if you don't trust the server provider, you can encrypt all you want, but they can just read out the RAM of the VPS or they could have backdoored the bare metal hardware to do the same. As long as the server has to somehow work with the data in question, the decryption keys have to be somewhere in there. And what do you mean by code integration? We're talking FOSS here, how could someone prevent me from removing any "is everything encrypted?" checks in Mastodon? Also, what does the encryption on other federated instances even matter? Without having any in depth knowledge about Mastodon, your user agent will hardly be sent to other instances, and when and what you posted is meant to be visible.
jeinzi
It can't be included in the official F-Droid repos, as it is not Open Source.
It's hardly better than any other proprietary software as the FUTO Temporary License does not allow users to make modifications and share them with non-programmers. They could include ads or spyware and no one would be allowed to strip that out and share the result with others.
They also clearly forbid redistribution "directed towards [...] monetary compensation". But F-Droid has to be compensated for their server costs as well, and they ask for donations as they should be. That's why limiting commercial redistribution alone is a huge issue that would keep it from ever being called "Open Source" or "Free Software".
It can't be included in the official F-Droid repos, as it is not Open Source.
It's hardly better than any other proprietary software as the FUTO Temporary License does not allow users to make modifications and share them with non-programmers. They could include ads or spyware and no one would be allowed to strip that out and share the result with others.
They also clearly forbid redistribution "directed towards [...] monetary compensation". But F-Droid has to be compensated for their server costs as well, and they ask for donations as they should be. That's why limiting commercial redistribution alone is a huge issue that would keep it from ever being called "Open Source" or "Free Software".
What's missing from the existing ones?
There are other fast charging standards than Power Delivery. USB Battery Charging defines that when the data lines are shorted, a device can draw more current (up to 1.5A), but still at 5V. QuickCharge on the other hand uses the data lines to negotiate higher voltages, so an A-to-C cable can't protect you from that.
For Power Delivery, higher voltages are negotiated using the CC (configuration channel) pins. If you use an A-to-C cable, the A side does not have the CC pins and therefore you can't get more than 5V.
Have you checked what voltage arrives on the board if you use a regular USB-C charger? Maybe the headphones negotiate and need a higher voltage than 5V. Does it charge with only 5V supplied? (could be forced by using an A-to-C cable in case of Power Delivery)
That's what I've been using for a few years now, with SimpleCalendar (soon Fossify) on my phone. Didn't have any problems yet.
Ich kann das nicht unkommentiert lassen! https://de.wikipedia.org/wiki/Leerzeichen_in_Komposita