When an eSIM in a phone is provisioned to a carrier, with some plan, usually it does have a phone number and could send and receive SMS. Though yes you are correct, if you're only thinking of a single chip (eSIM)…
This service wouldn't be useful to me because the number reputation seems poor. Actual delegation would not rely on pooling numbers for increased user per SIM card. It's one client per SIM card.
Ensuring that everyone is enslaved by their telco and becoming more dependent on their data collection device (phone) on them at all times and subsequent payment infrastructure used to facilitate etc. Avoiding saying no…
Great unanswered question. Nothing mentions "eSIM". I really have no idea. Speculative questions: Maybe there are some number switching, chip level protocol mitigations inherent to the standard? Maybe carriers can push…
You're right - It shouldn't matter - having separated accounts makes sense if you're concerned with putting all your eggs in one basket.
[dead]
Many clients are dependent on me to ensure their accounts are safe and backed up - lockouts with no recourse are real. I will not tolerate having a singular SIM card being the point of failure across a client pool,…
I need a reliable way to manage OTP codes for many clients, having one SIM is just not good enough. Partially the same problem because I've run into limits - having a separate card is just less likely to be a problem.
Mitigating account lockout risk across lots of clients. Separate SIM for each client, having account lockouts are unacceptable. Yes, I've had problems with no recourse.
What about the sim farm I use to delegate my SMS OTP codes to? No VOIP numbers don't work for everything, no using the same SIM card doesn't work, no I don't want to worry about running dozens of phones with batteries…
When an eSIM in a phone is provisioned to a carrier, with some plan, usually it does have a phone number and could send and receive SMS. Though yes you are correct, if you're only thinking of a single chip (eSIM)…
This service wouldn't be useful to me because the number reputation seems poor. Actual delegation would not rely on pooling numbers for increased user per SIM card. It's one client per SIM card.
Ensuring that everyone is enslaved by their telco and becoming more dependent on their data collection device (phone) on them at all times and subsequent payment infrastructure used to facilitate etc. Avoiding saying no…
Great unanswered question. Nothing mentions "eSIM". I really have no idea. Speculative questions: Maybe there are some number switching, chip level protocol mitigations inherent to the standard? Maybe carriers can push…
You're right - It shouldn't matter - having separated accounts makes sense if you're concerned with putting all your eggs in one basket.
[dead]
Many clients are dependent on me to ensure their accounts are safe and backed up - lockouts with no recourse are real. I will not tolerate having a singular SIM card being the point of failure across a client pool,…
I need a reliable way to manage OTP codes for many clients, having one SIM is just not good enough. Partially the same problem because I've run into limits - having a separate card is just less likely to be a problem.
Mitigating account lockout risk across lots of clients. Separate SIM for each client, having account lockouts are unacceptable. Yes, I've had problems with no recourse.
What about the sim farm I use to delegate my SMS OTP codes to? No VOIP numbers don't work for everything, no using the same SIM card doesn't work, no I don't want to worry about running dozens of phones with batteries…