kimusan

Some time ago the Tidal music streaming service stopped working at my home. I wrote to their support but it took weeks to get a reply. Initially they told me that my IP was on a blocking list (RBL) and this was the reason. I got removed from that list (it was some irrelevant RBL nobody uses) but Tidal did still not work.

I eventually got one of their more tech savvy supporters (like that is a thing - NOT!) which told me that my IP was blocked because somebody was abusing it for a Tor Exit node. He even linked to a page that listed my IP as having a tor node (clearly stating that it was NOT an Exit Node). I told them that the Tor Node was mine and left there intentionally to support the Tor Network + for my network tech research.

Their answer was that I could change my IP or use a VPN (or kill my Tor Node of course!) if I wanted to continue to use Tidal.

Neither of those options are possible for me so as I need to Tor node for work research, my IP is static and "rented" for 10 years to come. VPN is just not possible for every device in the house that would normally run Tidal.

I guess that Tidal just don't want to have customers anymore.

So what should Tidals Argument be for blocking IP's with a tor node? I mean, I will be able to get many IP addresses blocked simply by turning on the Tor Browser while using some network. It seems like a stupid decision made by people who do not know how Tor works.

The Android bluetooth team has finally released some documentation for the new android bluetooth stack called gabeldorsche (or gd for short). They discuss it in the informative video linked in the GD readme found here: https://android.googlesource.com/platform/system/bt/+/refs/heads/master/gd/README.md