jaxxed

joined 10 months ago
[–] jaxxed@lemmy.world 1 points 6 hours ago

I'll still get around to opening up an issue

[–] jaxxed@lemmy.world 2 points 7 hours ago

Any hope at restoring peace and sanity, we'll take.

[–] jaxxed@lemmy.world 3 points 2 days ago

The other day I realized that there is a lot of cardboard in my brand name boots. Not the sole so I can't feel the cobblestones.

[–] jaxxed@lemmy.world 3 points 2 days ago (1 children)

I don't think that Israelis en masse want a a war with Iran, but Bibi appears to.

[–] jaxxed@lemmy.world 1 points 5 days ago* (last edited 5 days ago) (2 children)

Hey, sorry for taking a long time, but I am farting around with the pinentry option now.

I don't have screens, but I wanted to point out a few scenarios that are challenging with fuzzel:

  1. as I was trying to describe before, the ability to write accompanying text is pretty important, as you need to be able to describe what gpg key is to be unlocked, and typically a string like "Enter PIN for Richard Nixon nobody@trickydicky.gov" is used - which is too long for fuzzel (https://gorbe.io/posts/gnupg/pinentry/documentation/#set-the-descriptive-text-to-display) Also keep in mind the error scenario, which adds even more copy (https://gorbe.io/posts/gnupg/pinentry/documentation/#set-the-error-text). Lastly there is a "set window title" feature, which is perhaps not important for us (https://gorbe.io/posts/gnupg/pinentry/documentation/#set-the-button-texts)
  2. There are message scenarios which are difficult to place with fuzzel. Even if I wanted to just fail out some scenarios like reties, I would want some "notification", and would probably like to have fuzzel also used for that in order to keep the UI consistend across use cases. (https://gorbe.io/posts/gnupg/pinentry/documentation/#message-box)
  3. There are cases where pinentry is expected to set copy for buttons for OK and Cancel and "Do not do this", IIRC to get internationalization. I think that these are less important. (https://gorbe.io/posts/gnupg/pinentry/documentation/#set-the-button-texts)

(ping @markstos@lemmy.world )

https://github.com/james-nesbitt/pinentry-fuzzel is a first try, shamelessly stealing everything from https://github.com/zamlz/pinentry-rofi/blob/main/src/pinentry-rofi.sh

[–] jaxxed@lemmy.world 9 points 1 week ago

This is an example of why erosion of public confidence in democratic institutions is a critical problem. We want to be able to follow an institutional opinion on this topic, but our trust has been eroded by another topic, which makes it less trustworthy.

[–] jaxxed@lemmy.world 3 points 1 week ago

I didn't know about Cypress CA, but probably should have expected such.

[–] jaxxed@lemmy.world 10 points 1 week ago (4 children)

Do you mean "Cyprus" the country, or Cypress the type of tree?

[–] jaxxed@lemmy.world 1 points 1 week ago

In most linux tiling managers it is used with directional keys to nav windows and desktops.

[–] jaxxed@lemmy.world 9 points 2 weeks ago (4 children)

Is emacs considered a modal editor?

[–] jaxxed@lemmy.world 2 points 2 weeks ago (3 children)

Let me try for a pinentry script over the weekend first, to see how the placeholder looks.

 

I have an inventory of hosts, and from them, one of the tasks should choose a leader by running a command on each until one of the machines produces an expected output (json value.)

I want some code to run on that leader to initialize it, and then I want some of the other roles to delegate some tasks to that leader.

Not sure how to do this?

Should I use dynamic inventory to analyze a group of hosts, and create a new group (can you run built_in.command in dynamic inventory? Should I write a role task that runs the identifying command on each host, capturing the result globally if it returns what I want (but then running on each host even if I have found my leader?)

view more: next ›