The lock is in the radio part of the phone, a seperate processor and firmware, accessible through a radio interface (ril). GPL doesn't apply here.

To avoid having to deal with blocked AS, you have to monitor and control you customers. I scan all my ip addrs daily in the populars dnsbls. If a user gets listed, block direct outgoing mail (automatically), tell them to use the (scanning) smarthost and offer services to fix the source.

My (receiving only) mail cluster is in the backscatter dnsbl. since I like to do sender verification (with result caching) . This hasn't affected my outbound machines/AS in all these years.

SV is only to be used for scoring, there are enough legit retards out there without valid from or misconfigured BATV setups to cause false positves when you use it for immediate rejects before data.

All interfaces mentioned are incompatible at app. levels. But all interfaces have something in common: they all have the same CLI.

You can open a xterm (which in itself isn't a KDE app) in KDE. telnet/ssh into the settop box/server. Open an adb shell to the android device (or install a termianl emulator (like connectbot)).

This can be used to sync data between them all in some way.

-phone: linux with android on top
-desktop: linux with kde on top
-laptop: linux with kde on top
-tablet (hypothetical): linux with android on top
-settop box: linux with enigma on top
-server: linux

In my case linux just works fine as OS, the actual interface to is is use case specific. Only use case for Windows in my case is games but haven't felt the need since getting a console and finding out Civilization actually runs fine with wine. YMMV.

You should read/watch more news: demand for fuel is dropping.