• Content count

  • Joined

  • Last visited


About Jacket

  • Rank
    Founder & Development
  • Birthday 03/31/1984

Contact Methods

  • Skype

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

3,312 profile views
  1. Server Changes?

    We have upgraded nginx to the latest version 1.13.8. There seems to be a breaking change in 1.13.6 that's causing Retrofit and OkHttp to throw this error. For OkHttp upgrading to the latest version seems to be fixing the issue. I'm not sure about Retrofit though. Can you try to upgrade it? Here's the link to the nginx issue - https://trac.nginx.org/nginx/ticket/1397
  2. Server Changes?

    There were some infrastructure changes over this weekend. However we haven't touched anything in the app logic. You will greatly help us if you check what is causing your app to crash? Do you get any response from the API? Do you have the usual headers present in the response? Do you receive http code 200 or something else?
  3. inoreader.com Outage?

    The issue should be fixed. We apologize for the slight delay, but we had to find the root cause.
  4. RSS Guard - Inoreader integration plug-in incoming

    That's great! I just tried to test it however and was greeted with a blank dialog when trying to start the OAuth2 process: This is on High Sierra. Let me know if you need further info for my environment.
  5. I understand the frustration. We are trying to find the right balance between protecting our databases from malicious feeds and not disturbing the regular usage. However we cannot leave this unattended. Our databases are quick, but we are not a huge company and doesn't have unlimited funds to expand hardware to unrealistic scale. We are talking about tens of millions of articles entering our databases each day. We keep them all forever. There are feeds which post several thousands of articles per day, 99% of which no one ever reads, mostly because those feeds only have one or two subscribers. We already have 12 million feeds so micromanaging is just not possible. Most cloud-based RSS readers also only fetch 20 items at most at each poll. We've increased that limit to 100 a while ago and ever since we have a problem with feeds that post too much content, because they organically reach the shortest possible polling interval. The only way for us to keep things in order is to place some kind of thresholds and watch what happens. We will try to further optimize those thresholds in the future.
  6. Account type degraded

    It was a global issue with the team settings. Should be fixed now. Sorry about the troubles.
  7. search reset

    Should be fixed too now.
  8. JSON Feed Support

    Yes, we are using only the "alternate" link in the RSS. My mistake with the terminology. However see here: https://jsonfeed.org/mappingrssandatom I think that's an issue with the DF feed. Or rather, now the feed is correctly presenting its internal and external urls.
  9. JSON Feed Support

    Do you have an example of an old feed that shows the alternate URL? I don't think that we've ever parsed and saved those alternate URLs. Where exactly? I think we've added it everywhere.
  10. JSON Feed Support

    That's coming too, although I don't think there will be a choice. We'll just choose the best format, maybe it will be JSON Feed Currently we are doing that with sites that offer both RSS and Atom. P.S. some new goodies:
  11. search reset

    Yes, it was inconsistent. It is now fixed. Thanks for the report.
  12. JSON Feed Support

    Yes, we really liked the idea and the best part is that the id is now mandatory. I wish it was in the RSS spec too...
  13. It was an issue with one of the database queries. It should be fixed now.
  14. Yes, this one seems like a regression. We'll look into it.
  15. inoreader has stepped on the gas!

    No changes at all to the backend recently. There's no reason for slow-downs and we are not seeing any on our monitoring. Can you tell us in more details what exactly feels slow?