-
-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR]: Problem with synchronizing unread mesages on Reedah #382
Comments
Wow, this seems like some major clusterfuck from my side. Will investigate. |
OK, I fixed a couple of Reedah-related bugs. Will continue fixing the rest of it tomorrow. |
@cocowash OK, I fixed the part with repeated unnecessary obtaining of token which is now obtained correctly only once. Updates should be now much much much faster, please check with latest development build, please. https://github.com/martinrotter/rssguard/releases/tag/devbuild |
I tested with devbuild, added 100 feeds and initial sync of messages took 25 seconds with 70 messages per feed and 1 minute with all messages per feed. |
With the newest Development build all syncs a lot faster. Nonetheless, for me now its evident that none of the YouTube feeds are working. (no read or unread messages) [As an example this is the regular structure I use for YouTube feeds on Reedah https://www.youtube.com/feeds/videos.xml?channel_id=UCJHA_jMfCvEnv-3kRjTCQXw] any of the YouTube feed is visible in Reedah but empty on RSS Guard. Could you make a test with a YouTube feed in your account pls? Edit: Also I found certain feeds that remain empty (no read or unread messages) during these tests on RSS Guard. All have in common that download a xml file if they are pasted on a browser. These are some examples of this issue: |
Thank you, I will test them. :) |
Fixed with fd7e43a. The error was that "id" of the feed was not properly encoded in request URL so the query failed for all feed "id"s which contained "?". Should now work. |
#### Brief description of the issue.
Rss Guard syncs already read messages but can't reach to unread messages.
#### How to reproduce the bug?
#### What was the expected result?
The Program syncs fully with Reedah in seconds.
#### What actually happened?
It took me 2 days to have an unread message
#### Other information
I contacted Reedah support and they kindly wrote me back:
The text was updated successfully, but these errors were encountered: