meshchat v0.7b3 released

our $pi_zone                    = 'MeshChat';
our $local_meshchat_node        = 'k7fpv';

sudo /etc/init.d/meshchatsync stop
sudo /etc/init.d/meshchatsync start

Play sound alert when a new message arrives

Mobile layout fixes

Permission problems on FreePBX - thx KE2N
Action Scripts ready for testing
Ctrl-Enter will send a message vs clicking the Send button

v0.7b2 Release Notes:

Fixed Updated secs on files and status pages

Poll lists / zone fixes

Lowercase node names on Pi

File table layout fix

Detect apache user and set permissions accordingly

Fixed height on channel drop down

Keep log of message ids processed by action scripts so they can’t repeat

Support USB drive for files on AREDN node if mounted

Action script log on status page 

v0.7b1 Release Notes:

Zones: You can now have segmented mesh chat databases on a single mesh. Mesh chat looks up the service name it has been given in OLSR. The default is MeshChat. It will only sync with other nodes / pi's that share the same service name. Now you can setup SoCalMeshChat, UtahMeshChat, etc and only the nodes with the same service name will sync with each other. Now when you tunnel into another mesh you won't dump your whole message db into their mesh chat, unless of course you share the same service name.

Change max message db size from bytes to 500 max messages: There was some issues when the db would get full, the whole db would get sent over every sync since the version did not match. To make things simple and robust all message db's are limited to 500 messages so when it is full, the quick version check works properly. Message db's are now stored in sorted order as part of this change too.

Added channels: You select or create a new channel when you send a message. You can select the drop down filter at the top of the message pane to select which messages to display. All message db's contain messages from all channels. They are filtered client side with the display filter.

Action scripts: Action scripts are only supported on the Pi version. This is pretty much done but needs more testing. If you feel adventurous you can add a line in /etc/meshchat_actions.conf You can read the comments in that file on what kind of matches you can do. I have a SMS gateway and archive working. More details and code to come.

Fixed + in messages

Added version, node, call sign, and zone to top of every page

Cleaned up interface

Added config option on Pi for mesh chat node - see above

Added config option for zone name on Pi - see above