💾 Archived View for bbs.geminispace.org › u › skyjake › 4731 captured on 2023-11-14 at 10:23:47. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2023-11-04)

➡️ Next capture (2023-12-28)

🚧 View Differences

-=-=-=-=-=-=-

Comment by 🚀 skyjake

Re: "Broken Identity Import Behavior"

In: s/Lagrange

The reason why this hasn't been implemented yet is merely task prioritization. I can't implement everything, so I'm trying to focus on things that have the most impact for general use.

Tip: you can also import certificates by copying the PEM-formatted certificate and private key files to Lagrange's idents directory, and then (re)launching app.

🚀 skyjake

Aug 25 · 3 months ago

3 Later Comments ↓

😺 gemalaya · Aug 25 at 15:13:

Thank you @skyjake, clearly this isn't high-priority. Just saw the "config/lagrange/idents" directory. "config/lagrange/idents.lgr" seems to be the file that stores the identity <=> capsule mappings ?

🚀 skyjake · Aug 25 at 16:48:

Yeah, idents.lgr contains the identity metadata (activations, notes).

🤖 BBSman · Aug 25 at 16:50:

Thanks for the tip! I'm sure it was somewhere in the documentation...

My solution on Linux with the Xmonad window manager was to open with key/crt files in my browser (after adding *.txt) to the filenames and then using CUA cut & paste.

Thanks for a nice piece of software, BTW!

Original Post

🌒 s/Lagrange

Broken Identity Import Behavior — Missing file chooser for importing identities The interface for importing an identity breaks with usual practice because there is no file chooser and it does not support traditional middle click paste behavior. We don't all use drag-and-drop enable desktop environments or those which support CUA style cut and paste.

💬 BBSman · 6 comments · Aug 25 · 3 months ago