I am going to complete a thread about Congress participation in Ram Mandir donation drive. It will be handy for Congress leaders to show voters from majority community when they ask the party to show their love for Shri Ram Ji.

Thread 👇

MP Congress secretary Vivek Khandelwal said he has collected Rs 70,000 over the last three days. He said the drive will continue until the end of January. https://t.co/TaG5gMN7Le
Ek Rupya Ram ke Naam': Congress' student wing starts drive to collect money for Ram temple construction.

https://t.co/81Qxh8zdCN
DCC vice president, a Congress leader inaugurates fund collection for Ayodhya temple. https://t.co/ywSsYa1Lxb
Digvijaya Singh Donates Rs 1.11 Lakh For Ram Temple. https://t.co/XFcEFOjFRM
Congress leader in Uttarakhand begins donation drive for Ram Temple. https://t.co/gJfMi78JPX
https://t.co/tBW8cjb1tU
Bhopal Congress workers on fund collection drive for Ram temple construction.

https://t.co/QVKnV5GaTN
Hardik Patel announces Rs 21,000 donation for Ram temple construction.

https://t.co/VqGkDX0uxf
https://t.co/Krj9rv8Ktb

You May Also Like

Trading view scanner process -

1 - open trading view in your browser and select stock scanner in left corner down side .

2 - touch the percentage% gain change ( and u can see higest gainer of today)


3. Then, start with 6% gainer to 20% gainer and look charts of everyone in daily Timeframe . (For fno selection u can choose 1% to 4% )

4. Then manually select the stocks which are going to give all time high BO or 52 high BO or already given.

5. U can also select those stocks which are going to give range breakout or already given range BO

6 . If in 15 min chart📊 any stock sustaing near BO zone or after BO then select it on your watchlist

7 . Now next day if any stock show momentum u can take trade in it with RM

This looks very easy & simple but,

U will amazed to see it's result if you follow proper risk management.

I did 4x my capital by trading in only momentum stocks.

I will keep sharing such learning thread 🧵 for you 🙏💞🙏

Keep learning / keep sharing 🙏
@AdityaTodmal
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.