So I've been thinking more on this topic..
It's really not very portable. If you want to write a game or app for mystic, then sure it will work. If you want to write a game or app for Magicka, that will work too, but if you want to write a game or app for any bbs it gets a bit trickier.
I am not a developer myself but was reading some developers some time ago trying to come up with a "standard" for interbbs traffic.
I'm on the fence about FSX_DAT now, in that I wonder if sending data over echomail is a good idea or not, regardless if it's going to be sent,
then a seperate channel would be good.
I am not a developer myself but was reading some developers some
time ago trying to come up with a "standard" for interbbs traffic.
I'm there with you. I have no dog in this fight. I know how to manipulate basic code from others to hopefully get it to do what I need, but I couldn't tell you how it works.
I think given 90% of the people here run Mystic so it's likely that the majority will be mystic mods using this system. So it's really going to be InterMystic communication rather than InterBBS.
So I wonder if there is another solution. What about something web based, but instead of a different script for a different door, it could be more generalized, kind of a service that many doors could use. You could do something like MQTT where your doors subscribes to a channel, and when a
This is what I was getting at with my last message about hosting somesort of
web service. The bit that bothers me though is that it would need to be decentralised for it to not just get lost when someone gets bored of it.You
then get into the situation where you have a shit-tonne of infra just tosolve
a small problem, so then you might as well have just used echomailanyway.
So if you write a door, you need to interface with the message base yourself, so that means JAM if it's mystic or magicka, SQLite if it's ENiGMA 1/2, WWIV's format if it''s WWIV, synchronet's format etc...
It's the same with echomail. If Paul one day gets bored of BBSes and
shuts down fsxnet, that would leave all the FSX_DAT using programs cut off, but they could then just go to another net.
It's the same with echomail. If Paul one day gets bored of BBSes and
shuts down fsxnet, that would leave all the FSX_DAT using programs cut off, but they could then just go to another net.
On 01/30/18, apam said the following...it's
So if you write a door, you need to interface with the message base yourself, so that means JAM if it's mystic or magicka, SQLite if
toENiGMA 1/2, WWIV's format if it''s WWIV, synchronet's format etc...
This isn't really any different from modular database support in a web application. Though of course those have the advantage of having access
well-vetted public libraries for the purpose.
So I've been thinking more on this topic..
It's really not very portable. If you want to write a game or app for mystic, then sure it will work. If you want to write a game or app for Magicka, that will work too, but if you want to write a game or app for any bbs it gets a bit trickier.
So if you write a door, you need to interface with the message base yourself, so that means JAM if it's mystic or magicka, SQLite if it's ENiGMA 1/2,
WWIV's format if it''s WWIV, synchronet's format etc...
I think given 90% of the people here run Mystic so it's likely that the majority will be mystic mods using this system. So it's really going to
be InterMystic communication rather than InterBBS.
Which is fine I suppose, given that people seem to prefer to write mods than doors anyway.
So I wonder if there is another solution. What about something web based, but instead of a different script for a different door, it could be more generalized, kind of a service that many doors could use. You could do something
like MQTT where your doors subscribes to a channel, and when a door updates, the message is stored in that channel, when it fetches, it gets messages
from it's channel. That way someone could host this service, and anyone could use it, rather than a different service per door. If that makes sense.
I'm on the fence about FSX_DAT now, in that I wonder if sending data over echomail is a good idea or not, regardless if it's going to be sent,
then a seperate channel would be good.
My thoughts on the matter...
2. DOORS Vs Scripts!
DOORS!!! If someone want to make an App or Game, it should be a DOOR. We should consider Scripts, as a fast way to do something that a DOOR can't or its overwhelming to do as a complete program. We still use DOORs from the DOS era.. where are all those scripts from the past? Nowhere.
I'm not sure I agree that an app or a game should always be a door, as opposed to a script. I look at MPL as pretty robust programing
language. Consider that the BBS functions in MPL are merely library functions. Is MPL's WRITE() function any less of a libray function than OpenDoor's OD_PRINTF(). Also, I seem to remember g00r00 making a comment that he's considering removing many of the BBS functions (one-liners, voting booth, last 10 callers, BBS list) from the BBS itself and using MPL/LUA/Python replacements.
The other feature for using MPL is that it is platform independant. The MPLs I write are the same for all the different platforms of Mystic. If
I were to write a game in pascal or C/C++, I'd have to maintain
different code libraries and build environments. That's not something I really want to do.
In summary: Doors Vs Scripts : Doors! Windows Vs Linux : Linux! Closed Source Vs Open Source : Open!
On Saturday, February 3rd xqtr was heard saying...
In summary: Doors Vs Scripts : Doors! Windows Vs Linux : Linux! Close Source Vs Open Source : Open!
Depends on the usage. BBS package specific mods are slick. The problem comes when you start talking inter-BBS, games, and so on. For that,
doors are certainly nicer.
It's incredibly easy to write multi-platform code, so that shouldn't really be a barrier to anyone. Language need not matter, either. That's why dropfiles were created.
Incredibly easy? Writing the code? Maybe. Compiling the code? Not as much. We've heard many times from g00r00 how he's had issues with some platform versions of Mystic while other platforms didn't have the same issue.
Incredibly easy? Writing the code? Maybe. Compiling the code?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 285 |
Nodes: | 16 (2 / 14) |
Uptime: | 76:50:51 |
Calls: | 6,489 |
Files: | 12,096 |
Messages: | 5,276,365 |