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

@JamesBot Room Owner Access #72

Closed
jbis9051 opened this issue Dec 1, 2019 · 12 comments
Closed

@JamesBot Room Owner Access #72

jbis9051 opened this issue Dec 1, 2019 · 12 comments

Comments

@jbis9051
Copy link

jbis9051 commented Dec 1, 2019

Hi!

Since @rlemon and his bot, Cap, have left the room, JamesBot has replaced Cap as the main bot. Most of the functionally has been copied over including the auto welcome, detecting unformatted code as well as fixed features like the mdn command.

To help with moderation, I propose adding JamesBot as a RO as Cap was. This will allow unformatted messages to be moved to the trash and allow for greater moderation functionality in the future.

Some information on the bot itself:

JamesBot is open source and on Github. I can add RO's as contributors to the repo so they can add commands and fix things as they see fit. Testing can be done in this room (or in the sandbox). I have also given RO's permission on the bot to disable it and ban people from using it as necessary. I am currently working on an import script to import all the learned commands from Cap. The bot runs off of my home server. Unlike Cap, it does not run in a browser instance. Instead it runs in a node instance. This reduces overhead. Eval is done using a combination of Cap's (Zirak's) whitelist eval script as well as the isolated-vm module for secure evaluation. We (me and some of the other regulars in the room) are still working on even more secure evaluation. Included in the repo is also unofficial documentation of the StackExchange Chat API.

If anyone has any questions about the bot itself feel free to ask! :) Also feel free to open issues or PR's on the repo.

Thanks,
@JBis

@tentonaxe
Copy link
Member

I think in this case, this is more than just a vote for RO access for a bot, it's a vote for RO access to both the bot and the person running it... because at that point they are an RO, as they own/control both accounts. It doesn't really make sense in my opinion to do one without the other.

@tentonaxe
Copy link
Member

That said...

I don't think moving poorly formatted code to the trash is as important as it used to be, due to how little activity the room gets now.

@jbis9051
Copy link
Author

jbis9051 commented Dec 3, 2019

@tentonaxe I think you make a very good point here. By giving RO to the bot user your are effectively giving me RO. However, I would like to point out an important distinction between my user (@jbis) and bot user (@Jamesbot) getting RO.

As I see it, voting for someone to become RO comes with two main components. You trust that person not to abuse their power and also that they will be an effective and fair moderator. They are there to help settle disputes if they arise and have the power to kick someone and even disable to room temporarily if necessary.

By voting only for Jame's user (and not me) to become RO, you are trusting that I won't abuse the power of RO through Jame's user. However, it does not mean (or at least I don't see myself this way) that I have any more authority than a regular user. I am equal to a non RO user. Assuming you trust me not to abuse my power, I see a distinction between me being RO and James being RO.

That being said, with the loss of a couple ROs, I am willing to become a RO. I am not sure if other RO's want that. Most of the people voting on this have will have interacted with me at some point and have seen me interact with others so I see no reason to explain why I think I would be a good RO. That is for you all to decide.

@forresthopkinsa
Copy link

+1 for James and Josh being distinct users that I don't expect to overlap. I say we make an existing RO (Kevin?) a joint owner of the James repository and account credentials, to discourage abuse.

I don't really think we need any new actual ROs; whenever there's a problem, it's easy enough to ping someone else to take care of it. But I did encounter someone post unformatted code that James caught but couldn't do anything about (and was therefore left unchanged) within the last hour. It's annoying.

@tentonaxe
Copy link
Member

Giving me access to the repo wouldn't do much, i'm too lazy for that to make any difference, bsides, ownership of it isn't required to see/monitor it.

@benjamingr
Copy link
Contributor

Honestly the RO list needs an overhaul anyway and anyone not active in the last 2 months should be removed. I would be fine with stepping down as well if people want me to and new people (the ones active now) should take charge of managing the community.

As much as I would love to have Octavian/Jan/Denys/Ben/Eva and the rest of the gang active that ship has sailed years ago and we old folk should make way for new leadership.

@Canop
Copy link

Canop commented Dec 5, 2019

I already said that I have no objection in being removed if it seems I'm in the way of a new leadership.

The new leadership of SO made me stop answering questions already...

@Canop
Copy link

Canop commented Dec 5, 2019

Hey... I'm not so old!

@ikariiin
Copy link

ikariiin commented Dec 5, 2019

lmao, I misrecognized the issue I was commenting to, but glad you took it in a fun way.
😄
shouldn't have deleted that comment either now that I think of it, mb :P

@forresthopkinsa
Copy link

We should open a new issue for the topic of New Management. I think we can safely call this proposal separate from that (much larger) one.

@tentonaxe
Copy link
Member

I went ahead and made this happen since no one opposed it, feel free to open another issue if this needs to be revisited.

@jbis9051
Copy link
Author

jbis9051 commented Dec 5, 2019

https://chat.stackoverflow.com/transcript/message/48034105#48034105

@jbis9051 jbis9051 closed this as completed Dec 5, 2019
@jbis9051 jbis9051 mentioned this issue Jan 23, 2020
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

No branches or pull requests

6 participants