Niccolo,
I usually don't engage with stuff like this, but your behaviour is what
makes open source development harder and often not fun.
I hope you know that all posts in the Gajim MUC are public:
https://conference.gajim.org:5281/muc_log/gajim/2023-01-19
You barged in there requesting help because you're "loosing money", and
Gajim devs + other people immediately tried to help you.
They very clearly explained that this is a libproxy bug and told you
that downgrading libproxy works as a temporary workaround, which you
don't want to do because of "dependency issues", which is your choice.
The devs and maintainers in the MUC then very clearly explained to you
why the Gajim devs can't do anything about this problem.
You then continue to mix up "upstream", "Debian developers" and "Gajim
developers" and finally (because you have nothing more to add and out
of frustration) you start lamenting about Gajim being a resource hog
because it's written in Python.
They (understandably imho) ban you from their MUC and you end up here
writing things like
> That's speak volumes about the Gajim team. They not only suppress
freedom
> of choice but thay are also recurring to low level methods in order
to hide
> Gajim issues and bugs. I felt compelled to report this incident
downstream.
which is absolutely ridiculous and unjustified.
Also:
> I'm running Debian testing.
Well, yeah.
