WMI

Tingkatkan Performa Blog Dengan DNS Cloudflare Increase Blog Performance with Cloudflare DNS - Basically all DNS is the same, namely the function of connecting a domain name with the user's IP so that the domain can be accessed by users. However, each DNS server provider certainly has a different performance, so this affects the speed of a website's response when accessed. So that the speed of this server response needs to be considered also after we increase the blog loading speed by improving the blog template used. And Cloudflare is the best for DNS server performance in the world, and we can use it easily and for free to improve the performance of our blog. Like this Magic Company, even though the blog was deemed fast enough when accessed, it turned out that the server response speed from the domain that I used was quite slow around 250 ms. After I replaced it using DNS Cloudflare, the server response speed was quite high only 1-2 ms, wow .... If you ofte

How to protect javascript from developer tools ? here the answer. put this code into your page or template before closing body ( </body> ) <script src="https://cdn.jsdelivr.net/gh/dimaslanjaka/Web-Manajemen@master/js/protector.js" async></script> This script functions to hide the output from console.log, console.error, console.warning, and so on. and will also notify visitors that the site being opened is in a time suspension, because the visitor is opening the developer tools in his browser. This article about : protect javascript from debugging hide javascript console from developer tools protect site from debugging

CURLE_UNSUPPORTED_PROTOCOL (1) The URL you passed to libcurl used a protocol that this libcurl does not support. The support might be a compile-time option that you didn't use, it can be a misspelled protocol string or just a protocol libcurl has no code for. CURLE_FAILED_INIT (2) Very early initialization code failed. This is likely to be an internal error or problem, or a resource problem where something fundamental couldn't get done at init time. CURLE_URL_MALFORMAT (3) The URL was not properly formatted. CURLE_NOT_BUILT_IN (4) A requested feature, protocol or option was not found built-in in this libcurl due to a build-time decision. This means that a feature or option was not enabled or explicitly disabled when libcurl was built and in order to get it to function you have to get a rebuilt libcurl. CURLE_COULDNT_RESOLVE_PROXY (5) Couldn't resolve proxy. The giv