>Just think, if you hadn't used a proprietary messaging solution as your default contact method, you'd be able to easily control how you receive the messages.
He would also have lost other benefits, such as convenience, automatically using data instead over SMS for casual chatting, using the method he damn wanted, etc.
What having a problem like this justifies is FIXING the problem, not not using the technology in the first place or some ideas about proprietary and OSS.
Not to mention those are beside the point. Even if he DID use a proprietary messaging solution, he might very well have the same issue. It's not an issue that stems from being proprietary, it's an issue that stems from a stupid caching implementation. If some FOSS mobile chating app had the same bug, he would have been bitten by it just the same.
He would also have lost other benefits, such as convenience, automatically using data instead over SMS for casual chatting, using the method he damn wanted, etc.
What having a problem like this justifies is FIXING the problem, not not using the technology in the first place or some ideas about proprietary and OSS.
Not to mention those are beside the point. Even if he DID use a proprietary messaging solution, he might very well have the same issue. It's not an issue that stems from being proprietary, it's an issue that stems from a stupid caching implementation. If some FOSS mobile chating app had the same bug, he would have been bitten by it just the same.