thomasDE

By that logic, I guess you are fine with using `exec` to run Python code to rename the file? It's "just another API".

Can you share the program to consolidate cards? We are also using Wekan in our company and would be very interested in that.

We have been using it for 3 years now at a small company. There were some minor bugs in the past (mainly UI related), but in general it is a very good replacement for Trello.

We run it in a Docker container with LDAP integration so that people can log in with their Windows accounts. The operating of it has been very straightforward.

> It's like writing shitty PHP code without templates.

For me, it's the other way around. I feel like you can still separate the logic and markup, but instead of the template engine syntax you can just JavaScript.

From the top of my head, I can at least remember six template engines' syntax I've learned: Smarty (PHP), Mustache, Blade (PHP), EJS, Angular and another custom template engine. When I tried React I was so happy that I did not have to learn another template syntax as it all was just JavaScript.

Another template engine syntax? No, thank you. I stick to React.

100% agree. Running Seafile for ~1.5 years with >100GB synced and ~5 users. Couldn't be happier. The sync-part just works.

Big advantages over own/nextcloud:

* Easy updates that work. When I tried owncloud, nearly every update I had to fiddle around with the database to make it work. Didn't have a single problem when updating Seafile so far.

* Block-level sync. Meaning if you change one line in a 10MB file, it will only update that part. Last time I checked, owncloud did not support this.

* Sync just works. When I tried owncloud, folders disappeared, folders were duplicated. Never had this problem with Seafile.

What exactly was the problem with Seafile? I was looking for a Dropbox alternative. Tried Owncloud and was fairly disappointed. But Seafile is working great for me (using it for ~1.5 years now).

Well, okay, it "represents" a block size increase, so that you can put ~70% more transactions into a block. In reality, it is not a block size increase as the block size will stay at 1MB.

But I don't think that this is enough long term. I would much prefer an increase to 4MB or even 8MB.

I think you are right. Thanks for correcting me. I thought the Elsevier thing was part of the deal with VG Wort as most mails which are currently going around in my university seem to combine both issues.

German researcher here.

There are multiple problems with the offer from VG Wort (which is the German association "representing" authors and publishers). One is that they raised the license fee. Another one is that they want to replace the current "flatrate" (where a university pays a fixed sum for the right to copy books or parts of books for education) with a individual billing concept. That means, lecturers have to report to administration for EACH part of a book or paper that they distribute. This model is not feasible as the administrative costs exceed the royalties which have to be payed for the copyright.

For this reasons, multiple virtual learning environments (which are used to distribute books and papers) in Germany might go offline in 2017 because the copyright situation is currently unclear.

More information (in German): https://netzpolitik.org/2016/deutsche-universitaeten-2017-im...