jaxxed

You can advocate for hungry people after eating a meal. You can advocate fornsex worker rights even if you are a virgin.

You can’t tell people you are “working class” if you’re rich. You can’t advocate for punishing day people while pretending to be straight.

It is not complicated.

It is in no way conclusive, as the operation was not very feasible to perform from a small yacht. It is more likely that a proper naval team was involved.

I know how to multiply by zero

Ah yes, a move to be more like Clinton, and Biden. They had strong campaign ideas.

I thought that LORA was optimized for low data throughput? Running WIFI over such a link would suck.

I’ll still get around to opening up an issue

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.

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

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

It might be nice to have a way of giving more context, which is what the message option was good for in rofi. Not knocking it though, I am a happy fuzzel user.

The script is there in the post, but I haven’t tried it yet. It would be nice if fuzzel had a message option, like rofi, so that key information could be displayed in the passphrases request; that s is what pinentry-rofi uses.

Has anyone done any greenhouse automation with hass? I don’t know where to start.

It used to be considered a security risk back in the day. Maybe it just a security “unknown”

I should have read the article first – passphrases and pinentry are here

Fuzzel is great. I only wish it had a pinentry option.

Have you tried niri yet? What about river?

Kent developed for like 10 years on his own. He’s just having a hard time learning how to play with others, and deal with large priority cycles. He just needs to know that sometime his changes will get pushed to the next cycle.

I use a poopy nano https://ploopy.co/nano-trackball/

Perhaps not useful, but my linux machine doesn’t sleep unless I disconnect my ploopy trackball first, exhibiting the same symptoms.

I am not sure that businesses like Boeing make risk decisions like that. You would think that they would only take a risk that they know they can win, but many times they take a risk and hope that the dice land their way. This would be lives at risk, with calculations assessed by people with very poor records with such assessments.