This repository has been archived by the owner on May 26, 2023. It is now read-only.
toots that are only an image do not crosspost to twitter #679
Labels
Comments
|
Bumped—I have a bot on mastodon I want to crosspost to twitter that just posts images (with captions). |
|
I think this is a side effect of treatment for empty toots. I think pleroma in the past allowed completely empty posts (no picture, no body, no CW) and this would fail on twitter |
|
My toots with text and images don't get cross-posted |
renatolond
added a commit
that referenced
this issue
May 26, 2023
Closes #930, #913, #911, #906, #904, #897, #896, #895, #890, #886, #880 Closes #877, #872, #871, #868, #866, #863, #862, #859, #820, #810, #809 Closes #724, #721, #711, #688, #679, #606, #603, #593, #581, #577, #551 Closes #533, #517, #506, #505, #493, #430, #422, #311, #297, #241, #238 Closes #233, #197, #165, #164, #161, #160, #159, #151, #150, #148, #146 Closes #140, #139, #138, #135, #134, #127, #124, #123, #120, #119, #118 Closes #116, #112, #109, #106, #105, #103, #96, #90, #88, #86, #85, #74 Closes #65, #55, #47, #36, #33, #28, #19, #18 Closes #957, #955, #953, #950, #949, #936, #927, #925, #894, #873, #867 Closes #864, #650
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
i have checked all the mastodon->twitter options to see if i had missed anything but it seems there isn't such an option.
when i post toots on the mastodon instance that i use (not own), i expect them to be crossposted to my twitter account. i tried several times yesterday to have twitter catch the toot i kept sending that was only an image. it finally worked when i added text to the toot.
i decided to queue three unthreaded toots to the crossposter: one text-only toot without an image, one just with an image, and one with an image and text. on twitter only two of those posts arrived: the text-only post, and the one with both image and text. screenshots here. (i hope you'll pardon my snarkiness here.)
i perused the issues forum for a similar issue but it seems to have never come up. is this a bug in the crossposting software or a configuration issue with my instance?
The text was updated successfully, but these errors were encountered: