In my country we have a telecom service provider law, which states, among other things:
ARTICLE 57. - Network neutrality. Prohibitions. Service Providers shall not:
a) Block, interfere, discriminate, hinder, degrade or restrict the use, sending, reception, offering or access to any content, application, service or protocol except by court order or explicit request of the user.
The problem is always going to be bandwidth as doing any kind of communication across systems optimized for human text will throttle you: you'll trigger spam warnings, rate limits, etc - and the modern web is extremely demanding
My first priority is to get an LED blinking, and keep it blinking. Every other feature is less important.
No, needs work.
Part 1 - No system can be 100%, then you hit the Two Generals' Problem..
Part 2 - Just because you can send a bit, that doesn't mean you can send 8 in a row. So you write a protocol, then they block that protocol, you adapt, they adapt etc etc
Maybe something like ~ any system where you have any control over information flow someone has written a protocol to send porn over it.
That's just jumping of Rule 34, you could change porn to something else
The only issues ended up being that 1) WhatsApp messages are limited to 1600 characters
Concidentally, that's not much bigger than the MTU of standard Ethernet. I don't know how "transparent" the data channel is with respect to non-ASCII (and probably Unicode), but if you use one of the various binary-to-text encodings that exist, you could probably implement Ethernet over WhatsApp. ;-)