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

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

Open
IAmDarthMole opened this issue Jan 4, 2025 · 2 comments
Open
Labels
Needs triage [Type] Bug Something isn't working

Comments

@IAmDarthMole
Copy link

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
Copy link
Member

@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
Copy link
Author

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

Link examples are:

...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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs triage [Type] Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants