Roland Kuhn

also: rework `ax apps sign` to take the key material from default places unless provided

what Benjamin said

Analysing the requirements I find it difficult to reconcile a few details. ## After the removal, the app shall be in state as if the removed events had never been...

Speaking with Mike @ Xitaso: another additional use-case is replicating some state into an external storage system (events or derived data), where the removals also need to be reflected for...

So here’s a draft: ## UX Design A new panel in the Node Manager allows the selection of events to be deleted for a specific node. The events are selected...

@rklaehn @mcamou That’s exactly what `WITH antiEvents` gives you. Actyx CLI feature will probably mirror Node Manager in some way, UX remains to be defined (could be “read a file...

@rklaehn Same as for Benjamin: please forget about the implementation at this stage and describe first the user-visible behavior. Otherwise I cannot understand your point and reply in a meaningful...

@benjamin-actyx I don't yet understand the third case with the exporter: if I get anti-events I better got the corresponding event first, otherwise I’ll be confused. The assumption that handling...

I know that from personal experience and speaking with other Linux admins in the past - they don’t like installing software that does not come with _Debian stable_ (well, as...

Thanks everyone for illuminating the problem space from so many angles! I’m now convinced that in this last-ditch context the right thing to do is the following: - admin connects...