I do something like this. I run wireguard in a container along with dante-server (a socks proxy daemon). I then configured a Firefox profile to connect to the socks daemon running in the container.
This way I have a single browser profile that is routed through Mullvad while everything else works normally.
A fair bit of the stability of a bicycle (especially at low speeds) is due to the fact that you have a human holding onto a bar that behaves exactly like a thing that a human would grab onto to steady themselves. If you grab this bar and rotate it clockwise, then you yourself will rotate anticlockwise - and that is true whether the bar is the handlebars on a bike or a random bar fixed on a wall. Holding ourselves steady by grabbing onto something is something that humans have a remarkably effective and quick feedback loop for, which is why bicycle riding comes naturally once you get over the fear of falling off and just do what feels right.
Rigging the handlebars to turn the wheel the other way cancels out that automatic feedback loop.
I'm very upset by this decision. I've been using Signal as my SMS app for a very long time.
Messages that I would have sent via SMS currently will automatically get sent via Signal if the person I'm sending to has started using Signal without my knowledge. This has happened in several instances where I was pleasantly surprised to see a friend had started using Signal. Now that I'm forced into a separate SMS app, this will no longer be a possibility. I certainly won't be firing up Signal to see if a contact has joined before sending them an SMS.
This. Now you have to remember who is in Signal and who isn't. All because apparently the double-check mark for messages between Signal users and the unlocked icon for SMS messages is too hard to comprehend. SMH.
If I understand this, if I use SMS, I can send to everyone. If I use Signal, I can send to Signal users only. But I don't remember who's on Signal, and who's not. So I guess I will stop using Signal.
If I want to message someone I open the contact and click on one of the messengers that are listed for the phone number. Why would I leave the memorizing to my brain?
Huh. I've never used contacts that way. I suppose it could work but that's a new extra step. My Contacts list is gigantic and full of bullshit I don't care about because it's sync'd from work and flooded with people I don't know. Usually I just find the conversation from the chronological list (which is more of how I remember things). Maybe there's some way to sort contacts by recent use? It just seems like that's leaking metadata to push all of that context into Contacts. Anyway that seems maybe plausible if it can index or springboard to convos in other apps.
Theoretically couldn't an Android app be built using notification access to track notification history and coalate messaging notifications (combining notifications from all/selected/configured) messaging apps? That sort of a "messaging hub" could be even better, frankly.
What'd be even better is if there was a central "messaging" interface where all the various implementations can register as messaging service providers and all your conversations end up in one place.
Off topic slightly, but it amazes me how much SMS is used in outside my country (maybe just US?). I literally never SMS any personal contacts, usually WhatsApp. Even business stuff, sometimes initial contact may be SMS and then could often move to WhatsApp.
I use signal with a small circle of friends, but no one I know uses SMS anymore.
I have WhatsApp installed for two different group chats, Google Chat for another couple of group chats, but apart from that SMS is the standard here (which means opportunistically iMessage / Signal). I'm in Australia, where SMS typically have no per-message cost (the only thing that's charged per use on most mobile plans here is data and international calls).
In Ireland, an SMS used to cost 13c, if I remember correctly.
So when apps like viber, WhatsApp, etc came on the scene, people jumped on them quickly and completely stopped texting.
This was before they even had voice calling.
With voice calling, it is also popular, as you can call someone irrespective of what country they are in and not worry about roaming or international call charges (even though in the EU now we do not have roaming charges anymore).
Some people even use WhatsApp for normal calls over normal cellular calls!
I have been receiving notifications that a person in my contact list is now using Signal for years.
Apart from that, your use case has another possible issue.
If a person stops using Signal, your messages will go to the void until Signal actually removes the user and your client switches back to SMS. This has caused a lot of confusion for some of my friends when I switched my signal account to a different phone number.
I think it's more reliable to use Signal for Signal.
Well this is also a problem. As it's said in the article, you risk getting charged for an SMS, that in some countries are expensive, most mobile plan in my country have 30+Gb for 7 euros at month, but SMS are 20 cent *EACH*. Practically in my country nobody uses SMS, and SMS are used only to receive 2 factor authentication codes (and spam).
Anyway a normal person already uses multiple messaging applications: WhatsApp, Telegram, Facebook Messanger, Instagram direct messages, the good old email, SMS (I guess somebody they are still used reading the comments), adding Signal it's not that big deal.
I finally set up two factor auth in gmail using FreeOTP and have Fairemail (fdroid version) configured using an app password. (I run LineageOS with no Google services installed or account setup so the OAuth method isn't an option for me)
From speedtest's official cli program, on my 2.5gbase-t connected machine I get 2200mbps up and down.. but from the open source speedtest-cli I get 300-350mbps.
(Here, I only got ~900mbps because I was running from a raspberry pi with a 1000BaseT link).
I've been running OpenWrt on my original r2 as my primary router and it has been rock solid. (both snapshot builds and now builds from the 21.02 branch). The default builds for the r2 available for download from OpenWrt are very bare bones so I don't recommend that route.
The onboard mediatek wifi isn't usable but using a mini pcie ath10k supported wifi module has worked great.
It definitely wasn't easy initially tracking down info for getting things working. No argument there.
I'd be happy to share my OpenWrt build config for the r2 for anyone interested.
I was successful in using this guide: https://aws.amazon.com/blogs/opensource/open-distro-for-elas... to setup Amazon's Open Distro version of Elasticsearch/Kibana. I had to modify it to work with Elasticsearch 7.x (which corresponds to Open Distro 1.x). This guide was written for Elasticsearch 6.x (which corresponds to Open Distro 0.x).
This way I have a single browser profile that is routed through Mullvad while everything else works normally.