The ๐ฉGentlemenโs Suite ๐ฉ TradingView indicator has been updated, refined and received new features.
Use code "TOP_HAT" for a 15% discount โ๏ธ
Additional discounts for 6-12 month subscribers.
See below for details on how to access:
https://t.co/C1zhpdxMG5
$BTC HTF update.
Whilst I was hoping for a little more late long capture and short clearout as part of the weekly swing into the ~$86-87k region, it's looking like ~$85k might be all that big daddy orange could muster up currently.
IF this is the correction beginning into the weekend, you already know the areas im looking at.
Enjoy your weekend ๐
$BTC HTF insights from a chart fairy ๐ง
Part of the reason we are seeing price compression at this range is due to $BTC dealing with the following:
โ๏ธ Fighting overhead high time frame (HTF) resistance
&
โ๏ธ Simultaneously retesting and attempting to hold lower timeframe support.
$BTC 15m update.
Well unless there is a late attempted spike up into US close I think this fizzled. Pretty weak set of friday sessions across the board really.
One would assume a sweep of the ~$80k zone is now on the cards.
$BTC 15m thoughts.
I think I can spot 3 clear impulsive downside moves here with both VOL and movement.
Sooooo I will be looking to see if Asia can present a small retracement setup to the target zone today
ATTN: Gentlemen's Suite Premium ๐ฉusers.
Script updates pushed this morning.
Keep an eye out for the purple update icon next to the indicator in @tradingview to get the update.
$BTC $ETH #indicator#tradingview#gentlemenandladies
Release notes
The ๐ฉGentlemenโs Suite ๐ฉ TradingView indicator has been updated, refined and received new features.
Use code "TOP_HAT" for a 15% discount โ๏ธ
Additional discounts for 6-12 month subscribers.
See below for details on how to access:
https://t.co/C1zhpdxMG5
$BTC 15m thoughts.
I think I can spot 3 clear impulsive downside moves here with both VOL and movement.
Sooooo I will be looking to see if Asia can present a small retracement setup to the target zone today
Security called me at 6:12 AM today.
"Patch every PHP server immediately."
I asked what happened.
"Two critical vulnerabilities. Remote code execution. No authentication required."
Cool.
How many PHP servers do we have?
According to inventory: 12
According to reality:
Nobody knows.
We found one running WordPress.
Three running old internal tools.
One under someone's desk.
Two inside vendor appliances.
A forgotten employee directory from 2016.
And a server named:
PHP-OLD-DO-NOT-TOUCH
Naturally, that one runs payroll exports.
Then we found a PHP 5.6 box.
I asked who owned it.
The documentation said:
BRIAN.
Brian left in 2019.
We called Brian.
He said:
"Oh wow, that's still running?"
Excellent.
By 8 AM, leadership joined the incident call.
CEO:
"Can hackers actually get in?"
Security:
"Potentially yes."
CEO:
"Without a password?"
Security:
"Yes."
CEO:
"Then why do WE need passwords?"
Not the lesson.
Finance asked if we could wait until the weekend to patch because downtime affects revenue.
Security explained that the alternative was letting strangers execute code on our servers.
Finance asked for a cost comparison.
At 9:17, someone suggested temporarily taking the vulnerable websites offline.
Marketing refused.
"Our campaign is live."
So for the next hour, the company officially decided maintaining a landing page for 20% off webinar registration was more important than preventing remote server takeover.
We finally patched everything we could find.
Then our scanner discovered another PHP server.
Hostname:
TEMP-PHP-2014
Uptime:
4,512 days.
Nobody knows what it does.
Nobody owns it.
Nobody can shut it down.
But every time we block network access, the warehouse stops printing shipping labels.
Security has classified it as critical infrastructure.
It is running PHP 5.4.
The vulnerability has existed longer than half our employees.
The emergency patch took four hours.
Finding out what PHP actually runs took eleven.
The internet isn't held together with code.
It's held together with servers everyone is afraid to turn off.