stefansundin

I would love if this could also convert between timezones. My servers use UTC, so it would be nice if it could print the converted time as well.

Yes! Unfortunately it is no longer mainstream since the monetization opportunities are fewer. But a lot of tech-savvy people prefer it for many reasons:

1. You get a personalized view of what you have and have not read. 2. You can scan over a lot of posts very quickly, and pick out what you want to read. 3. You can aggregate a lot of different websites in a single place. No need to visit each website individually. 4. Increased privacy. 5. Less tracking. 6. Increased control. 7. Fewer ads.

Probably more reasons, but these are the primary reasons why I still prefer RSS.

> Though it should be “then you will be able”.

Fixed. Thanks! :)

> What if we don’t have control over the frequency of requests (e.g. using a service like Feedly)? Do those happen often enough that we’d need to host the app ourselves?

I know the wording is a bit vague, and I know that most services don't let you customize this. I added it after I suddenly started receiving tons of traffic caused by, I suspect, a single user. This person was purposefully fetching feeds multiple times a minute.

Anyhow, if you aren't actively trying to abuse the service, you should be good. Some RSS readers have "boost" features to fetch feeds more frequently (often a paid feature).

Once I am able to add some good caching, then I may be able to remove that notice. But right now, the service is kinda overloaded and that is why some of the services (Twitter and Instagram in particular) may give you errors at the moment.

I will look into this. Thanks!

RSSBox used to have Facebook support (but only for public pages, no personal content), but when Facebook started cordoning off their API two years ago, I had to turn it off since I was unable to get my application approved. The code is still there, but I am doubtful it would work even if you manage to get an API key that works. I think the best option may be to scrape the web content now, unfortunately.

You are correct in that it is somewhat starved of resources. The free Heroku instance that I host is running on the free Heroku dyno (512 MB RAM). I do not have a good caching solution currently, which is why Twitter and Instagram are almost always returning errors now. I suspect a single person is responsible for most of the issues (see GitHub issue #38). It's actually amazing how well it runs considering how much traffic is thrown at it.

At some point I hope to get enough time to implement a caching solution, which should hopefully resolve most of these issues.

Not at the moment, unfortunately.

Instagram used to have an open API, but that is closed down now. The app is currently using some private-ish endpoints, but they are ratelimited. I need to add caching. More people have started using my app recently, and I have not had time to add caching yet.

Sorry, recently the ratelimit has been exhausted almost all of the time. I need to add caching to solve this problem but have not gotten to it yet.

Sorry about the rate limit issue everyone. I tweeted the ipinfo guys and it seems like they're willing to give me a limit increase, but they haven't yet. You can give them a nudge here: https://twitter.com/ipinfoio/status/861701746158170112

Also, if you want to self-host the website (and thus get your own ipinfo ratelimit quota), it seems like the Google Maps API now requires you to get an API key (it didn't before). Get one here: https://developers.google.com/maps/documentation/javascript/...

There's a bash function in the README:

function traceroute-mapper { xdg-open "http://stefansundin.github.io/traceroute-mapper/?trace=$(tra... -q1 $* | sed ':a;N;$!ba;s/\n/%0A/g')" }

Kinda.. You can download the HTML file and host it on localhost, but it still relies on ipinfo.io. If you can figure out how to use e.g. the MaxMind GeoIP database in javascript, then it should be simple enough to hook up and run everything locally.

Hi Dave. Because of overzealous filters, unfortunately. The "EasyPrivacy" seems to block the whole ipinfo.io domain if it's included as a third-party request.