Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

What's wrong with HTTP basic auth for this use case?

https://subscriber-id:subscriber-token@podcast.host/feed.rss

In what way does this "pollute" or "pervert" the open standard? Apple and Spotify are companies, not people, this is not high school, Apple is not "bully"ing Spotify, they have a business relationship.

In general your comment is loaded with emotional language that seems to muddle the issue rather than clarifying.



I didn't consider HTTP basic auth as part of the open ecosystem because it's not, as far as I know, widely supported by clients. Is it? Maybe my assumption was wrong.

But it's also not part of the original "open" podcast vision because it is closed by definition, on an access level, and opens the door to tracking. Wouldn't most users in the open ecosystem be confused by an auth prompt? Wouldn't it be better for the open ecosystem if this sort of essentially closed feed just be cleanly inside Spotify (or whoever else's app)? This is my thinking, although I appreciate that opinions can differ.

I agree my language like "pervert" and "corrupt" can read as emotional, but I deployed it because I was trying to argue against the people who criticize Spotify using similar language, not to criticize anyone or raise emotions. If anything I'm trying to praise Spotify here.


As someone with a few Patreon feeds, yes it is widely supported, and the few that don't support it do support URL parameters so a token works fine as well.


I Patreon (verb?) two podcasts and for both it was just a custom URL, I don't recall an option to use a password though maybe I missed the option.


Patreonize? :)

I pay for a couple podcasts as well and I’m pretty sure they just sent me a custom RSS feed to drop into my player.

No way in hell am I going to fall for Spotify’s middle-manning attempts here. Hopefully they don’t manage to close off too much.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: