SI
SI
discoversearch

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
BeFree, Linkshare, and cj.com
An SI Board Since July 1999
Posts SubjectMarks Bans
13 4 0
Emcee:  Leeza Rodriguez Type:  Unmoderated
 Previous 25 | Next 25 | View Recent | Post Message
Go to reply# or date (mm/dd/yy):
ReplyMessage PreviewFromRecsPosted
13 I started a BFRE Thread. Am I correct that BFRE is the first "affiliates Herc-11/8/1999
12 WHo else joined the BeFree club?Madharry-11/3/1999
11 BFRE priced at $12, above the expected $8-10 price, which could indicate high dKS-11/2/1999
10 Leeza, here are the quarterly revenues from their S1 filing: 992Q: 863 thousandJoseph Waligore-10/10/1999
9 Joseph, My own observation is that a few companies have been leaving BeFree forLeeza Rodriguez-10/10/1999
8 Leeza, BFRE looks to Ipo soon. My worry is that their revenue did not grow mucJoseph Waligore-10/10/1999
7 Hi Leeza, Just came about this thread and was wondering when you are going to sBrooklynDave-10/9/1999
6 GD and thread. Please take note who is putting their $ on BeFree...Michael DellLeeza Rodriguez-8/29/1999
5 Leeza: Thanks, await guide for dummies. Appropriate for me. Since own SFE angdichaz-8/5/1999
4 gd: This is like a flashback to 1995 when I started writing about bandwidth .NoLeeza Rodriguez-8/5/1999
3 Leeza: Hey, back on the old AOL/Fool networking thread as MF Mom and (briefly) gdichaz-8/4/1999
2 Hi Leeza. I'll be following this thread with interest as your theory beTodd DeMelle-7/15/1999
1 At the risk of sounding like I'm having a monologue with myself I predict tLeeza Rodriguez-7/15/1999
 Previous 25 | Next 25 | View Recent | Post Message
Go to reply# or date (mm/dd/yy):