This repository has been archived by the owner on May 26, 2023. It is now read-only.
If toot got crossposted to Twitter, if retweeted, toot the original message #809
Comments
|
Looks close. I might have a look at some point. Has been on my mind for some time. |
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.
Since you keep a reference to the toot being posted to Twitter, as replies to ns up on Twitter, but would that same source be used to crossrefence if a retweet needs to be boosted/retooted instead?
At the moment it just wraps the tweet and places it as a new message on the toot time-line, linking to the crossposted tweet.
If this (local/known) reference is not found in the instance, you just use the current behaviour of wrapping a new message.
The text was updated successfully, but these errors were encountered: