Help for pylily
PyLily largely retains the original lily look and feel and features. However, it
has been enhanced in a number of areas. Here's a summary of some of the more
significant differences:
* Lily relied on local clients to provide the best experience. While PyLily
still supports these clients, it also allows you to connect directly using an
SSH client and get functionality comparable to what you'd get with "clily"
running over an SSL tunnel, without having to install clily or set up stunnel
to encrypt the connection. See "/help ssh" for details.
* PyLily adds support for Unicode characters encoded using UTF-8, including
"wide" characters such as kanji and emoji. See "/help sending unicode" for
details.
* PyLily supports for rich text and color styling on terminals which support
it. See "/help sending markup" for details. Users can also write custom rules
to add styling to incoming messages and notifications. See "/help style" for
details.
* PyLily supports sending multi-line messages with explicit line breaks. This
can be useful when sending something like a table of information, or anything
where you need line breaks and/or whitespace preserved. See "/help sending
multi_line" for details.
* PyLily supports adding inline images to messages, info files, and memos.
Images can be loaded from a URL, or stored as memos, which have been extended
to allow their content to be text, images, or binary data. Currently, inline
image display in the terminal only when using iTerm2 on the Mac, but other
recipients will be shown a URL they can used to view the image. See "/help
sending inline_images" for details.
* Users running iTerm2 can also take advanced of new "upload" and "download"
options on the info and memo commands. as an alternative to using SFTP or
SCP.
* PyLily has more advanced "settings" support, and a handful of new settings.
Enter "/set" to see a list of settings and their current values, and "/help
settings" for details about what they do.
* Unlike lily, PyLily allows a user to be logged in on multiple connections
simultaneously. Each connection is able to provide input and all connections
see all output, with that output automatically adjusted to fit the terminal
size and capabilities of each terminal. So, some connections have wider
terminals than others or might have different levels of support for rich text
and PyLily will adjust the output accordingly.
* PyLily can import $transfer output from lilyCore, so it should be possible to
import information from an existing lilyCore server, preserving users and
discussions and their info, memos, memberships, permissions, review buffers,
etc.
* Do you have other functionality you'd like to see in PyLily? If so, let Maker
know!