Can we store the since_id instead of looking it up each time? Now, if the most recent post is deleted, the since_id will be that of the next post, and the more recent toot will be imported again.

Alternatively, but this seems overkill, keep a list of previously imported toot IDs. (This is how we would do it for APIs that don't support a since_id.)

Make it possible to skip statuses based on what's in $status.

Ran into this issue with another plugin where a hook that's supposed to run twicedaily ended up getting triggered many, many times in a row. Due its callback itself spawning multiple WP requests or something and the hook not being “locked” automatically—pretty weird. But, even if this is a rare hosting setup thingy, it would be easy enough to prevent it anyway by, e.g., setting a transient …

Hi there,

Any plans to support favourites?

This wordpress plugin looks awesome. Thanks for sharing it and developing it.

I would have an use case for something a little different, was wondering if it could be done with this plugin or not.

I have a wordpress blog and also post to mastodon. Sometimes, when I do an elaborate thread or a series of toots on a given project, I think "I should archive or do a more elaborate post on my blog". So I'm looking for a tool for that, point to an URL (or a list of URLs), import the content, rework a bit the content then publish.

Any chance that some of the code here could be used for that ? Could this plugin be configurable to the point of addressing the described use case ?

Don't think we'll want to poll for replies as well (and repeat this, because of new replies, etc.), but threads might be worth looking into.

It should be possible to get the in_reply_to_id and use it to look up a "parent" status, and then either explicitly link to it in the post content, or choose to insert the status as a comment rather than a separate post.

This should probably go into a separate, add-on plugin. Or not.

Solved this in Import From Pixelfed recently, do the same here.

Authentication/authorization isn't actually required to read public toots. Make auth optional? (And provide a username field as an alternative? Or use / replace the instance URL field, but let users input an account's timeline/URL instead.)

Either include them in the post content or set them as featured/attached image(s).

Filter $args or $query_string before the API call is made.

Main goal of this plugin is to import toots going forward, not create a complete copy/archive of an existing Mastodon account. With that in mind, it may make sense to only import a single pre-existing toot (to be used in combination with since_id next time the cron job is run).

I.e., if no since_id is found, set the limit to one, otherwise set it to the max value.

To do something (like actually add them to the post content) with images after they've been uploaded.

I'd love to be able to set a Category for the incoming Toots as they currently all just get added to the default Uncategorized category.
It would be easy to find all my Toots then.

There are options to ignore Boosts and Replies , but not Direct Messages.
I've tried deleting the posts created from a Direct Message but it gets recreated too.

Know of at least one occurrence where wp_http_validate_url() returned false where it shouldn't. It's probably safe to remove.

Got everything up and running on my site, but was wondering if this could be improved to support more indieweb ideas/plugins.

For instance, would love to have a syndication link to the original toot. I'm using the Syndication Links plugin and it looks like the only thing needed would be to create an mf2_syndication meta field.

I'm also using Post Kinds and in the past I've used the 'note' kind for microblogging/tweets. Apparently post kinds are just another taxonomy, would it be a case of just listing taxonomies on the settings page and choose one (or multiple) to apply to the imported toots?

Once a day should be OK, no?