Post ASMIEwlRZdMLYcZRsu by dave@podcastindex.social
 (DIR) More posts by dave@podcastindex.social
 (DIR) Post #ASMIEw8ntIS1cmUaem by dellagustin@fosstodon.org
       2023-02-04T14:34:48Z
       
       0 likes, 0 repeats
       
       @dave are you adding to the exported DB the info on whether the podcast feed can be fetched with CORS?If not, would you consider doing it? It would be a good info for people considering to implement offline first PWAs.
       
 (DIR) Post #ASMIEwlRZdMLYcZRsu by dave@podcastindex.social
       2023-02-05T04:49:34Z
       
       0 likes, 0 repeats
       
       @dellagustin I’m not sure I understand what you’re asking. Can you give a bit more detail?
       
 (DIR) Post #ASMIQc887I6H2LkH7g by jamescridland@podcastindex.social
       2023-02-05T04:51:36Z
       
       0 likes, 0 repeats
       
       @dave @dellagustin A new podcast website I set up this weekend - I've ensured CORS on the RSS, transcripts and audio. Probably one for your client to check though - CORS can be set on a host-by-host basis.
       
 (DIR) Post #ASNKpw0DlL2gyaCvLc by dellagustin@fosstodon.org
       2023-02-05T16:53:24Z
       
       0 likes, 0 repeats
       
       @dave what I mean here is that I would like to know which feeds can be fetched js code running on different domains (thus, CORS). The reason is that a PWA can't simply fetch a feed that does not allow CORS. With that info, people interested in having podcast aggregators as PWAs could do advocacy work, specially at large hosts, for allowing CORS at podcast feeds (and other artifacts such as chapters, the audio file, transcriptions, etc...).