How the website ( works

On this page, we’re going to explain how our website works and how we manage to post the contents available on the website ( server is based in the United States of America, which includes the actual space for hosting the website and the database server. The mail server is hosted on a different server in India.

Because is a news website, the content is organized in articles. Every article may include text, audio content, video content or image/s. Expect for the plain text, which is saved locally on our database, the other contents are usually loaded from external sources.

Because of the standard-setting of WordPress, the author displayed on the articles sometimes may not be the same user who has written the text or uploaded a certain image or included a certain video. This because WordPress associates to the user who creates the article, the author’s role. In most of the case, because roles are different, the user who creates the article leaves it blank, adding only the title and fixing the URL. Then, the article is completed by other users, with the task to add all the missing contents as the text, images, videos, links, etc.

Talking about video and audio, our sources are most of the time YouTube, Soundcloud, Spotify, Clyp and the most common social media as Facebook, Twitter, Instagram, VK and Reddit. We use this method firstly for transparency with our readers, who can rapidly see where the information came from and also to not overload our website. In this way, we can deliver huge content (in terms of a megabyte) in a relatively small time.

We use a small different approach with images. In this case, there’s no common way to operate. Some images are hosted directly on our server and some others are embedded from external sources. Despite the position in which the images are saved, the website uses a CDN, a special javascript and a caching system to load them in the most efficient way. The website uses jetpack CDN (Formerly Photon). The images themselves are not directly loaded by the HTML page but thanks to a javascript. The website uses a lazy load method that, loads the images when they are actually visible to the user. In this way, the website saves bandwidth and speeds up the website for a better user experience. Because the images are loaded with a javascript, if the browser has javascript disabled, no images will be displayed.

HTML, CSS, and javascript used to generate the pages of the website are minified. This prevents excessive use of bandwidth and a faster load of the page. The minification is made both first, with certain files already minified and on-demand by our caching plugin and Cloudflare, when the files are requested.

The website is optimized for the mobile experience. The code that loads the mobile version of the website is different from the one for the desktop version. This is why, sometimes, because old cache files (read the next section to know more) that you may have saved on your pc from previous visits to our website, the pages could not display correctly. In this case, we suggest reloading the page.

The website uses a caching system to improve the performance of the website for the end-user. Our caching system tends to preload the pages, downloading the static content from external to our server and delivering the page faster to the end-user, to finally delate the content to our server, saving space. This process is completely automatized and it’s managed completely by our caching system. The preloaded pages are encoded and different for every user that accesses the website to offer the best experience according to the browser and device the user is using.

In addition to the caching described above, we use the Varnish cache and Memcached.

Besides the caching system internal on our website, we also use Cloudflare for another layer of performance. Besides the classical Cloudflare caching system (including rocket loader), which automatically uses the nearest Cloudflare server to deliver the content to the end-user for the best performances, the website ( uses also the Cloudflare KV workers. This system lets Cloudflare add a new layer of cache, caching HTML pages on the Cloudflare CDN. The calculation of javascripts (like the lazy load which loads the image) and PHP are made with this method.

Because the multiple layers of processing that the content must go through, sometimes the pages of the website may not be displayed correctly. Minification, caching, loading via javascript are all operations that could create some glitches on the final displayed page. Sometimes it’s enough to reload the page but other times is necessary to intervene directly to the code. If you see some strange behavior please let us know via our contact form so, we can deliver a fast fix.

The website doesn’t store any type of personal information, if not the one inserted by users themselves on their profile page or via the contact forms. The website doesn’t store logs regarding the changes in the website itself. The only log available is regarding the access to the site and all the analytics provided by Google and Facebook analytics (which are stored in the respective domains).

Some of the articles and/or pages of this website may not be available in some countries.

Some of the articles and/or pages of this website may not contain advertising.

Privacy policies and disclaimers here.

This page may change at any time and without further notifications.