Give cypherpunks account and other new accounts possibility of editing title, keywords, ...etc of already filled tickets

seems like that's no longer the case, can we get that thing back?

added component::internal services/service - trac owner::qbi priority::medium severity::normal status::new type::defect labels

The cypherpunks account can no longer create or even reply to tickets. Not sure if something else broke while someone tried to work on this...

The obvious workaround is to use this account (cypherpunks3) with the same password as the original cypherpunks account. Or, if this behavior is deliberate, someone should update the main page to report that the cypherpunks account has been disabled (due to abuse?).

@cypherpunks3 The problem with that approach is that one (read: trolls) can easily change the password and it won't be reset to the default writecode.

Talk about the spammer(s) that led to the lockdown of the cypherpunks account came up on the mailing list last month: https://lists.torproject.org/pipermail/tor-dev/2018-July/013337.html

I'm ok with a captcha all the things with cypherpunks account.

Doesn't much matter what you're okay with, because the admins don't seem to be okay with it. teor said right there that the spammer can already solve captchas.

The current captcha isn't a captcha, it's a joke of a captcha, with a relatively real captcha like the Google ones I think it should be ok. Also we haven't seen such a breakdown on cypherpunks here on trac since '92.

Replying to cypherpunks3:

The current captcha isn't a captcha, it's a joke of a captcha

What is the current captcha implementation in use, exactly?

Is trac.tpo using a custom plugin-within-a-plugin using this? https://trac-hacks.org/wiki/TracCaptchaPlugin https://www.schwarz.eu/opensource/projects/trac_captcha/

Google reCAPTCHA may not be desirable for privacy reasons, but in general is it feasible to change what kind of captcha is in use, or improve it, in a way that doesn't use third-party servers?