The_Decryptor

The Category 5e specification improves upon the Category 5 specification by further mitigating crosstalk. The bandwidth (100 MHz) and physical construction are the same between the two, and most Cat 5 cables actually happen to meet Cat 5e specifications even though they are not certified as such.

I did kinda mean it as a joke originally, but yeah 5/5e are the same outside of crosstalk resistance.

Well if they’re only getting 10Mbps over Cat5 then the cable’s busted, since normally they’re rated for 2.5GbE.

I agree with you, but the cash example is a bad one because there is a push to move entirely to electronic payments.

There’s less microplastics now than in the 70s?

If ghosts are dead people, with the passing of time there should be more ghosts and be easier to spot.

One estimate I can see of the total cumulative human population is about 100 billion people, if there was just a 1% chance of becoming a ghost when you die there should still be about a billion of them on Earth currently.

Imagine if 1 in 9 people on Earth was actually a ghost.

Some newer radiation hardened stuff is 10x larger than that, older gear even more so. But that just reduces the risk, not sure it’s possible to negate it entirely.

An easier way is to just include more CPUs as part of the system, run them in lockstep, then compare the results by majority rule. If 2/3 CPUs say one answer and the third says something else, you discard the result of the third and go with the other CPUs.

The ladybird devs are currently in the process of switching language again from Swift to Rust, using LLMs.

This isn’t sending your packets anywhere but their closest datacenter, not sure I’d trust MS (Or rather, Cloudflare) with your porn rather than your ISP who you’re actually paying.

The original use case for this stuff was unencrypted HTTP with a public WiFi connection, in which case your ISP is the owners of whatever shop you’re in and yeah they could see everything.

If you’re at home or whatever it offers effectively no benefits, doesn’t “block trackers” or whatever nonsense like Nord claims, but I don’t think Microsoft ever claimed that it did.

IPFS has gateways though, so you can link to the latest version of a page which can be updated by the owner, or alternatively link to a specific revision of the page that is immutable and can’t be forged.

Seems like we need to switch to URLs that contain the SHA256 of the page they’re linking to, so we can tell if anything has changed since the link was created.

IPFS says hi

It’s the same person running all of them, so yeah it is.

No, Nokia do own a bunch of patents on it, I’m pretty sure they also created (and have patents on) the HEIF format used in HEIC/AVIF as well.

Edit: search results were failing me, but here’s a couple.

https://blogs.windows.com/devices/2013/03/18/h-265hevc-high-quality-video-at-half-the-bandwidth/ https://mspoweruser.com/nokia-details-its-contribution-to-h-265hevc-hints-at-integration-in-devices/

Much in the same way that laws don’t prevent crime, a project banning AI contributions doesn’t stop people from trying to sneak in LLM slop, it instead lets the project ban them without argument.

In Australia and most other jurisdictions an “e-bike” is defined by law as a bike with pedal assist up to 25km/h.

I’m pretty sure they’re intentionally conflating them to either downplay the risks of unregulated electric motorcycles, or as some odd kind of anti-bike push, depending on the person making the argument.

The news is constantly bemoaning the dangers of e-bikes, while actually talking about motorcycles, too many times for it to be accidental.

Compared to e.g. pushing a button in VS code and having your browser pop up with a pre-filled in github PR page? It’s clunky, but that doesn’t mean it’s not useful.

For starters it’s entirely decentralised, a single email address is all you need to commit to anything, regardless of where and how it’s hosted. There was actually an article on lobsters recently that I thought was quite neat, how the combination of a patch-based workflow and email allows for entirely offline development, something that’s simply not possible with things like github or codeberg.

https://ploum.net/2026-01-31-offline-git-send-email.html

The fact that you can “send” an email without actually sending it means you can queue the patch submissions up offline and then send them whenever you’re ready, along with downloading the replies.

Sourcehut uses it, it’s actually the only way to interact with repos hosted on it.

It definitely feels outdated, yet it’s also how git is designed to work well with. Like git makes it really easy to re-write commit history, while also warning you not to force push re-written history to a public repo (Like e.g. a PR), that’s because none of that is an issue with the email workflow, where each email is always an entirely isolated new commit.

SpaceX wrote in its July permit application — under the header Specific Testing Requirements — Table 2 for Outfall: 001 — that its mercury concentration at one outfall location was 113 micrograms per liter. Water quality criteria in the state calls for levels no higher than 2.1 micrograms per liter for acute aquatic toxicity and much lower levels for human health

Cool, you can drink the mercury water, but I’ll pass thanks.

I’ve got some numbers, took longer than I’d have liked because of ISP issues. Each period is about a day, give or take.

With the default TTL, my unbound server saw 54,087 total requests, 17,022 got a cache hit, 37,065 a cache miss. So a 31.5% cache hit rate.

With clamping it saw 56,258 requests, 30,761 were hits, 25,497 misses. A 54.7% cache hit rate.

And the important thing, and the most “unscientific”, I didn’t encounter any issues with stale DNS results. In that everything still seemed to work and I didn’t get random error pages while browsing or such.

I’m kinda surprised the total query counts were so close, I would have assumed a longer TTL would also cause clients to cache results for longer, making less requests (Though e.g. Firefox actually caps TTL to 600 seconds or so). My working idea is that for things like e.g. YouTube video, instead of using static hostnames and rotating out IPs, they’re doing the opposite and keeping the addresses fixed but changing the domain names, effectively cache-busting DNS.

SpaceX like to dump their waste in the closest river.