The only point that the OpenBSD situation made clear to me was that both Pale Moon developers are good with code, but terrible at basic human interaction.
The maintainer was still in the phase of trying to make it work, the code was on a personal github... there was no Pale Moon for OpenBSD, no decision on actually making it available, let alone forking it or giving it another name... it never got to that point. And that's why approaching the issue with that style made no sense. "You will revise your mozconfig..."? The average person will tell you to take a hike. "I will not be as educational next time."? Would you continue working (for free!) on making someone else's "product" when they make a threat the first time they interact with you?
What's wrong with a "Hey, thanks for working on this, however since you're not using our libraries and <insert reasons>, you'd need to rename the browser as per our license and we also don't want to be associated with ports that do this. Let me know if we can help with anything."
There's nothing wrong with not wanting to be associated with something that might not work as you intend it to, not want to support it, etc, but you can't behave like an asshole if you want people to work with you. Like, you're being more hostile than someone like Mozilla would usually be under similar conditions... no wonder the attempted port died with that Github issue.
In any case, and going back to my point about them being toxic, Moonchild was fine with Tobin's behaviour (and vice-versa) towards others and even joined in sometimes... so only blaming Tobin makes no sense. Moonchild still doesn't see anything wrong with the way they approached the My Pal and OpenBSD situations, so it's only a matter of time until the next drama. Essentially, it might be a less toxic project now, but some of the people who made it toxic are still there and have not changed their ways. That's their right, I guess, but it's not something I want to be associated with.