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
Mike Doughty used to sell burned CDs of the show at the merch table (afterwards in case anyone was worried he was using some Is Chicago, Is Not Chicago technique to violate the space time continuum) back in the aughts.
It's not just a subscription thing, you can purchase individual shows ala bandcamp too.
But yeah, jam bands have really embraced this more than any other category of artist - it's quite common even among low-mid tier jam bands that every single show ends up on Nugs. These bands are often pretty friendly to recordists too (a recent show I was at has two recordings on the IA as well as the Nugs version. Everyone's happy!)
Phish gives people a code that lets them access the show they attend on livephish.com without a subscription. You can subscribe and get access to all of the shows. I think livephish.com is run by and/or shares the same platform as nugs.net but it's a different subscription.
Strong agree. We were using Fargate nodes in our us-east-1 EKS cluster and not all of our nodes dropped, but every coredns pod did. When they came back up their age was hours older than expected, so maybe a problem between Fargate and the scheduler rendered them “up” but unable to be reached?
Either way, was surprising to us that already provisioned compute was impacted.
Saw the same. The only cluster services I was running in Fargate were CoreDNS and cluster-autoscaler; thought it would help the clusters recover from anything happening to the node group where other core services run. Whoops.
Couldn't just delete the Fargate profile without a working EKS control plane. I lucked out in that the label selector the kube-dns Service used was disjoint from the one I'd set in the Fargate profile, so I just made a new "coredns-emergency" deployment and cluster networking came back. (cluster-autoscaler was moot since we couldn't launch instances anyway.)
I was hoping to see something about that in this announcement, since the loss of live pods is nasty. Not inclined to rely on Fargate going forward. It is curious that you saw those pod ages; maybe Fargate kubelets communicate with EKS over the AWS internal network?
I'm a software engineer specializing in building stable, scalable consumer-facing websites and refactoring large codebases. Looking for consulting or contract work, working solo or with a team. Some previous projects:
- Built a comprehensive CI ecosystem for a 30+ app polygot environment using Jenkins, Docker and Github. Reduced test suite run time in their monolith from 25 minutes to 10.
- Refactored the real time auction draft system for a fantasy sports company to increase stability and support four times as many users without additional hardware.
Indeed - I've hiked almost 3k miles carrying an umbrella. Worn rain gear is a compromise between breathability and waterproofness - even if you keep the rain out, you'll sweat and it's trapped inside. Umbrellas keep rain off you, are very breathable, and double as sun protection when it's really hot. Only downside is when it's windy and rainy, so it's nice to have a poncho too.
I'm a software engineer specializing in designing and building stable, scalable consumer-facing websites and refactoring large codebases. Currently, I'm helping clients with dev ops problems like setting up web apps to scale for 10x more traffic, profiling/optimizing slow code paths, and building analytics pipelines with AWS.
Before that, I was a principal engineer at Vox Media, and worked on some notable projects:
I'm a software engineer specializing in designing and building stable, scalable consumer-facing websites and refactoring large codebases. Currently, I'm helping clients with dev ops problems like setting up web apps to scale for 10x more traffic, or building analytics pipelines with AWS.
I'm a software engineer specializing in designing and building stable, scalable consumer-facing websites and refactoring large codebases. Currently, I'm helping clients with dev ops problems like setting up web apps to scale for 10x more traffic, or building analytics pipelines with AWS.
Before that, I was a principal engineer at Vox Media, and worked on some notable projects:
