Inconsistent behavior of "Read" button

[mcnesium]

First of all thank you for sharing this great app! I am aware that it is claimed "opinionated", so this is rather a question than a bug report.

Using the button underneath any article entry in the list on the Unread page, e.g. http://localhost:8080/unread, makes the respective article entry disappear right away and shift the rest of the entry list, while hitting the read-button on a dedicated feed-page, e.g. http://localhost:8080/feed/1/entries or a category page, e.g. http://localhost:8080/category/1/entries, the article is marked read by turning its headline gray, but keeps in the list.

While I like the latter better, both ways of behavior are legitimate imho. I would just expect the read-button to behave the same way everywere. So I would like to ask whether this behavior is on purpose or maybe by accident and might want be fixed.

[mcnesium]

As a second thought, when using the swipe gesture on a mobile device to dismiss an entry, it makes sense indeed that the item disappears then, instead of just being marked red.

For now the swipe gesture also removes an item on /unread/ page, but on feed- or category-pages it only marks them as read.

So I would like to suggest a UX improvement: split up the functionality between the read-button and the swipe gesture, so that the read-button only marks the article but keeps it in the list, while the swipe gesture removes it from the list.