Under the disguise of being too combative because he stood up and asked for a release policy he now has a 1 month ban.
4 Likes
#freejames
4 Likes
The message says “Repeated ad hominem attacks” and links to the Code of Conduct which was last updated in September 2024. Below is the screenshot of the offending posts which led to the silencing of @jfinstrom – hard to post these – would really rather not do it – will refrain from posting the actual text – but the fairly mundane topic which was being mostly productively debated (whether there are 2 or 3 currently supported versions of FreePBX) absolutely did not need to sink to this level.
I think we all agree with
So why on earth did you make it so sink ?
3 Likes
You’re kidding here right? That was no attack at all. You can not keep acting this way Chris. This is not how a community is built and maintained. You are now forcing me to rethink doing a full fork here and bringing up a new forum for the users. Do you really want the death of FreePBX under your watch and leadership? That will be a great resume builder.
He asked other Sangoma people to rein you in and your answer is to block him for 30 days.
Back in my day I flew the whole FreePBX team in once a year for a week for team bonding and planning. I even brought in @ncorbic and @mwhite and most people crashed at my lake house and it was a great event. Lots of relaxing, planning and amazing memories and stories of broken jet skies, drones and fireworks being launched from drones.
10 Likes
That is not (necessarily) the ad hominem portion of what @jfinstrom wrote – please review the screenshot image for the repeated ad hominem portions.
EDIT: added “(necessarily)”
Please why don’t you break down what you FEEL exactly is a violation and defend it. This censorship is just foolish.
4 Likes
If you do this I will be the first person to jump ship and leave Sangoma.
2 Likes
But you will admit to blocking him for 30 days because he was “mean to you” ?
When I repeatedly get censored the message I get always says “Flags” not “Flag” , can you show me who “flagged” my posts apart from yourself ?
3 Likes
@jfinstrom violated the Code of Conduct by making “repeated ad hominem attacks” and you can plainly see these in the screenshot of the previously deleted posts.
There’s no need to open up the GIMP and take a highlighter out for the already posted screenshots of @jfinstrom’s posts which made repeated ad hominem attacks in violation of the Code of Conduct which last updated in September 2024.
Those are not ad hominem attacks. Just because you keep saying they are does not make it reality. Chris you are not god here. This is a community not your cult. You should not have single authority to make ultimate decisions like this.
7 Likes
The specific portion of the Code of Conduct (last updated in September 2024) that was violated by @jfinstrom in the above posted screenshots reads as follows:
Some might prefer to label @jfinstrom’s words as “Name-calling” and others “Ad hominem attacks” but the CoC forbid both, thus, the silencing.
@penguinpbx it might be wise to spend 12 bucks and get this book.
3 Likes
Book suggestions notwithstanding – still trying to stick to clarifying OP’s as-of-yet retracted assertions – please refer to the screenshots for why @jfinstrom was silenced due to repeated ad hominem attacks in those posts in clear violation of the Code of Conduct (which was last updated in September 2024.)
I disagree and do not see them as violation of your COC so I will not be changing my stance. Just like you refuse to admit you are wrong on EOL of FPBX15 and keep doubling down on your mistakes. I have admitted in these forums more times than I can count when I was wrong on something. You on the other hand have no ability to accept or admit mistakes and are happy to kill the FreePBX project and community with your behavior.
I wonder why almost everyone who has worked on FreePBX has left Sangoma and now work for leaders who cares and have vision.
6 Likes
It is 
s and 
s to compare your continued support of ad hominem attacks with debates on EOL schedules. The screenshots clearly capture these deleted posts with the ad hominem attacks that resulted in the silencing of @jfinstrom in accordance with the Code of Conduct last updated in September 2024. The EOL date of FreePBX v15 has no bearing whatsoever on the forum moderation decision making process.
So how would one in the community address what they feel is inappropriate moderation for the forum?
8 Likes
You can’t. We all know this. We can’t mark any of @penguinpbx post as off topic or violation of COC. He also is allowed to continue to post in slow mode threads when we can’t which makes it look like we are ignoring his replies to us. The rest of us can only post or edit once per day and he can keep posting.
Even worse if he marks one of our post for hiding since it’s a slow mode thread we can not go edit the post to try and fix it as slow mode threads don’t allow edit.
1 Like