>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.
That’s not true. Elastic acquired Found in 2015 and immediately offered their managed Elasticsearch service. It was publicly announced at their user conference early that year.
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.
You seem to know more about this than I do, but my layperson's takeaway from the Snowden revelations is that the NSA records every url we browse. Are you saying that's incorrect?
The only way NSA can record the URL without having infiltrated Kagi's datacenter, is for them to have broken the encryption algorithms behind TLS/HTTPS.
If that's the case, nowhere on the regular Internet is safe.
Snowden revealed that NSA has infiltrated all the major industry players (Apple, Microsoft, Google, etc.), also ISPs. But the only way NSA can know what your plaintext HTTPS URL is either by having access to your PC, or having access to Kagi's servers. Or as I said, that they've cracked encryption schemes everyone assumes to be safe.
>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.
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.
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 can do it on a decentralized finance app like compound: deposit a stablecoin you trust (which could be USDC) and borrow Tether, then immediately sell it and put it into something else that earns interest, incl outside crypto. You continue to earn interest on the deposited USDC (currently .86%, Tether borrowing cost is 3.62%, all ignoring Compound rewards). You can borrow against 82% of the deposited USDC, but 70% would be better to cover the interest accumulating and possible temporary spikes in Tether value.
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