CorvusCorax

unfortunately not. I had to backbench this issue for now. I have near zero experience with tensorflow, so my personal workaround was to run caffe instead ;) I was hoping...

A workaround could be to erase the chat history. This might be useful in combination with the planned "export/backup" of chat history. I know some other messengers only keep the...

workaround: i just tested, you can erase the chat history manually by deleting a contact. the contact will then show up in the list of archived contacts, and can be...

this can probably be closed now :)

Edit: I take that back, the issue IS reproducible. just not every time, but both in main and staging. the first media-tag is not being shown with this "not a...

Edit: Does not apply! ( _Was: that would also explain why it worked with media-tag-nacl.min.js because that has older (but working) dependencies all packed internally_ )

update. the bug is reproducible after all, sadly. the first media-tag does not show up (with "not a media-tag" error logged, all further media-tags do show up)

I'm being stupid.... I always tested the mediatag functionality with exactly 4 mediatags or less - which obfuscated the issue. the mediatag/main.js is a stub. instead of cycling through ALL...

a simple foreach instead would fix this I have a feeling the code in mediatag/* was used to develop the mediatag functionality that eventually made it into the compiled obfuscated...

the following - much shorter version of main.js in mediatag works correctly: ```js require([ 'jquery', '/mediatag/media-tag.js', '/bower_components/tweetnacl/nacl-fast.min.js' ], function ($, MediaTag) { console.log(MediaTag); console.log($('media-tag')); if (typeof MediaTag === "function") {...