Erik Moeller
Erik Moeller
Some users find it helpful to be able to watch a short video, to understand what they can do with a piece of software. Let's keep it simple so we...
iframes currently render as broken within the extension preview of a result set. That's because Chrome doesn't support them. We should use webview instead: https://developer.chrome.com/apps/tags/webview This can be done purely...
Retrieve button sometimes is briefly enabled when it shouldn't be, make sure we always check whether the plugin is busy doing stuff.
Kindle highlights have been suggested, since they're very hard to manage currently. Look at https://kindle.amazon.com/your_highlights to see how hard they'd be to scrape
There's really no good reason to do this client-side, and this will get us closer to having a functioning site without JS.
We're duplicating code for rendering sitesets in the extension and the web service right now. Let's turn this into a library so we can use it easily in both.
## Status Ready for review. Can be approved in draft form. ## Description of Changes Part of https://github.com/freedomofpress/securedrop/issues/6520. See https://github.com/freedomofpress/securedrop/issues/6520#issuecomment-1253044091 for context on the switch-over.
Currently we have developer documentation split out in a few places: - https://docs.securedrop.org/, as its own section below the end user documentation - Various GitHub wikis - Various GitHub READMEs...
Currently we have multiple wikis used for dev info: - https://github.com/freedomofpress/securedrop/wiki - https://github.com/freedomofpress/securedrop-client/wiki - https://github.com/freedomofpress/securedrop-workstation/wiki - https://github.com/freedomofpress/securedrop-debian-packaging/wiki (lots of individual pages for diff reviews) I would suggest we consider consolidating...
SecureDrop uses the term codename in two very different ways: - to refer to the Source's codename, which they need in order to log back in through the *Source Interface*;...