@nikolat I tried to open tama and ghost_terminal together to test whether ghost_terminal's event messages were being received by ghost, then I found that tama didn't respond to this at all, so I think this must be a mistake somewhere. This has happened with previous some versions of SSP, so I guess it's just the SSTP over HTTP update that caused the previous patch to go wrong.
@ponapalt In my attempt to migrate taromati2's recycle bin cleanup related functions from gomi saori to \![execute,emptyrecyclebin], I noticed that gomi saori might return a value indicating failure, but if ssp does \![execute,emptyrecyclebin] will only trigger OnRecycleBinEmpty, does this mean that ssp's emptying of the recycle bin will not have a failure or I need to check the args of event? :meow_thinking: And also, if other ghosts do \![execute,emptyrecyclebin], is the OnRecycleBinEmpty triggered only for the ghost executing the sakura script?
It looks like using a submodule in dic files will cause the CI check to fail to load the dic files in the submodule. I don't know if there is any way to fix this....
https://ukadon.shillest.net/@ponapalt/109964907602141841 This trick may not work very well with a ghost that doesn't introduce itself on first boot... On the other hand, ghost's OnFirstBoot may use reference0 and not deal with the absence of reference0, or use OnFirstBoot to initialize variables. This may lead to confusing logic or to ghost reverting to the way it was when it was first installed. My personal recommendation is to read the ghost code directly, as this is probably the least error-prone way to recall and understand ghost.
Perhaps we should update something to meet the following conditions. The web side can send and receive sstp directly with ssp by some means a new sstp that gets what ghosts are currently available and whether they have been started.
@ponapalt Can we add a parameter to the OnURLQuery event indicating the types of processing that ssp can do for this url, and add a new sakura script for the specified action on the specified url? On the one hand, the MIME type is not enough for ghost to know what ssp itself can do with this url (let's say the MIME type of a page that supports rss is still text/html), on the other hand, I would like my ghost to provide the option to process the page in the way that baseware provides when baseware can process it. and provide the most basic options if baseware doesn't know how to handle the url.
@ponapalt Can we skip the OnUpdateProcessExec event by adding a new parameter to the sakura script that triggers the update, or can we pass additional parameters to the OnUpdateProcessExec event by that sakura script? That way if someone needs to write an update event they don't need an extra global variable. :blobok: