Secret schema on Linux is inconsistent with python, go keyring libraries

[ccope]

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

Unfortunately it doesn't seem like there are predefined schemas for secrets in the freedesktop secretservice backend, other than for network servers. Keytar chose to use account and keyring chose username. The keychain library for go, keybase/go-keychain, also chose username. Setting both fields would allow the libraries to interoperate.

https://github.com/atom/node-keytar/blob/master/src/keytar_posix.cc#L14-L17
https://github.com/jaraco/keyring/blob/master/keyring/backends/SecretService.py#L84-L87

Steps to Reproduce

1. Add a secret with either library.
2. Try to retrieve the secret with the other library.

Expected behavior:
The secret should be returned

Actual behavior:
It fails

Reproduces how often:
100%

Versions

5.0.0-beta.2 (but all are broken)

Additional Information