 | | Re: Problems with Brickshelf? —Matt Hamann
| | | | (...) <https://www.brickshelf.com/ Try this.> Click OK to be able to view it. (17 years ago, 15-Jul-07, to lugnet.general, FTX)
| | | | | | | | | | Re: Problems with Brickshelf? —Jeff Stembel
| | | | | | (...) Looks like that one has now been taken down as well. Jeff (17 years ago, 15-Jul-07, to lugnet.general, FTX)
| | | | | | | | | | | | Re: Problems with Brickshelf? —Kelly McKiernan
| | | | | | (...) That hole has apparently been plugged. It was open a few minutes ago, then it was closed. Which means that Kevin is reading this, and this is unlikely to be a hacker attack. Kevin, I think it would be a good idea if you could take a couple of (...) (17 years ago, 15-Jul-07, to lugnet.general, FTX)
| | | | | | | | | | | | Re: Problems with Brickshelf? —Steven Asbury
| | | | | (...) It no longer works. Clearly, someone is reading these posts and responding by making changes to the site. Kevin (or whomever is managing the site), since you're obviously reading, can you please let us know what's going on? If it's a financial (...) (17 years ago, 15-Jul-07, to lugnet.general, FTX)
| | | | | | | | | | | | Re: Problems with Brickshelf? —Travis Cobbs
| | | | | (...) While it may well be true that he is reading these posts, the fact that the hole was closed implies no such thing. As a server admin, he's going to see traffic. When he gets a sudden huge spike in traffic to a site that he just shut down, he's (...) (17 years ago, 15-Jul-07, to lugnet.general, FTX)
| | | | | | |
