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

Set the display name of the bot to the web site for transparency #257

Closed
bkil opened this issue May 31, 2023 · 6 comments
Closed

Set the display name of the bot to the web site for transparency #257

bkil opened this issue May 31, 2023 · 6 comments
Labels
T-Task Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.

Comments

@bkil
Copy link

bkil commented May 31, 2023

Right now, this should be https://github.com/matrix-org/matrix-public-archive but after #219 is fixed, this could be simply https://archive.matrix.org

It might also be included in the user avatar as well if some platform fails to forward the display name.

The top of the web page and the readme should link to the FAQ that answers something like

Why did @archive:matrix.org join my room?

Background

Certain communities have a policy about only allowing bots that identify themselves, share their source code and the result of their activities. Some ask that bots respond to !botlist, !rollcall or if the bot is @-mentioned.

Alternatives

This could be achieved in multiple ways. The least intrusive of which is to make it trivial to find information about the bot, such as running it under its own subdomain & domain with information about it. The second best is what I suggested above.

Another possibility is vocally announcing itself after joining, but some may actually find that creepier and more intrusive.

@bkil bkil mentioned this issue May 31, 2023
@MadLittleMods MadLittleMods added the T-Task Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks. label May 31, 2023
@MadLittleMods
Copy link
Contributor

Ideally, we'd have something like extensible profiles to add a proper explanation and links but that isn't available yet.

The best we can probably do is update the display name. #219 will be fixed in any case so we should be thinking of names in that context. Here are some names that have come up:

  • archive.matrix.org observation assistant
  • Read-only user for archive.matrix.org
  • Non-archiving user for archive.matrix.org
  • Exploratory user for archive.matrix.org
  • archive.matrix.org permissions check

It would be best if the name could preempt assumptions and wrap the kind of explanation I gave yesterday.

Having some avatar would be good but ideally would just be the custom logo of the Matrix Public Archive which doesn't exist yet.


I don't think we'd be able serve any bot commands since that would require it's own infrastructure just to answer a rollcall command explaining itself. Something that's really just better served by some profile information anyway.

@bkil
Copy link
Author

bkil commented May 31, 2023

Thanks. !botlist & !rollcall should be separated to another issue, just mentioned it for completeness sake.

From the looks of it, I don't think that extensible profiles are going anywhere. Neither do I see an obvious way how you could filter the member list to gather presently joined bots.

If you moderate a room with thousands of users and you plan announcing a change in bot policy for example, you issue a !botlist to see which operators need to be negotiated with first. Or you could similarly query for log bots to see whether the room is off-the record.

And when I'm inspecting membership, I can safely kick out ones who are neither documented bots, nor humans who respond after @-mentioning by a mod within a reasonable amount of time.

@Mikaela
Copy link

Mikaela commented Jun 1, 2023

archive.matrix.org observation assistant

I prefer this one as it clearly communicates that it's observing me and my room non-consentually.

MadLittleMods added a commit that referenced this issue Jun 6, 2023
Using the join `reason` added in MSC2367

Related to adding some better profile information, #257 (comment)
@jonaharagon
Copy link

Ideally, we'd have something like matrix-org/matrix-spec-proposals#3795 to add a proper explanation and links but that isn't available yet.

Could you just set the display name to https://archive.matrix.org/bot or /faq or /about or whatever, and host a proper explanation on that page?

@MadLittleMods
Copy link
Contributor

@jonaharagon Sounds workable. We could just add a redirect from /faq to the FAQ on GitHub. PR welcome ⏩

MadLittleMods added a commit that referenced this issue Jun 9, 2023
Using the join `reason` added in [MSC2367](matrix-org/matrix-spec-proposals#2367). Unfortunately, this PR doesn't have much effect because it doesn't look like many clients support it yet (Element doesn't support it for example).

Part of #257
MadLittleMods added a commit that referenced this issue Jun 22, 2023
MadLittleMods added a commit that referenced this issue Jun 22, 2023
Part of #257
so we can set the display name of the bot to `archive.matrix.org/faq` and
people can read about the project is about and why the bot joined.
@MadLittleMods
Copy link
Contributor

A /faq redirect was added in #265

And the display name for the @archive:matrix.org bot user has been updated to archive.matrix.org/faq

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Task Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.
Projects
None yet
Development

No branches or pull requests

4 participants