* Send Staging (#447)
* - js for in-page tabs
- send category early drafts of articles
- send images
* fix scrolling on tab
* send web vault
* mobile image
* redone 'receive send' article
* send from browser ext & mobile
* send work
* improvements to 'about'
* send additions
* so much send
* lotsa send
* all send all the time
* ain't nothin but a send thang
* cli
* send cli
* simple cli sends in /create-send/
* simple disable & delete in /send-lifespan/
* send desktop screenshots
* send final cleanup
* cli final cleanup
* send edits
* fix
* send final touches
* fixed links & non-send updates
* new import message documentation, several import articles condensed to use tabs, U2F support for Edge, excluded domains article, remove in innacurate note on emergency accesss
* Firefox Attachment Workflow + Date Picker for custom timestamps
* safari attach file Send req
* excluded domains addition
* fix tab titles
* release notes
* unlock articles
* link to status feed
* small typos
* test
* updated release notes
* lastpass article form fill rewrites
* import to org & personal clarifications
* send self-hosting, safari web extension edits, and release notes
* Add regex example to "Match detection for URIs" that is not broken
I find it important that examples actually follow best practices. The
current regex one is not. `^https://.*google\.com$` is an improper regex
(as already pointed out because it also matches `malicious-site.com`)
that is only there to show the weaknesses of regular expressions for
this use case. I find such an example very good for this purpose but
there should also be a "good example" that complements it.
I found such a "good example" that I hope is more useful and has no
unwanted loopholes.
* Change wording from bad/good to unsafe/safe in regex match detection
* Update uri-match-detection.md
Co-authored-by: fred_the_tech_writer <69817454+fschillingeriv@users.noreply.github.com>
-typo in Getting Started Web Vault
- Browser Ext Biometrics note on "Allow access to file URLS"
- Correct "Deauthorize Session" button name
- Org FAQ on preventing self-registration w/ env variable
I find it important that examples actually follow best practices. The
current regex does not escaping dots in URIs when writing regex is a
mistake that is often made, even by advanced regex people. I think this
comes from the way we humans look at URIs. Dots are so common in there,
aren’t they? Yes, but we write proper regular expressions here, not
something in between.
Updates: #41
Alternative: #158
Replaces: #160
* - Few Typos
- New 2FA FAQ Item
- Corrected recommendation in /forgot-master-password/
- Added 'Delete a Collection' section to /create-collections/
- Fix recommendation for 2FA Recovery Code
- Update plans flowchart & text
- Added 2019-2020 plans comparison tables
- Added linking to feature table in /about-bitwarden-plans/
- Added search example for org
- Added additional information about removing and org user to
/managing-users/ and /delete-your-account/
* typo fix
- A typo
- Clarification on yubico validation URLs
- Post-release updates to "About Bitwarden Plans"
- Improvements to Lost Two Step Device vs. Recovery Code articles
