The default docker ran with the command from the docs

mkdir /usr/local/citadel
docker run -i --rm --network host --volume=/usr/local/citadel:/citadel-data citadeldotorg/citadel

opens starttls ports, but not tls ports. Why would this be?

I've figured it out, the ports are set to -1 by default and the documentation on default opened ports is wrong. You can edit them with this: citadel.org

If you're a user of the text mode client, there has been some significant refactoring of that code. Not a lot of what we did is readily visible but we had a few people who wanted to build on top of it so we did some very nice cleaning up in that part of the system. It was really old code, full of gotos and other horrors, so it needed some love :)

 

 

 

Yep, I saw the code improvements being made (I legitimately look at the code page once a day as a matter of interest) and am honestly quite pleased with the text mode client currently.  Behaves fine as far as auto color detection for any reasonable terminal -- gives only monochrome in Syncterm but I kind of like that (use a real terminal for citadel amirite?.) and doesn't have the usual code spillover for color detection like it used to in any situation I've been able to test except for one condition: if the baud rate is too low and the logon screen doesn't finish before the auto-detect threshold (I'm presuming that's the time criteria) then you will get said spillover. Honestly, not that big a concern as even my C128 wifi modem does 9600 normally (too bad I don't have access to it to test right now) but it is a case where such can happen. I would hope anyone crazyenough to access my BBS with a 300 baud modem would also be smart enough to just backspace before putting in their name. ;)

Secondly, I have to applaud that the formatting of text in the messages folder is now respected by the text client -- something I was meaning to ask about but didn't as I don't want to be annoying and at this stage everything I think could be improved seems to be improved in the next build. Really makes my logon screen work well, and I can use an ASCI banner on the logon and know it will print correctly on screens larger than 80 columns wide!

Screenshot from a Windows 2000 VM, for that Y2K authenticity.

PS: Also working perfectly in the telnet client that comes with FreeDOS, for what that's worth. :D

Fri Jan 17 2025 03:19:34 UTCfrom IGnatius T Foobar Subject: Re: Citadel Protocol binding for Dart Native?

Your project sounds interesting and fun. Looking forward to seeing it.

You can monitor the progress at my CodeBerg.org repo. So far it's a mockup of some of the screens with placeholder text. Once I started getting the hang of the Dart language, it's turning out to be pretty easy to work with. Every now and then I have to look up a command syntax on the webs but as long as I'm using Intellisense on OSS (VS Code with the snooping taken out), it's starting to go pretty smoothly even.

I looked through the C source file you indicated on the text client. It's clean code for C and I have no trouble reading it. At this point the only reason I'd reinvent the protocol source is if I wanted it to be the same license as the client itself.

Of course, making the C client code into an LGPL shared object would tip the scales fully in favor of using the C client code. On the other side of the scale, Dart makes code that's portable across 5 platforms plus 2 in the browser itself (standard web page with JavaScript or compiled web page with WebAssembly). If one platform didn't support such a shared object, I'd probably translate the code into MIT licensed Dart.

I noticed a few bugs in the web interface or the underlying infrastructure. If they are all in WebCit, I wouldn't be surprised.

1. I entered an event in the calendar here and it translated the times into a different timezone. I don't mind if it's stored in the server as GMT because the server uses Linux. When it gets sent back to my browser it shows in GMT still instead of my native timezone, though.
2. I've noticed some of the HTML formatting in the editor is not as flexible as raw HTML in the respective mode of the editor. In other words, I can edit paragraph tags into header tags and it shows headers right after I submit the changes. It's probably a minor matter as the text editor upstream hasn't been updated. 
3. The only way I've found to enter links on this page is to do it manually in HTML mode as well. Once entered, the ghosted link icon springs to life and lets me edit the link I've just created.
4. Once a message is saved to drafts, there is no way to make it post. Even moving the message to a room is typically unsuccessful. (This is on a system a few versions back.)

I wouldn't be surprised if this is all WebCit standard bugs, so I just would like to know if these are known bugs or not?

Dear all,

Is this settings enouth for a citadel email server co-sited with Apache to be deployed?

Email server with only two active users. Apache with less than 10GBytes/month activity.

VPS with 2 CPU cores, 3 GB RAM. I am doubting about 2CPU cores as the minimum number of threads of citadel is 5. Must I limit the number maximum number of threads? I have now 16.

Thanks,

Luís Gonçalves. 

I have a fair number of users in DE and FR who would like the interface to be in their native language.

How do I do that?

I wonder if it works like their other belongings without a stated plan for their "estate", it goes to the spouse by default, and if that isn't available it goes into limbo with probate and people have to fight over things. And if no one steps up there, it goes to the state and is lost forever.

But i don't claim to be an attorney, nor have i stayed at a holiday-inn, in perhaps 50 years ..

I Tue Jan 21 2025 02:57:08 UTC from IGnatius T Foobar Subject: Re: Citadel Protocol binding for Dart Native?

.

We have to work out two issues on that. The first is that the primary author of citadel_ipc.c would be difficult to contact for relicensing permission because he died in 2021. I don't know how that works; to the best of my knowledge he left no successors or assignees. The second is that citadel_ipc.c depends on libcitadel, which has numerous authors.