Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : The *NEW* Frank Coluccio Technology Forum -- Ignore unavailable to you. Want to Upgrade?

To: ftth who wrote (1723)	1/13/2001 8:22:44 PM
From: Frank A. Coluccio	Respond to of 46821

Now you know what I meant when I stated shenanigans, both stated and implied, in my post. The Interfiber snip was both interesting and instructive. The "what's good for the goose.. " mentality, or lack thereof, is in dome ways playing into my ability to retain my telephone number as we move our office a quarter mile away. When we moved to our present location we elected to use MFS/WCOM, for reasons that you would neither believe nor be interested in. Suffice it to say we had to pick a new directory number at the time, because local number portability (LNP) did not exist then. LNP is a translation feature that allows customers to move from one carrier to another without giving up their directory number. It exists today. However, it only exists in an unencumbered way for a limited number of CLECs, if you want to move from an ILEC to a CLEC. If you decide to move the other way, i.e., from a CLEC to an ILEC (I don't know that this is true for all ILECs, but it is in my business district, at least "MY" ILEC), get ready to pick a new number again. It's as though the ILEC couldn't care less (forsooth!), and they don't want to manage a telephone number that doesn't belong to one of their exchanges <nxx's>. Or, could it be that they are saying... "see what happens when you stray too far from Mom?" ---------- BTW, disregard me email concerning SI performance. It was my browser. I'm using a LAN-based device today, from a client's office. Seems as though the "machine" that I'm on was told by server central [?] to "upgrade" to the next version of IE, while I was in the middle of doing something else, and it has since degraded to a crawl, and then a standstill. So, I switched over to an older version of Netscape and I'm back up to speed. FAC