How to set Small Stop loss ??
Please👇
1️⃣ If we trade on Monthly chart - stop loss set on weekly lower low
2️⃣ If we trade on Weekly chart than SL on Daily LL
3️⃣ Daily chart - Hourly LL
4️⃣ Hourly chart - 15 minutes LL
5️⃣ 15 minutes chart - 5 minutes LL
More from jitu
More from Stoploss
I follow SL for my long term positions based on weekly previous swing lows. I am out if it gets hit.
So, I am least worried in these minor dips as manier times it will give you opportunity to add more of your favorite names.
So, I am least worried in these minor dips as manier times it will give you opportunity to add more of your favorite names.
LEARNING \u2b55\ufe0f\u2b55\ufe0f\u2b55\ufe0f
— The_Chartist \U0001f4c8 (@nison_steve) April 7, 2021
Balaji Amines -
An explanation of how trailing stop loss works. With every base formation, the stop loss level is moved up thereby locking profits. Stop-loss can be placed via GTT Orders.
Assumption - Trading on a weekly scale pic.twitter.com/hojzClLOhg
The absolute best thread to read on trailing methods by @Traderknight007
Read and follow this.. he has aptly explained about various methods to trail.
Read and follow this.. he has aptly explained about various methods to trail.
2. TRAILING METHODS-
— Trader knight (@Traderknight007) December 24, 2020
1. SWING POINT METHOD-
In this method we use the swing points or the HH- HL OR LH-LL points for placing sl,
In this method we trail our sl when the stock make a Higher low after our entry and keep Trailing the sl till it hits. pic.twitter.com/CqzCkLdWmC
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x

PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ

The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.