Page MenuHomePhabricator

[lib] Stop shimming Blob-hosted multimedia messages
AcceptedPublic

Authored by bartek on Thu, Nov 7, 3:37 AM.
Tags
None
Referenced Files
F3178023: D13888.diff
Fri, Nov 8, 12:43 AM
F3177994: D13888.id45693.diff
Fri, Nov 8, 12:37 AM
F3169458: D13888.id45655.diff
Thu, Nov 7, 11:30 AM
F3168660: D13888.id.diff
Thu, Nov 7, 7:22 AM
F3167973: D13888.diff
Thu, Nov 7, 4:53 AM
F3167964: D13888.diff
Thu, Nov 7, 4:51 AM
F3167332: D13888.id45655.diff
Thu, Nov 7, 3:51 AM
F3167326: D13888.id.diff
Thu, Nov 7, 3:51 AM
Subscribers

Details

Summary

Points 3a and 3b from ENG-6459.

Test Plan

Replaced next code version constant with a past version and verified that robotext no longer appears and blob-hosted media messages are displayed.

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

bartek held this revision as a draft.
bartek edited the test plan for this revision. (Show Details)
lib/shared/messages/multimedia-message-spec.js
256

We've never been shimming these for web. This code was written before we started versioning web

This revision is now accepted and ready to land.Thu, Nov 7, 5:29 AM

First, give this comment a read.

Basically my thinking is that if we want to have clients immediately start sending blob-hosted multimedia in thin threads, we should also stop shimming blob-hosted multimedia on the keyserver for recent codeVersions.

Rather than only unshimming for the most recent codeVersions, we should instead unshim for any codeVersion that can support blob-hosted multimedia.

This revision is now accepted and ready to land.Thu, Nov 7, 7:22 PM
lib/shared/messages/multimedia-message-spec.js
256 ↗(On Diff #45693)

Please replace NEXT_CODE_VERSION here with the earliest codeVersion that supports blob-hosted multimedia. (Would be helpful to explain your reasoning)