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

New Issue

Open

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

Ghost commented

2022-12-11 02:22:03 +00:00

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.