The 'Talkboard Forum 2' (in short TBF) is a PHP– and MySQL/MariaDB–based software which supplies a discussion board for every men (or women, Lorretta) website. It has been existing as of 2001 and has developed since then. The forum comes at no extra charge and its source is available — a free/libre open source software. Two languages are supported, also allows free layout arrangement as far as possible and provides anything you expect from modern forum software; themed by its motto 'merge own ideas with the best of other forums'.
The recent stable branch 2.2 is shipped as of November 2015 and replaces the older releases. This fixes bugs of course and brings some new stuff which were planned quite some time ago. On this webpage you can inform yourself about the project and its history. By using so called templates the layout of your forum can be modified. To do so a new one can be created but also one of the ready–made be used.
What would a software project be without support? Of course, you get that. Details are on the corresponding section. Every download includes a 'readme.txt' in the 'docs'–folder to help you making the installation and doing the first steps. Now, don’t let me keep you from looking around 😇
#46 — Talkboard Forum 2.2.3 (stable) released
⏲ April 2020
Here is another update to the stable branch of the forum. Its codename is "Hydra". This is the next moon around Pluto on the mission "New Horizons" the current version series is dedicated to. No critical issues have been fixed as there are no known. • The minimum version of PHP is now 5.2 which is available since the medieval IT year 2006. • An overhauled authentication system to support multiple credentials. Beside the old password and keyfile you can now use security keys following the U2F/FIDO(2) standard. • You can export the userdata according to the regulations of the GDPR with a console script. The data format is JSON which can be read easily. • Fixing the bugs #000289, #000293 und #000300 You can find the package in the download area as usual. Advanced users can grab an unified diff file to preserve own changes to the source code. The files are signed cryptographically. Details can be found on the downloads page.
The Talkboard Forum 2.2 has the following requirements:
You can use the following options, if you want (needs more PHP modules):
My current development environment consists of:
|2.2.x||Sending PGP encrypted mails to users if they provide a public key (local/keyserver)|
The history of the TBF
It all began in January 2001. I was looking for a script language to decorate my homepage with dynamic action. First I played a little bit with Perl, but by coincidence I finally found the open–source language PHP. All my programs were written in this. In March 2001 version 1.0 was finished and provided for download. But then it became more quiet around this one, because I focussed on other scripts instead. This was the time when the 'Archilles Scriptworld' was born and offered a broad variety of applications to the public.
In the early–winter of 2001 TBF reached version 1.2 having bugs fixed. At the beginning of 2002, I decided to rewrite it from scratch. This was just intended to be version 2 right away, but I stayed in the 1.x branch to gain more experience. That decision turned out to be good later on. During the year 2002 it arrived at its final version 1.7.12, which was much more complex than the initial release. Many ideas were included and hours passed by. But unfortunately, I was not confident about this and started developing on the new version 2 in November 2002. In February 2005 it (finally) was completed and replaced the successful 1.x branch.
Another milestone was reached with version 2.1 in April 2007 which delivered 'real tree structure' to forums and an updated password storage. A lot of security enhancements and a simple chat followed. During the years it has become more silent around the TBF because 'basic requirements' of internet users for their daily discussions were narrowed down to big companies (see 'Web 2.0' as keyword). Techniques used in the web made great leaps and the other competitors making forum software bore to this challenge. I had simply no time for that and frankly no intent to run after these 'trends'. Eventually the current 2.2 branch became available in 2015. It mainly provided adjustments to (at that time) modern PHP versions and databases besides full support for IPv6. Again I renewed the password storage.
What is important to the Talkboard Forum…
The weaknesses of the Talkboard Forum…
Which progress is planned for the future?
For any version you can find different packages to download. I recommend you to use the most recent version. New installations and upgrades are made with the 'Full Package'. They come in two flavours of compression – old ZIP and fresh LZMA ('7z'). Some versions have errors fixed after some time and are provided as 'Patch Level [Number]'. These are simply copied over your existing installation. Advanced users can apply changes from one version to the successive by using a special tool¹ either on the server or their local machine. This can be done by a 'Difference File'.
All files have a so called hash. This is a long string of numbers and characters located at the corresponding version block. You can verify whether your download is correct. If just a little changed, your hash will be different from the one in the listing. I use the standard algorithm 'sha256' to calculate them. To help you verify you can look for a hint on your trustful search engine ('verify sha256 hash').
All files are digitally signed. If you grab my public PGP key you can verify the files for authenticity and integrity. This means they were not changed since the signature has been created. And the used key for that is in my possession. You can check the fingerprint to make yourself certain. To help you verify you can look for a hint on your trustful search engine ('verify gpg signature'). You can find the signatures in a detacted '.sig' file. Moreover it exists a file with all hashes which is also signed. Even the template files are included.
As of 2018 there is a new keypair for the next years in order to replace the old one. For compatibility reasons I stick to the RSA algorithm. Until everybody has a quantum computer in his cellar. I placed a transition document containing all details and signed it with both keys.
pub rsa3328/0xA2360C8CD49BBD5E 2018–06–09 [C] [expires: 2028–06–06] Key fingerprint = 38EF 94F0 C94E 8063 FC2D 1C21 A236 0C8C D49B BD5E uid Stefan Kühn <webmaster AT hasenharem DOT de> uid Stefan Kühn <stefan AT hasenharem DOT de> uid Talkboard Forum 2 (Encryption and File/Mail Signing) <support AT tbforum DOT hasenharem DOT de> sub rsa2048/0x1ADF2E5C6C4E2F95 2018–06–09 [S] [expires: 2023–06–08] Subkey fingerprint = 9122 2CDF CDB5 9ACD 3D8B 0867 1ADF 2E5C 6C4E 2F95 sub rsa2048/0xD4CCBA0B9F9F6E3B 2018–06–09 [E] [expires: 2023–06–08] Subkey fingerprint = 52E4 CBDC C9C7 0ED3 FEF3 6B81 D4CC BA0B 9F9F 6E3B
¹ patch. A lot of linux distributions have it preinstalled. Windows ports are available, too.
89da62ca1c96b2c40581b5ac6efd668d16d44bfe8cca36001d5735187e324682 tbf_222.zip sig 78cedcc1669da63ae33d639e318cbe91e672dd86ff526d4608f0b03ddf7bf916 tbf_222.7z sig c1882d33dc3694a392e80cb27dae5155acd8a3292cfd399fe35e395ff8835e2d tbf_221-222.patch.gz sig d34514ca520d01c54acf3265ed32f2dabe4ed57f900dfb35d57fa025473d0ea2 tbf_222-pl1.zip sig
4a6023212559de198998892a1b1d80dd1e5970d2faac84d96895edad8e231cbe tbf_221.zip sig 809ccb31ea85c8e51bfd07c8afac6b6e0ea757d00b0ccb3ee8e04e78889bd738 tbf_221.7z sig 1168c188b4959485a115f2bebf2e0a80e24d5798db019a3467636acce9a4298c tbf_220-221.patch.gz sig d9118121de0396923cd213f154614b0fffd1fe185f94dfd3ed76b04eb6e2f58f tbf_221-pl1.zip sig
2725816d1a8dcf210d6b0c1374a94d31210e181c97b2a5f3eaa0f906cc63b4c6 tbf_216.zip sig 4930625d2d4d9aa719c40f96c6484dcfd1add79e52440b0f4f1bcd3f9a0dafa7 tbf_216.7z sig f217ceb063b0f0bade6cdf0ec0456985ce75e75717c9c415c7a6e728b3839c4f tbf_215-216.patch.gz sig 1f051acaa1982f9282916a8f6f9a02e11534567fc8cad33e2cca83ed9e09b02c tbf_216-pl1.zip sig
b57b9907a1b3cd72d5273ac79df22b441611c1d2c8039aad801f43976fea3682 tbf_211.zip sig 0d91d9c215313fd83efa4f434358e46ecede923e94281518d7f53fccf5fb0c0b tbf_211.7z sig 8a8841d11e70a6c938775a232def3848c86e631cff80e2379de02486e61055d3 tbf_210-211.patch.gz sig ef8381d2894dfdbe0e8a4835548c53762f558cff0e48ce48b28cba596b00026d tbf_211-pl1.zip sig
8327505ff799627fa5e0a759f4e02ad2e88a9b8ca61c3e645306e000845c24ab tbf_210.zip sig aa3bb23f247e935e608a0bfcd24131cce35b3dc26574846ffc7fc6e68f82f965 tbf_210.7z sig e090f4d30c8c54dfcb5cca2f11b7830f7de8ffb03c2027437472e98f04c4244c tbf_206-210.patch.gz sig cc75948510352fee574efa2b7effa4fc40c3922613d8466dae469ef629553a5c tbf_210-pl1.zip sig
941f2eaed8d8a5d7d9374ece1f15209fbf995beb91012b4c3748e8082f615a68 tbf_204.zip sig 8ccda54768fe45b587e65e5eb282b80c0fbb8b1dbb6dfb8b478dfe9b68a7f3c4 tbf_204.7z sig c07d3b744dce06244579a892071a23c4853fd6b56f03beeffb1c05b229464693 tbf_203-204.patch.gz sig e6d2b2bbd38a8dce837d551c601a2104af13f5edbd9faf9568f679ea299e8228 tbf_204-pl1.zip sig
Please try the german version. It should be pretty strightforward even if do not understand this language. Basically you have to download the zip file to your corresponding forum version and have a look at the containing 'readme.txt'. New images should be copied to your 'template/tbfV2' folder and the stylesheet/css has to be imported through the administatration panel at 'Configuration\Templates'. I also have an image showing this procedure.
Since Version 2.2.1 you can include the 'Open Sans' font from an external resource. Grab the zip file from the Open Sans Homepage and extract the containing 'OpenSans-Regular.ttf' to your 'usr'–folder as 'opensans-regular.ttf'. In a second step you have to enable the font in your template stylesheet/css located on your administration panel. Take a look at the upper paragraph for details.
IMPORTANT: Please take note of the support plan of your TBF version.
If you speak german you can have a look at the archive of the old support forum. Or you use an automatic translation. The most interesting one should be the 'Häufig gestellte Fragen und Antworten (FAQ)' section. There is no direct search option but you can restrict your focus in common search engines by appending 'site:tbforum.hasenharem.de' or 'host:tbforum.hasenharem.de'.
You can also get in touch by e–mail or have a look at the following tracker, if there is already an entry addressing your issue or an official bugreport is existing. My e–mail address is support at tbforum dot hasenharem dot de.
My support to this software comes without any charge and is voluntary! You have no claim of prompt reply. But you can be sure I read all requests and try to answer in my free time. If you like to donate something just make me an offer…
Responsible for the content of this website is:
D–58452 Witten, NRW
E–Mail: webmaster AT hasenharem DOT de
This is no support address for the software! Take a look in the upper navigation bar 'Help' instead.
All textual contents and images are subject to the following license, if not declared otherwise: Creative Commons Attribution–NonCommercial–NoDerivatives 4.0 (CC BY–NC–ND). You are free to use it for non–commercial purposes, copy and distribute the contents. As long as you credit the source and leave the contents untouched.
I assume no liability for any damages you may be exposed to by using the information on this website except I have done a big mistake. Any consequences for your life, if you stay here too long and your dog will die of starvation or your friend will leave you, is not my business.
On this website you can find links to other external webpages. Although I check the contents of the destination page before linking them, please note that I am not responsible for the whole contents of the foreign website. I do not control them afterwards for unwanted changes or if the link is still valid. Please notify me by e–mail, if something has catched your eye.
The website is delivered by Net–Build GmbH as service provider. They collect personal data of my customers during the normal server/computer operations. I am unfamiliar with what (personal) data are gathered by the service provider. But they are subject to strong german privacy laws ('Bundesdatenschutzgesetz') and since May 2018 the 'General Data Protection Regulations' in the European Union and you should contact them if in doubt. I have lost access to the provided webserver protocols since the GDPR has taken place. These could be used to make statistical analysis of my visitors but nevertheless I had not been doing this for years.
The website itself does collect personal data in very low volume. Please note that all website data is transferred unencrypted. It is possible to leave an e–mail address in the bug database ('tracker') with your request, if you want to be informed about new comments. The address will not be shared or displayed to the public and deleted when the request is closed ('Status: closed') or at least after sixty days. Certainly you can demand to delete it at any time.
This website does not use permanent storage machanism in your browser. Like cookies, 'Local Storage', 'Indexed DB' or others. Additionally there is no 'fingerprinting' to recognize you on subsequent visits. The bug database ('tracker') store your filter settings as long as your browser session lasts in a cookie. All content (texts, images, stylesheets, scripts, fonts and software packages) are local only.
If you send me an e–mail I will of course get one/your sender address. You may use a 'disposable address', when you just want to send a comment, a feature request or similar and do not expect a reply. I will not share your address. All mails are fetched through a secured connection ('SSL/TLS') from my service provider and are stored in my long–term archive (unlimited time) for later reference on encrypted drives. Of course you can tell me to delete them at any time. Therefore every sender mail address gets an individual delete code in my reply´s signature.