clo / User Vetting public

Dave Cooper (@dcooper) on GitLab, 2024-12-30.

@sync @cshapiro

[this Issue refers to the sync username created 2024-12-30]

Welcome to gitlab.common-lisp.net! Because we've had a issues with opportunistic users and/or bots who do not have the best interest of our site and services in mind, as a secondary vetting step, could you please comment on this Issue with a brief paragraph introducing yourself, and describing your purpose for registering an account on our server?

Please respond within 24 hours or your account will be deleted. If you don't have time to respond fully, a short acknowledgement will buy you another 48 hours.

Thanks,

Dave Cooper, clnet gitlab Admin team

Carl Shapiro (@cshapiro) on GitLab, 2024-12-30.

I sent an e-mail reply which does not seem to be appearing here (yet). Here is a copy.

Hi Dave,

You've met me many times (albeit, years ago) and I have been registered
on c-l.net for many years so I am assuming you're asking about "sync".

However, that is not a user, it is the name of an access token with only
read_api privileges that I create every year for the past couple of
years so a script we run on the cmucl.org webserver can access the
Gitlab API to download new builds of our website artifacts.  Pretty tame
stuff.

Let me know if you have any other questions.

Kindly,

Carl

Dave Cooper (@dcooper) on GitLab, 2024-12-30.

User vetted successfully.

Dave Cooper (@dcooper) on GitLab, 2024-12-30.

I didn't recognize what this was, but if I see things in the future which look like tokens generated by already-registered users then they probably won't need to go through this vetting process.

Carl Shapiro (@cshapiro) on GitLab, 2024-12-31.

Thanks, keeping abuse under control is a endless task, and we are grateful that you are taking care of it.

To try and make your life easier, I went looking for a way to tell if a Gitlab user belongs to project access token. I am not sure what you guys are using but the API has an attribute on the /users query called humans that, at least in name, sounds like it might be a useful filter for this case.

https://docs.gitlab.com/ee/api/users.html#for-admins

I have no way to try this out so this suggestion might just be noise. Nevertheless, I hope it helps.

Carl Shapiro (@cshapiro) on GitLab, 2025-03-30.

Hi Dave,

You've met me many times (albeit, years ago) and I have been registered on c-l.net for many years so I am assuming you're asking about "sync".

However, that is not a user, it is the name of an access token with only read_api privileges that I create every year for the past couple of years so a script we run on the cmucl.org webserver can access the Gitlab API to download new builds of our website artifacts. Pretty tame stuff.

Let me know if you have any other questions.

Kindly,

Carl