UX deviation from expected behaviour in 2.0

  • Resolved solarbird

    (@solarbird)


    10 months, 2 weeks ago

    Okay, first, 2.0 IS AMAZING HOLY CROW I just left a review. ??

    But. The actual issue.

    1. Create a post, as wordpress user “A”.
    2. Reply to your own post, from WordPress, as user “A”, tagging in another account that in my case is on Mastodon, user “B”. The reply federates, as expected, as a reply, and the Mastodon account “B” gets a notification. This is amazing and perfect.
    3. Mastodon account “B” replies to the reply in which they were tagged by “A”. The reply federates back, as expected, as a reply, and shows up on the blog. Perfect.
    4. “A” replies to this reply from “B.” The reply gets posted, and it does Federate and is visible to “B”, but “B” does not get a notification.

    UX expectation: As user “A”, I would expect “B” to get a notification, the same as would happen if “B” had started the reply thread. However, “B” did not get one.

    The scenario as described is at the included link, and I didn’t get a notification.

    The page I need help with: [log in to see the link]

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

    (@pfefferle)

    Thanks a lot for your nice review ??

    I will see how I can resolve that issue (it was also already reported on GitHub). I would love to enable notifications without the need to automatically add the @-reply at the beginning of each comment (like what mastodon is doing). I will see how this works out.

    Thread Starter solarbird

    (@solarbird)

    Thanks! And again, thanks for all your work on this too, this is the kind of thing Federation is for and I love to see some of the promise start to be realised. ??

    Plugin Author Matthias Pfefferle

    (@pfefferle)

    2.1.0 should now send notifications.

    Thread Starter solarbird

    (@solarbird)

    Oh, delightful! Thank you ^_^

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘UX deviation from expected behaviour in 2.0’ is closed to new replies.