Indeed. The instances that have solid uptime have, in most cases, sold their soul to the devil (aka Cloudflare, which is a centralised threat on the free world and all things good).
activistPnk
Interesting. I think I read that somewhere else recently. But I have never seen the rechargeables or the batteries. As someone who buys local and boycotts Amazon, I don’t suppose these are within reach.
For a bit more depth on this, the EDPB elaborates on the controller/processor separation and relationship in their 2020/07 guidelines.
It’s a long read, which I just skimmed. It’s mostly grim news. There is even a specific example in that doc stating that an email provider is a processor. But I see an angle:
A data processor has a duty to offer an appropriate level of security to controllers under Art.32. Another finding by the EDPB is that processors who violate the GDPR can be treated as controllers. It could be argued that (unlike protonmail) Google and MS both fail to offer e2ee and simultaneously supplies its insecure email service to controllers who handle sensitive info like lawyers, hospitals, and banks. The violation of art.32 by Google and MS enables them to be treated as controllers.
For me, rats are filthy, gross, and creepy. But that is not why I fight them. I normally would not care about their presence as long as they stay on their side of the walls. But I fight them for two reasons:
- Their teeth never stop growing. So they are teething their whole life and also build nests, which means non-stop house destruction.
- They can carry hantavirus. It’s an airborne transmission and can come from rat urine and feces.
- The day I decide to remove my ceilings (likely to take away rat turf), I expect to get a shower of feces.
Google is certainly obligated to comply with the GDPR. But I suspect they are shielded if they can call themselves a /data processor/ and not a /data controller/.
It’s certainly a big hole in the GDPR. The GDPR framers did not consider the fact that in some situations you have countless data controllers all using the same giant processor, in which case it’s only reasonable for data subjects to be able to go direct to the data processor rather than playing whack-a-mole with controllers.
I’ve heard that as well; and claims that they are essential to keeping the sewer pipes clear. Not sure to what extent I would put stock into all that but they are certainly a pest. Disease, filth, destruction of homes.
My city ultimately considers them a pest considering there is a tax-funded public pest control office fighting rats year round. People can call them and they will come to the home and deploy rat control measures (usually poison) at no cost, just like a pro exterminator.
hmm.. painful. That page assumes I speak the language of whatever country my Tor circuit exited. I see at the bottom there is a Google reCAPTCHA barrier.
Nonetheless, I’m glad to know my options but I guess I’ll have to keep trying that page until it speaks my language before I can work out whether it’s a lesser of evils.
In the end, my question is more legal than technical. I could find out Google’s postal address and send them an anonymous letter. But the problem is perhaps that legally Google only needs to honor the GDPR requests of those whom it can identify. In fact, I think it’s expressly written somewhere that anonymous people do not have GDPR protection.
My question may have no answer. Perhaps I have to let Google have my identity as a trade-off to getting GDPR rights.
Would be useful to plant a specie that attracts rats, so the trams can cut down the rat population.
The middleware app you link to says this:
Navigation apps that support the default Android Developer Option's 'mock location' feature location source.
I installed a similar FOSS middleware app (which apparently no longer exists):
https://f-droid.org/en/packages/org.broeuschmeul.android.gps.bluetooth.provider/
It worked as far as getting the fix via NMEA over bluetooth and sending the mock location to the kernel, but the problem is that OSMand and Organic Maps are not written to make use of it. What version of OSMand are you using? I am trapped on an old version because OSMand decided to leave those with pre-AOS7 devices in the dust. Maybe they added mock locations afterwards.
Not sure where to start with an eyeroll? from a clueless Cloudflare boot-licker. Coming from a CF domain (another technofeudal fiefdom) there is probably no hope for you. But since there are at least 6 others equally clueless, I’ll go out on a limb and link the research in the off chance the extent of disclosure with Google’s Location service sinks in with someone:
http://web.archive.org/web/20250422153816/https://www.scss.tcd.ie/doug.leith/apple_google.pdf
Downtime by a freedom-respecting trully decentralised node like slrpnk.net really exposes how Lemmy clients leave a LOT to be desired.
The prospect of data loss is gutting. A proper client would be syncing threads of interest between the server and my PC, so during downtime I can still at least locally access past content. No proper clients exist for Lemmy.