Open MikeKMiller opened 6 days ago
From what I have read, the limit of the API is 1300 chars. Do you think it's lower?
Yes, however Postiz is cutting it off way before that. Here is an example.
Here is what I schedule in Postiz: (1,207 characters)
Most entrepreneurs think scaling is about adding more.
But the truth? It’s about adding smarter.
When I was trying to scale, I kept piling on new services, more offers, and extra projects. I thought more was the answer. But here’s what I learned: adding more can kill your momentum.
Here’s how to scale smarter, not just bigger:
1) Optimize Before You Expand: Before you double down on growth, ensure your operations can handle it. Are your processes streamlined? Are your costs under control? A solid foundation is key.
2) Invest in Your Team: Scaling means more work. Make sure your team is ready for the challenge. Invest in training, resources, and most importantly, in your people.
3) Customer Experience is King: Never sacrifice quality for quantity. A great customer experience is what drives sustainable growth. Focus on delighting your existing customers—they’ll become your best marketers.
Scaling isn’t about adding more stuff; it’s about creating exponential growth with what you already have.
Your Move: What’s one thing you can optimize today to scale smarter?
--
♻️ Repost this if you know someone who needs to scale smarter, not just bigger.
Here is what was actually posted (350 characters)
Most entrepreneurs think scaling is about adding more.
But the truth? It’s about adding smarter.
When I was trying to scale, I kept piling on new services, more offers, and extra projects. I thought more was the answer. But here’s what I learned: adding more can kill your momentum.
Here’s how to scale smarter, not just bigger:
1
@nevo-david in investigating more, I think the problem, 'actually' lies in the characters in the post not being properly handled/escaped.
For example in this reference post, it gets cut of at the first ')', and going back to issue #273 it got cut off on the same character.
📜 Description
This is a follow-up to Issue #273, which was marked as closed. The issue of LinkedIn posts being cut off around 715 characters still persists, specifically when using the Docker Compose version of the app. Despite the initial resolution, users continue to encounter this problem, indicating that the underlying bug might not have been fully addressed.
👟 Reproduction steps
👍 Expected behavior
The complete post should be visible on LinkedIn, matching the content entered in the Postiz app (up to LinkedIn’s character limit of 3,000).
👎 Actual Behavior with Screenshots
When posting via the Docker Compose version, LinkedIn posts longer than 715 characters are truncated. The same behavior noted in the original issue (#273) is still occurring.
💻 Operating system
Linux
🤖 Node Version
Docker version
📃 Provide any additional context for the Bug.
The issue is observed in the Docker Compose deployment, as shorter posts are unaffected and publish correctly. The same truncation behavior is consistently observed with longer posts, suggesting that the original bug fix may not have fully resolved the issue or is not compatible with the Docker Compose setup. Unsure if the bug exists in other deployment methods.
👀 Have you spent some time to check if this bug has been raised before?
Are you willing to submit PR?
None