Moritz Staudinger

> You could always add post-processing that null'd out strings with length 256 I suppose I don't think that would work, BinarySerializer would read 256 bytes when it should read...

Other serializers expose some way to deal with a "Formatter" or "CustomSerializer". And then you'd just decorate your field like this: `[TypeConverter(typeof(MySpecialStringFormatter))] public string Name;` and inside `MySpecialStringFormatter` you have...

- [ ] Track "speed" of a topic: incoming messages per minute / hour. - [ ] Explore persistent storage options so stats don't reset when backend instances restart; alternatively...

@chrisjbremner > I would also benefit from this feature, or by being able to provide these values in the query params Makes sense, but serach filters are js, and while...

Message count in detail view is done. Showing it for all topics might be somewhat expensive though (in terms of performance)

For 'delete' topics: easy For 'compact' topics: exact count would be too expensive, but we can do a few random samples in the topic to compute an average message size,...

I'll take a look and fix those two issues (the exception/type error thing; and the refresh not working) Thx for reporting, and thx for the additional info 😄

That should already be possible. Try this as filter code: `return headers["metadata"].source == "SUMPTIONBUCKETS";`

I think both types of access should already work. (If not, it might be a bug in the interpreter) I'll add headers and a few examples to the help things...

Glad to hear that property-access works. But the other issue (maybe it's because it is a boolean or something??) is definitely a bug. I will put it on my list...