gwicke

3 ms·

1.
by gwicke 4y ago
I agree the FreeCAD UX could use some improvements, but I think even more important would be improving reliability and feature coverage in the OpenCascade CAD geometry library it uses. Slightly more complex things like fillets, lofts, nurbs
2.
Wikimedia REST API hits v1.0(blog.wikimedia.org)
9 points by gwicke 10y ago|0 comments
3.
by gwicke 10y ago
I wrote a fairly similar library that additionally uses data from last.fm and pandora, and supports compiling by track similarity as well: https://github.com/gwicke/compilation I'm using it to power the auto-playl
4.
by gwicke 10y ago
I wonder if Amazon is also deduplicating. It seems likely that a share of users would store large media files or software packages without encryption.
5.
by gwicke 10y ago
At Wikimedia, we are using firejail to lock down services. We encountered some bugs in older versions, but those have since been fixed. Overall, it has been working fairly well for us.
6.
by gwicke 12y ago
We are actually working on a storage service called RESTBase ( https://www.mediawiki.org/wiki/RESTBase ). RESTBase has pluggable table storage backends, starting with Cassandra. Other backends will scale this down for sm
7.
by gwicke 12y ago
This depends on the definition of compliant. By the paper's feature-based approach, Parsoid would be 'compliant' with the PHP parser. There is more to compliance than a simple feature comparison though, most of which can only
8.
by gwicke 12y ago
Nothing beats being told that what you just did is in fact not feasible ;) Check out this page: https://www.mediawiki.org/wiki/Parsoid This is the bidirectional conversion engine between wikitext and HTML+RDFa that pow