Hacker Newsnew | past | comments | ask | show | jobs | submit | bofaGuy's commentslogin

This is mostly misleading. Here is a detailed write up on the actual changes and what they mean.

https://rentry.co/tbr2owcq


This is pedantic. Disney is clarifying that live content will have ads. They are not Disney's ads they are network ads from that live channel, usually a 3rd party to Disney. This is seemingly because all of Hulu's features will be ported to the Disney+ app, including live TV and replays of live TV and so whatever ads are in that live content and playback will be there for everyone.

Also, Hulu include content from other companies which require ads to be played and only offer the ad free experience on their own platform.

Here is a more detailed write up on the actual changes. https://rentry.co/tbr2owcq


It is not. The exact wording, as it sits in my inbox:

> We’ve clarified that all Service Plans may include: (i) promotional content, (ii) sponsorships, and (iii) advertisements before/after playback of Content and in channels, live/as-live, special events, and any third-party services content.

Emphasis on "before/after playback of Content" and live etc. So they are opening the door for ads everywhere, not just on live TV or Hulu.


I just did a diff of the previous terms to the current (as of 10/22/26) terms and found nothing really related to the article's claims at all. Also this is not in the US terms at all -> "We’ve clarified that all Service Plans may include: (i) promotional content, (ii) sponsorships, and (iii) advertisements before/after playback of Content and in channels, live/as-live, special events, and any third-party services content."

It seems it is only in the UK and European subscribers TOS from 06/18/26.


>This is pedantic. Disney is clarifying that live content will have ads.

This is pedantic. If folk can't see that this is a slow roll towards rolling out the same thing in the US eventually, I've got a bridge to sell you.


Again nothing of the sort changed in the US.


Justifications don't change the ground reality: more ads are coming.


This guy works for flock


Dynamo DB isn’t even good at being a KV store. Almost every time we have to also back it with S3 because of size limitations.


If you know your access patterns really well and they are non-relational, then you can design the best possible tables for dyanmoDB. In such a case DynamoDB works and scales amazingly. Ofc, you cannot do multi table relationships etc shoehorning a relational scheme onto DynamoDB does not work.


did you use single table design?

and yeah you have to spend a lot of upfront time designing your data models



I saw these referenced in the repo. Maybe the hand written parts are here?

https://github.com/nordstjernen-web/lexbor

https://github.com/nordstjernen-web/quickjs


No, as those are just forks of already existing projects and the forks don't contain any additional commits compared to upstream.


I feel like the CAN-SPAM Act should apply to push notifications as well. I don’t know of any case that has tested this.


Netflix has been the worst performing and lowest quality video stream of any of the streaming services. Fuzzy video, lots of visual noise and artifacts. Just plan bad and this is on the 4k plan on 1GB fiber on a 4k Apple TV. I can literally tell when someone is watching Netflix without knowing because it looks like shit.


