Not exactly (site:gitlab.open-xchange.com in a search engine gets you the links to access the projects directly), but the explore page is indeed restricted.
The history of Qwant itself should be a big red-flag.
At this point, why keeping the brand?
They have no real IP of interest and they are only associated with bad things... for the few people that knows them.
The only thing that is stable in its history, is the public funds put in there...
Now I assume that it's the only reason for Qwant to exist: to get public funding and do everything but an actual European search engine/index.
Also, Octave is quite successful on his hardware/network ventures, it's the complete opposite for the software/service part.
OVH would be much more popular if they knew how to make software, which is a decent Manager.
Hubic is another disaster from Roubaix.
So this partnership is pretty meaningless for us I'm afraid.
I've been using Qwant, people have to be paid and there was never silence about the difficulties that qwant had. In fact, it would be odd if they would be hiring people and not really clear how they are being paid.
> however the new public API has an animation, after which a special window opens and requires you to click a "share" button before Flameshot can work with the screenshot. You need to go through that every time you use Flameshot.
I don't think that's quite in compliance with GPL3, but I'm not a lawyer. The bundled release artifact doesn't allow someone to build the extension, and I think GPL3 takes that into account. If I have a Java program, I have the bytecode, and unless it's been run through and obfuscator, I can pretty easily recreate the Java code. But the GPL3 doesn't count that as compliant.