653 karma · joined August 19, 2022
Many of then have an example image attached.
I translated this one with DeepL for you. https://www.moses-verlag.de/black-stories-8/106746
(Trigger Warning Eating Disorder)
Translation (story): > The queen
> After the meal, the queen died. If the guests had been more boring, she would still be alive.
Translation (solution): > A beauty queen (like e.g. Miss America) was invited to dinner every night after her election. To maintain her weight, she stuck her finger down her throat after each meal. At a reception she was involved in many interesting conversations and forgot to retire to the toilet after the main course. Her overfull stomach ruptured and she died as a result.
https://w3c.github.io/webappsec-change-password-url/response...
> Google Camera can take full advantage of the available cameras and image processing hardware as it can on the stock OS and does not require GSF or sandboxed Google Play on GrapheneOS. Direct TPU and GXP access by Google apps including Google Camera is controlled by a toggle added by GrapheneOS and doesn't provide them with any additional access to data. The toggle exists for attack surface reduction. Every app can use the TPU and GXP via standard APIs including the Android Neural Networks API and Camera2 API regardless.
> We aim to reduce the benefits of Google Camera compared to GrapheneOS Camera over time, especially on Pixels. Many features of Google Camera will end up being available for GrapheneOS Camera in the next year or so via CameraX extensions including more aggressive HDR+, Night Sight and Portrait. Video features such as slow motion and time lapse are likely further away than within the next year. These video features could potentially be provided via CameraX vendor extensions or could be implemented via our own post-processing of the video output. Panorama, Photo Sphere, Astrophotography, Motion Photos, Frequent Faces, Dual Exposure Controls, Google Lens, etc. aren't on the roadmap for GrapheneOS Camera. Video frame rate configuration and H.265 support should be available for GrapheneOS Camera in the near future via CameraX improvements along with DNG (RAW) support in the further future.
All the info: https://grapheneos.org/usage#camera
I don't know much about android and kernels, but seems like only rooting your phone still would not be suffice.
https://unifiedpush.org/users/faq/#will-unifiedpush-ever-wor...
The whole point of unifiedpush is, that earlier when people did not want to use Google services in their application, they all needed to listen/poll on their own to some endpoint from the Application backend, which can be quite battery draining when you have multiple apps that do this. With ntfy you have only one app that listens/polls for these and can efficiently send them to the apps which want these notifications, exactly like Google Firebase notifications
It contains a google library, but can't find what exact library they are referring to, as the link they've provided is dead.
EDIT: Found it in an old commit from around that time the comment was made https://github.com/massivemadness/Squircle-CE/blob/1818d3904...
A googleplay "appupdate" library, I don't have knowledge about App development, but I don't see how this library is needed in the fdroid version?
..."Lastly, FeverPhone uses root-level access for reading a broad set of thermistors and a custom user-debug Android kernel for accessing raw touchscreen capacitance data. These requirements limit FeverPhone to phones with fine-grained sensor access. Temperature data from the battery thermistor is more readily accessible but did not yield comparable performance relative to temperature data from other thermistors. Still, future work could explore a more accessible version of FeverPhone with specific considerations paid to the battery thermistor. Similarly, the TouchEventAPI is publicly accessible at the cost of coarse-grained information about touch location. The use of this API in place of the raw capacitance data could be explored in future work."
[0] https://www.borgbackup.org/ [1] https://torsion.org/borgmatic/
I use urlchecker [0] for this on my phone and have it set as my" browser" that way, every link i click on, I see a popup with the link and with one or two button presses I can remove the tracking parameters and/or unshorten it and then open it. Works like a charm. May be to much friction for some, but I like it.
[0] https://www.f-droid.org/de/packages/com.trianguloy.urlchecke...