X/Twitter Threads Creation

[MikeKMiller]

🔖 Feature description

It would be great to have a feature that enables the creation of X/Twitter threads by posting all the content in a single post using a specific delimiter (like "///") to indicate where tweets should be split.

🎤 Why is this feature needed ?

In my use case, I often post longer content that fits better as a Twitter thread rather than a single tweet. Having a way to easily write everything in one place and split it up automatically would make the experience smoother and more efficient. It would reduce errors and time spent manually splitting posts.

✌️ How do you aim to achieve this?

It would be great if Postiz could detect a delimiter in the content and automatically split it into individual tweets, making it seamless to publish full threads in one go. This would add to Postiz’s flexibility for managing longer content, especially for Twitter users who rely heavily on threads for engagement.

🔄️ Additional Information

I’ve explored other tools that offer thread creation, but adding this feature to Postiz would streamline the process and reduce the need for additional apps. It’s just a thought that could really enhance the user experience!

👀 Have you spent some time to check if this feature request has been raised before?

• [X] I checked and didn't find similar issue

Are you willing to submit PR?

None

[nevo-david]

I think Hypefury has it, but I was never quite fond of it. Let's see if it gets some upvotes :)

[MikeKMiller]

Hypefury has the ability to create threads..... but only by character count. Meaning you have to have 280 characters for it to split it, not simply by a delimiter.

[jontstaz]

Is the X integration working for you guys currently?? When I try to link my X account, clicking the "X" icon in the Add Channel modal simply directs me to a 404 error page. Specifically, url.com/undefined. The other sites which I've setup such as Reddit work fine. It's just X.

[MikeKMiller]

Is the X integration working for you guys currently?? When I try to link my X account, clicking the "X" icon in the Add Channel modal simply directs me to a 404 error page. Specifically, url.com/undefined. The other sites which I've setup such as Reddit work fine. It's just X.

Yes, after I added the X API credentials in the docker compose environment section.

Which API type did you setup, X has two types, curious if that could be why?

[sy3c4ll]

@nevo-david I would like to give this a try!

Plan

I plan to implement this feature the following way:

• The moment our user inputs the delimiter (currently fixed to be ///) the editor splits and opens a comment tab just below the working tab, as if 'Add comment' has been pressed.
• Whitespaces around the delimiter are automatically trimmed. This allows the user to precede the delimiter with e.g. a space bar for ergonomics and not have that blank carry over to the posts.
• Whitespaces at the start/end of the entire thread are not touched, and leading/ending whitespaces can be inputted normally from the created editor tabs - this trimming is only for when the editor splits, only around the delimiter.
• Copy/pasting an entire thread that contains multiple delimiters will work okay, multiple editor tabs will be immediately created to accommodate each post/comment.
• But you cannot have the delimiter as text within your post.

Code

After having a look at the source, I've gathered this can be fixed on the frontend. AddEditModal seems to be relevant in managing editor data, adding comment tabs and defining callbacks, and I plan to specifically modify the changeValue callback function.

• Currently, changeValue only sets the model content at the called index to the newly changed editor content.
• This will be changed to have the callback look for the delimiter every new input.
• changeValue will split the content at the delimiter, and insert new model items to the list with regards to the split array.
• The first post of the split editors will retain any images or ID info of the original post before the split.
• Trims will be applied as discussed. If there exists no delimiter, nothing should be trimmed. If at least one delimiter is present, the first split content will have trimEnd applied, the last will have trimStart applied, and anyhing else will be trimmed front and back.
• Ultimately, there is no longer a guarantee that changeValue preserves the number of elements in the model list. I don't know if this is regarded as an invariant anywhere, if it is please tell me and I will try to come up with another solution.

Room for improvement

• The delimiter could be made configurable by the user. This would certainly be useful in that as per my suggestion, it is impossible to include /// in the post, while if the delimiter were configurable the user could choose whatever sequence they plan on not using.
• The thread creation mechanic could be made configurable by the user, including but not limited to turning it off and having the split be applied on edit or a specific button press.
• All-in-all, both require a design change which I believe merits a discussion of its own.

If you approve of my plan, please assign me or otherwise show me your approval so I can get started on the PR! If not, please don't hesitate to tell me, this is my first contribution to open source and I may have made mistakes I'm not aware of. I would hate to accidentally sabotage a codebase as my first 'contribution'.