I highlighted the big selling volumes for you. Did I know the CEO will resign? No.

I just noticed the selling by informed insiders on the chart. And here you have the news with a LC.

Ignore the charts at your own peril

Jubilant Foodworks https://t.co/E1C2eWrPHp

More from The_Chartist 📈

More from Screeners

TradingView isn't just charts

It's much more powerful than you think

9 things TradingView can do, you'll wish you knew yesterday: 🧵

Collaborated with @niki_poojary

1/ Free Multi Timeframe Analysis

Step 1. Download Vivaldi Browser

Step 2. Login to trading view

Step 3. Open bank nifty chart in 4 separate windows

Step 4. Click on the first tab and shift + click by mouse on the last tab.

Step 5. Select "Tile all 4 tabs"


What happens is you get 4 charts joint on one screen.

Refer to the attached picture.

The best part about this is this is absolutely free to do.

Also, do note:

I do not have the paid version of trading view.


2/ Free Multiple Watchlists

Go through this informative thread where @sarosijghosh teaches you how to create multiple free watchlists in the free


3/ Free Segregation into different headers/sectors

You can create multiple sections sector-wise for free.

1. Long tap on any index/stock and click on "Add section above."
2. Secgregate the stocks/indices based on where they belong.

Kinda like how I did in the picture below.

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.
The entire discussion around Facebook’s disclosures of what happened in 2016 is very frustrating. No exec stopped any investigations, but there were a lot of heated discussions about what to publish and when.


In the spring and summer of 2016, as reported by the Times, activity we traced to GRU was reported to the FBI. This was the standard model of interaction companies used for nation-state attacks against likely US targeted.

In the Spring of 2017, after a deep dive into the Fake News phenomena, the security team wanted to publish an update that covered what we had learned. At this point, we didn’t have any advertising content or the big IRA cluster, but we did know about the GRU model.

This report when through dozens of edits as different equities were represented. I did not have any meetings with Sheryl on the paper, but I can’t speak to whether she was in the loop with my higher-ups.

In the end, the difficult question of attribution was settled by us pointing to the DNI report instead of saying Russia or GRU directly. In my pre-briefs with members of Congress, I made it clear that we believed this action was GRU.