Replies to mas.to posts using "Reply from..." bookmarklet not posting

[IAmDarthMole]

Quick summary

I thought I had seen two of my replies to a mas.to post appear, albeit greatly delayed, but I have must have been mistaken because now I can't find them.

Every reply I make to a mas.to post using the "Reply from..." bookmarklet never appears. It works great on maston.social, toot.social, and mstd.party posts but not mas.to posts.

I have also tried posting with a post topic and without and neither work.
I have posted without tags and with tags and neither worked.

Maybe there is a setting in Mastodon that mas.to has turned on or off?

Steps to reproduce

1. Go to a mas.to post.
2. Click the "Reply from ..." bookmarklet
3. Loads new post in WordPress.
4. Type post title and reply.
5. Publish

What you expected to happen

The post should appear in the replies/comments section of the post in question.

What actually happened

It never appears :(

Impact

All

Available workarounds?

No but the platform is still usable

Logs or notes

No response

[pfefferle]

@IAmDarthMole can you give us an example URL you tried?

...and please be a bit more conservative with your "Impact" definition. "All" means, that nothing works and all WordPress/Fediverse instances are affected, so our toolings and reportings are raising a lot of alarms ☺️

[IAmDarthMole]

@IAmDarthMole can you give us an example URL you tried?

Link examples are:

• https://mas.to/@snazzyq/113575926507194823 (my Reply Post: https://madmolelabs.com/2024/fake-it/)
• https://mas.to/@snazzyq/113723458041696316 (my Reply Post: https://madmolelabs.com/2024/does-that-include-you/)
• https://mas.to/@kims/113768006557097839 (my First Reply Post: https://madmolelabs.com/2025/champions/ | my Second Reply Post: https://madmolelabs.com/2025/champions-2/)
• https://mas.to/@BirdPerHour/113768095850318838 (my Reply Post: https://madmolelabs.com/2025/cute-burb/)
• https://mas.to/@BirdPerHour/113763848561373243 (my Reply Post: https://madmolelabs.com/2025/467/)

...and please be a bit more conservative with your "Impact" definition. "All" means, that nothing works and all WordPress/Fediverse instances are affected, so our toolings and reportings are raising a lot of alarms ☺️

My apologies! I didn't realize the "zomg it's all broken" status I was selecting. I'll definitely be more conservative!

[obenland]

Is this particular to using the bookmarklet? Inserting the block manually works as expected?

I was unable to reproduce with mas.to/@kims/113768006557097839, my reply was posted as expected, albeit using the block directly.

[obenland]

Hm, same with https://mas.to/@BirdPerHour/113763848561373243, using the bookmarklet.

[IAmDarthMole]

Is this particular to using the bookmarklet? Inserting the block manually works as expected?

I was unable to reproduce with mas.to/@kims/113768006557097839, my reply was posted as expected, albeit using the block directly.

I'm not sure what you mean by inserting the block manually? Can you please elaborate?

Sorry about that, I figured it out after posting this reply. No, even manually adding the block in the post doesn't work.

Hm, same with https://mas.to/@BirdPerHour/113763848561373243, using the bookmarklet.

So you were able to use the bookmarklet to make the bird post?

Also, quick question regarding your webfinger setup; did you have to make any files manually or did the plugin work as intended out of the box? I'm not sure if they are related but I know because of my webhost I had to manually create the webfinger file so I'm curious if you are able to post as intended that there is something unique with my setup.

I also noticed that your replies contain a URL back to your blog's original post but mine (the successful ones) don't.

Follow-Up: Does the wordpress theme being used matter at all when it comes to sending replies?

Thank you!

[obenland]

Correct, I used the bookmarklet to make the bird post. I didn't have to change any files manually after I installed the plugin, it worked out of the box.

I don't think the theme should matter, but the manual webfinger file might be an indicator. @pfefferle is currently AFK, but he might have further troubleshooting steps when he gets back.

[IAmDarthMole]

Understood and thank you for the clarification.

I'm not sure if it is relevant, but if the theme doesn't matter what about post "Format" ?

I just find it strange that, at least for me, mas.to has been the only service (unless you are also able to reply to Threads posts) that I'm unable to reply to.

Additionally, I just noticed that a reply I just posted on a https://nileane.fr/ Mastodon post was formatted similar to the way yours was on the mas.to posts (with a link back to your original post). That functionality, for me, has only appeared on the recent https://nileane.fr/ post and none of the others (ie: mastodon.social or toot.community).

[IAmDarthMole]

Additionally, if I try to follow my WordPress + ActivityPub profile with my mas.to profile, it can find my WP+AP profile and I can select "Follow" but my mas.to profile doesn't show up in the WP+AP follower list. After refreshing the mas.to page the "Follow" button now states "Cancel Follow" instead of "Unfollow".

[IAmDarthMole]

Update: I have changed hosters and am still experiencing the same issues (the reply to mas.to posts not appearing and also the inability to follow my wordpress profile from a mas.to account).

I also tried to use post a reply manually with the block.

I also confirmed I'm unable to follow my wordpress profile with a pixelfed.social account.

I deactivated and reactivated the AP and Webfinger plugins and then deactivated, deleted and then reinstalled and activated in two different steps.

I'm able to post to the fediverse thought he behavior is sporadic at best as described in my reply to (#1177 ).

[IAmDarthMole]

So I'm going to close this. It took several tries and only migrating the bare minimum but I was able to get everything working as intended. The above simply seems to be an issue with SiteGround not allowing the custom .well-known routes as the plugin requires, not a bug. Thank you!