![](https://radiation.party/pictrs/image/141f2b46-3cf2-43be-aa47-13d675abc438.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
Umami has been pretty good to me. Plausible was a close choice but I ran into technical difficulties getting it going.
I didn’t get around to trying it, but goatcounter looked promising as well.
Umami has been pretty good to me. Plausible was a close choice but I ran into technical difficulties getting it going.
I didn’t get around to trying it, but goatcounter looked promising as well.
It was more common for commercial discs and some consumer discs to have the data layer sandwiched between the bottom surface and label layer, especially later in cd/dvd’s heyday, to prevent tiny scratches on the label or sharpie marks from destroying bits in the data layer.
Plex has been good to me but I grow ever more concerned that they will drop lifetime Plex pass features as they become more focused on being a provider of media and not just a streaming middleman.
My gut feeling is that that is apples entire game plan with the Vision Pro- seed an expensive version of the tech, then refine it with what they learned into something leaner and significantly cheaper.
I could be wrong, but given the current price point that’s my guess.
They make a lot off of paid repositories and enterprise contracts, id be shocked if they had to enshittify it
A gun would help stop those witches from flying in the sky.
I may be taking this analogy the wrong way.
Unless they are permanently only using specific addresses or blocks and will never change that up, I’d consider it a moving target.
A flatpak of the snap, running in a docker container inside a vm for maximum security.
Checking ip ownership is a moving target more likely to result in outcomes these sites don’t want (accidentally blocking google bots and preventing results from appearing on google).
Checking useragent is cheap, easier, unlikely to break (for this purpose, anyway) and the percentage of folks who know how to bypass this check is relatively slim, with a pretty small financial impact.
Their point was that, on macOS, other browsers don’t use the safari engine under the hood like they do on iOS. That commonality is why the article states the exploit works in those browsers on iOS.
Hey! I resemble that statement!
But, eventually exploitable is still a pretty major concern for anybody who has systems running longer than a few days at a time.