Thank you so much for this valuable feedback.

one of my big issues with moving back to resource credits is that after reviewing the code and all available documentation, I cannot with any clarity tell you how the resource credit system works.

I can tell you the simplified version that was told to users, but unfortunately that's not how it actually works.

So, I will take that advice into account and move toward keeping the fees, in a way that is controlled by witnesses.

When it comes to curation compensation, how would you feel about reducing the compensation for curation to 10%?

What I mean is a post's author does the creative work. They generate the value. Curation does have value, but I think that in our current model, we are overvaluing it.

Before hard fork two, I will make a post detailing all proposed changes. We very much value feedback from the community, so when it comes up please do feel free to comment on it and suggest any changes that you would like.

In addition to that, we do code reviews. Usually, this just consists of @baabeetaa passing a merge request to me for code, or of myself passing a merge request to @megadrive for docs.

In discord, we have a channel, git.

In that channel, you can see all of the commits, merge requests, pipeline bills, and everything else in the blurt organization on GitLab.

seems to me like it might be a good idea to rig up an account that serves the same purpose and makes posts to Blurt every time something happens in our GitLab org.