>The issue that Elastic had is that their entire business model was offering a managed elasticsearch solution. Amazon then created their own offering of the same thing
Amazon first offered Elasticsearch as a managed service in 2015.
Elastic began offering managed services in 2018.
This is not correct. ISPs cannot see the actual URL being requested. Your DNS provider can see the hostname. The ISP may be able to see the hostname unless encrypted SNI is in place. The ISP can see the IP address you are connecting to.
It might have been called something else like cloud hosting, but it was definitely equivalent to a shared hosting model. We didn't manage the web servers, no root access etc and the database server was shared between 300+ of their customers.
>Highly trained people handled the company’s incoming telephone and online inquiries
Not sure I can agree with this. Almost a decade ago we had some shared hosting accounts at Rackspace for some very legacy clients (ones that even accounting had forgotten about and not billed them for years). We had an issue with accessing one of the databases to export for handover, and so I got in touch with their online support. They gave me full admin access to their database server which had several hundred other clients on there. I could also see the historical metrics for the server which were interesting. I told them immediately but it took them almost a day to revoke my access.
I've never shorted or taken out crypto loans, but you could theoretically:
- Take out a loan of USDT, using a stablecoin you trust as collateral
- Immediately trade all USDT into your stablecoin
- If the USDT price crashes, buy it up to repay the loan.
e.g. Binance lets you borrow 800k USDT with 1.23m collateral. Over 180 days, interest paid would be 36k.
Say USDT crashes and you repay your loan at 10c/USDT - you would pay at most 84k to settle the loan. You then end up with 1.94m, a 58% return on investment.
You could also open restricted system preference panes by searching for a relevant term in Spotlight and going to a User Guide article. Often they would have a link to open the preference pane which would bypass any restrictions.
>If a request goes through multiple proxies, the IP addresses of each successive proxy is listed. This means, the right-most IP address is the IP address of the most recent proxy and the left-most IP address is the IP address of the originating client.
This blog post[1] has a good explanation of ConfigData updates. The flag would appear to force the install of new Gatekeeper configuration updates.
>To help distinguish Gatekeeper and XProtect updates from other updates in the software update feed, Apple marks them as being ConfigData updates.
>Marking these updates as ConfigData cues the App Store to not display these as available software updates in the App Store’s list of software updates. These updates are meant to be under Apple’s control and to be as invisible as possible.
Amazon first offered Elasticsearch as a managed service in 2015. Elastic began offering managed services in 2018.
https://en.wikipedia.org/wiki/Elasticsearch#Managed_services