bofaGuy

Again nothing of the sort changed in the US.

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 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.

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.

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?

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.

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.