Just keep in mind each person is impacted differently. Symptoms aren't one size fits all, and even NTs get some relatable symptoms occasionally.
Zikeji
joined 2 years ago
And despite having cloud integrations, if my WAN is offline I can still view my doorbell. I haven't tested it HA received notifications or anything though, as I just rely on the Unifi Security app.
Someone doxxed me and spread a photo of my face with the text "she said she was 18" superimposed on it (in meme format), and then spreading it in the community.
All because they took issue with a friendship I had with another user who "sounded young". Which culminated in the community leadership getting her to prove she was, in fact, not underage, "just in case" we ended up in a relationship because they "know how these things go" or something.
"hot tub - $$$$"
Right under "fix the back pain that plagues my life" which is right below "get LASIK".
"funny" 🙃
Both should if your goal is to not have a reusable fingerprint (which for a privacy focus would be). Server should change more frequently since it has access to less information about the browser. Server based fingerprinting is fairly unreliable, client side uses Javascript to generate more bits of unique data.
The bottom result (the % certain one) is just a fuzzy match of similar fingerprints AFAICT.
The test is simply showing two fingerprints for your browser. One, the server fingerprint, is one that any tracker can see. The other, the client fingerprint, is what can be used if you have Javascript enabled.
Instead of inundating you with test results, this one is simple - check to see if your fingerprints change between browsing sessions. If they don't change, that means you can be tracked. In which case you can mess with settings and try again.
So server code is your fingerprint based on what a server is able to see. This would be your fingerprint with JS disabled, essential. Client code is the JS generated fingerprint.
For the emojis I have no idea.
One of the points of Libre Wolf is to make you unique, but each session should be unique.
You can find some additional setting tweaks here: https://librewolf.net/docs/settings/
The "letterboxing" feature is an additional uniqueness feature you could consider enabling.
I'm particular you could check your result in this experiment: https://fpresearch.httpjames.space/
Try it in both normal and in a private tab, then record those results, reopen Libre Wolf, and try again.
You're right. And my library aversion definitely made it harder. I think the day I learned the most was day 19, the towel one. Seemed simple at first but I just couldn't wrap my mind around it, looked at a few solutions and one of the dynamic programming one solutions just blew my mind. Took me an hour or so to just wrap my head around it and then once I understood it I was able to write that abomination I posted from scratch (well, without needing to reference what I studied).
If this is your take your exposure has been pretty limited. While I agree some devs take it to the extreme, Docker is not a cop out. It (and similar containerization platforms) are invaluable tools.
Using devcontainers (Docker containers in the IDE, basically) I'm able to get my team developing in a consistent environment in mere minutes, without needing to bother IT.
Using Docker orchestration I'm able to do a lot in prod, such as automatic scaling, continuous deployment with automated testing, and in worst case near instantaneous reverts to a previously good state.
And that's just how I use it as a dev.
As self hosting enthusiast I can deploy new OSS projects without stepping through a lengthy install guide listing various obscure requirements, and if I did want to skip the container (which I've only done a few things) I can simply read the Dockerfile to figure out what I need to do instead of hoping the install guide covers all the bases.
And if I need to migrate to a new host? A few DNS updates and SCP/rsync later and I'm done.