cheeaun / phanpy

A minimalistic opinionated Mastodon web client
https://phanpy.social
MIT License
935 stars 85 forks source link

Automatically bookmark posts based on customisable interaction criteria #581

Open confluence opened 2 days ago

confluence commented 2 days ago

Is your feature request related to a problem? Please describe.

I typically open interesting-sounding links in new background tabs to read later. I frequently find myself reading an article, wanting to boost the post where I found it, and having to perform a forensic investigation in my feed to figure out how to find a post that I may have scrolled past hours before, which may be a boost of an older post, and may not have any identifiable keywords in the body.

At the same time, I find the post saving / bookmarking feature completely useless, and never bookmark posts manually.

Describe the solution you'd like

It would be really useful if I could configure Phanpy to automatically bookmark a post if I click on a link inside the post. This would make it trivial to find the source of an external page. Perhaps this could be extended to other configurable types of interaction -- for example, any post I reply to, or even any post that I like or boost or expand. (I don't know how achievable this is in Javascript; some of these may be difficult or impossible.)

This would turn the existing saved / bookmarked posts feature into a private (ish) history of interactions which may not otherwise be recorded. I realise that while bookmarks are not visible to other users, they are still stored on the server and not locally, so they are not truly private, and not everyone may want to have this kind of behaviour enabled, which is why it should be opt-in and configurable.

Describe alternatives you've considered

I could manually bookmark a post whenever I open a link in that post, but in practice I never remember to do this.

Phanpy currently saves shortcuts locally, so perhaps a feature like this could also save state locally instead of using bookmarks -- this may be preferable for both implementation and privacy reasons. Since my use case would be satisfied by a short-term record stored on the same device where I click on links, this would also solve my problem.