That's the point. Someone finds something not successful, sees that they could make a lot of money off it, takes it for their own, has copyright over their new content. The labels you're talking about would gladly just mine what was released ${term}+1 years ago.

The point is that everything is copyrighted by default, unless you release it into the public domain.

> Right now if I want to sample a song made 50 years ago I still have to pay thousands to license it even if everyone involved has long since left.

And that's right. Why should someone else get to make money off someone else's work without compensating them for it, if they haven't released it to the public domain?

You're assuming that copyright protects the big labels -- it protects your creations too. The most famous case of this is Charles Dickens: https://foleyhoag.com/news-and-insights/blogs/making-your-ma...

If you look back at what was created in the past, 30 years seems like an absolute minimum, 50 years seems about right -- perhaps with a registration requirement for the full term so that works with an unclear publication date and ownership can be easily traced. That would mean the film Logan's Run would just be leaving copyright protection now.

For context, I believe in the UK, there is a 50-year term for broadcasts, computer-generated works, Crown Copyright (125 years or 50 from first commercial publication if within 75 years of creation), and certain classes of films. There's a schedule here: https://www.gov.uk/government/publications/copyright-notice-...

Huh? We're talking about the same S3 right? At list pricing, 1TB is $23/TB to store for one month, and about $90/TB (plus request fees) to send it out to the internet.

While hard drive prices are roughly 3x what they were a year ago, the price per TB of a new hard disk averages around $30/TB -- assume 2x overhead for other hardware and extra space for parity etc, a disk pays for itself in less than 3 months and lasts 5 years or more.

If you assume it takes 1 month to download that 1TB (about 3Mb/s) that's $29.16/Mbps. When I first started buying internet transit in Europe back in 2008 I think I was paying under $10/month. It's now under $0.10/Mbps pretty much anywhere in the US or Europe at the big datacenters.

None of the "big" object storage services are cheap. They're somewhat reasonable if you only access the data from within the same region, but absolutely insane if you ever want to ship that data outside of that cloud vendor (or to another region etc). The pricing of storage and egress has not changed in a decade (I believe AWS last lowered the price of either in 2016) and in fact it costs even more now due to things like NAT Gateways etc.

It's definitely not "shockingly cheap". It's just cheaper than $80/TB of gp3 or $45/TB of st1, and while sc1 is $15/TB it has a baseline performance of only 12 MB/s. There's quite a few companies out there that have $6/TB/month object storage plans with similar performance, rising to about $15-$18/TB/month for SSD backed storage with far lower latency figures.

Dual SIM Dual Standby (two or more SIMs, one radio) is cheaper, less battery, less space, and usually good enough. It's literally a few dollars, not 200-300.

> Gofmt's style is no one's favorite, yet gofmt is everyone's favorite.

I'd argue it has, but that's not the point. IPv4 is pretty much mandatory for most users of the internet. Yes, individual users probably neither know nor core whether they're on IPv4 or IPv6, but it's so difficult to run IPv6-only that you just wouldn't bother.

Trying to teach someone about how to use ULA vs. GUA only leads to headaches. In fact, I'd go so far as to say the reason why the internet became so ubiquitous was because of NAT -- static internal addressing is pretty much fundamental to an easy-to-use experience. Having multiple addresses on a host only makes things far more confusing, so people don't bother, because IPv4 just works.

Meanwhile, having "custom properties" attached to each repo feels very much like administering JIRA, and schema-less YAML blobs that pervade the GitOps world.

Is it just me, or isn't the glaringly obvious solution to this an actual database and API, rather than just tacking on random bits of metadata that have no real-time validation etc?

Though I did a quick check and apparently DRM+ uses QAM-16, so perhaps my knowledge is far too out of date :S

Some people save energy by turning their appliances off at the plug rather than leaving them on standby. Clearly Radio 4 chose to avoid having Brian Blessed on too frequently instead ;)