Yes but that is just a tiny part of the whole CF worker ecosystem. The other services are not open source and so the lock-in is very very real. There are no API compatible alternatives that cover a good chunk of the services. If you build your application around workers and make use of the integrated services and APIs there is no way for you to switch to another provider because well, there is none.
It's really up to the artists. Many are surprisingly cool with it, though there are a few notable exceptions (i.e. Prince). Sounds like the artist in this particlar case gave their blessing.
Many bands (like GD and Phish) specifically note in their rider that venues must allow and provide space for tapers to bring their rigs in.
A sibling comment in this thread pointed out my project Relisten[0], which now has over 4,000 bands who have given explicit permission for people to tape, record, and share their concerts non-commercially. We've been operating our FOSS platform for 12 years, and most of the audio is hosted by Archive.org. I can't tell you how many bands have begged us to add them to our platform.
Prince had intense business instincts, not just for becoming a vertically integrated multi-instrumental composer manager, bandleader and of course prodigious artist. Its rumored that to ruin the market demand for his bootleggers, Prince started his own sockpuppet bootleg label, that eventually released over four hundred CDs of content. Concerts, studio alternate cuts, and of course After-Shows. That label is curiously named Sabotage.
Whether the rumor is true or not, I can't confirm. What I can tell you is it's an amazing soundboard quality collection of his work product that I'm still not all the way through exploring after it briefly circulated among fans for a brief moment shortly after his death.
> though there are a few notable exceptions (i.e. Prince)
There was an episode of "What's Happening" when Rerun gets in trouble for bootlegging a Doobie Brothers concert, does anyone remember? It aired when I was a kid and now I somehow still feel guilty when I listen to bootlegs.
Yup, just remembered around ’99 I bumped into “Rerun” in full costume dancin’ for a small crowd in the parking lot of a Sugar Hill Gang concert in Santa Monica. Didn’t carry a camera in those days, as they weren’t allowed inside anyway. :-P
We landed an update on mobile last week that brought all 4,000 artists with a "collection" onto Relisten. That'll be coming to the web and sonos shortly as well.
We've been discussing the Aadam Jacob's collection with the archivists for some time. It comes with its own unique UX[0] and data constraints so we've been iterating on that and waiting for a critical mass of uploads before tackling it. We're getting closer though.
I agree with most of the sentiment in these comments. Archive and share non-comercially all the things!
[0] it's not "one" artist so it requires some custom UI, it should be unified through a single Aadam Jacob's collection, and it has a unique data path/structure on Archive.org relative to other collections
I run Firefox latest so it should work. There's always a risk when going from HTML5->Web Audio. There's an occasional blip that's impossible to avoid (or at least, I have never found a solution). It doesn't happen every time though. Try going from track 2 to track 3 in the second tab of the demo (if both are "READY" as web audio).
The problem with exclusively using the web audio API is that the entire track must be loaded into memory before playing it, whereas HTML5 loads progressively. So we use both to balance the techniques.
In prior versions of the library, we'd load the track in parallel to HTML5 and make the switch mid-track so it's actually far less noticeable even if it does blip. I'm considering adding that to the new version.
Another alternative is building a custom buffer using RANGE requests to exclusively drive it via the web audio API. But obviously that is a far more complex undertaking (and requires the server to support RANGE requests). I'm open to implementing it, though.
Gapless 5 was actually the precursor to this library over a decade ago, so Rego deserves full credit. They built the first example of gapless playback on the web and I took inspiration from their techniques.
Gapless 5 has a built in UI and style. Our library is headless: you bring your own UI and controls. It just depends on what your use-case is.
RSC by design does not ship everything to the client. That's one of its basic premises. It ships markup, composed in client interactivity, but you can shed a lot of the code required curate that markup.
I obviously meant traditional React components, not RSC. RSC can eliminate some client code, but they can be very awkward to use in practice, and lines between server and client get blurry really fast. The mental model is difficult for many to fully grok. I say this as someone who has lead engineering teams with folks of varying skill levels. RSCs are not worth the extra complexity and mental overhead they bring.
https://github.com/cloudflare/workerd
reply