You won’t be making any changes to Lemmy source code itself, that’s what I mean. I wouldn’t count adding something that is independent from the service as “customizing it”, but if that is what you meant, fine.
That setup required an additional server for AZ
What I had in mind would be to run the relay myself, and you would only have to set up/manage an extra service that could run along your Lemmy process.
You seem to think (…) we’re willfully not taking an action that we should be taking.
Well, yes? You have the possibility to take the initiative and mitigate an issue that is affecting your users, and you can solve the problem independently of the third-party’s cooperation. Why put yourself at the mercy of others when you have enough power and agency?
With the resources available its not feasible for AZ to develop/deploy custom solutions that can be resolved by remote instances with trivial configuration changes.
I’m not going to address specific parts of your post, suffice to say I disagree on almost everything you said.
As I said previously, if you have a workable solution please do devlop it and submit a PR to the lemmy devs. I’d be happy to try your suggestion should they roll it in.
Setting up parallel sending also would require more resources on their part.
It is your problem to fix, yet you are only willing to take action if the solution comes in the form that is most convenient to you. I genuinely don’t understand why, but I guess it’s between you and the users on your instance.
You won’t be making any changes to Lemmy source code itself, that’s what I mean. I wouldn’t count adding something that is independent from the service as “customizing it”, but if that is what you meant, fine.
What I had in mind would be to run the relay myself, and you would only have to set up/manage an extra service that could run along your Lemmy process.
Well, yes? You have the possibility to take the initiative and mitigate an issue that is affecting your users, and you can solve the problem independently of the third-party’s cooperation. Why put yourself at the mercy of others when you have enough power and agency?
With the resources available its not feasible for AZ to develop/deploy custom solutions that can be resolved by remote instances with trivial configuration changes.
I’m not going to address specific parts of your post, suffice to say I disagree on almost everything you said.
As I said previously, if you have a workable solution please do devlop it and submit a PR to the lemmy devs. I’d be happy to try your suggestion should they roll it in.
Setting up parallel sending also would require more resources on their part.
It is your problem to fix, yet you are only willing to take action if the solution comes in the form that is most convenient to you. I genuinely don’t understand why, but I guess it’s between you and the users on your instance.
You’re wrong, I’ll leave it at that. Won’t be replying any further.