Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

createdAt as an argument to bs_post? #21

Open
grasshoppermouse opened this issue Dec 20, 2024 · 2 comments
Open

createdAt as an argument to bs_post? #21

grasshoppermouse opened this issue Dec 20, 2024 · 2 comments

Comments

@grasshoppermouse
Copy link

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())

@christopherkenny
Copy link
Owner

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.

@grasshoppermouse
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants