Late to the party, but <applause!>
I knew something was different about today. It was quiet.
I have been receiving 6 to 8 spam calls a day every day for as long as I can
remember. Thanks!
sonic.net prides itself on privacy policies. I unsubscribe to announcement mailing lists. I got this announcement anyway because it said it is "mandatory". The question was asked but not answered, why was this mandatory? I conjectured that it is because the feature was enabled by default. If this is true (as yet unconfirmed), then unnecessary enabling by default disrespects the clear preference to be left off of mailing lists. Leaving it disabled and emailing those who have said they are happy to get these notifications disrespects nobody.Guest wrote:Guest wrote:And you could also argue that, no default "on" results in an invisible loss of fusion service features as well. Assuming you're talking about those who don't read their email or what not and don't know of the service change, in which case those same people not reading wouldn't know they have the ability to have those numbers blocked. Two sides of the same coin.Guest wrote:In this case, default to "on" results in an invisible loss of service, i.e., the ability to receive phone calls from certain numbers. To me, that's the wrong default.
You know about it, so it's not invisible to you.
In hindsight, I think you are right. For those who get our newsletters, I should have enabled the feature and sent the notice. For those who have unsubscribed from the announcements, we should have left the feature disabled, silently. They don't want notice of new free features, so they would just miss out.Guest wrote:sonic.net prides itself on privacy policies. I unsubscribe to announcement mailing lists. I got this announcement anyway because it said it is "mandatory". The question was asked but not answered, why was this mandatory? I conjectured that it is because the feature was enabled by default. If this is true (as yet unconfirmed), then unnecessary enabling by default disrespects the clear preference to be left off of mailing lists. Leaving it disabled and emailing those who have said they are happy to get these notifications disrespects nobody.Guest wrote:Guest wrote: And you could also argue that, no default "on" results in an invisible loss of fusion service features as well. Assuming you're talking about those who don't read their email or what not and don't know of the service change, in which case those same people not reading wouldn't know they have the ability to have those numbers blocked. Two sides of the same coin.
You know about it, so it's not invisible to you.
Your argument is invalid. Leaving it disabled results in no change, not a loss or gain.
This is where the real power of the system will benefit customers.dane wrote:.....
Per-customer configurable call blocking is the final portion, and we will be adding that too at a future time.
There was talk of a *86 code to add numbers to a per-line blocking list some time ago, but I'm not sure where that ultimately fell on the feasibility scale. As somebody who isn't keen to wade through a phone tree or wait for a human to get off somebody's list, this would be my ideal option, personally.ravens wrote:I don't see that anyone has quite posed the question this way, but are you considering suggestions via this thread to add to the list? Are they most useful as CIDs or as numbers?
My ideal would still be the ability to add to the list as an individual user.
Thank you. I had two arguments against the enable-by-default:dane wrote:In hindsight, I think you are right. For those who get our newsletters, I should have enabled the feature and sent the notice. For those who have unsubscribed from the announcements, we should have left the feature disabled, silently. They don't want notice of new free features, so they would just miss out.Guest wrote:
sonic.net prides itself on privacy policies. I unsubscribe to announcement mailing lists. I got this announcement anyway because it said it is "mandatory". The question was asked but not answered, why was this mandatory? I conjectured that it is because the feature was enabled by default. If this is true (as yet unconfirmed), then unnecessary enabling by default disrespects the clear preference to be left off of mailing lists. Leaving it disabled and emailing those who have said they are happy to get these notifications disrespects nobody.