Talisman v0.39 is out now!

• Support for new user password. Incase you want to run a private BBS.
• Support for font loading on login, fonts definable in data/fonts.toml
• Support for sending sixel images from gfiles.

Talisman will determine if a terminal supports sixel or fonts or both, either by testing the term type to see if it’s magiterm, or using a cterm device capability string for syncterm.

Other terminals that support these features may not be detected if they do not support the cterm string. See cterm.txt under CSI = Ps n (CTSMRR).

Talisman v0.34 is out now!

• Auto detection of UTF-8 Terminals. Converts appropriatly
• Misc bug fixes.

NOTE:

• Talisman does not accept UTF-8 input.
• Doors under Windows are not converted to UTF-8.

Talisman v0.33 is out now!

• Improved logging when loading invalid toml files.
• Support for @USERNAME@ in login menu data
• New “Top” user attributes and script functions
• utf8 to cp437 conversion. (converts utf8 in some toml strings, strings.dat and utf8 messages)
• Reply to Netmail function.
• @MSGCONF@ available in fsr_header_*
• Fixes for file listing descriptions.
• Fix for toolbelt when importing files.na

Hi all, as you may have noticed in the past few weeks, the talisman website has been spread out across two domains, www.talismandocs.com and www.talismanbbs.com.

talismandocs.com is hosted by aLPHA, who stepped up when I was having trouble paying for a server to host the docs / releases on. aLPHA bought a domain, and put the docs up and has been paying for the server for the last several months.

I am extremely grateful for this, it has been a real help. However just recently I spun up a new server to offer dynamic dns to talisman sysops, and it seemed to me that it would be best to put all the docs on the one site, and save aLPHA from the continuing cost when it was no longer really necessary.

So, in short, talismanbbs.com is the home for Talisman BBS again, talismandocs.com might point here in the near future, but I imagine it will eventually go away.

aLPHA, thankyou for all your support this year, both financially with hosting the site, and your continued enthusiasm and assistance with the Talisman BBS project :)

Talisman v0.32 is out now!

• Fixes for postie working as a point (Thanks Sneaky!)
• Several new scripting support functions
• Initial support for Synchronet style HEADERS.DAT in qwkie
• New script hook, can be run from fsr_header_* gfiles
• Fix for internode chat causing a crash

Talisman v0.31 is out now

• New split screen chat option between nodes.
• Built in RLogin and Telnet clients, accessible via menu and scripting
• Full screen ANSI editor accessible via scripting.
• Upload / Download available by scripting.
• Pruning message bases with toolbelt.
• Postie bug fixes and improvements.

Talisman v0.30 is out now.

• Includes various bugfixes to postie, with added debug logging.
• Includes toolbelt “adpost” command and “pack” command, for posting text files to message bases and packing message bases respectively.
• Fixed file search, fixes for Qwkie.
• Added optional newuser.lua to be triggered when a new user signs up.
• bbs_set_user_attribute added to lua scripting to set attributes for users.
• Added optional scan hook and toss hook to message areas in postie.
• Reworked events, so they start based on the start of the month (or an optional start day/time), instead of when Servo is started.
• Log files now include the pid of the logging process.

Talisman v0.29 is out now, with reworked lastread pointers and message deletion.

It’s important you recompile all your executables this time if you’re on linux, as the Squish stuff has changed.

Windows can of course just install over the top of their old installation.

To delete a message, you need to either have deletion enabled for your security level, or be in a message area that allows deletion for your security level.

sec_levels have the additional flags:

can_delete_own_msgs = false
can_delete_msgs = false

these default to false.

Message areas have the optional additional flags

delete_sec_level = 99
delete_own_sec_level = 99

These default to -1 or NO ONE.

So, if you only want sysops to be able to delete messages, you would enable it in seclevels.ini for the sysop security level. If you also want level 25+ to be able to delete their own messages in a particular base, you would add delete_own_sec_level = 25 to that message base.