fox
21
you’re (well, not you specifically, an api consumer) is supposed to login as necessary and otherwise maintain a single login session. not only logging in for every request bloats up tt-rss sessions database, it’s simply terrible application design.
TT-RSS has app passwords?! I just hunted it down, implemented that, and it fixed the problem with my Fiery Feeds. Thank you.
At the risk of breaking Fiery Feeds for myself, I’ll have to agree with you. Going through the login process this many time in such a short period seems very wasteful. Rate limiting API endpoints especially one used for authentication would make sense as well. I have sent the developer an email. Hopefully they adjust their app to send requests less frequently.
xtaz
25
I use Fiery Feeds as well. I’ve just checked and my ttrss_sessions table had 19854 rows in it. If I truncate the table I can see that every time the app is refreshed it adds 4 rows to this table.
In comparison the tiny Reader app adds 1 row to the table and then persistently stays logged in. So yes, guess which one is using the API correctly and which one isn’t!
On the plus side I’ve also now learnt that app passwords is a thing 
