HN user
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.
https://en.wikipedia.org/wiki/Elasticsearch#Managed_services
Generally safe operating temperatures are between 0 and 70 degrees celsiuis.
e.g. Samsung https://download.semiconductor.samsung.com/resources/data-sh...
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 can do this with Localstack, however it's gated behind their pro service.
https://docs.localstack.cloud/user-guide/aws/iam/#explainabl...
https://twitter.com/sanitybit/status/1610829345676996609
I've been investigating the use of a @ThinkstCanary AWS token that was improperly accessed on December 27th and suspected as much.
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.
Onyx Boox tablets can convert your handwritten notes to text, and export them as TXT files. I'm not certain but the export can probably be automated.
At work I use the handwriting keyboard input to write directly into Confluence notes.
AWS has a compatibility mode that allows your cluster to report its version as 7.10.
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.
It's probably not that simple however.
It doesn't exist yet.
As a comparison, USDC reserves are 100% backed by US dollars held in custody accounts, currently 9.3B.
https://www.centre.io/hubfs/pdfs/attestation/grant-thorton_c...
A perfect use case for Number.prototype.toLocaleString.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
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.
You could add this repository to get the latest github releases: https://archive.newpipe.net/fdroid/repo/
Some ongoing discussion on this issue thread here. https://github.com/TeamNewPipe/NewPipe/issues/1981
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-...
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.
[1] https://derflounder.wordpress.com/2014/12/27/managing-automa...
My power company (the sole government-run provider in my area) now has reCAPTCHA on their payment form.
I'd guess that the warning period was set to 168 minutes (2hrs 48 minutes) instead of 168 hours (7 days).
Common things like rolling updates were a 3-step operation (or they were for us), and node replacement was a pain
I had the same experience until I created an ECS stack using CloudFormation, which made it much easier to manage.
The Cost Explorer now has Reserved Instance utilization and coverage reports which are quite useful.
In their blog post on medium[1], they mention that it is built on git. webdesignledger.com[2] claims that it supports full version control.
[1] https://medium.com/@FolioForMac/building-a-better-time-machi...
For Android: XPrivacy will alert you when apps attempt any type of network access and allows you to whitelist or blacklist specific hostnames or wildcards.
That isn't it's main/only function though. From their github page: "XPrivacy can prevent applications from leaking privacy-sensitive data by restricting the categories of data an application can access."
It is a module for the Xposed framework, and requires root.
This is one of the clear areas where performance is nowhere near previous versions. One solution is to switch to the "Picture-in-picture" zoom style under the Accessibility preferences.
It's not completely fixed. My guess is that only certain Airport Express cards are affected, as I have some machines that fail to reconnect and others that are fine.
To be fair, ST3 is pretty stable for everyday use.
With regards to Joomla, it really is terrible when it comes to security. Versions 1.5-2.5 have major vulnerabilities that allows anyone to create an admin user unless you disable account registration. Popular plugins like TinyMCE allowed unauthorised users to upload arbitrary files with a specially crafted request.
There are also plenty of bots that scan for vulnerable Joomla installs as they do with Wordpress.