Looks like there is a missing link to the main chat object.
If you look at say this chat file as a chat file it has a pointer back to the mother chat object. inde:this flow:message :5f843367dc95072254cfc258 .
where @prefix inde: <../../../index.ttl#>.
The pointer back to the chat object allows the UI to show the message in context of the rest of the chat.
With the new data browser as a web app, you do not get all of the information you may want in a view, such as if you notice, Portal gives you more options with its version of the mashlib code than the modified mashlib code in the code repo on github. Thats why I mentioned on gitter that it appears that Solid is becoming more restrictive but, that just may be me being paranoid lol.
Hi @adventure thxs for searching a fix with me .
In fact, my question is just why does the databrowser consider that file as a chat file ?
This is only a file with many articles !!!
Is it the name of the file 2020-11-05.ttl similar that the one used by a LongChat ?
Is it the ‘replyto’ predicate ?
I don’t see anything in my file that say the databrowser must use the chat-pane to display it…