Alex Kirk

Currently there are these buttons for a post by a friend:

• Reblog will create a draft of a reblog so that you can edit it before you post it.
• Share is only there if you have the Post Collection plugin installed.
• Boost will send an Announce via ActivityPub, it is not otherwise reflected (there is a log where you can verify that it was sent).
• Reaction sends a Like via ActivityPub, same as for boost.
• Comments will load the comments via ActivityPub and you can respond. This will happen as a comment to the private post type.

The automatically generated status posts are created as a draft indeed.

Oh, thanks for pointing that out. I need to update the FAQ. At the top of the README it says:

Since version 2.6.0, no users will be created for subscriptions.

Regarding the posts, you are correct, they are stored as posts. It won’t notify users of your email subscription plugin though, since the incoming posts are created under a non-public post type (they are created as “publish” but this is just the somewhat unfortunate naming of the “not draft” post status for WordPress).

Having a faq or wiki page about this might also be helpful.

Indeed, I’ll add that, thank you very much for the suggestion!

Do you mean a link that you send through a Mastodon app and what the people clicking the link (to your own WordPress) see? Is this via ActivityPub? Because then the problem would rather be in the ActivityPub plugin, see this issue on the ActivityPub Github repo: WordPress sometimes returns JSON to a Webbrowser instead of the HTML page. #580

Thank you for the feedback! Could you elaborate on this or maybe even file a bug at https://github.com/akirk/enable-mastodon-apps/issues so that it can be fixed? Who are the people who see raw XML and where do they see that?

Just keep in mind this plugin has to do a lot of mimicking of Mastodon internals and conforming to expectations of apps that expect to talk to the “real” Mastodon. While there is a documentation about their API, many apps make some assumptions that are true for the Mastodon implementation but are defined more loosely in the spec.

This makes it unfornately prone to what can be experienced as “buggy” behavior when it’s trying to achieve something that Mastodon didn’t plan for when they implemented their API.

Easiest through the UI at wp-admin/options-general.php?page=enable-mastodon-apps&tab=registered-apps and then click on the app name to see the tokens.

Or use wp cli with wp term list mastoapi-at (don’t forget to specify the --url parameter when you talk to a multisite).

They are stored as taxonomy items. What are you trying to do with them?

Thanks for the report. I hope I fixed it with https://github.com/akirk/friends/pull/354 and released it in 2.9.8.

Thanks for reporting! I fixed it in https://github.com/akirk/friends/pull/353, shipped in version 2.9.7.

Hi! This is currently by design. The /friends/ page will only show posts from friends (i.e. the friend_post_cache post type).

The exception being the status feed (/friends/type/status/) which is intended to be modeled more along the lines of other social feeds that do show your own posts. The thinking was also that in that format (with usually limited length of the posts) the feed can still feel balanced with not one author outweighing all others.

What’s your reasoning behind seeing your own posts in the /friends/ page? I am not opposed to making it possible but I am curious about the scenario you were expecting.

Hi!

As per the Mastodon API, you first need to register an app. You could POST to the /api/v1/apps API endpoint but since you’ll later want to create an access token anyway, you might also want to do this from PHP:

$app_name = 'feditest';
$redirect_uri = 'https://feditest.org/'; // you can also use: Enable_Mastodon_Apps\Mastodon_OAuth::OOB_REDIRECT_URI;
$scopes = 'read write follow push';
$website = 'https://feditest.org/';
$app = Enable_Mastodon_Apps\Mastodon_App::save( $app_name, array( $redirect_uri ), $scopes, $website );

You can then use this snippet to create an access token:

$desired_token = '123';
$user_id = 1;
$oauth = new Enable_Mastodon_Apps\Mastodon_OAuth();
$oauth->get_token_storage()->setAccessToken( $desired_token, $app->get_client_id(), $user_id, time() + HOUR_IN_SECONDS, $app->get_scopes() );

This is a simplified version of what is done in the unit tests.

Hope this helps! Let me know if you need anything else to get things working with Feditest, I think it’s a great initiative!

Thanks for reporting. I am wondering what kind of data you see in the options table, do you still have screenshots or similar?

On the one hand, when uninstalling (from the UI, not just deleting the plugin files), an uninstall routine should delete everything associated with the plugin.

On the other hand, the plugin doesn’t add a lot of data in the options table in the first place, so maybe something broke in an unexpected way.

In any case it would be helpful to understand how you were able to fix it in the end so that I hope I can backtrace to what happened. Thanks!

• This reply was modified 1 month, 1 week ago by Alex Kirk.

Thanks for bringing this up, I believe this exposes one more angle of how currently the blog user is implemented in the ActivityPub plugin (fyi @pfefferle).

As you noticed, this is currently not possible. Actually, the ActivityPub plugin would need to extend the Enable Mastodon Plugin to allow this. I filed https://github.com/Automattic/wordpress-activitypub/issues/800 to suggest that.

I think it’d be helpful to understand in what ways you’d like to manage the blog user and what behavior you’d expect? This is how I see it but I’d be curious for your view:

In the timeline, I suppose you’d see all posts of your blog (this is already the case when you log in with any blog user).

You could view your blog followers, but you could not follow anybody.

There are profile editing capabilities coming (see https://github.com/akirk/enable-mastodon-apps/pull/157), so this could also allow editing the blog user. I think it’s worth a discussion that through this you could accidentally rename your blog when you only wanted to rename your blog profile.

I currently don’t see how you could reply via ActivityPub (which I think is one of the motivations to actually create a real blog user?), I am not sure how to prevent this except through generating an error message.

I am marking this as “not a support question” / “resolved” since this is ActivityPub plugin territory.

Indeed, sorry about that! I’ll remove that again, it looks like this was a brief effort at CloudFest that didn’t go anywhere. I intend to release it in a new version tomorrow.

In the course of implementing https://github.com/akirk/friends/pull/312, I also fixed a bug that might also manifest in what you are experiencing. I have released 2.9.2 some days ago with that bugfix, could you take a look if you still experience it? Thanks!

Thank you for the great review! You might be also interested in the Enable Mastodon Apps plugin which allow you to use (mobile) Mastodon apps to interact with your setup.