4 ms·
I'm not sure e2e-encrypted applications can be reasonably expected to handle this. The bytes they are transmitting are effectively not copywritten, and cannot
by bin0 7y ago
I'm not sure e2e-encrypted applications can be reasonably expected to handle this. The bytes they are transmitting are effectively not copywritten, and cannot be deciphered into copywritten information without something which the company does not have. I could also see a huge increase in client-side processing requirements due to this, meaning this could translate to substantial financial loss and an undue burden.
- kccqzy 7y agoOn the contrary, client-side processing means it is burning the battery in users' devices, not consuming any cloud resources. It could very well be cheaper for the companies to implement.
- mycall 7y agoIf it is running on my device, software can be cracked. This will prove fun.
- darkpuma 7y agoThat some technically proficient people will find ways around it is beyond doubt, however it may prove to be an effective system for information control despite that, if the common user finds it difficult to circumvent.
- TotempaaltJ 7y ago> The bytes they are transmitting are effectively not copywritten Eh, that's too limited a definition of copyright. Technical implementation doesn't really matter to the law; only whether or not you are in fact transmitting copyrighted information. That is decidedly the case: the author is knowingly sending a certain piece of content, which the receiver can then access. Here's a great article on it: https://ansuz.sooke.bc.ca/entry/23 https://ansuz.sooke.bc.ca/entry/23