Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Generic timelines #450

Closed
elegaanz opened this issue Feb 25, 2019 · 0 comments · Fixed by #525
Closed

Generic timelines #450

elegaanz opened this issue Feb 25, 2019 · 0 comments · Fixed by #525
Labels
A: Backend Code running on the server C: Discussion We need to talk C: Enhancement New feature or request

Comments

@elegaanz
Copy link
Member

This is a proposal to re-work our approach to timelines, to make it more flexible. The idea would be to have different timelines stored in the database. A timeline is basically a list of posts, and some rules to know if a post belongs to this timeline or not.

The benefits would be that it would be easier to customize the feeds on the homepage (one could select the timelines to display) hiding the federated feed on a personal blog, or showing various hashtag timelines on themed instances. It would also allow to organize your subscriptions, and eventually keep an eye on blogs without even following them.

I can see two problem to this approach:

  • would the performances be good enough? Handling timelines this way would probably mean that we should check if a post should go in all the existing timelines when it is created/received (currently the feeds are computed on request every time we display them).
  • how do we store the rules for a timeline in the database, as they should ideally follow a complex logic (so that we could build, for instance, a timeline with only a specific hashtag, from specific instances but excluding a some blogs)

(I didn't opened a Loomio discussion because this seemed to be a technical discussion, but I can copy my message over there if needed)

Plume version (and/or commit): 0.2.0

@elegaanz elegaanz added C: Enhancement New feature or request A: Backend Code running on the server labels Feb 25, 2019
@trinity-1686a trinity-1686a added this to To do in Instance customization via automation Feb 26, 2019
@elegaanz elegaanz added the C: Discussion We need to talk label Mar 12, 2019
Instance customization automation moved this from To do to Done Oct 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: Backend Code running on the server C: Discussion We need to talk C: Enhancement New feature or request
Projects
Development

Successfully merging a pull request may close this issue.

1 participant