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.

Strategies & Market Trends : BAK - Investing -- Ignore unavailable to you. Want to Upgrade?

To: Covenant who wrote (505)	3/5/2012 1:33:45 PM
From: bankbuyer	1 Recommendation Respond to of 3249

Re: "The second is b) maintaining a topic" Amen

To: Covenant who wrote (505)	3/5/2012 2:20:05 PM
From: SI Brad	8 Recommendations Read Replies (1) \| Respond to of 3249

Re: SI format sucks *(1) automatically include the "RE:[topic]" as the first line in the editor* Well, number 1 is 80% done :) I implemented it only for this subject for now. I still need to get the cursor planting in the right place, so for the next day or two you'll need to click below the RE: line. The RE line will truncate at the first carriage return, so it only picks up the first line of the message you are responding to.

To: Covenant who wrote (505)	3/5/2012 7:35:01 PM
From: SI Brad	6 Recommendations Read Replies (1) \| Respond to of 3249

Re: SI format sucks Number 2 is done. *(2) keep track of unread messages in the database rather than relying on the browser.* With the exception of NEXT 100, the system will record which messages you have visited, and display the link as having been visited in the list of messages....no matter which computer you are on. When we add the threaded view, I will record those messages as well, but I don't think it's appropriate for Next/Previous 20 (or 100) I started recording visits to messages a few hours ago, so for messages prior to this afternoon there will still be a difference between browsers. I've made quite a few little changes today, so hopefully I didn't break anything. This feature is live site-wide. I don't anticipate any performance issues however...the CPUs were begging for more work.