Tweet
It might sound a bit weird that we need something to fetch fake news with - and indeed crawling is not an alternative. At least not in the perspective of the amount of what Google works with. Besides data regulations is something that must be considered too.
However, utilizing some of the content of specifically chosen sites, known to spread fake news, for example, may be needed. Especially with what I have in mind.
As of today, NetCurl has developed to be a quick-configurable library that calls for http-sites and parses them to usable objects or arrays. Netcurl activates whatever it need to fetch on high verbose level. It utilizes http codes to make throwable calls and extracts body data if necessary. However, the code was initially not written to be PSR compliant. The target of this code base right now, is to do so. One reason of this is that make the library less conflicting with PSR-compliant sites as the ecommerce base it is implemented in requries safer code. Also, the plans to build in more default communication engines (like before) so, regardless of what drivers a web service uses, communications should always be available and chosen by "best practice".
More details (and the history of "NetCurl", if you can handle the amount of text can be found here!
However, utilizing some of the content of specifically chosen sites, known to spread fake news, for example, may be needed. Especially with what I have in mind.
As of today, NetCurl has developed to be a quick-configurable library that calls for http-sites and parses them to usable objects or arrays. Netcurl activates whatever it need to fetch on high verbose level. It utilizes http codes to make throwable calls and extracts body data if necessary. However, the code was initially not written to be PSR compliant. The target of this code base right now, is to do so. One reason of this is that make the library less conflicting with PSR-compliant sites as the ecommerce base it is implemented in requries safer code. Also, the plans to build in more default communication engines (like before) so, regardless of what drivers a web service uses, communications should always be available and chosen by "best practice".
More details (and the history of "NetCurl", if you can handle the amount of text can be found here!
Comment