We're initially launching this to the Comm staff community so we can test things out.
Details
Details
I loaded up my local dev environment, which has a mirrored copy of the Comm community.
- I uploaded an encrypted photo to the Comm community root from native and confirmed it appeared as encrypted in the MySQL database (has an encryptionKey)
- I uploaded an encrypted photo to the Comm dev team channel from native and confirmed it appeared as encrypted in the MySQL database (has an encryptionKey)
- I confirmed I was able to view the encrypted media from the web
- I confirmed I was able to view the encrypted media from native, but only after the initial upload
- I confirmed that after logging out and back in on native, the encrypted media upload appears as a messageTypes.UNSUPPORTED ("ashoat sent a photo")
- I uploaded a photo to a different chat and confirmed it was NOT encrypted
- I uploaded a photo to the Comm dev team channel from the web and confirmed it was NOT encrypted
- I sent a message with a photo and a video to the Comm community root from native and confirmed it resulted in three encrypted uploads in the MySQL database (all had an encryptionKey, one was for the thumbnail) and that the video was viewable from the web
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Branch
- ashoat/media
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
| lib/shared/thread-utils.js | ||
|---|---|---|
| 1565 | The community root will not have anything set for the community field, so we need to special-case that. I introduced this utility function in the hopes that it will make this nuance less likely to be missed in the future | |
Comment Actions
Would be great to test a MULTIMEDIA message with eg 1 video, 1 video + 1 image, 2 videos in addition to photos mentioned in Test Plan (if not done already)