We build Signal in the open, with publicly available source code for our applications and servers. To keep Signal a free global communication service without spam, we must depart from our totally-open posture and develop one piece of the server in private: a system for detecting and disrupting spam campaigns. Unlike encryption protocols, which are designed to be provably secure even if everyone knows how they work, spam detection is an ongoing chore for which there is no concrete resolution and for which transparency is a major disadvantage.
Try Status instead of Session.
Fully FLOSS and their developers are not dicks who prioritize “muh dont want fixed notification” to digital rights.
I tried it in the past and I was welcomed with messages from scammers and no moderation in any groups that I saw. I may give it second chance one day though.
Session is quite new project, gains much more users then Status and thus generates more issues. If you would be a developer and you would prioritize fixing notifications that work for most users anyway over working on new open group server implementation to mitigate spam then your project wouldn’t last long. As a user I would rather see no notifications than get lots of spam that would make the platform unusable.