While you all are deciding what to do with the adoption process, could you please unprotect the code files in yapperbot so that they are readable by me? I would not need to be able to modify them--only read. At this point, I don't need the password. If you are unfamiliar with Go (language)--which is new to me too--I can do my best to explain what any or each of the files and directories are for. The documentation for the code is sparse, and I do plan to add documentation somewhere for future code review.

A number of the directories(folders) and files that run the yapperbot code are protected--at least for me. Try these commands:

cd /data/project/yapperbot
ls -ltR

(The last command is a recursive list of all files starting from the top directory.)
You will see that important directories (and files) are protected from view, e.g. /data/project/yapperbot/frs, which has the most important code.

In researching the above jobs, I looked up the "uncurrenter", originally approved as:

https://en.wikipedia.org/wiki/Wikipedia:Bots/Requests_for_approval/Yapperbot_2

It appears to have been taken over by ProcBot_10:

https://en.wikipedia.org/wiki/Wikipedia:Bots/Requests_for_approval/ProcBot_10

If that is the case, then should the job described above as:

name: uncurrenter
command: bash -c "cd uncurrenter && ./uncurrenter > /dev/null"
image: bookworm
schedule: "0 * * * * 
mem: 950M"

be disabled?