I'm really not sure where you got that idea. You asked how much of this can be omitted if you want to only publish privately, and the honest answer is, you can reasonably skip all of what I described. If you plan to share a direct link only, the RSS won't be very practical, as that's for publishing publicly, especially to podcast services. Just upload to a private location on a web server or what have you, and share the direct link.
I am sorry if something I said gave you the idea that I was being sarcastic. That said, I would recommend getting into the habit of reading the best into a statement, rather than the worst.
Thanks for the follow-up, sorry for assuming the worst. What I need to do is leverage the podcast client's ability to subscribe and mark played. I assume I need an RSS link for this, at least initially. If not, is there another type of document/protocol or endpoint I can serve so the client sees it as a usable podcast?
I'm not entirely sure. I suppose if you want people to be able to use a client with the podcast, but not list it anywhere, you could still set up the RSS feed on the same web server where you host your podcast episodes, and provide the link directly to said RSS.
But, honestly, I'm not sure. I think you'll need to experiment a bit. Let me know how it goes! I'm quite curious now. ;)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Probably all of it. The purpose of the RSS is to publish it.
Well excuuuuuse me for posting.
I obviously don't belong here.
Blinks.
I'm really not sure where you got that idea. You asked how much of this can be omitted if you want to only publish privately, and the honest answer is, you can reasonably skip all of what I described. If you plan to share a direct link only, the RSS won't be very practical, as that's for publishing publicly, especially to podcast services. Just upload to a private location on a web server or what have you, and share the direct link.
I am sorry if something I said gave you the idea that I was being sarcastic. That said, I would recommend getting into the habit of reading the best into a statement, rather than the worst.
Thanks for the follow-up, sorry for assuming the worst. What I need to do is leverage the podcast client's ability to subscribe and mark played. I assume I need an RSS link for this, at least initially. If not, is there another type of document/protocol or endpoint I can serve so the client sees it as a usable podcast?
I'm not entirely sure. I suppose if you want people to be able to use a client with the podcast, but not list it anywhere, you could still set up the RSS feed on the same web server where you host your podcast episodes, and provide the link directly to said RSS.
But, honestly, I'm not sure. I think you'll need to experiment a bit. Let me know how it goes! I'm quite curious now. ;)