HN user

baconomatic

251 karma
Posts12
Comments87
View on HN

I used to work at a place about 10 years ago where we had a cluster of six Android devices that we had used for our SMS gateway. At the time it worked fantastic, we eventually rolled off it to a different service. Somehow, we never ran into issues with carrier.

The proxy is part of our platform so the source isn't public, but the concept is straightforward and the blog post covers the core logic. Happy to answer questions about the approach if you're building something similar!

Thank you! DNS-based adoption works well for this. You point the unifi hostname at the tenant's subdomain and the Host header handles routing from there. We also have a DHCP Option 43 generator for setups where DNS isn't practical.

It would definitely be simpler, however the routing issue still stands. You would need to have a public IP for every VM, which is getting less practical. The MAC-based proxy makes it so we only need one IP and we can worry about the routing within our platform instead.

This is similar to how I approach things on my todo list as well. If the task is going to take less than five minutes just do it now and be done with it.

Do I need it? No.

Do I want to have a nice phone that is a bit of a luxury good from an ecosystem that I'm a fan of? Yes.

No one is making anyone buy a $1000 phone, but why not if you want to?