Kevin Quick

Also worth noting: once the session has expired, Matterhorn will no longer get and display channel updates so new messages on these channels are not highlighted or otherwise indicated and...

See also https://github.com/matterhorn-chat/matterhorn/wiki/Channel-History-Search

It seems like this would result in un-reproducible builds and builds that can be dependent on elements not captured in the store or the derivation?

Maybe you could say more about what problem this addresses, because a CI testing system that doesn't generate builds that are reproducible or stable doesn't seem ... useful?

It would be nice to have the hackage version updated: some distros won't ship 8.10.5 for a while, so having an stm indicating compatibility with >= 8.10 && < 8.10.5...

Hi @gerowam , thanks for the report and the corresponding analysis. I can confirm that I see just over 800 bytes of consumption for each `createActor()` call with a `globalName`...

Thanks for the detailed information. I don't know for sure, but what I expect is happening is that an Admin is still running. In general, the multiproc bases will start...

I'm glad to hear you got things working, and I really appreciate the feedback! It's nice to know things work well and the documentation is useful, and I'm definitely interested...

That information is currently not exposed to the Actor itself, so your methodology of a message send from the parent is the recommended Thespian solution. There is no fundamental reason...

Thank you! I appreciate the suggestion and I will look into adding this as a feature in the near future. -Kevin Pawel Lampe writes: > Well, thank you for explanations....