Thank you, I was unaware of that. It looks like it's already support in the acme.sh client, but there is a Let's Encrypt discussion saying it's still pending at LE:
CAUTION, though, the last time I downloaded a binary release, ClamAV triggered on it, so I kept my old version which worked. I was using the 1.0 series (without any problems!), and now it seems the project has picked up development again with a 2.0 series.
> Liminalism (if we can christen this as a movement, and we should) is a form dedicated to the discovery of digital found art. It is important not just because of its content, but because it signals the migration of critical terminology and thinking into popular discourse in a truly democratic sense, independent of the traditional confines of the art industry as expressed in exhibitions, galleries, and museums.
This is not the language of an elitist.
If anything, it sounds like someone defending Liminalism's inclusion in the contemporary canon from arrogant elitists.
The heavily ironic implication is that they're under NDA, so they can't attest to it, while more or less attesting it. Senator, I cannot confirm or deny that we definitely do this.
This could also be an unofficial-official way for Apple to "leak" that yes, they do this--which is on brand for how Apple handles "rumors" etc.
They cannot envision the scenario where their AI-powered robots turn on them, or at the very least are used against them (and then inevitably turn on everyone).
M4 Pro 64GB (14 CPU / 20 GPU), Gemma 4 31B Q4_K_M GGUF, LM Studio: time to first token 0.92s, 11.56 tokens/s.
Edit: For comparison with the other poster, same setup as above, but with Gemma 4 31B Instruct 8bit MLX (not sure if exactly the same model): time to first token 4.62s, 7.20 tokens/s; with a different prompt, 1.17s and 7.24 tokens/s.
First, they can't attack a WiFi access point for which they do not know any password(s). Thus your multi-SSID access point with multiple passwords is "safe" from this particular attack.
However, second, they can attack an access point for which they know any password, gaining access to clients on the other SSIDs. This means your security is now effectively only the security of your worst SSID's password. It also may defeat your purpose in having multiple SSIDs/passwords in the first place.
The "We" is short for Westinghouse, or at least it was: Westinghouse Steered Stabilized Camera Mount, thus WESSCAM. Then they dropped an "S".
Granted pronouncing the name is ambiguous, Wes-cam or We-scam. But they're known well enough in the industry at this point that it's not a problem for them.
ETA: The above link is at the bottom of the original submission's README. (https://github.com/sst/opencode) I posted it without context, and I have no opinion on the matter. Please read theli0nheart's comment below for an X rebuttal.
Plex forces centralized Internet authentication for your locally-hosted server, and uses a variety of centralized services that have access to your served files' titles and other metadata. Furthermore Plex collects a variety of usage information statistics. I don't think it's possible to entirely opt out of these services or collection, or indeed use Plex at all without Internet access.
Although Plex claims to "care deeply" about privacy in its privacy policy, there is no blanket statement guaranteeing the privacy of your data and usage habits, or at least none without weasel words.
No, he's upset that Snowdenrevealed that the government is doing things that affect his investments. His comments make it sound like the government is neutral or somehow the victim in this.
https://community.letsencrypt.org/t/dns-persist-01-deploymen...
I wonder if the interim version has been rolled out to some CAs.