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

Add an option to display local timeline on homepage by default #617

Open
agateblue opened this issue Jun 16, 2019 · 4 comments
Open

Add an option to display local timeline on homepage by default #617

agateblue opened this issue Jun 16, 2019 · 4 comments
Labels
A: Backend Code running on the server A: Front-End Related to the front-end C: Enhancement New feature or request
Milestone

Comments

@agateblue
Copy link
Contributor

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

When you use Plume as a regular blog engine, and don't really care about the discovery part, it's annoying to have the federated timeline showed as the default.

Consider https://blog.funkwhale.audio/: it's mainly used for announcements about Funkwhale releases, yet I cannot simply link our audience to https://blog.funkwhale.audio/, because it shows completely unrelevant entries (in multiple languages, absolutely unrelated to Funkwhale, etc.)

My current workaround is to always link to https://blog.funkwhale.audio/local, but this is far from perfect: if users click the home button, they will land on the homepage anyway, and people searching for funkwhale blog on search engines will still arrive here.

Describe the solution you'd like

I'd like an option to promote the local feed of my Plume instance on the landing page, instead of the federated one. The most basic option I can imagine is an environment variable, like HOMEPAGE_CONTENT={all|local}, with all being the default (current behaviour).

Setting HOMEPAGE_CONTENT=local would display only local content in the homepage, which I suspect is only a matter of adding proper if blocks in the homepage template.

This isn't required to solve this ticket, but we could also imagine supportingg more complex customization using that variable. E.g. specifying HOMEPAGE_CONTENT=local,federated would display the local and federated blocks, in that order. I think it would give an easy option to display the federated feeds, without being annoying to instance owners who want to show their own blogs first :)

@agateblue
Copy link
Contributor Author

Possibly linked to #450, and closable when Generic Timelines are implemented :)

@elegaanz elegaanz added A: Backend Code running on the server A: Front-End Related to the front-end C: Enhancement New feature or request P: Medium labels Jun 16, 2019
@elegaanz elegaanz added this to To do in Instance customization via automation Jun 16, 2019
@elegaanz elegaanz added this to the 1.0 milestone Jun 16, 2019
@elegaanz elegaanz removed the P: Medium label Aug 1, 2019
@KitaitiMakoto
Copy link
Contributor

@agateblue I propose (and will release) to make local timeline default: https://fediverse.blog/~/PlumeDev/Plume%20Development%202022-05-06
Please comment if you have any idea!

@agateblue
Copy link
Contributor Author

thank you @KitaitiMakoto, I'm not using Plume anymore, but I still think it's an improvement!

@KitaitiMakoto
Copy link
Contributor

Thanks!

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 A: Front-End Related to the front-end C: Enhancement New feature or request
Projects
Development

No branches or pull requests

3 participants