Isn’t there a logstream they could tap into to have a separate async tally going on instead of doing it synchronously? Probably a lot of things could be delegated to an async job performed when server load allows?
I’ve had to really adjust my thinking with this project. They want to do things a very particular way and it goes back 4 years, and a lot of the mistakes are just now getting noticed/attention. For example, comments were not deleting on all the servers, I was testing that after comparing server copies of the same communities and found they were not the same. It just didn’t seem to have a lot of people spot-checking it for mistakes. I am learn to just “go with the flow” and face that it’s more like how musicians would approach design and running a project. Media-focused systems can be that way.
Isn’t there a logstream they could tap into to have a separate async tally going on instead of doing it synchronously? Probably a lot of things could be delegated to an async job performed when server load allows?
I’ve had to really adjust my thinking with this project. They want to do things a very particular way and it goes back 4 years, and a lot of the mistakes are just now getting noticed/attention. For example, comments were not deleting on all the servers, I was testing that after comparing server copies of the same communities and found they were not the same. It just didn’t seem to have a lot of people spot-checking it for mistakes. I am learn to just “go with the flow” and face that it’s more like how musicians would approach design and running a project. Media-focused systems can be that way.
Going with the flow is both ways. It’s a community project so everyone’s opinion matters, especially those who contribute PRs.