
I would go with direct burial shielded twisted pair and coax if I were doing it, especially if it will run directly inside for termination.

I would go with direct burial shielded twisted pair and coax if I were doing it, especially if it will run directly inside for termination.


… It was incredibly sobering that a case about our privacy was being conducted both in private and in secret. So we’re pleased to see a course change here. That said, the battle is not yet won. The arguments to break encryption do not just relate to this specific case and we are having to constantly make the case for why encryption is vital in our democracy; nor does this judgment stipulate that the case will be held fully in the open moving forward – as it should be – only that we can know the “bare details”. We welcome this news but we continue to fight for full transparency here.


The legislation would force companies to store and provide law enforcement with access to their users’ communications, including those that are end-to-end encrypted.3 The consensus among cybersecurity experts is that complying with this requirement for end-to-end encrypted communications services will be impossible without forcing providers to create an encryption backdoor4 —akin to a master key that unlocks every door in a building.
Hopefully they don’t pass this devastating legislation. One has to wonder who this would be benefitting the most? I doubt law enforcement even cares that much. My guess is the same that is responsible for Brexit and destroying the US. Resist wile you can, or better yet get the things you care about enshrined in your constitution and advertised among your constituents. Don’t think it can’t happen to you next.


The LAP can issue loads to addresses that have never been accessed architecturally and transiently forward the values to younger instructions in an unprecedentedly large window," the researchers wrote. “We demonstrate that, despite their benefits to performance, LAPs open new attack surfaces that are exploitable in the real world by an adversary. That is, they allow broad out-of-bounds reads, disrupt control flow under speculation, disclose the ASLR slide, and even compromise the security of Safari.”
SLAP affects Apple CPUs starting with the M2/A15, which were the first to feature LAP. The researchers said that they suspect chips from other manufacturers also use LVP and LAP and may be vulnerable to similar attacks. They also said they don’t know if browsers such as Firefox are affected because they weren’t tested in the research.


Very long wind up to a fucking ad.


Unless it’s required to load the words, it’s probably JavaScript that is trying to prevent the user from selecting it, so disabling javascript would make it selectable because the thing blocking the select is disabled. If javascript is loading the words in, then blocking javascript will make it so the page doesn’t load. But they are typically separate scripts from whatever is blocking the select, so addons can selectively block scripts that are detected to block things like select or right-click, etc. If they obfuscate the javascript to where the word load and the blocking are combined, then another method will probably be the easiest to employ like one of the other options I noted above, or going to developer options and copying the text from the inspector.


Several options to get around that. (1) Install a browser extension that will disable whatever block the page has, (2) open developer tools on a desktop browser, delete whatever javascript is preventing it, (3) possibly print to pdf, someone else suggested screenshot + OCR, etc.
Let me get this straight. A contributor was only temporarily traveling in a US-sanctioned region, they didn’t attempt to push a commit while they were there, only that they visited the region?


I’m out of the loop. Why did github “block” Organic Maps?


It’s the little things that always add up. It’s not the lack of feature but their dismissal of it I guess.


Good to know. My experience with nginx is definitely on the light end. I much prefer traefik I guess coming from k3s world.


As if I needed another reason to avoid nginx.
Seems like a very simple, lightweight and elegant solution to keeping the engine up to modern standards. If they were serious about keeping complexity out they wouldn’t have such garbage site configuration.


Where can I find the protocol specifications?


Great question! Unlike Lemmy, which relies on federation with dedicated servers, Plebbit is fully peer-to-peer (P2P) and does not have a central server or even instances. Instead, storage happens via a combination of IPFS and users seeding data. Here’s how it works:
Subplebbit Owners Host the Data (Like Torrent Seeders)
Users Act as Temporary Seeders
IPFS for Content Addressing
PubSub for Live Updates
| Feature | Lemmy | Plebbit |
|---|---|---|
| Hosting Model | Federated servers (instances) | Fully P2P (no servers) |
| Who Stores Data? | Instance owners (like Reddit mods running a server) | Subplebbit owners & users (like torrents) |
| If Owner Goes Offline? | Instance still exists; data stays up | The community disappears unless users seed it |
| Historical Content Availability | Instances keep all posts forever | Older data may disappear if not seeded |
| Scalability | Limited by instance storage & bandwidth | Infinite, as long as people seed |
It’s a radical trade-off for decentralization and censorship resistance, but if no one cares about a community, the content naturally dies off. No server, no mods deleting you from a database—just pure P2P.
Hope that clears it up! 🚀


Plebbit only hosts text. Images from google and other sites can be linked/embedded in posts. This fixes the issue of hosting any nefarious content.
Nowhere in the project whitepaper or FAQ does it talk about banning image hosting. Base64 encoding images in the text post is trivial, so maybe OP is the one projecting this intent or feature?


I rip with makemkv then use handbrake for slimming down to hevc/aac. I have too many discs and not enough storage to keep the raw rips. Newer handbrake supports nvidia transcoding for hevc, getting some great quality, but I wish it would support audio tracks and subtitles better… for multilingual subtitles I have a custom ffmpeg script that does a decent enough job.
Also cropping can be a pain in the ass with both ffmpeg and handbrake, much less so on the latter.


It would be nice if FTC or someone would sue them for anticompetitive behavior.
I’m not familiar with Tryesto but it doesn’t appear to be AitM attack resistant. What is your usecase for this?