Hey! I commented on your previous update post. Right here:
It's not an issue with 3speak itself, it's an issue with how ecency handles 3speak embeds... I covered the issue comprehensively in my comment
😄
You are viewing a single comment's thread from: