```
Too Many Requests
The page you have tried to access is not available because the owner of the file you are trying to access has exceeded our short term bandwidth limits. Please try again shortly.
Details:
Actioning this file would cause "jbkempf.com//blog/2026/dav2d/" to exceed the per-day file actions limit of 160000 actions, try again later
```
Hacker news doesn't generate much traffic, despite what people are saying.
The host here has a limit of 160000 files served each day. That is extremely low. If the site has an icon, css, a js file and a few images it's 10 files each visit. That's will limit it to 16k visits/day. If there are more files loaded it might just handle a few thousand visits, and they have received more than that from HN now.
Well, if every asset request hits the origin (no CDN, no caching...) that would be a misconfiguration of the website. It should never happen for a blog.
Yeah, it's hard to tell thb, just a guess. But potentially the site also misconfigured their server, causing too much cache misses and hitting the server direclty.
This is Trump's second term and MAGA views won't disappear 3 years from now. Even if they assume that there will be a peaceful and lawful transition of power, I can see why they may be planning on the assumption that the "instability" (from their point of view) will continue into the future.
I disagree. You literally have one single human being in charge of 3 main branches of government, and multiple smaller agencies. Noone will manage US like Trump does.
I think it's fair to call out the parent comment for things that are not exactly caused by Boeing (eg: the engine failure), but I also think it's important to look at the why.
In the case you're referring too, the focus was on poor training and failure to follow up on earlier incidents. It's not the same as designing a system based around a single sensor that is known to fail or forgetting to bolt a door.
> It's not the same as designing a system based around a single sensor that is known to fail
Right, they designed the their system with two sensors, and if they disagree, the system gives misleading indications to the pilots! That’s so much better!
My understanding is that the Airbus equivalent (they don't really have the same thing) uses 3 pitot tubes/angle of attack sensors, not 2. More importantly, Airbus pilots know about the system, while Boeing only told airliners about MCAS after the Lion Air crash.
I'm not a pilot and I don't know that much about planes, but I've read/watched enough about crashes to know that these sensors fail way too often. To rely on only one already sounds like a bad idea, but it's irresponsible not to tell pilots and train them on how to deal with the new "feature".
Airbus aircraft are normally fly-by-wire and a system like MCAS would just be folded into the envelope protection that Airbus does. It's already very easy to cross-train from once Airbus to the next because FBW is used to give them all similar handling characteristics.
That wasn't possible in the 737 MAX because the airplane is an older design with hydraulically connected control services, so a separate system had to be added to force the nose down using the trim.
It may be easier to convince them if the Internet Archive doesn't allow access for <period of time>. Not good for the average user now, but at least it would be archived for the future. Better than having no archive at all.
Yeah IA needs to get their heads out of their asses and just do that. It's an archive, but if it's available at the same time as it's relevant, then it's being used as alternate access.
> Edit: lol -4 , like seriously, its a pretty bad show. [...]
I don't think the downvotes are because you expressed the view that the film is bad.
It's mainstream science fiction using tech we don't have. It will never make a lot of sense. And then you decide to bring skin colour/race into the discussion. What do you expect?
They won't, its literally part of their sales funnel. They've specifically engineered a bad experience for anyone outside the ecosystem by making it all of their friend's problem too. Its very important for their stock price that text messages sent by non apple products are just slightly more difficult to read.
> in my experience, most Meshtastic nodes are NOT listed, while a good number of Meshcore nodes are.
I don't know about online tools, but it should be the opposite when actually using it, as by default Meshtastic is much more chatty (and wasteful) than Meshcore.
Meshtastic is horrible in a metro area. The area I live in has a huge user group and it's almost impossible to get a message across more than 3 nodes reliably. Meshcore, on the other hand, is far less popular but still has a nice amount of repeaters and it's, conversely, very good. I've since moved all of my devices to Meshcore. I'm on the edge of a metro (about 30 miles out) and have a repeater at one of the highest points in my geo and can seamlessly message users on the other side of the metro (~60 miles).
I tried Meshtastic here in London (UK), but was struggling with anything more than 1 hop away. There's no coordination, everyone's using the long fast preset, etc. Then found out about Meshcore, flashed the firmware, selected the UK narrow preset, and it's a day and night difference.
Still wouldn't rely on this for anything serious because it's not reliable at all, but it's nice to be able to send a message across the city or to the other side of the country.
Similarly, I put a repeater in an upper story of an apartment building in Boston and am reliably able to talk to people over 10+ hops. Right this second I'm able to talk to someone 99.5 miles away in Vermont.
We had to create different channels for different regions (connecticut, new hampshire, massachusetts, rhode island) just to keep from having hundreds of messages in a single public channel when posts are generally about local things.
Unfortunately it doesn't fix congestion issues completely, repeaters still repeat everything (and can't listen while transmitting) so packets from connecticut still put traffic onto the entire mesh all the way to new hampshire, but at least it's better organized.
It seems like there are some ideas to help with congestion, maybe making channels region specific (repeaters can be programmed to only repeat traffic with a certain region code) but for now it's shocking to me how far I can reach with a 0.125W radio.
But yeah, it's not "reliable", that's what TCP/IP is for =) Definitely a toy network for now, and a single malicious bot on the frequency band would absolutely wreck it. Or a single high power jammer sending out noise at just the wrong frequency. Definitely a fun project for people who would do ham radio if they had any interest in taking a test...
I wouldn't use it for emergencies though, it's theoretically a backup if the cell network and internet go down but the reliability just isn't there and I suspect never will be.
My understanding is that the split is more superficial than that. The contributor in question (he used to do YouTube videos mainly, no contributions to the firmware) created his own vibe coded app/client and is trying to own the trademark on the Meshcore name. He controls the .co.uk site, the youtube channel, and the discord group. The firmware is still the same, created by the people behind the new .io website.
So the split is just a "the development team has nothing to do with the .co.uk site, his youtube channel and discord group", not a fork.
That post is about the development team "splitting" with the PR guy that is trying to get a trademark on the name and creating their own vibe coded paid client/app.
There's a history between Tastic and Core, but it's a different one. Meshtastic doesn't scale that well in urban areas and it seems that some on the Mestastic team didn't see that problem as a priority/ignored the problem/are too stubborn. And then Meshcore is created with a different routing, works much better in practice, proving that the mesh could be much better. In countries like the UK it seems to have replaced Meshtastic in most places.
- https://web.archive.org/web/20260531130034/https://jbkempf.c...
- https://archive.md/ln5UE
reply