IPhone users have a weird obsession with Blue bubbles. The rest of us find it childish and annoying. They refuse to use any messenger other than iMessage.
I have a friend, not currently on iPhone, who was having trouble with SMS (note that SMS has a known message failure rate of about 10%+). He refused to switch to another messaging app, doesn’t want to have multiple places to message from. 🤦♂️
This is the mindset of iMessage obsessors. Frankly I see it as pretty juvenile. They don’t want to put effort into solving a problem.
This same person always has dozens of notifications sitting in the notification shade. Stuff you just don’t need to see, that Android lets you silence. Or just app notifications. Well no wonder he doesn’t want another messenger, with that much garbage he wouldn’t know he got a new message.
Sounds like it transfers the ID Out-of-band, so that’s good, does the desktop get the chat history then? (It’s possible it pulls chat history from the phone).
Oh, I agree with the closed source issue. That makes it a no-sale for me.
I carry an iPhone for work, corp IT manages it, I use little more than comm stuff there, so theres no advantage to having an Android. (Before that my work phone was a blackberry, because I need work calls, email, messaging, etc to just work, and you couldn’t beat the battery life).
My personal is Android, because I want the tools I can use there.
Two very different use-cases.
And I really dislike iOS UI/UX, the limitations are very constricting. But for the basics it “just works”, but it isn’t something to recommend for privacy.
I assume when you say externally you mean via Tailscale, but without running Tailscale on each container/service?
What I currently do is run Tailscale on a few workstation-type devices, but everything else in my network doesn’t run the Tailscale client (partly because things like printers, outers, etc can’t run the client, and it’s less convenient for things like servers).
Those type of devices can be accessed by running one Tailscale node as a Subnet Router. This device is then able to route traffic to it’s subnet. Currently I use a Raspberry Pi for this.
My Pi also runs PiHole and acts as my DNS server, so it can name resolve local resources, though I don’t think this is required, because Tailscale has its own DNS resolution called Magic DNS. So your Subnet Router should be able to resolve those names anyway (going off memory here, so be sure to check the docs, I may be misremembering how it works since I use the same device for DNS).
You don’t even need Tailscale on a remote device to access your LAN - if you enable the Funnel service, you can provide an inbound encrypted path to specified resources.