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

Handle resolution WP/URL #1124

Closed
NiceGuy2065 opened this issue Jan 5, 2025 · 2 comments
Closed

Handle resolution WP/URL #1124

NiceGuy2065 opened this issue Jan 5, 2025 · 2 comments
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". Needs triage [Pri] High [Status] Escalated to Product Ambassadors [Type] Bug Something isn't working

Comments

@NiceGuy2065
Copy link

Quick summary

It seems to me that the plugin does not resolve Fediverse handles anymore and refers to the http-URL when sending a reply to a comment received via AP while entering the Fediverse handle in a WP comment does resolve fine. It might be a local configuration issue, haven't seen other examples in the wild other than related to my own blog.

Reference on WordPress: https://nexxtpress.de/mediathekperlen/2025/01/05/daniel-radcliffe-jungle-2017-zdf-mediathek/#comment-1883
Reference on Mastodon: https://mastodon.social/@rhrwllnrtr/113775321422132860

Steps to reproduce

  1. Reply to a Fediverse comment
  2. Check comment on a fediverse instance, i.e. Mastodon.social.

What you expected to happen

The original handle (Fediverse ID) should be send.

What actually happened

The URL to the original poster's profile is sent (as a html link)

Impact

One

Available workarounds?

No but the platform is still usable

Logs or notes

No response

Copy link

github-actions bot commented Jan 5, 2025

Support References

This comment is automatically generated. Please do not edit it.

  • 2017-zen

@github-actions github-actions bot added the Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". label Jan 5, 2025
@NiceGuy2065
Copy link
Author

NiceGuy2065 commented Jan 8, 2025

I closed the issue, because it's already analyzed in #1135, so #1124 became redundant.

Many thanks @jeherve !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Customer Report Issues or PRs that were reported via Happiness. Previously known as "Happiness Request". Needs triage [Pri] High [Status] Escalated to Product Ambassadors [Type] Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant