Okay, as this has come up more than once, really what is needed is not just forwarding, but proxying. Is there actually software for Android that will do that?
I think you need to consider the user interface here.
Someone with the phone number A texts a message to number B. Say the message is forwarded to number C. In order for the user with device C to respond to A, it would first be necessary for B to rewrite the message text to say that the message came from A. They then the user of C needs to make sure to manually send the message to A. Now, depending on how savvy the user of A happens to be, they might not find it completely disorienting. If you were to attempt to send to both A and B via a group text that might help some. But then you'll also be getting extra copies of your messages fed back to you from B. Unless the forwarding on B is also smart enough to filter them. And then there is still the problem that in future conversations, the user of A might just send messages directly to C, bypassing the other forwarding recipients of B, defeating the point of having a shared point of contact.
So forwarding has considerable awkwardness and room for error.
I suppose I thought your use case was mainly getting alerts and 2FA stuff and wouldn't require replying back so often.
But in any case I think proxying is absolutely possible and would b easy to setup, especially on a rooted phone.
The first thing that comes to mind is setting up a web frontend, so messages would be forwarded to your s and your wifes phones, and then you would access a web frontend hosted on the phone with the $ simcard with a 'real' number which would send out the reply sent via the web form.
That also looks quite intriguing as well. Though perhaps a bit more industrial than I might need, there is definite potential. I would need to investigate which have more friendly user interfaces. While I might be hip to using "AT commands" to "Send/receive batch SMS up to 300 characters", my wife would perhaps not find that amusing.
Forwarding is only half the requirements here though. Sending responses from a different number will generally lead to confusion, and further messages from the sender will not necessarily be shared. Though maybe if the sender is savvy enough with group texting it might work out okay.
To clarify on "grandfathering": our use of the service predated our provider's involvement with TCR. Any new accounts created with the provider now requires you provide complete information on your business and its purpose to qualify for the product. As our account existed before that time, and they still wanted to take our money, they didn't cancel our account. Yet.
I suppose I should have been clearer, while I don't like spam, the issue is that TCR is about much more.
There was some discussion about dual SIM solutions with a cloned SIM in a different thread. But even ignoring the potential for incurring our carrier's wrath, with not all messages will be available to both parties, it doesn't meet the minimal functional requirements.
Why are writing the same thing to me twice? I understood it the first time bud.
I don’t see how you could incur a carrier’s wrath. You could spend a few minutes on google and find many carriers talking about it. They get paid.
As for your idea that they will block it, you’ll have to cite some sources for that. I used this for the first time over twenty years ago and had zero problems, and you can still do it now. You’re inventing problems now.
I’m not going to reply anymore because your requirements are extremely unclear and I’m not really here to provide free tech or developer support. This is just a fun place I occasionally contribute to.
If nothing else works, build it yourself. It wouldn’t be too difficult to get something basic built up and you’re good at inventing problems so you might be great at solving them. Have a nice rest of your day and best of luck with your project.
I hadn't caught that you had responded in multiple locations.
If you see this as inventing problems, then it is clear you don't understand the use case.
Even ignoring the issue of carriers cracking down on SIM cloning, as you've said not all messages will be visible to all participants. So that makes it DOA.
You also clearly do not understand that the issues here are not all technical. Sure I could definitely bang out something using Twilio to send and recieve SMS, etc. Except Twilio requires you to comply with TCR. So again, that is DOA.
Sure if I was really adventurous I could buy tens (hundreds?) of thousands of dollars of telecom equipment and work on then have to negotiate peering with other providers. But you know, I figured I might ask on Hacker News as start.
Yes, I should have perhaps more clearly stated that while the ostensible goal of TCR is reduce spam, it is at least as much about control and rent seeking.
I think that may have actually been the exact original motivating use case. That the bank kept trying to send 2FA codes. Though I recall that may not have worked at first as our provider was probably still classified as not being a valid destination.
I'd need to check, but I'm on team spaces and I think she is on team tabs.
I believe I had come across Missive while investigating. I will admit I haven't tried signing up. But given that it is marketed towards businesses, I expect as soon as one does they'll require you to provide all the information you would need to be registered as part of TCR. If this is incorrect, let me know and I'll dig deeper.
reply