uMatrix + NoScript personally (yes, seems silly, but I find NoScript's UI more convenient for script toggling, while liking uMatrix's fine grained controls)
Did you enable firefox resist fingerprinting?
Also maybe letterboxing, which I think is not enabled by that flag by default, and also helps with CSS fingerprinting.
It hasn't received updates in a good long while, but seems to work fine, for me anyway. Has some rough edges, logging blocks when there's a bunch of redirects is a bit of a pain, making it hard to fix whitelisting in complicated things (like the dozen domains microsoft uses for auth) but apart from that...
(and ofc there's a bunch of forks adding bugfixes, some even relatively recent in activity, but unfortunately none have become the blessed official maintainer)
Indeed. I've had my XCover 6 for 3½ years now. I've dropped it many times, on hard surfaces (like outdoor concrete/brick). I've undoubtedly been fortunate. the plastic has gouges in it. there's (small) scratches on the screen (some from my keys), but the screen is not cracked. When it is dropped the back and battery pop off, which I think helps dissipate the forces. BTW, for anyone trying to extend their phone life, I strongly recommend those magnetic USB connectors. Reduces wear and tear on the USB port, and is also kinda convenient for quick disconnect.
> I strongly recommend those magnetic USB connectors
Note that these connectors are in violation of USB standard and potentially harmful as they expose the pins in an unintended way. For instance, notice that all the connection on the USB port are not all the same length, it is a form of protection, to make sure the power lines are well connected before the data lines make contact. With magnetic USB connectors, you lose that feature, in addition to potential issues with ESD, short circuits, etc...
I have a friend who swears by them and never had a problem, but still, that's good to know.
> notice that all the connection on the USB port are not all the same length, it is a form of protection
This was noticeable on USB-A connectors when you look closely where the two outside pins were slightly longer than the two inside pins: the Make-First, Break-Last (MFBL) principle. You can also see the same thing on SATA edge connector pins.
Take care googling for photos because many are CAD mockups misinform (because they are drawn pretty incorrectly and show no physical length differences).
USB-C does have longer pins for the ground, and the CC (configuration channel) connects last. A USB-C host doesn't deliver power until it is negotiated using the CC pins.
So USB-C via a "magsafe" connector is safe.
But maybe look for the two outermost pins to be longer.
You mention ESD which could be riskier since charged fingers or worse could touch contacts directly. However the lip around the contacts is usually grounded so any spark should be grounded first. I would also assume modern electronics are well protected against ESD (nobody wants occasional undiagnosable failures leading to refunds). Sure that stuff from earlier this century wasn't so well protected. YMMV if you are a sparky person in a sparky environs: weigh the downside costs of different approaches appropriately.
At least the USB-C ones I purchase are not flush - I never found those to be reliable. It's a male prong that looks pretty much identical in wiring to the male prong on the phone, that connects to a female one plugged into the socket. That plus a bit of a collar to help hold it in place. So I don't see why there would be any difference in grounding, it's the same connection...
(that plus the comments from the more knowledgeable person below)
Eventually they start wearing out, and I just replace them. I've had no issues with high voltages (45W+ charging on phone and steamdeck) and with peripherals (hub for example).
You want to get everything grounded before the data wires connect. But that's more about the shroud than the pins as far as I understand it, and a magnetic connector could ensure grounding if it was designed to do so. And for charging purposes you could skip the data wires entirely.
At least on Android, when my Samsung Galaxy Note (I loved that phone - replaceable battery, pressure sensitive stylus, IR blaster, OLED, audio jack, water resistant - they went downhill from there IMO) finally end of lifed, I just used the official Samsung tool to upload a community image on it. The process wasn't horrendously difficult. I don't know if people would do it, but it was a clear set of steps that even a tech novice could accomplish if following carefully.
So, they have an XCover 7 now - with similar specs.
Also, they committed to a rather long support cycle for the xcover6 (5 years I think?) - I have one and it is still going strong. I've replaced the battery twice - not because I desperately needed to, but... why not. They are cheap, and I use the older ones still as backup battery packs since they are fast to swap in.
Yeah they are really meant for businesses. Frontline workers, factory floors.
This is what we use them for and they do stand up to the abuse. Of course people treat them very badly as it's not something they paid for. Really long support too.
They're not good in terms of specs for the price but that is not what these phones are about.
Yeah, the specs were... decent... nothing standout. Really I was going over the list of things I had lost after the Galaxy Note got rid of all their features and decided the replaceable battery was the one I cared about the most. The ruggedness was just a nice plus.
So, as a long-time mercurial users, revsets in jujutsu were a major feature for me.
And if you don't want to use them, don't. But if you are looking to treat your VCS DAG as a queryable database they are awesome. And, they are great for avoiding having to chain a bunch of commands together, inefficiently, to get the same effect. Although you still can do that if you really want to. Just like you don't have to use jq to query JSON - you can do terrible cursed things with grep and awk and sed and it'll even work for simple cases. But you might want to give jq a spin - and really there are strong parallels in how they work.
I suspect they are replying to this part of the article:
"What you actually want to say is: “an element is effectively-dark if it has data-theme=”dark”, or if it has an effectively-dark ancestor with no effectively-light ancestor in between.” That’s a recursive relational definition. CSS cannot express it. CSSLog can:"
The entire article doesn't seem to mention the existence of :has() which is rather surprising given how recently it was written. Not even in the footnotes.
Yeah, that example is bad. The query doesn't require recursion, but they affirm it does by demonstrating a recursively-defined version of it. This is called "affirming the consequent"; "P -> Q" doesn't mean "Q -> P". Ironic, given the use of propositional logic throughout.
"Since 2005 China's Deputy Health Minister Huang Jiefu acknowledged on several occasions that approximately 65% of organ transplants in China were sourced from executed prisoners.[33][34][35] In 2006 the World Medical Association demanded that China cease harvesting organs from prisoners, who are not deemed able to properly consent.[36]"
...
"Experts have also expressed concern that in addition to executed prisoners, non-death-row political prisoners and prisoners of conscience are also being used to supply the organ transplant industry.[39][40] Researchers, including ones affiliated with The Epoch Times, the International Coalition to End Transplant Abuse in China, and the Victims of Communism Memorial Foundation, point out that data from China between 2010 and 2018 may have been falsified or manipulated because of "contradictory, implausible, or anomalous data artefacts" and because they match a quadratic equation with model parsimony that is one to two orders of magnitude smoother than those of other nations."
I remember reading a very similar chain last year, trying it on my Proxmox host, and then being surprised it didn't work. I'm sure it's not the only modern distro this way, but I can't claimed to have tried very many after that.
I don't have debian handy to check at this moment, but the devuan machine (and devuan is typically debian config for the 99% of things that are not systemd) I have installed using mostly defaults, does not have it enabled by default.
Yeah, the kurzgesagt episode on meat production did note that overall cows have a pretty good life right up until the final fattening feed lots which is pretty bad.
https://www.youtube.com/watch?v=5sVfTPaxRwk
They did note though, that it wouldn't cost that much, relatively, to give chickens pretty good lives. That really we're doing this just to drive the price down by pretty small amounts.
Did you enable firefox resist fingerprinting? Also maybe letterboxing, which I think is not enabled by that flag by default, and also helps with CSS fingerprinting.
reply