Example of high probability setup for long intraday entry by using readily available free resources at your disposal

Watch out for top Gainers/Losers from NSE site
https://t.co/rldBIkYzMY

Check if the respective sectoral Index is also among the top performing index.
Here the criterion is met as top gainer as well as sectoral index are matching.
https://t.co/D9lDQ7ieR8
Check if open interest is also supporting the criterion

https://t.co/eHkCqvcYeC

Here this criterion is also matching as Cipla is showing good rise in open interest among the constituents of pharma index
Finally lookout if the intraday price action is also supporting long entry.
Kindly wait for 1 hour for market to settle & to ensure all above criterions are met.
Same can be replicated for short entries as well. There are many ways of deciding your own criterion for long/short entries like
1.Rise in Volume & rise in Open Interest.
2.Above previous day's high or below previous day's low.
3.Pivot/CPR/VWAP Etc. for entry/exit.

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.