[mirrors/libpurple-core-answerscripts.git] / TODO.md

#What TODO?
  * Add way to block messages (eg. based on return value?), so you can write antispam filters using answerscripts.
  * GUI for managing answerscripts with following features
    * list answerscripts
    * enable/disable answerscripts (by chmod +x/-x on them)
    * edit/create/delete answerscripts
    * install/update/share answerscripts using online git repository (aka script market)
  * Add more ANSW_ variables and features
  * Make this answerscript API stable
  * Port whole idea and plugin to other (non-purple) libraries/clients while maintaining compatibility of existing answerscripts and API
    * probably move answerscripts out of ~/.purple/ to ~/.config/answ/ or something, so they can be shared between multiple agents
  * Figure out why is first reply always followed by some ugly binary mess
    * visible in irssi
    * but it happens even for messages not sent by this plugin, so probably not my fault
Commit	Line	Data
0de4c204	1	#What TODO?
c8c87c89	2	* Add way to block messages (eg. based on return value?), so you can write antispam filters using answerscripts.
0de4c204 TM	3	* GUI for managing answerscripts with following features
	4	* list answerscripts
	5	* enable/disable answerscripts (by chmod +x/-x on them)
	6	* edit/create/delete answerscripts
	7	* install/update/share answerscripts using online git repository (aka script market)
	8	* Add more ANSW_ variables and features
	9	* Make this answerscript API stable
	10	* Port whole idea and plugin to other (non-purple) libraries/clients while maintaining compatibility of existing answerscripts and API
	11	* probably move answerscripts out of ~/.purple/ to ~/.config/answ/ or something, so they can be shared between multiple agents
5cd90c72 TM	12	* Figure out why is first reply always followed by some ugly binary mess
	13	* visible in irssi
	14	* but it happens even for messages not sent by this plugin, so probably not my fault