Biep

I was told the following might belong here: **Give image/file posting its own eventType** *That way it can be assigned its own power level, allowing people to post messages but...

The only way to get rid of the "unread messages" marker seems to be to post a message. Which is not always desirable, e.g. in emergency message rooms.

The server admins did that - see [this message](https://matrix.to/#/!zUZMscRWCUCFnzKviF:nltrix.net/$NtGkD9QZCI0JMbfKtbH6eD67tou_xyz1llWty258fzs?via=nltrix.net) and [this message](https://matrix.to/#/!zUZMscRWCUCFnzKviF:nltrix.net/$7ozjURgHrlN6aOrwF84dHOyy5aJk0JLSNRJlzp9m56o?via=nltrix.net). Any technical questions are better asked to the poster of those messages, who is one of the two...

Red marks still percolate to the top:  But others stay below the spurious ones: 

I had the same thing, with a new file I added and then moved up. https://github.com/olivierkes/manuskript/issues/796#issuecomment-680263157

I see you are a contributor (and Dutch - 👋). Is there anything you can do yourself to repair this?

I am on Ubuntu 20.04 - and the corresponding older version of Manuskript - still 0.10.0. Here it happens too, but not consistently. But then I haven't been experimenting with...

And local files is exactly the main reason for wanting this, for me and many others I know..

Please thumb up this issue, to get more attention for it. I reported my instance as #1129.

Same here. I am quite willing to test experimental code on my Era.