Skip navigation


note: this manual has not yet been updated to cover the graphical Syndie client. This information is still however relevent for those running the text-only client (syndie.exe --cli) or for use with the text-only tab in the graphical interface.

The Syndie text interface is a context-sensitive menu driven application, and is fed commands from the standard input, allowing scriptable operation.

The application itself can be launched with zero, one, or two parameters:

    syndie [@script] [data_root]

The optional @script parameter reads in the contents of the script file, running them as if they came from the standard input. The optional data_root parameter tells Syndie where to locate the database, archive, and related data files. If not specified, it uses $HOME/.syndie/ (or %HOME%\.syndie on windows).

When the interface starts up, the data_root/scripts/startup script is run, and when any nym logs in, the data_root/scripts/login script is run, if they exist. When a new nym is created (with register), the nym is given the preferences from the data_root/scripts/defaultprefs file (which contains newline delimited name=value pairs). The new nym is also given the aliases from the data_root/scripts/defaultaliases file (which also contains newline delimited name=value pairs)

The menus are outlined below, with unimplemented commands prefixed by //.

An example script:
    menu post
    create --channel 0000000000000000000000000000000000000000
    addpage --in /etc/motd --type text/plain
    addattachment --in ~/public_html/webcam.png --type image/png --name cam.png
    listauthkeys --authorizedOnly true
    authenticate 0
    authorize 0
    set --subject "Today's MOTD"
    set --publicTags motd