.\" Automatically generated by Pandoc 2.0.6

.\"

.TH "MINITALK" "1" "November 2018" "Minitalk User Manual" "Minitalk 0.2.5"

.hy

.SH NAME

.PP

minitalk \- small, simple chat system

.SH SYNOPSIS

.PP

minitalk FILE [NICK]

.SH DESCRIPTION

.TP

.B FILE

File to use as \[lq]room\[rq].

Must have read/write permissions.

.RS

.RE

.TP

.B NICK

Specify nick to use.

Default is current username.

.RS

.RE

.SH EXAMPLE

.PP

Join a room controlled via /var/chat/general.

.IP

.nf

\f[C]

$\ minitalk\ /var/chat/general

\f[]

.fi

.PP

The same, but specifying the username \[lq]admin\[rq].

.IP

.nf

\f[C]

$\ minitalk\ /var/chat/general\ admin

\f[]

.fi

.SH NOTES

.PP

The primary issue is a security concern.

Anyone that needs to chat in the \[lq]room\[rq] has to be able to write

to the control file.

Anyone that needs read from the room needs read access.

Anyone that has access to these \[lq]control\[rq] files can also inject

anything they want into the chat.

This truly is built on the honor system, and was designed around a

single purpose: multi\-user chat between trusted users on a single host.

.PP

Don't expect this to be secure.

.SH AUTHORS

.PP

Andrew Benson.

.SH COPYRIGHT

.PP

Copyright © 2018 Andrew Benson.

License: MIT

.SH AUTHORS

Andrew Benson.