phil-s
phil-s
I'd figured everything not labelled **Required** was optional?
I reported a test message with no score, and I got a 200 response and the "Content reported." message. I was tracing the plz call and confirmed it only had...
Heh, ok, need to avoid this: > Error running timer `plz--respond': (ement-api-error "400: Content must be a JSON object.")
I believe this is good, now. I'm not seeing any errors from plz in any of the test scenarios. In each case I get the following from tracing `plz`: `(plz...
Untested as yet, but I think we want this as well, so I'll just drop it in here for now. ```el (defun ement-room-report-delete-ban (event room session reason) "Report the current...
I hadn't thought about marking messages, but I had pondered iterating over all of that sender's messages and prompting the user to report/delete them all. What about a search loop,...
Rebased over master, squashing some fixups.
I've pushed a command `ement-room-report-delete-ban-selected` for feedback. You'll note that at present it doesn't issue the actual report/delete/ban requests (which have been pretty well-tested at this point, so ought to...
I had an opportunity to use the new command in practice today (after I removed the training wheels, locally), and it worked fine. I'm still interested in feedback on the...
See also https://github.com/alphapapa/ement.el/pull/247