Another cold rainy day in the NY Metro area. Looks like downtown service on the 1/9 was shut down this morning, but probably back up by now. Maybe it's a smaller system, but I can count all the system outages I've seen on PATH with the fingers on one hand. Obviously you can't include the PATH station closings at ExchangePlace and WTC after the September11th attacks. Other than that, there were a couple track problems in 1998 or 1999 that were fixed. Maybe a couple of other things, but in the 8 years since I've moved down here, they're few and far between.
I'm still wondering if PATH runs faster than it used to between WTC and ExchangePlace. I'd swear it does, but still don't have any definite answers.
Tuesday, February 24, 2004
Saturday, February 07, 2004
Just for fun, did an egosurf of TransitCat on Yahoo and Google. Why the heck is this site listed on auction sites? Hey, anybody want to kick in some cash to keep this running? :)
I'm listed on a couple more other web sites, including New York Wiki who identifies this as "mostly broken". Good point, I've been getting beaten up by webbot indexing. When google hits the Wiki, the whole site pretty much shuts down. That's MS Access for you. I've been planning to convert the key Wiki queries to something else for a while. So far, MySQL has some really nice features, but my ISP doesn't support it. Makes me seriously consider spinning off the Wiki to somebody that DOES support it. (hint.. hint..)
Then again, there's a number of open source Wiki engines out there, why make a new one? I guess because I'm still planning a whole different creature from a standard Wiki. I'm combing through RDF ad GML specs for an updated Wiki XML language I plan to use internally. (I did create a simple XML Wiki language as part of the original Wiki. I don't know of any others that are hybrid DB/XML projects like mine, and certainly not developed as early as 12/2000.)
Have to admit, the portion of the site that uses the Access DB engine is what kills the rest of the site. That, and offloading to browser-side XML transformations for those browsers that can handle it, like IE and maybe Netscape.
---
Have a good weekend with the snow and rain and all that. Stick to rail if you can.
I'm listed on a couple more other web sites, including New York Wiki who identifies this as "mostly broken". Good point, I've been getting beaten up by webbot indexing. When google hits the Wiki, the whole site pretty much shuts down. That's MS Access for you. I've been planning to convert the key Wiki queries to something else for a while. So far, MySQL has some really nice features, but my ISP doesn't support it. Makes me seriously consider spinning off the Wiki to somebody that DOES support it. (hint.. hint..)
Then again, there's a number of open source Wiki engines out there, why make a new one? I guess because I'm still planning a whole different creature from a standard Wiki. I'm combing through RDF ad GML specs for an updated Wiki XML language I plan to use internally. (I did create a simple XML Wiki language as part of the original Wiki. I don't know of any others that are hybrid DB/XML projects like mine, and certainly not developed as early as 12/2000.)
Have to admit, the portion of the site that uses the Access DB engine is what kills the rest of the site. That, and offloading to browser-side XML transformations for those browsers that can handle it, like IE and maybe Netscape.
---
Have a good weekend with the snow and rain and all that. Stick to rail if you can.
Subscribe to:
Posts (Atom)