I typically would follow news on OpenAI using the RSS feed at openai.com/blog/rss.xml. However, I noticed recently that the OpenAI website was revamped, and the RSS link does not work anymore, and I am also unable to find the new link if it exists.
Is the RSS feed gone forever or will it come back at some point? As an RSS enthusiast and someone who likes to be updated on OpenAI’s stuff, I would be very disappointed if it’s the former.
I tried looking for a way to contact support about this but I was redirected to a chatbot with limited options with no way to contact human support. Please let me know what other options I should try to get into contact with OpenAI regarding this issue.
Just generated an RSS feed through Open RSS for the news section below. The forum wont let me post links so change [dot] to an actual dot.
openrss[dot]org/openai.com/news
Since the feed is new, it only has last couple of entries. But it should populate new items. It at least is a workaround until Open AI can provide one.
The RSS feed was the only channel through which I followed OpenAI’s blog/news; it’s regrettable that an RSS feed is not currently provided.
I hope the RSS feed comes back–it would grant OpenAI’s blog a much larger readership.
Totally agree: the RSS is the noiseless and focused way to get updates on products. I hate social networks as new channels, they steal my time. Visiting website’s news in hope to get updates steal my time too.
Devs, please, add RSS, that is a matter of few hours of work.
Thanks!
You seem to be right. Seems that now my previous link redirects to https://openai.com/news/rss.xml. I guess there is now an official feed again. Although it seems the posts in the feed are not in chronological order. Then again most RSS readers should handle that with no problem when sorting.
NOTE: I had trouble getting this feed to work on RSS Guard. When I asked the dev about it, he didn’t ran into any issues. For me, changing IP addresses, user-agents, RSS readers and even OS’s did not fix the issue. Making it weirder was that the feed was still accessible via a browser and curl with a correct user-agent parameter. Turns out RSS Guard has a feature to enable “HTTP/2.0” and when I enabled that feature, the feed magically worked. I don’t know if this is the correct solution, but I am documenting it anyways in case someone comes across a similar issue.