Nice. Software developer, gamer, occasionally 3d printing, coffee lover.
incompatible with port forwarding with any VPN
I’m not sure if there is a misunderstanding here, but port forwarding through a VPN is generally agnostic of most network setups. It’s a tunnel, doesn’t require your network to have port forwarding setup or even for it to be capable of it.
There’s Filler Checker as well for those that don’t have such a collection.
There are quite a few text equivalents. text-generation-webui looks and feels like Automatic1111, and supports a few backends to run the LLMs. My personal favorite is open-webui for that look and feel, and then there is Silly Tavern for RP stuff.
For generation backends I prefer ollama due to how simple it is, but there are other options.
Despite have AI off as much as possible within our Google Workspace at work, today all of my coworkers have received multiple ads / prompts by Google to use Gemini. In Gmail, in Google Meet, and more. Our policies don’t allow us to use it so this is just ridiculous.
So far I’ve helped my team of 5 get on them. Some other teams are starting as well. We’ve got Windows, Linux, and Mac OSX that developers are running on their work machine (for now), and the only container specific issue we ever encounter is port conflicts, which are well documented with easy to change environment variables to control.
The only real caveat right now is we have a bunch of micro services, and so their supporting services (redis, mariadb, etc.) end up running multiple times, so their is some performance loss from that. But they’re all designed to be independent, only talking to each other via their API, so the approach works.
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.
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.
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.
Are you copying it to a locally mounted ext4 or is it a network share of an ext4 drive, and if so - what type of network share?
The ad serving companies (Google) don’t care about what happens after the click (yet). As far as I’m aware no “handshake” process exists that would allow an advertiser to communicate with the as server and validate a click (such a process could be abused).
Most likely the advertiser would be using some form of client side analytics, so the click wouldn’t show up in their statistics, meaning the advertiser would see a huge discrepancy between the clicks they saw in the campaign and the clicks the ad server reports.
I’m not sure what you mean by “open source compatible”. Do you mean the camera itself can have open source firmware installed, or that it’s compatible with open source NVR software such as Shinobi or ZoneMinder?
If the former, I know some of the Wyze cameras have that option. Like OpenMiko. There’s all OpenIPC, which does have a list of supported devices.
If the latter, any camera with RTSP and some sort of API to expose PTZ controls would do. My personal recommendation would be Axis, which makes solid cameras.
Incoming based on the code here:
Holy shit, 10,000 commits because each change was individual (I’m assuming automated).
I’ve seen it a few times in passing and always assumed it was like, a tech demo or proof of concept.
I’ve had bad tinkering break my system before, but never had an update break it irreversibly. The closest would actually be on Silverblue itself, when an update to the kernel was using different signing keys that cause the system not to boot. Fortunately it was simple, I selected the previous deployment and I was in (on a non versioned OS I would have selected the previous kernel which most are configured to retain the last few). A quick Google revealed Ublue had a whole kerfuffle and after verifying it was legit, I enrolled the new certs into my MOK.
Although one time on Arch I had installed an experimental version of Gnome from one of their repos, and was pleasantly surprised when that version finally released and I removed the experiment repo and did an update absolutely nothing at all broke. Nothing.
Yup, with PIA the port is random but yes, there should be scripts out there to leverage PIAs forwarding with your torrent software. And yeah, if you were to port forward through your router that could lead to accidentally exposing your actual IP.