1,256 karma · joined August 20, 2009
Basically embarrassed by everything I said more than a few years ago. This statement, however, is perennial.
[ my public key: https://keybase.io/chrisrhoden; my proof: https://keybase.io/chrisrhoden/sigs/pLa3Wia0cebxwDtOIDo1QjfqF8MclTNpELYuox3C9Jo ]
They seem to be, for now. Not sure whether that's because it's just easier on iOS or habit. In any event, we're pretty sure that won't last forever.
GUIDs, as defined in the RSS spec, are also not required to be globally unique - they're only supposed to be unique to the feed that includes them. This, combined with the fact that a feed that doesn't include them at all is still completely valid, is usually a pretty big stumbling block for developers looking to consume RSS. This is the biggest issue that got talked about during the Atom vs RSS discussion of a decade ago.
And if you're referring to the UUID I'm automatically adding to every feed, it's so that there is an unchanging canonical way to refer to a feed that follows it across URL changes etc. The sibling comments get it perfectly.
My headline is in response to certain voices in the industry which seem to be rooting for the end of RSS in favor of proprietary APIs - essentially, the YouTube-ization of podcasts. There's lots to unpack there, and to a certain extent it seems likely that more things will move away from open standards, but I'd prefer to hold the line to the best of our ability.
The short answer is, we're still figuring it out! Part of the approach we're taking is about letting us test things with real users against live feeds without bugging people every time we change our minds (about the content of the extensions or about the format of them), and we're still at the very early phases.
The somewhat longer answer is, we know we would like to get better promotional / onboarding data from the feeds - including things like a 140 character description for the feed that references similar content from other media (like tv), or the best gateway episodes to present new users with. Ordering is a big one, for shows that are e.g. serialized, or even for shows with short, strictly ordered series embedded (think 2 part specials in a daily news feed). The folks at https://syndicated.media (including me) have been keeping track of ideas on Github (https://github.com/syndicated-media/sn-spec/issues), and you would be most welcome in the slack group for syndicated media, where things are just starting to pick up. Shoot me an email if you would like an invite!
Join us in creating a delightful consumer podcast listening experience that is scalable, beautiful and of the highest quality. We want to create something that people love and recommend to their friends.
We're looking for someone to join our brand new team working on our Website and APIs. You'll have the opportunity to influence the technical and product decisions at a seed stage company that's rethinking radio. You'll work directly with members of the founding team, and add your own expertise to the conversation. You'll shape the future of podcasts by helping to build an exceptional listening experience for our apps and on the web.
We currently have a mix of Rails, AWS Lambda (using Node), Postgres, and ElasticSearch on the backend, and CSS, HTML, XML, and some XSLT for good measure on the frontend. Javascript is coming very soon (React or Angular look likely). Everything our stack does is important, but none of it is precious. We're looking to pick up some serious speed in the coming months.
We're only set up to handle employees in the US right now, but will try to work something out for an exceptional candidate.
More Info & Apply Here: https://radiopublic.workable.com/jobs/328055
Generally, a degree that comes after years of professional experience indicates a career switch, and those employees often need to work harder to find a good fit – usually, an organization that can make use of the skills they learned in the previous phase of their career. The reasons for this mostly come down to being very junior in skill level but having difficulty working under the same circumstances (low pay, trained by a 25 year old, potentially long hours...) of the typical junior hire.
There are exceptions to this, and there are many career switchers that navigate this well, but it's definitely worth keeping in mind.
No. From the very line you quoted:
> ... the cached data coming from the web is the _content_ of the page, where the checked out repo I'm in is dealing with the _layout_ of the page.
> What better than the real content for that?
Nothing, which is why that's what they do. They figure that the content of the page as it exists when you first load the development server is sufficient, and so cache that content. It seems unnecessary to me to have my development server update the content if a new post goes to production in the middle of my work.
RadioPublic is making listening to podcasts better by listening to the people who make them. I think we're inventing the future of radio.
We're looking for:
- Senior & Intermediate iOS Developers
- Senior & Intermediate Android Developers
We have a brand new team, with lots of fun problems to work on, and already some industry buzz around what we're doing.
Apply at https://radiopublic.workable.com/ or email me at chris [dot] rhoden [at] radiopublic.com and I will answer any questions you have.
As the developer of an RSS parser
Some people use the ability to be authorized to access an account on e.g. Facebook as a stand-in for authentication, but that's a different issue.
The rest of the shows are either strictly podcasts (Planet Money), not NPR produced (This American Life, Left Right & Center) or built specifically to fight this trend (Ask Me Another).
The reason why the way you listen matters is because NPR gets its money from broadcast stations. Every time they do something that has a whiff of asking listeners to donate directly to them, there is a backlash from the stations they are bound by contract to serve. If you listen via podcast and you don't donate to your local public radio station, there's no very good way for NPR to get paid for that listening. Ads exist, but they generally do not support this type of programming entirely and NPR has a complicated relationship with them anyway.
Your local station is probably not airing NPR content at every time of the day – it could be airing local content, or content produced or distributed by one of NPRs competitors. Interestingly, NPR is sort of a special case among these groups because they are bound to serve the broadcast channels not only by the current market realities, but by charter. It's why you are never asked to make donations directly to NPR, but to your local station (or in rare cases, directly to programs not produced by NPR).
At PRX you will find talented, passionate, and thoughtful people who create products that bring millions of listeners to shows created by public radio and podcast producers. We work with top-tier shows like This American Life, The Moth, and 99% Invisible, host the highly successful podcast network Radiotopia, and our own XM radio station. We are looking for enthusiastic, experienced, and creative software engineers with a passion for building robust, scalable applications with simple interfaces.
You'll work closely with our entire team on all phases of the development cycle including planning, development, and testing. We believe in open source and share as much as possible. If you check out our public GitHub repositories, you'll see our projects, team members, technologies and how we work: https://github.com/prx
Our web applications are primarily Ruby on Rails and Angular.js, and we develop native iOS and Android applications, but we'll use the right tech for the job.
Apply here: https://prx.workable.com/jobs/82747
The idea is that something like actually distributing the code to a front-line server seems to add to boot time, so if the lambda is not warm, it will be a little slower. If you keep it warm by having at least occasional traffic headed to the server, you're able to avoid this penalty.
If you look above, you'll see someone else did the math for you, and you're actually only talking about 864s of execution time, not 3M.
It also sort of looks like you just pulled up the pricing example which describes 3M requests that take 1s and worked back to it, because when you do the math you describe it works out to ~ 2.5M
It's my single biggest recommendation when people complain about the speed of the Internet in their home. More often than not, they're underspending on their networking equipment, not their ISP package.
At PRX you will find talented, passionate, and thoughtful people who create products that bring millions of listeners to shows created by public radio and podcast producers. We work with top-tier shows like This American Life, The Moth, and 99% Invisible, host the highly successful podcast network Radiotopia, and our own XM radio station. We are looking for enthusiastic, experienced, and creative software engineers with a passion for building robust, scalable applications with simple interfaces.
You'll work closely with our entire team on all phases of the development cycle including planning, development, and testing. We believe in open source and share as much as possible. If you check out our public GitHub repositories, you’ll see our projects, team members, technologies and how we work: https://github.com/prx
Our web applications are primarily Ruby on Rails and Angular.js, and we develop native iOS and Android applications, but we'll use the right tech for the job.
Apply here: https://prx.workable.com/jobs/82747