Björn Schießle

It would be really great if we would become reuse compliant, thanks for bringing this up @CarlSchwan Sometimes we also need to provide a overview over all Free Software licenses...

You need to keep the lock until both the meta data and the file is uploaded completely. The whole purpose of the lock is to keep to separate request together...

> if we want for me is not a problem move unlock 100 line after (after send file) ;-) but for me this will become a big issue with several...

About the original request by @tobiasKaminsky: > - file size - on lock the clients tell server the file size - an unlock the server checks if the correct file...

I agree with @tobiasKaminsky. This is on the road map but will be probably a v2.0 feature.

> And with OMEMO, once chat is encrypted, you cant' search it, you can't really sync it, How do you come to this conclusion? With OMEMO and Message Carbons (XEP-0280)...

> I don't get it why you all want me to work for free so you can have convenient OMEMO in your device. I don't need or want OMEMO, so...

> OTR or OMEMO solves only one security problem - if you don't trust your chat provider, because the only real advantage it gives you over unencrypted messaging is that...

Just as a quick note, because it isn't mentioned explicitly (although I expect that this is the way it will be implemented): It would be nice if users can chose...

For the whole blog you could either use `@` or let the admin define a random actor name. I agree with @manoelnascimento that having "meta users" for categories/sections and tags...