It wasn’t really that kind of thing and I don’t think that I would see it that way. You may still be right, but I think we are not as different as you are supposing.
The exact situation in that particular case that I was describing was basically that:
- I happened to have my modem switch on as well as the wifi switch, despite being indoors. A lot of times I turn on modem while on the go, and wifi while indoors, and keep the other of the two switches off
- I initiated a transfer of a substantial portion of my personal savings within my bank into a different type of account
- About 30m after the transfer of money, a bank official tried to call my number. [After I did get a hold of him, he even said most people he calls for this kind of thing take a week to reply so he appreciated that I called him back]
- When he did call, I heard the ringing of the phone because the modem was unusually on at that time, so I figured I would go ahead and break my focus and try to answer. I switched on the microphone that I usually have off, so that I would be able to talk to this bank man, and I then pressed the Chatty icon to answer the call
- The call connected and I said “hello” into it a few times, hearing only dead silence in reply. “I guess maybe my phone is having trouble,” I said into the receiver, and then hung up. I didn’t recognize the number, and I didn’t know who had called, although I probably suspected that it might have been the bank. But I surely didn’t know that at the time.
- Chatty showed an incoming call a second time shortly after. It was the same number again. I was frustrated again, wondering whether Chatty would function as expected if I answered this time. I didn’t know. I wasn’t sure if I could trust the current state of things, because it had just reduced my trust in it from the previous call. So, I let this call go to voice mail.
- Later, I called back the bank guy a different way, using a different proprietary system whose functions maybe aren’t even worth focusing on, because ideally they shall be eliminated from my life in the long term.
- When I talked to the man, he said that in the first call he could hear me say, “Maybe my phone is having a problem” even though I could not hear him at all. So, notably, it seems like that is not the kill switch that is a problem in that situation. It’s a software failure. We did it wrong. Collectively, as a community of people who try to build free software with special licensing and ideology behind it to share with each other, we failed. Or at least I did, because I haven’t taught myself even the proper channels or places to report this kind of failure, or the proper log to read which dang file descriptor of sound information was enumerated stupidly, or what it was.
So, in particular, I would even suggest that you will at some point most likely have a similar problem – if indeed Chatty sometimes cannot playback audio – even if you only make outgoing calls and never incoming calls. Saying that your policies are different from mine, I would figure, is almost just a distraction from the fact that these systems failed and it wasn’t the hardware switch being switched the wrong way, and it wasn’t even really a failure for me to be available. It was a failure of the “call function” that I did not write myself, so I did not study how to debug. And anybody who uses the “call function” is liable to potentially have this problem until the bug is isolated and resolved.
Maybe I’m wrong. Maybe you only constrain yourself to using your favorite XMPP app for calls, and so Chatty just simply doesn’t matter to you. Even if so, I don’t think that stops us from continuing to discuss the sort of problem I was facing, because it is a seemingly real problem with the software of the Librem 5 and also not really dependent on any desire whether to be available or not. I assume I would have had the same problem if I didn’t notice the call until 5 hours later, saw a missed call, and then called that guy on the Librem 5. Some how, some way, there is a bug in Chatty and it dropped all incoming audio data. The cause was probably either (1) that I switched on the mic switch prior to answering the Chatty call but after it registered an incoming call was available, or (2) that I might have plugged in earbuds and expected them to be plug-and-play while Chatty was already open waiting for me to click the button to answer a call. But I have not spent further time to isolate that.
So, I think that a difference of opinion on whether to be reliably contacted is one thing, but I almost feel like it is a distraction from the more important problem: whether I only make 1 outgoing call with the phone features per year, or whether I take 1000 incoming calls per year, until the free software community can identify, record, reproduce, and fix all the bugs in Chatty I believe there truly is a value to having a “backup” or “second system” to check for bugs. And maybe some people only use data, and only use XMPP, but for those who do occasionally use the other features it is valuable to have a second system to continually verify that they are actually working, at least until we reach a future where they are always working reliably for the long term (at which time, I’m sure, big telecommunications companies will try to make pull requests to break them under the guise of legitimate contributions, and it will be up to us to turn them down).
Now, maybe I spent too long over-focusing on how I am seeing this differently than what you described, but I really think there is an issue that could be considered here that isn’t simply a matter of throwing up our hands and saying that I’m compromised/unable to achieve freedom, simply because I feel there is utility to me to have texting and calling that always works in some way – or that failing, that I can at least always know if I missed something, at least at those times that I choose to look.
And, all of this, distracts away from my other problem, which is that I don’t want my Librem 5 to send messages to Mozilla Location Services [Powered By Amazon] anymore, so that Amazon will not have a location history of where my device has been!