You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to use this package to transfer my tweets to Bluesky using the original tweet date and time. Any interest in making createdAt an argument to bs_post, with a default?:
bs_post(..., createdAt = bs_created_at())
The text was updated successfully, but these errors were encountered:
This would be very easy to add. My reason for not doing so is that posts are intended to be timed in a "true" manner. Posts with a createdAt date very different from their indexedAt date (the time that the server first sees the post) are flagged with a warning.
That said, I'm happy to add the argument if it's helpful with that warning in mind.
I agree with the archived flag that Bluesky adds on backdated posts. In fact, I think that flag makes it safe to add this argument, i.e., it's a supported feature of Bluesky.
The ability to import tweets into Bluesky with their original post date would be incredibly helpful.
I want to use this package to transfer my tweets to Bluesky using the original tweet date and time. Any interest in making
createdAt
an argument tobs_post
, with a default?:bs_post(..., createdAt = bs_created_at())
The text was updated successfully, but these errors were encountered: