Chris

there's a problem with this approach: we must change how we deal with errors, we can't use onDeuMerda like Debug.crash, to make this work, we'll need to use more Results

We still need a tool for removing them, a simple bash script might do it, but I don't know where to start :T

- [x] **1)** logs are editable now, but yet not propagating to the server - [x] **2)** not empty anymore, we're slowly adding sites - [x] **3)** filesystem is highly...

I'm leaning toward the 2nd method, but my opinion might change depending on the outcome of the later problem (or even other not discussed yet problem).

> > > are you sure that #40 is fixed with that? because it seems that I still get it > > > > > > just do: > >...

:+1: on this. really hard and time consuming, but great reward :smiley:

:+1:

> I disagree, it's not very clear how one should implement that effect (or their simulation) on their own... It doesn't matter "how one should implement that effect", we should...

~~I've updated the issue to present an alternative that might make you happy @PedroHLC~~ **EDIT:** nah, forget about it, adding a msg back to `Effect` would require the `onLoopback` to...