They detect lower than usual TTL of packets coming from your mobile device when it routes packets during tethering. They might also set TTL to 1 to packets going from internet to your mobile, so they get dropped instead of being forwarded further. You would need to plug the SIM card into your own modem+router combo with TTL modification rules in place to avoid detection. But then they might just block your modem by checking IMEI…
Maybe the instance admin, @ruud could help?
Isn’t it actually “For Fuck’s sake”?
Give it some time, people will get comfortable here, the revolution dust will settle an we will be adding ‘-Reddit “Lemmy”’ to search queries (fingers crossed!)
Found it here: https://github.com/LemmyNet/lemmy-ui/issues/1103
XDCC
I couldn’t understand how those changes back then crippling the user experience were “better” in any way, this explains a lot!
One guy from Poland posted a video in polish on YT where he calculated that his roof solar in last 10 years of operation provided significantly less RoI than if he simply bought gold at market price 10 years ago and sold it now.
This is a freaking scam over here. We need power mostly in winter, especially with the push to install more heat pumps. Solar is not working in the winter here, people literally got scammed by government that subsidized solar and heat pumps installations for lower income families on the condition that they remove coal or wood powered heating. Now they can’t afford to run those heat pumps!
Mlem, the alpha version of Lemmy client for iOS, has this feature.
Give it some time, this ecosystem has to mature.
ctOS, it is happening
Someone gave a great workaround though - use an app that creates a local proxy available through legacy Wi-Fi Direct
It is unintended, a bug that is already known and will possibly disappear when support for websockets is removed (i.e. only plain HTTP traffic from you web browser to the server will remain).