It's not AV1's fault though, I'm pretty sure it's that they cheap out on the bitrate. Apple is among the highest bitrates (other than Sony's weird hardware locked streaming service).

I actually blamed AV1 for the macro-blocking and generally awful experience of watching horror films on Netflix for a long time. Then I realized other sources using AV1 were better.

If you press ctl-alt-shift-d while the video is playing you'll note that most of the time that the bitrate is appallingly low, and also that Netflix plays their own original content using higher bitrate HEVC rather than AV1.

That's because they actually want it to look good. For partner content they often default back to lower bitrate AV1, because they just don't care.


This is actually their DRM speaking. If you watch it on a Linux device or basically anything that isn’t a smart TV on the latest OS, they limit you to a 720p low bitrate stream, even if you pay for 4k. (See Louis Rossman’s video on the topic)


OP said they're using an Apple TV, which most definitely supports the 4K DRM.


The bit rate is unfortunately crushed to hell and back, leading to blockiness on 4K.


Oh oops


Have same experience as OP on newest ATV 4k. Good it's not only me who wonders how is it possible that they describe such great approaches to encoding, but final result is just so bad.

Good that the OCAs really work and are very inspiring in content delivery domain.


Yep, and they also silently downgrade resolution and audio channels on an ever changing and hidden list of browsers/OS/device overtime.

Meanwhile pirated movies are in Blu-ray quality, with all audio and language options you can dream of.


I also find Netflix video quality shockingly bad and oddly inconsistent. I think they just don’t prioritize video quality in the same way as say apple or Disney does.


I cancelled Netflix for this exact reason. 4K Netflix looks worse than 720 YouTube, yet I pay(paid) for Netflix 4K, and at roughly 2x what I paid for Netflix when it launched. It's genuinely a disgrace how they can even claim with a straight face that you're actually watching 4K. The last price rise was the tipping point and I tapped out after 11 years.


Netflix on Apple TV has an issue if "Match Content" is "off" where it will constantly downgrade the video stream to a lower bitrate unnecessarily.

Even fixing that issue the video quality is never great compared to other services.


I was able to improve things somewhat by going to https://www.netflix.com/settings/playback/<myprofileid> and changing "Data usage per screen" from Auto to High


Probably some function of your location to data centers. I find hbo max to be aysmal these days. But I've learned to just stop caring about this stuff since no one else in my life does


https://xkcd.com/1015/

Now you can be mad about two things nobody else notices.


Oddly enough, I observe something to the opposite effect.

I wonder if it has more to do with proximity to edge delivery nodes than anything else.


If I am unique every time I reload the page in a new private window, that means the fingerprint is not the same as the last time I visited right?


I run Redis across dozens of applications. So when Valkey became available for a discounted price on AWS I was excited. We finally got around to trying it out about 2 months ago and all was going well. No noticeable difference in performance. Until Valkey just died. It died in such a way that AWS still thought it was running happily but it was completely offline. It took 12+ hours for it to come up again and then it happened again... AWS researched the issue for 2 weeks and couldn't figure it out. It will be a long time before we attempt to use Valkey for anything critical in the future. We since have replace that Valkey with Redis under the same workload and have no issues.


Probably AWS issue. Our production RDS postgres cluster did that a few months back. Just stopped responding on the network. Health checks were fine. AWS support was mostly useless and couldn't work it out in an hour, despite having their top tier enterprise support, so with customers down we had to create a whole new cluster and do a restore from backup which took 4 hours.

RDS is now gone. It's on a couple of EC2 instances with replication, hourly EBS snapshots and daily shipping to S3.

I'm loathed to use AWS's "encapsulated" services for anything since.


I think these are isolated incidents though. We’ve ran several tens of RDS clusters for 6 years running, and nothing has ever gone wrong. Maybe the ap-northeast-1 region is well maintained?


Could that be an AWS operational issue, and not related to Valkey?

I only run redis myself but wouldn't immediately place blame on Valkey if that happened.


Yeah I don't understand how something could be "completely offline" and still have health checks passing.


"completely offline" also doesn't sound like a problem with a software project. At best it's a particular managed service experiencing downtime. Would Linux be to blame if my power supply goes up in smoke?


It’s a bit confusing to me exactly what went wrong. I think that when you have a redis/valkey cluster with multiple nodes and you use the cluster uri, there must be some kind of load balancer or custom routing. When we would attempt to connect to valkey the connection would look good, but when we would submit commands to it they would never execute. We had written our application so that it would operate with no issue (just slower) if the cache goes down. In this case, connections looked good but no work was actually being done. AWS support suggested we restart the nodes but because they were not responding they never shut down … or at least it took a really long time. They were never able to tell us what actually happened. My guess is that valkey command execution got stuck somehow but was still able to create new connections.


“Completely offline” and passing health checks don’t typically go together…


Can’t be reached outside the network that the instance and health check are running on? Maybe available in one AZ, but not on the one that’s trying to connect.


Why you don't just run new instance with your own Valkey?


Because when you’re in production with many users, it’s not worth the risk when you’ve already been burned, especially when the downside is a small discount.


The aws managed cache offerings are not just a small premium, they're like 10x more expensive than the ec2 instance types they represent.


Its more but I doubt its 10x or even close to that.


It's not even 2x. I spot checked 2 instance types and they were 36% and 69% more.


What instance types were you using, just for reference?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: