Domain: moo.ca
Stories and comments across the archive that link to moo.ca.
Comments · 14
-
Re:47%
Firefox 1.5-2.0 have Gopher support, as did IE5 and IE6 (although it was later disabled in a patch). I believe the reason that it was removed in Firefox and IE was because it's a codepath that wouldn't receive much testing and so it might have bugs or security holes. Considering any Gopher ramifications of any protocol change or sandbox change is an unnecessary overhead (and if you really need Gopher to view a gopher site you can just install a Gopher client... speaking of which that'd be something to have as a Firefox addon).
-
Re:Compatibility
Here is an HTML chat client without Javascript. Here is an HTML chat client with Javascript. Javascript not required? Maybe if you really enjoy the stone age it's not required. Otherwise, yes, it is required and you'd be retarded not to use it.
-
Re:Compatibility
Here is an HTML chat client without Javascript. Here is an HTML chat client with Javascript. Javascript not required? Maybe if you really enjoy the stone age it's not required. Otherwise, yes, it is required and you'd be retarded not to use it.
-
Re:What gentle prose...
Profiling is a very well-used tool in law enforcement. Profiling is only illegal when it involves race and other naughty issues.
As a person who doesn't "get" racism at all, I believe that if sa 80% of Uzi shootings in Toronto are done by black males, 18-25 and 75% of 30-30 shootings are done by while males, 35-50 then when someone is shot with an Uzi, they might want to check the local black male population.
Racial profiling can also be bad of course, and one must always remember the other 20/25% (in my made-up numbers that have no resemblance to reality whatsoever). That said, you don't look for the shooter to be a two year old a local grade school when the weapon was a PSG-1 either, but is that age discrimination? -
Object Oriented Database
I'd like to have an object oriented database, like Lambda MOO, but accessible from a multitude of languages, instead of just one.
-
Again, MOOs work for this sort of thing.
This purpose has been adequately served for several companies I'm involved with by using a MOO or other MU*s. My bias may be revealed by the fact that one of those corporations is in fact dedicated to running a particular MOO.
However, I have to say that it satisfies all of your requirements and provides a great deal of flexibility for the future as well. It has its own internal programming language (affectionately but not officially known as C&) which allows you to modify basically everything without requiring a restart. It has full support for TCP/IP and file IO, and though the binary support leaves something to be desired, it is quite possible to write a fully functional HTTP server for example. -
Again, MOOs work for this sort of thing.
This purpose has been adequately served for several companies I'm involved with by using a MOO or other MU*s. My bias may be revealed by the fact that one of those corporations is in fact dedicated to running a particular MOO.
However, I have to say that it satisfies all of your requirements and provides a great deal of flexibility for the future as well. It has its own internal programming language (affectionately but not officially known as C&) which allows you to modify basically everything without requiring a restart. It has full support for TCP/IP and file IO, and though the binary support leaves something to be desired, it is quite possible to write a fully functional HTTP server for example. -
MOOs work for this sort of thing
Warning: Shameless plugs ahead. Disclaimer: I don't make any money from my pimping of MOO.
Although I don't know of something that does specifically for what you're asking for, in my experience a MOO makes a good platform for conducting official meetings. Everyone logs in, you can talk to one another (privately if you wish), and logging is easy.
Plus, it's decently easy through the MOO's C-like internal programming language to code up a motion/voting system in a certain room so that everyone can head in there for a meeting and have everything handled and logged correctly.
More info about MOOs can be found here and documentation is plentiful on the web. Additionally, I could probably even give you some pointers if you were to drop by my MOO. -
MOOs work for this sort of thing
Warning: Shameless plugs ahead. Disclaimer: I don't make any money from my pimping of MOO.
Although I don't know of something that does specifically for what you're asking for, in my experience a MOO makes a good platform for conducting official meetings. Everyone logs in, you can talk to one another (privately if you wish), and logging is easy.
Plus, it's decently easy through the MOO's C-like internal programming language to code up a motion/voting system in a certain room so that everyone can head in there for a meeting and have everything handled and logged correctly.
More info about MOOs can be found here and documentation is plentiful on the web. Additionally, I could probably even give you some pointers if you were to drop by my MOO. -
Pueblo
...is the way to go. I run Pueblo on Wine on my Linux box. Pueblo
-
Mozilla Development
I've been developing a Mozilla-based application component since August 2001. It's an HTML-rendering MOO client, and recently I've been pouring some 90% of my free time into working on it.
75% of that 90% of my free time lately has been updating the application to newer standards which have come into place since August 2001. For example, the Navigator/Mail/Editor/Chatzilla options used to be on the 'Tasks' menu in Mozilla, and were moved to the 'Window' menu around 1.0rc1. Bang, suddenly my application stops working properly, and less importantly, stops being a friendly component which works like all the others. A patch from a friend moved just about everything over to the 1.0rc1 way of doing things, and all was fine. Not everything worked flawlessly, though. The 'MOO Client' menu option didn't have an associated key visible, and the 'Window' menu inside MOOzilla didn't have any visible keys. The menus inside the application had long since stopped graying-out/disabling properly depending on what you have selected in the window. Many hours of last weekend was spent fixing these problems by conforming to new command handler expectations, and so on. (Where 'new' means 'changed since 0.9.6'.
;))XUL is a wonderful tool. However, it runs dog slow on OS X. You don't have to take my word for it, just look at the Pheonix project. Pheonix is available for Windows and Linux, but not for OS X. Why? Because Chimera exists for OS X, which is faster (I'm using it right now) and integrates with the OS better. But... it doesn't support XUL. That's why it's faster. So where is my Mozilla application left? Stuck in the massive Mozilla suite when it's run in OS X. Mozilla, at startup, uses over 120 megs of RAM on my TiBook. Thank God for good VMs.
When initially writting MOOzilla, the XUL documentation was shit. The only place to go for any idea of how things really worked was deep inside the Mozilla source. And sure enough, this worked. The official XUL documentation at that time had sections which trailed off in 'blah blah blah' often because someone got bored of writting. I specifically remember it once read 'This is very important because blah blah blah'. Arrrg! How frustrating!
Mozilla is a powerful application development environment. XUL is a wonderful tool. Books like this one are going to make the world a better place for Mozilla component developers. And more cross-platform software developed with Mozilla makes the world a better place for users. Now... if only we can somehow apply this book heavily to the head of people who don't want to download Mozilla to try out an application, because they don't want to use it as a web browser. *sigh*.
-
Mozilla
Currently I like using Mozilla to access my mail and news simultaniously, as well as have access to a MOO client (MOOzilla) and a web browser all with one package. It is, however, a tad buggy.. I find that some newsgroups consistantly cause the mailer to crash, and I haven't yet gotten a resolution for this bug.
I used to use a perl script I wrote, fetchnews, to read newsgroups and deposit them into mboxes for use with Mutt. Posting to USENET was done by sending to local nntp-alt.bitterness, or whatever newsgroup, which used a qmail wrapper script to send the mail out properly. It was a nice setup, but since I've lost most of the configuration, I've switched to Mozilla.
-
Language tags.I worked for four years on Internet content for the Canadian government. Everything had to be bilingual -- on pain of death. It took a long time, but we eventually came up with an extremely simple and effective method of tagging languages. It involves splitting up <<different languages&&andere sprache>> using tags and parsing these files server-side.
I created a web page describing the system, and some of the problems to be avoided: http://files.moo.ca/multilingual
-
MOO.ca
Check out MOO Canada, eh!. They offer free email, homepages, custom portals, etc... all programed in MOO.
We even have a Lord clone and a few other fun text based games(fishing, paintball, blackjack, roulet, etc...)
The moo is mainly targeted at youth and has strict policys(please read them).
telnet://moo.ca:7777