WordPress / Mastodon “Display Name not valid”

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Matthias Pfefferle

    (@pfefferle)

    7 months, 3 weeks ago

    Hey @nexxtpress 👋

    it seems that Mastodon has issues with “number only” tags. Can you remove the “2013” tag and re-test it?

    If it will work after removing the tag, I will report it to Mastodon. I think it is fine to not support numerical tags, but Mastodon should simply ignore them instead of blocking the content completely.

    Thread Starter nexxtpress

    (@nexxtpress)

    7 months, 3 weeks ago

    Thanks for looking into this, @pfefferle. That has been a reasonable advice. To my regret, it doesn’t make a difference. All my posts do have a numeric tag (year), some work and resolve in the search, some don’t. I also had sanitization in mind, like accents, apostrophes, umlauts etc… but that doesn’t seem to have any impact either.

    Plugin Author Matthias Pfefferle

    (@pfefferle)

    7 months, 2 weeks ago

    I had another look and found special chars in the name attributes of the Hashtags. I am working on a fix to properly encode hashtags!

    https://github.com/Automattic/wordpress-activitypub/pull/2352

    Thanks for the report!

    Thread Starter nexxtpress

    (@nexxtpress)

    7 months, 2 weeks ago

    That’s truly fascinating stuff! Thanks a lot @pfefferle!

    Thread Starter nexxtpress

    (@nexxtpress)

    7 months, 2 weeks ago

    Edit: Message deleted.

    • This reply was modified 7 months, 2 weeks ago by nexxtpress.
    • This reply was modified 7 months, 2 weeks ago by nexxtpress.
    Plugin Author Matthias Pfefferle

    (@pfefferle)

    7 months, 2 weeks ago

    That is weird! You are using Note as federation object, and a Note does not have a title, but adds the title to the content instead and content should not have any issues with commas!?

    Maybe Mastodon tries to somehow handle the first paragraph as headline because of the <b>.

    Thread Starter nexxtpress

    (@nexxtpress)

    7 months, 2 weeks ago

    Ah.. you’re too fast for me @pfefferle. I just deleted my previous message… as it has turned out wrong… it’s not the “,” (comma) causing it. I found posts without it, which show the same behaviour.

    • This reply was modified 7 months, 2 weeks ago by nexxtpress.
    Thread Starter nexxtpress

    (@nexxtpress)

    4 months, 3 weeks ago

    So this weird behavior is – after 3 new versions of the plugin – still appearing. In the meanwhile, I have tested this on two Mastodon instances, but as well on Hubzilla and Misskey. It seems the problem throwing this error seems indeed only to exist on Mastodon, so probably I should better ask their devs to have a look?

    Thread Starter nexxtpress

    (@nexxtpress)

    4 months ago

    You deserve the follow-up: Mastodon-Dev has fixed and closed the issue! https://github.com/mastodon/mastodon/issues/37602

    Plugin Author Matthias Pfefferle

    (@pfefferle)

    4 months ago

    Thanks for taking care, filing the issue and letting me know about the outcome!!! 🙌

Viewing 10 replies - 1 through 10 (of 10 total)

You must be logged in to reply to this topic.

Tags