When marking an article un/read or un/starred, TTRSS allows the client to blindly instruct the server to toggles articles' state instead of explicitly setting one state or another. This is incredibly poor design in a potentially high-latency protocol, but it must be supported.
Unfortunately, I implemented the toggle incorrectly: the state always ends up being false instead of swapped.
When marking an article un/read or un/starred, TTRSS allows the client to blindly instruct the server to toggles articles' state instead of explicitly setting one state or another. This is incredibly poor design in a potentially high-latency protocol, but it must be supported.
Unfortunately, I implemented the toggle incorrectly: the state always ends up being false instead of swapped.
jking
added this to the 0.2.1 milestone 6 years ago
When marking an article un/read or un/starred, TTRSS allows the client to blindly instruct the server to toggles articles' state instead of explicitly setting one state or another. This is incredibly poor design in a potentially high-latency protocol, but it must be supported.
Unfortunately, I implemented the toggle incorrectly: the state always ends up being false instead of swapped.