stephen001 / chatters Goto Github PK

Implement persistence to SQL / savefile for the tracker.

TextMan appears to be using magic symbols as a placeholder when restoring links, this strategy should be replaced with one that is portable, and sane.

it should link to THIS repo! obviously.

Gain some points for successfully helping a developer with code problems. Like on the forums, but even more meaningless.

A command sent like this:

" POOP

doesn't get sent a proper message cause of the space, pls fix

When you put up a showcode window via /showcode, you cannot cancel out of this, meaning you must submit a showcode. We need some kind of cancel button or guard on empty submissions so people can cancel. Maybe even both?

Copyright � 2008 Andrew "Xooxer" Arnold

That's not a copyright symbol.

Pretty much as the description says. Perhaps use MySQL to record the chat, and allow for storing Chatter config that can be reflected between the web/DS clients.

Create a show code, then attempt to click on the view URL

The quotes system stored quotes rather oddly, and is altogether somewhat bulky. This should be refactored to allow the following:

A quote, which consists of:

Text (Mandatory)
Link (Optional)
Author (Mandatory)

We can then probably remove all the existing quotes, and create new development-based ones.

I think this is possibly one of the few things now not being saved to database or configured in the server config, so we should migrate this across.

We already have the ability to hear a sound when a person has had their name used or other key words have been said but I'd really like to be able to know when any message has been said while I'm not there.

Basically while my focus is lost on chatters I'd like a light sound to tell me that something was said. Also, someone logging out or in shouldn't make a sound or it should make a different sound to an actual message.

Let's do it.

The webclient is coming soonish and the current info is that some controls aren't supported yet, including some stuff that the current .dmf contains, so a new interface should eventually be made for a working webclient version so Chatters can go everywhere and stuff.

ignore dis pls

Showtext and Showcode shows up consistently far to the left of my viewable desktop area when Chatters is displayed on my second monitor.

Setup is as follows:

Windows 7 x64 Ultimate edition
Intel Core I7 CPU 3.0ghz oc'd to 3.6ghz
8 GB RAM
Nvidia 660GTXx2
Internet Explorer 11.0.9600
BYOND v. 504.1225

2x 27" monitors running 1920x1080 resolution each.

Second monitor is positioned to the left of the main monitor, listed as non-primary extended independent viewing area.

The source still figures itself as a hub of channels, when in reality there is no capability of doing that at this point. I think we've pretty thoroughly trashed this concept, and we should shift this concept of "the channels" into "the channel."

Channels are still saved in a "channels" folder, named after the channel in question. This should probably migrate to a "channel.sav" file or something in the saves directory.

The channel manager will in effect lose a lot of its functionality, we might even just get rid of it all together from what I can see.

The op interface is currently removed and did not function properly anyway. We need to be able to access all op commands as simple verbs. /addop, /removeop, etc

I think the config file over-reaches by trying to track operator priviledges and dev priviledges. These things make no sense in an ini file which is just to track settings, not lists of people with related information. XML or JSON or YAML or anything else would be better here.

As per the removal of the "channel server" concept, we can get rid of the "home channel" concept, and the "auto_start" concept, since it'll just load the one channel on startup. The node settings can also be removed.

Telnet password should be off by default, as it is an unnecessary chore for average users. We might want to add some command line functionality or interface stuff for managing it. I think the only reason to have it enabled is if you're being harassed by mass telnet connections.

The channel isn't auto-hosting on the config file's given port number. Not sure why, but it isn't.

We should have it automatically generate this config file if it isn't present as well. At the very least, there should be a valid set of settings that allow the server to run without this config file. As it stands, if a valid config file isn't loaded with atleast 2 settings (auto_start=1 and home_chan=something), it doesn't appear to load anything and just sits there. Not exactly an acceptable response, since you can't, say, load a channel manually. (nor should you)

For private showtext/code, etc.