[08:47:31] <tonythomas>	 qgil: saw your ping on the bug, but it seems like its getting more complicated. We have this testcase with someone creating a new newsletter via the API - and seems like we werent handling them all well :-(
[08:47:55] <tonythomas>	 should be doable, but would need bit more of bawollf
[08:49:27] <qgil>	 ok  :)
[08:49:42] <qgil>	 and... maybe this is a stupid question
[08:49:58] <qgil>	 Is it possible not to allow the creation of a newsletter via API?
[08:50:06] <qgil>	 What's the use case anyway.
[08:50:10] <tonythomas>	 doable though.
[08:51:04] <tonythomas>	 the case is someone trying to create a newsletter via pushing in all the contents as a JSON to the action=edit
[08:51:50] <tonythomas>	 the thing is since we are using contenthandler, on submit - we have the data going in as a JSON as well - so I am not sure about  totally discarding this
[08:52:14] <qgil>	 I am talking out of ignorance.
[08:52:30] <qgil>	 I just cannot imagine the need of creating a newsletter via API being a real need.
[08:52:34] <tonythomas>	 no worries. I too didnt knew about all this until last bawollfs patch.
[08:53:40] <tonythomas>	 the thing is - for some reason we are all calling this API on editing a newsletter anyway - like http://newsletter-test.wmflabs.org/w/index.php?title=Newsletter:TestPage&action=edit
[08:54:47] <tonythomas>	 ideally whatever we type in the form is transferred as a JSON to this action=edit API - and I see that currently - on creating a new newsletter - an exception is thrown - which never actually is displayed  (but it happens)
[08:56:56] <qgil>	 Ahm. Ah well.  :)
[20:05:42] <acagastyaSLEEPIN>	 Anyone knows who operates the IRC Echo bot rc-pmtpa?
[20:17:16] <Sagan>	 I guess operations does that
[20:17:25] <Sagan>	 the code is available in their puppet repo