Page MenuHomePhabricator

Get full text of echo notifications
Open, Needs TriagePublic

Description

Request Status: New Request
Request Type: project support request
Related OKRs: iOS FY21-22

Request Title: Get full text of echo notifications

  • Request Description: Echo notification system truncates long notifications at 150 characters. This means we can't show full notifications to users. Long notifications are shown truncated, reducing usefulness of the notification and reducing trust in the notifications overall.

We recognize there may be performance reasons to truncate notifications when making an API request that returns many notifications. While we could remove the character limit for the existing API, another solution would be to have a new simple API - send a request w/ notification revision ID, and (if user is properly authorized) return the entire body text of the notification.

  • Indicate Priority Level: Medium
  • Main Requestors: iOS team (this also improves Android app)
  • Ideal Delivery Date: mid-April 2022
  • Stakeholders: Wikipedia notification users that use the iOS or Android app (especially experienced editors)

Request Documentation

Document TypeRequired?Document/Link
Related PHAB TicketsYes<add link here>
Product One PagerYes<add link here>
Product Requirements Document (PRD)Yes<add link here>
Product RoadmapNo
Product Planning/Business CaseNo
Product BriefNo
Other LinksNoOKR: https://docs.google.com/document/d/1ClZdFuSLCdlPkHppkWAcq3YsWJ2dMahTDqr-gUYOOpo/edit

Event Timeline

The truncation was added in 2013 with rECHO0b1275b9e39b: user talk and mention notification improvement and the requirements document referenced in the commit is http://www.mediawiki.org/wiki/Echo_%28Notifications%29/Feature_requirements#Improved_Notification_Structure. That page references character limits of 140 or 255 (somehow 150 was chosen). It's possible it's as simple as removing the DEFAULT_SNIPPET_LENGTH constant (and where it's used) or increasing its length to some arbitrary large limit. I don't know of any broader implications of that, though.

@DMburugu plans to follow up with @MattCleinman to discuss further.

I’m not quite sure who tagged Growth on that ticket, I just see it as Restricted Application. I appreciate your work digging in, @kostajh. I’m also not sure the broader implications of removing that limit. 😅

As this isn’t presently blocking our work, for now I’m going to let it go through the Foundational Technology Requests and see what comes of this.

I’m not quite sure who tagged Growth on that ticket

Herald in H26.