They do have margin accounts, but as I understand it, that was not what caused these deposit requirements to shoot up. I.e. the margin accounts were not what caused the problem.
This is terrible advice. if your slippage risk is such that you aren’t protected by NBBO you have absolutely no business on a retail broker of any sort. Meanwhile limit orders minimizes the most likely risk a retail trader has to overcome. Either you don’t understand the advice you were given, you were duped or you are trying to be duplicitous.
In any case, terrible advice to be repeating in the context of retail trades.
I don’t give any advice. I was probing to see the reaction .
It is amusing to look at postings glorifying the pundits advice. They are not your friend.
Have you actually placed a limit orders? Do you practice this advice with your own $’s?
Do you know how much taxes you pay for a trade considered day trading? If the limit order is executed same day it is considered day trading. What is the point then?
Why retail investors are penalted for that but hedge funds are not? Are you retail trader or on the other side of the table? If so why you are giving advice to retail investors? The motivations?
When I used to follow the pundits “advice” they were always wrong - limited orders were immediately executed. These “fluctuations “ causing execution of limit orders are never reported in the historical data . I used to purchase historical data for thousand $’s and never found these fluctuations in the official dat I saw on the screen. Meaning you can never rely on historical data for analysis. If you had the same experience you would know. Learning from practice I’ve different way of making $’s.
I spent years writing HFT trading systems. I’ve built back testing systems that actually worked. I’ve been out of the industry for more than five years and every order I’ve sent since I left (all through retail brokers including RH) have been limit orders.
I’m going to guess that I’ve spent more time in front of a real market feed than you trying to divine how the orders are impacting the book but who knows.
All that said I’d love to subscribe to your newsletter and learn the secrets to why limit orders have a different tax treatment than market orders.
Also for the record market orders tell the market you have no price sensitivity. If your newsletter could tell me how that’s better for retail investors I’d appreciate it.
Got it , just an observer working for the establishment.
Why you didn’t invest your own $’s if your algo is so good? Other peoples’ money I know.
Is that a real job? HFT is a scam. What about naked short selling (hft by other name )? Making money out of thin air? Selling something you don’t own? You did the hft for that too? What about GME now? 1.8 million missing shares . What your algos will do to the market? Crashing it?
Now the hedge funds are a joke, no? They aren't buying 50 million shares at 30c, nor $100, nor $300, and that's their problem. You can do hft all in nanoseconds - nothing is helping them. PRICE DOESN'T MATTER
How hft algo is helping the hedge funds now? The market will be never be the same , no hft , no newsletters , no apps will save it .
Just try with your own $ and you will learn from practice. Good luck following recommendations. Practice is the best teacher. Now - do you have thousands $’s to learn from your mistakes?
Yeah, but in those days we did that because there wasn't any other option. It's not like the colour scheme of the monochrome terminal was chosen for ergonomic reasons.
If anything, amber terminals were easier on the eyes. Or the white on black ones. Those were nice.
When I go outside green is the color my eyes are looking for to relax. Also pixels in the white background emit the maximum energy. One reason Apple introduced the dark mode is the pixels to emit mostly the valuable information and save energy , thus saving the battery life.
The white background is fine for the eyes, so long as the brightness is set properly - minimum brightness for the surrounding lighting with medium-high contrast. IME, this setup in a well lighted office makes a marked difference in eyestrain at the end of the day when compared to dark modes, dark rooms, and high-brightness light modes.
It's totally individual though. Back when we finally got terminals with white background I was very pleased. A co-worker was completely unable to use them though - he had to set the terminal to reverse mode. We talked about it and it was clear his eyesight was completely different from mine. There's no "one size fits all" here, and I for one have problems with dark mode - I see "flares".
This is precisely why I use f.lux[0] on every computer. As the blue light is reduced toward evening, the screen becomes much less bright. Works great for eye comfort and is maybe even beneficial for sleep.
There is no evidence dark mode is better. In fact, human eyes don't have good night vision, we see best in daylight.
Light text on a dark background makes the eye work harder and open wider, since it needs to absorb more light. When this happens, the light letters can bleed into the dark background and cause halation. Our eyes focus better when the iris is narrow.
Additionally, most people are born with some form of astigmatism, a misshaped cornea that blurs vision. For people that have the worst forms of astigmatism, light text on dark backgrounds aggravates the condition. When looking at a light display, the iris closes more, decreasing the effect of the deformed cornea. When using a dark display the iris opens to receive more light and the deformation of the cornea makes halation worse.
On the flip side, dark mode helps with floaters, tiny fibers or spots that appear in a person's vision. These are caused by changes to the fluid in the eye which cause shadows to be cast on the retina. Floaters distort vision in light mode. This condition tends to increase with age.
Also, people with light sensitivity might be better served by a dark background.
I have found that dark mode works best in low light, 100% contrast can be harder to read with more eye strain, reading large amounts of text in dark mode is harder.
It is frustrating when people who work in IT don't take accessibility seriously. Not everybody is young and in perfect health. Both light and dark mode should be offered for accessibility reasons.
Green letters doesn't seem eye friendly at least to my eye. My eye much prefers white on dark grey for emissive screens (LCD, LED) or black on white for reflective screens (e-Ink).
I had the impression that pre-1980's screens were green for chemical reasons not for eye-strain optimization (?)
For anybody interested the following equipment works the best:
1) Oticon hearing aids + TV streaming device connected to iMac via audio interface.
It streams the audio from the computer to the hearing aids .
2) Teams + captioning. In order the person needing to see the captioning to see it he has to initiate the meeting and sharing the link. The link never expires and could be saved in Notes from all members of the group. The members of the group needs to share the meeting time via other means for example email , text message.
Compared to Zoom, Google meetups Team has superior video, audio and captioning capabilities.
There are desktop and iOS versions of Teams. No way to use Otter reliably with hearing aid device because it requires Chrome browser and needs physical sound from the speakers to work. Internal networking the sound is not working.
3) Phone calls - CaptionCall. It is free service paid by the FEDeral government. You sign up and receive dedicated phone number which you enter in settings for call forwarding. When you are calling or somebody is calling you CaptionCall is intercepting the call and forwards it for machine learning+ person transcriber. This is the best combination.
4) Messaging across devices -WhastApp. No video or audio captioning in iOS so - using only messaging. Used for announcing Teams meeting.
All other solutions do not do anything to accommodate-WebEx, BlueJeans, etc.
Microsoft is having the best accommodation service - there is dedicated web site with free 24/7 support for people needing accommodation. One Teams account is just $5/month and the support is responding within several hours.
I love how many different approaches there are for setting things up!
One quick note about Otter: I’m using LoopBack to create virtual audio devices that let me feed the audio as an input source as well as play it through an output channel. That might work with the hearing aids.
(I use somewhat outdated Phonak Naida V SP’s – looking forward to the next gen that have better Bluetooth support.)
With Otter it is complicated. It iMac needs the sound to be split but Safari is not allowing it. So they recommend Chrome and changing it’s settings. Then setting up aggregate device. But it is not working. The only way it is working is if the sound is also coming out from the speakers and the microphone is picking it up. Too complicated, there is a feedback and no streaming to the hearing aids. So Zoom + Otter is out of the picture. Teams has the captioning and the best quality. What happens is a lot of companies are demanding in using only Zoom. This is a misters why they just don’t use the link of the Teams invite. If they don’t have it installed it is working from the browser too.
Fast compilation was one of the main reasons Golang was invented.
The gradual accumulation of #include clauses in C programs scales very badly. A large distributed compilation system was created in Google to handle the slow compilation. One reason is you never know if some #include is actually needed.
In Golang unused dependencies are a compile-time error. The generated object file includes type information for all related import dependencies in binary format. This speeds up the compilation significantly.
Yes and no. Most of the time my enums are well defined: ContactStatus, AwardLevel, JugeStatus, for example. I have not control over the names or values and all have a "Revoked" value. When they come in from an external system it's pretty easy to parse them and convert them to the wrong type if someone isn't paying close attention. Then they don't get caught for a week or so because the code compiles, runs, and appears to work correctly except for these occasional odd results.
