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 element for discovering instance staff #27

Open
kaniini opened this issue Sep 3, 2018 · 10 comments · May be fixed by #84
Open

Add element for discovering instance staff #27

kaniini opened this issue Sep 3, 2018 · 10 comments · May be fixed by #84

Comments

@kaniini
Copy link

kaniini commented Sep 3, 2018

Pleroma recently added staff_accounts to metadata, as a list of a staff accounts (profile URIs) who can do administrative/moderation actions concerning the instance.

It would be nice to have an official element in the JSON for this that could be standardized.

@jhass
Copy link
Owner

jhass commented Sep 10, 2018

Yes I can see that.

The usecases I see is to direct emergency requests and content moderation reports, so akin to domain whois.

Question is, do we want internal identifiers here? My intuition says no and this should more likely be email addresses, akin to whois. Or have an option for both.

Naming wise, keeping the above usecases in mind, I'd go in terms of contact(s), so staff_contact(s), admin_contact(s) or operator_contact(s).

Either way it should be an optional element.

@kaniini
Copy link
Author

kaniini commented Sep 18, 2018

The identifiers should be profile URIs, as those are generic.

@jhass
Copy link
Owner

jhass commented Sep 18, 2018

That's just a statement, not an argument as for why. What use are internal profiles if an instance is down?

@kaniini
Copy link
Author

kaniini commented Sep 18, 2018

If an instance is down, you cant pull the nodeinfo anyway.

@jhass
Copy link
Owner

jhass commented Sep 19, 2018

But it can be cached by monitoring sites like https://the-federation.info/ Also there's multiple levels of down, like "I can no longer sign in" down.

@lanodan
Copy link

lanodan commented Feb 7, 2019

Well, a URI can also be a mailto: or xmpp:, which would also be a good idea in case you want to reach the node but your account/node is blocked.
Which means that it would be contact* flavour instead of *accounts.

@wakest
Copy link

wakest commented Dec 13, 2022

this should really be added! its been open since 2018!

@6543
Copy link
Contributor

6543 commented Dec 4, 2023

I'll create two competing proposals via pull :)

This was referenced Dec 17, 2023
@6543
Copy link
Contributor

6543 commented Dec 17, 2023

Ok there is #83 with an simple approach and #84 witch also allow simple answers but could be extended if the software supports it to fully cover all use-cases

PS: I personalty prefer #84 the more i thing about it :)

@6543
Copy link
Contributor

6543 commented Dec 17, 2023

I would day vote with 👍 / 👎 on the pull requests ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants