skullgiver
[This comment has been deleted by an automated system]
The web application, which is often repacked into "native" applications, doesn't support calling. Waydroid doesn't support audio/video in/output for WhatsApp according to various Github threads.
Your best bet may be to set up Android-x86 in a virtual machine and using USB forwarding to get video working. I'm not sure what you'd need to get sound working, though.
It's also possible that Google's development emulator can run this stuff, I recall it having a webcam forwarding feature at least, but I don't know about audio or if WhatsApp will work on there.
They don't support calling in any browsers. If I recall correctly they're using some kind of native library to encrypt and transcode the video, which the browser obviously can't use. You need to get the native app on Windows and macOS.
How is the server performance of Piefed compared to Lemmy? Python isn't exactly known for its speedy web frameworks.
Sync for Lemmy is the reason I'm using Lemmy over mbin right now. The *bin experience isn't bad per se, but native apps just feel a lot nicer to use on mobile.
I don't use any apps on desktop, mostly because there aren't any that look and feel as smooth and complete as the Android apps do.
Also, I feel a bit hesitant as quite a lot of the smap I see seems to come in from *bin servers. Could be moderator actions not federating well? I just need to know for sure that there aren't any spam scripts I need to start evading after a switch.
I did try out kbin very quick a year ago but the difference in CPU usage for basic federation and browsing was quite large. With Lemmy now consistently using 15% of a CPU core on federation, I dread to think what *bin would do to my poor CPU.
Lastly, I've heard some pretty bad experiences about *bin and database issues from people who run both services. Dunno if that's been cleared out yet, but if I ever switch over, I'm going to need to make sure that's been fixed.
CentOS 7 was already approaching end of life a few years ago, and it's dead now. There are reasons not to use CentOS 8 or its enterprise counterparts, but this is still very old software for a supposedly new-ish system.
I never really got why manufacturers like these went for CentOS when Ubuntu exists. You get the same level of support, with the same packages if you really want that SELinux experience, except you can actually upgrade between versions.