[feat] Control public access to /api/v1/instance/peers endpoint #363

Open
opened 2022-12-11 02:22:03 +00:00 by Ghost · 0 comments

The idea

The endpoint /api/v1/instance/peers should be controllable by the admin if they do not want to make this kind of information public.

The reasoning

There doesn't seem to be any genuine use case for this except posing a privacy risk, apparently by MastoFE?, and giving more data for those "fediverse scraping bots" which is not desirable.

Currently there is no way to control this except at the proxy level such as: respond /api/v1/instance/peers "girlboss.ceo" 451

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 The endpoint `/api/v1/instance/peers` should be controllable by the admin if they do *not* want to make this kind of information public. ### The reasoning There doesn't seem to be any genuine use case for this except posing a privacy risk, apparently by MastoFE?, and giving more data for those "fediverse scraping bots" which is not desirable. Currently there is no way to control this except at the proxy level such as: `respond /api/v1/instance/peers "girlboss.ceo" 451` ### 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.
floatingghost added the
mastodon_api
privacy
feature request
labels 2022-12-14 02:52:28 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
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#363
No description provided.