The Faceswap manifesto has a very interesting point when stating that “it was the first AI code that anyone could download, run and learn by experimentation without having a Ph.D.”.
I think it actually is a great thing that such a powerful technology is easily available to everyone. The technology itself was existing even before this open source project, so keeping it reserved to few skilled people did not prevent misusage
(especially because as most of IT technology, it comes with a low price to run, so the only barrier is often actually lack of knowledge).
In this article Bruce Schneier (quite rightly) complains about the security of WhatsApp next features and the possible impact on society. At some point, he claims that “Of course alternatives like Signal will exist for those who don’t want to be subject to Facebook’s content moderation” and in one of the comments a reader says that “Deleting whatsapp and installing Signal (Or other) takes less than 5 minutes. There just isn’t any excuse anymore. Do it. Do it now. Right now”.
The recentevents made me think a lot about business models.
Modern services are most of the time non sense business model; the vast majority is either free, or ads supported, or subscription based. All of these models are not OK for most of the cases.
I wanted to create an API in CLokure/Compojure that accepted an arbitrary number or parameters. I’m using Luminus framework, and I have generated an app using the +service template, which creates a RESTful API (see here for details).
I’m experimenting with Clojurescript; Clojurescript is wonderful (just as Clojure is)
and with Reagent it is lots of fun.
Unfortunately as for much of the Clojure-world there is not much documentation, but
there is a very handy recipe book
that together with the basic documentation should get you up and running.
Recently I had to find a bug which has shown to be very nasty (not to mention
not existent). One morning a customer called us claiming that one of our
services was not working. The service is composed of two APIs: a SOAP one and
a RESTful one. The problem was reported to affect the SOAP interface (even if
a later analysis show that also the REST API was suffering from the same
Knowing regexp is always a good tool. They can be useful for many tasks: from
searching strings to manipulating texts. A fun way to learn regexp is by using
this site; it basically is a crossword game
where definitions are in facts regular expressions.
Testing a RESTful API can be tricky, but it is totaly feasible. To keep things
as easy as possible I use curl to do all the calls. To clean the code as
clean as possible, instead of using the PHP implementation of curl, I prefer
to directly call the curl command.
Authentication in a RESTFUL api is crucial. You don’t want to give
unauthorized access to private resources, nor to allow dangerous operations.
There are many ways to authenticate a request. For instance:
Now that Yii 2 was released it may be not very useful, but I’m sure many people
are still using 1.1.x versions in production. Because of some internals of Yii
it is not possible to install the latest version of PHPUnit, but you have to
stick with an old one (I use version 3.7.1). There are basically two ways: PEAR (deprecated) or
I had to import a very large dataset (about 2.5M rows – OK, not that large,
but large enough to cut my teeth on it). After a quick search on google I found
out that the most efficient way to import data into mysql is to use
the mysqlimport command which is shipped with MySql.
Hi, you probably got here following this link on Stack Overflow.
Unfortunately, I never had the possiblity to actively support the tool, so it’s pretty useless. If you want, it’s available on GitHub.