jaxxed

I have no problems with the action, and I have no problems with his attitude.

The effort to isolate Russia is an acceptable result of the Russian violent invasion. Russian citizens are not to blame for their nation's behaviour, but they do share responsibility.

Removing contributes from the maintainers list is not an extreme action, but it is important as a statement.

As for not feeling the need to defend the Russian citizens, it is nearly righteous for people from nation's that have been bullied by their neighbours.

He went beyond that. "As a Finn, do you really expect me to up in arms to support the Russians..."

Bravo, slow-clap.

US legal mechanisms for internationally enforcing US law are not like domestic enforcement mechanisms. The scenarios that the pro-China folks here are talking about involve a (completely unrealistic) switch in Taiwanese allegiance, that would make US economic enforcement less relevant, and US military enforcement a serious international risk.

There are just a lot of tankies commenting, and you have to be able to interpret their logic.

Do you think China could soak enough capacity to get TSMC to turn away from all of its major customers? Isn't most of their industrial design focused on consumer products with automaton, not high end chips? Are there many high end Chinese chip designs?

The CCP definitely have more say in Chinese tech than the US Government has over US tech. In China, the government controls industry, in the US industry controls government. That said, both are likely backdoored.

You are forgetting that Taiwan has an interest in supporting the U.S. led sanctions.

his community can get pretty toxic, predgidist (sp?!?) but also just hostile and combative.

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

Not in the US, but every LTE home internet provider I've dealt with is just a SIM that you can use in any off the shelf LTE/5G to wifi router setup. Mikrotik options are cheap and can handle simple one-device implementations, and multi-device mesh setups (that require more effort to configure)

I'll still get around to opening up an issue

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.