JWBananas @ JWBananas @startrek.website

aka @JWBananas@lemmy.world

---

Read more

Posts

6

Comments

742

Joined

2 yr. ago

Except for Sisko

Launch him through the nearest Stargate.

Or, you know, Far Beyond the Stars.

The Vulcan Science Directorate has determined that Q are impossible.

Holy moly!

“If we don’t have Spotify working properly across Play services and core services, people will not buy Android phones,” Harrison testified.

Google: Sorry, other devs! You just aren't as important as Spotify!

[I mean, they aren't wrong. But this does not bode well for them!]

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.

Tetrisphere

I wish your pain was gone

One Scaramucci equals 10 days

With some of the biggest baseball caps you've ever seen

cough magnet link?

What is this, an extinguisher for ants?!

We can go deeper!

But he was very different to Dukat's daughter.

He was growing his beard.

theyrethesamepicture.jpg

It's particularly jarring that they get it right in some episodes and wrong in others. Might make a good drinking game.

To start things off:

I'm sure the first thing that will come to many people's minds is the infamous badging error in TOS:

https://www.startrek.com/news/starfleet-insignia-explained

Some may suggest that since it was caught during dailies and intentionally left in, then it should stay as it always was.

Others may suggest that if modern technology were around back then, it would have been fixed in post; so why not let that happen now?

For that specific example, I'd probably argue for leaving it alone.