The names are fairly obvious from a semantic standpoint, but in a technical sense Fresh, Archived, and Recently read are a black box. Someone not involved in programming The Arsse (for legal reasons) would probably have to look at the source code of TTRSS and write a specification defining the parameters of these feeds.
For Fresh and Recently read, there's clearly some temporal cut-off, but this is not apparently defined anywhere.
In the case of Archived, are articles automatically archived, or is this entirely manual? If it is only manual it can probably be ignored: the API has no means of archiving articles.
TTRSS has a set of "special" virtual feeds:
1. All articles
2. Fresh articles
3. Starred articles
4. Published articles
5. Archived articles
6. Recently read
The names are fairly obvious from a semantic standpoint, but in a technical sense Fresh, Archived, and Recently read are a black box. Someone not involved in programming The Arsse (for legal reasons) would probably have to look at the source code of TTRSS and write a specification defining the parameters of these feeds.
For Fresh and Recently read, there's clearly some temporal cut-off, but this is not apparently defined anywhere.
In the case of Archived, are articles automatically archived, or is this entirely manual? If it is only manual it can probably be ignored: the API has no means of archiving articles.
jking
added this to the 0.2.0 milestone 7 years ago
There is a freshness maximum age in preferences which defaults to 24 hours. Recently read is probably simply a view of read articles sorted in descending order by read timestamp.
The archive appears to be entirely manual, as there is no similar preference for auto-archiving. It's possible that archiving blocks purging as starring does in NextCloud News, but as archiving is an inert feature in the TTRSS protocol and no other prospective protocol obviously has an archive, this point is moot.
There is a freshness maximum age in preferences which defaults to 24 hours. Recently read is probably simply a view of read articles sorted in descending order by read timestamp.
The archive appears to be entirely manual, as there is no similar preference for auto-archiving. It's possible that archiving blocks purging as starring does in NextCloud News, but as archiving is an inert feature in the TTRSS protocol and no other prospective protocol obviously has an archive, this point is moot.
TTRSS has a set of "special" virtual feeds:
The names are fairly obvious from a semantic standpoint, but in a technical sense Fresh, Archived, and Recently read are a black box. Someone not involved in programming The Arsse (for legal reasons) would probably have to look at the source code of TTRSS and write a specification defining the parameters of these feeds.
For Fresh and Recently read, there's clearly some temporal cut-off, but this is not apparently defined anywhere.
In the case of Archived, are articles automatically archived, or is this entirely manual? If it is only manual it can probably be ignored: the API has no means of archiving articles.
There is a freshness maximum age in preferences which defaults to 24 hours. Recently read is probably simply a view of read articles sorted in descending order by read timestamp.
The archive appears to be entirely manual, as there is no similar preference for auto-archiving. It's possible that archiving blocks purging as starring does in NextCloud News, but as archiving is an inert feature in the TTRSS protocol and no other prospective protocol obviously has an archive, this point is moot.
The "Recently read" feed appears to actually use the same 24-hour cut-off as the "Fresh" feed. This will be relevant for
getHeadlinesonly.The "Fresh" feed is only ever unread articles.