Fun with Feeds (a proof of concept RSS reader)

[oeyoews]

It seems that this echarts addon of mine is used. Maybe a judgment needs to be added.

[gavcloud]

thank you I understood now. I removed the tiddler using that and tiddlywiki wiki --build feed is working.

[oeyoews]

The built-in electron.net.request method is not affected by CORS, which makes it very convenient for bypassing certain restrictions, such as some GitHub APIs.

[strivenword]

@saqimtiaz

the primary constraint is lack of CORS (cross domain communication) support for many of the servers hosting the RSS feeds, which necessitates use of a proxy server.

CorsProxy.io has a free tier that only works on localhost, apparently. To the extent of my understanding, it is possible to fetch RSS feeds from server environments, not directly from web browser clients. So, theoretically, it should be possible to avoid CORS by using TiddlyWiki through Node.js on localhost. And since the free tier from CorsProxy only works from localhost, some of the limitations are the same. In either case, one couldn’t simply share a flat-file TiddlyWiki and have the RSS fetch functionality work.

Has anyone ever successfully implemented RSS fetching with TiddlyWiki using a pure Node server solution?

[saqimtiaz]

@strivenword

Has anyone ever successfully implemented RSS fetching with TiddlyWiki using a pure Node server solution?

If you are running TiddlyWiki on node.js, it is a handful of lines to implement a proxy route for the server that can be used to query cross domain URIs.

[nemo]

I run TW on node, and happy to give it a try (in no small part because just a few days ago I was pondering TW as an RSS reader, and so am pleased to see the thought has been looked at already, and delighted that coincidentally this thread has revived itself too)

However, I’ll need some details on what those “handful of lines” would actually be