[feat] Allow local timelines (or federated timelines) to be disabled #603

Closed
opened 2023-07-24 16:39:00 +00:00 by argxentakato · 3 comments

The idea

Allows local timelines (or federated timelines) to be disabled without modification of the source code.

The reasoning

For example, a local timeline is useless on a server used by only one person. Even if this is not the case, there are many cases where local or federated timelines are unnecessary.

Have you searched for this feature request?

  • I have double-checked and have not found this feature request mentioned anywhere.
  • This feature is related to the Akkoma backend specifically, and not pleroma-fe.
### The idea Allows local timelines (or federated timelines) to be disabled without modification of the source code. ### The reasoning For example, a local timeline is useless on a server used by only one person. Even if this is not the case, there are many cases where local or federated timelines are unnecessary. ### Have you searched for this feature request? - [x] I have double-checked and have not found this feature request mentioned anywhere. - [x] This feature is related to the Akkoma backend specifically, and not pleroma-fe.
argxentakato added the
feature request
label 2023-07-24 16:39:00 +00:00

this sounds like options for options sake - I don't think the above justifies making API-level changes

it sounds like you are wanting UI changes, not API - what would be the purpose of toggling off an endpoint?

this sounds like options for options sake - I don't think the above justifies making API-level changes it sounds like you are wanting UI changes, not API - what would be the purpose of toggling off an endpoint?
Author

Hmmm, indeed. I was thinking that it would be nice to be able to disable it at API level so that it is also reflected when using an 3rd party client.

Hmmm, indeed. I was thinking that it would be nice to be able to disable it at API level so that it is also reflected when using an 3rd party client.

this would still require the third party client to detect such options, which I doubt they will

closing this as not something to do on the api level

this would still require the third party client to detect such options, which I doubt they will closing this as not something to do on the api level
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#603
No description provided.