On Friday, September 5, 2025 at 3:56:24 AM UTC-4 Edward K. Ream wrote: Félix, there is no one but you I would trust with such a project. Only you have the deep knowledge of Leo, your LeoJS scripts, and web technology that would be required for such a project.
But does the OP's request make sense? Isn't *possible malware* another name for an .html file? How will distributing Leo outlines as .html files pass the first security sniff test? It seems to me that the display of an outline should be read-only, with a few interactive features like expanding nodes. That way the user doesn't need to learn anything special. Security aside, this brings in the tricky question about how to handle @other trees in a way that a user can understand without climbing a learning curve. Named sections don't present a problem, I think. I'm also sure that sentinels should not be visible. I don't know where that leaves Leo directives. Security might be a real concern. OTOH, a Leo outline running in Leo could also be a security concern - it could modify a standard Leo command to do something nefarious. For myself, I use a javascript blocker in my browser. It would be best if the read-only representation of a Leo outline wouldn't need to import any script packages, for then a script blocker won't need to be told to make an exception, which once again could become a security matter. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/leo-editor/715e8006-b4e8-4960-b439-a5f6eb68319bn%40googlegroups.com.
