Copper - Weekly chart

Looking weak, sell below 732 SL 753

Next band of support 714-685

Copper - Daily

Cluster of supports in the area 685-714

RSI is hinting weakness. Break below 680 will invite more downside.
Copper - Monthly

650 previous major bottom.

Close below 680 can expect 630-575-520

500-520 is multiyear breakout. 8/10 times such multi year breakouts are retested.

Too early to comment but keep an eye on 730 then 680 these levels can decide next trend

More from Shivaji Vitthalrao🇮🇳

Hindcopper -- Can face selling pressure from 122-125 zone. Bull are weak and Previous bottoms 135-136 major hurdle. Not Crossing 125/135 can take stock to lower levels

#Hindcopper https://t.co/KMpDhWTc53

More from Copper

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.