u/SimplifyAndAddCoffee

Two issues, one clearly a bug that the application seems to have about a 50% chance of crashing any time I go to save an order template or watchlist and start typing in a name to save it, and 100% chance of crashing if I try to overwrite an existing template/list by saving with the same name... kind of annoying but I figure I might be stuck dealing with it unless someone here knows of a fix. I had to install and run it as root in /opt/thinkorswim/ to get it to launch correctly.

The other issue I'm not sure if it's something I'm doing just not using the software right or what, but I keep running into these situations where I set up a conditional OCO bracket to close out a position automatically, only to have it either:

a) somehow buy more shares than it closes with the conditionals, after they've all executed, leaving an open position after the trade should have closed.

b) somehow execute both orders from an OCO pair, or execute sell orders too many times, leaving me with a short position.

I've been playing with the application using paper money while I try and get a handle on how to use it and figure out why it's doing things like this before doing any real trading... I guess the question is, can I even trust it to not sink me with an improperly executed order? The last thing I want is a short position left open on a stock I didn't even know I had overnight.

P.S. the documentation on this application is atrocious or out of date (maybe just the ubuntu one?) and I'm having a really hard time following guides for how to perform certain actions in the interface. The docs seem to describe a lot of buttons and tabs that just aren't there on my application.

Say you go in on a pattern trade like a trend but then the pattern breaks immediately after. It's clearly no longer fitting your strategy, but at least you're not losing much yet so if you wait it out it could resume or it could do something else... Do you close out your position right away and take the L? or do you just shore up your stop losses and hope it turns back into an opportunity later?

Basically all my trades today were a wash, made like $1 at the end of the day. At one point I was up $100 but all my positions basically stopped moving. I probably could have kept the $100 if I'd closed them all out right away starting with the winning ones, but instead I just closed out the risky ones at market and put trailing stops on the others and lowered my profit goals in hopes they would resume the trend later in the day (I didn't have time to babysit them today with my day job). I came back to close out before market close to find about $201 in profitable trades wiped out by $200 in losing ones, and 4 positions still open that hadn't really moved all day.

I'm still new to this and honestly would have been up $80 if I hadn't somehow failed to double check everything closed correctly last night and left an open position to start me in the red this morning... but I really can't decide if I made the right call today. Felt like a coin toss. I'm not playing with a lot of capitol right now, just like 10k in savings so it's not a bad day but still pretty disappointing after how things were looking this morning for my strats.

looking for a specific software utility which booted from 3.5 inch floppy or USB and performed low level bit-by-bit copying between IDE and SATA HDDs. IIRC it had a guy's name as the brand, maybe Russian... the interface was all white (and maybe red/green/blue for accent) on black. It had a menu-driven interface navigable by keyboard, I don't think it had any mouse support. You could configure copy mode and settings like how many times to attempt to read a block before skipping it and moving to the next one, etc. It displayed progress as an array of ASCII block characters in a square frame, starting from the top left, moving left to right and top to bottom where a block represented a fractional chunk of the disk and would blink until it copied successfully or failed out based on the parameters you set. If successful it rendered a solid green (or perhaps white) block character for that chunk and moved to the next, if it had errors or failed it would render yellow or red. Copying could take a very long time if the disk had many unreadable sectors, but as a rule it pretty much always managed to recover any data that was physically readable from the disk in its present state.

I think to buy it you had to email the developer and they would send you a personalized copy that showed your registered name on one of the splash screens on launch.

stumbled across an ancient archive of the forgotten early web and want to rip a copy of it for posterity, but I don't want to be a dick and DDOS some poor webserver running on a potato. Are there any good FOSS tools that can slowly make a copy of a site over a period of days? Bonus points if it can mirror it on its own webserver.