lemonuri
Would anyone post a quick guide on how to run WhatsApp l using atl?
There is some documentation on https://gitlab.com/android_translation_layer/android_translation_layer/-/blob/master/README.md and I am rather sure it’s the right project, but some sort of installer would be nice. I think installing all those dependencies by hand is not a good solution in the long run. Wasn’t there supposed to be a flatpack container to be downloaded somewhere?
I’ve been using docus (izzys fdroid repo) for some time and can recommend it.
Edit: it seems it’s no longer being maintained.
Podcasts are a leftover from the non centralized and non-monetized internet of the past. Because is that most Podcasts are still available as rss feeds, so you should only ever get adds if they are spoken by the Podcasts hosts. Ate you taking about those? Only something like sponsorblock would help against those. I use antennapod (fdroid) on android to listen to Podcasts. Sine hosts always start their podcast with an add, but you can autoskip the first minute of a certain podcast with antennapod every time. It has a setting for that. Antenna pod itself is foss software without adds.
This is not bad for a start (common commands):
https://linuxblog.io/90-linux-commands-frequently-used-by-linux-sysadmins/
I have been using ps3 controllers on Linux for a couple of years now. They are dead cheap used but you might need to replace the batteries if you need to use them wirelessly. The drivers were included in popos, so plug and play basically. Just get a compatible bluetooth USB dongle, or maybe the deck already has Bluetooth? The original ps3 controllers are very sturdy and work reliably. I would still be using my old ps2 controllers, which are basically the same, but the usb adapters seem to brake way to often and wireless play is rather convenient.
I’ve been using xmpp for several years now. Even running my own server for family and friends. It’s a great feeling to be fully independent imho.
Conversions on android keeps a websocket connection open to receive messages. It’s supposed to generate very little overhead in battery consumption. The unified push app on android uses the same technique to provide other apps with pushes. So you could set conversations to be the push provider on your phone and would not need the unified push app any more. This way you would be using the same amount of battery as before.
The conversations xmpp support channel is very helpful if you have further questions: someone there will also very likely know if any apps with unified push support exist.
https://www.messenger-matrix.de/messenger-matrix-en.html
^^ Good comparison with other IMs.