aka @[email protected]
aka @[email protected]
We never find out exactly what happens to Benny Russell beyond this point, as after the breakdown occurs, Captain Sisko wakes up. Back on Deep Space 9, it seems as if his experiences as Benny Russell were all just a fantasy.
Yes, we do. He ends up in an asylum. He is shown briefly while Sisko approaches the Orb of the Emissary.
They do. By default the system partition is straight up mounted read-only.
Is that… ICQ? Why?
besides memory leaks
Have you tried auto memory reclaim yet?
Do you want to talk about it?
The customary reply is “Thanks! I’ll add it to my list”
That’s a funny way to say “Have you opened a ticket?”
Google Lens turned up this: https://www.cygnus-x1.net/links/lcars/star-trek-voyager-technical-manual.php
Maximum warp is not maximum cruising speed, even negating the need to refuel.
Bitcoin is deflationary. There is a hard limit on the total number of bitcoins that will ever exist. Every so often, the reward for mining a block is halved. Eventually there will be effectively zero reward for mining at all.
That might have been true a decade ago. But GPUs and FPGAs have long been obsolete for mining Bitcoin.
Mining is happening on custom silicon in large-scale operations. They specifically observed several of those large-scale operations in multiple nations and extrapolated out. I don’t see how that methodology is flawed.
…I didn’t believe you. I had to look it up to confirm it.
Damn. Never even noticed.
I asked DALLE-2 for a “wide shot of a delivery driver in a Louisiana bayou with bagged food” and it gave me this:
That’s certainly a fascinating way to interpret “bagged food.”
When your layer 1 problem turns into a layer 3 problem 😅
Sometimes, less is more.
I would recommend trimming all your custom configuration from your router/firewall, one change at a time, until you can no longer reproduce the issue.
Or go the other way around: set up a barebones configuration, confirm the issue is resolved, and begin adding one customization at a time until it breaks.
How do your bufferbloat tests look?
https://www.waveform.com/tools/bufferbloat
It sounds like you have a lot of stateful inspection configured. YouTube’s heavy usage of QUIC (i.e. UDP transport) may not play well with your config.
And, incidentally, what does your hardware look like?
Frankly, even the most barebones router should be able to handle YouTube. I am running pfSense in an ESXi VM, with passthru Intel gigabit NICs, 2 GB reserved RAM, and 2 vCPU (shared, but with higher priority than other VMs) on a Dell desktop with a second-gen i7 that was shipped from the factory in 2012.
Yes, I am routing on decade-old hardware. And I have never seen anything like what you are describing.
YouTube should “just work.”
I am going to assume that if you’re running OpenWRT, then you are probably using a typical consumer router? Please correct me if I am wrong.
Have you by any chance tried backing up your OpenWRT config and going back to stock firmware?
I know, I know, OpenWRT is great. I have a consumer router that I flashed with it to use strictly as a wireless AP.
But consumer devices flashed with vanilla OpenWRT tend to have very, very little resources left over to handle fun configurations.
And I have a feeling some of the fun configuration might be contributing to your issues.
It’s not just storage capacity either. Google uses custom silicon just to keep up with all the transcoding.
https://blog.youtube/inside-youtube/new-era-video-infrastructure/
At the time that article was released (April 2021), users were uploading over 500 hours of video per minute.
Nickelback