_jsnk

This is an exaggerated take. I've been running Signal on LineageOS for years across at least 5 different phones in exactly this manner with no Google services installed. I'm currently using a Motorola G84 and charge every 2 days with moderate usage; Signal is my primary communication method with family.

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.

I was excited to try this.

I'm bummed at the Google captcha forced down my throat and api.anonchatgpt.com consistently returns HTTP 500 when posting queries.

I also recommend the SmarterEveryDay video[0] where they rig a bike to turn the opposite way than it is steered.

[0] https://www.youtube.com/watch?v=MFzDaBzBlL0

I recommend Tyler Ley's youtube channel[0] entirely devoted to concrete. He has an episode[1] addressing GFRP that might interest you.

[0] https://www.youtube.com/@TylerLey

[1] https://www.youtube.com/watch?v=thUZImUTZn0

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.

Regarding authorizing suspect logins, the only thing that would successfully authorize my email client access was visiting https://accounts.google.com/DisplayUnlockCaptcha

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)

> speedtest-cli ... can't seem to ever report higher than 300mbps.

I routinely get 700-900Mbps reported using speedtest-cli from centurylink fiber. My bottleneck is the CPU on my router running openwrt.

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.

The cdable_vars bash option is among my favorites

  shopt -s cdable_vars
  p=/some/path/you/cd/to/a/bunch
  cd p

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).