Update: Turns out I was too concerned. The manual actually says to use the top rack.

UPDATE: Stopping and reopening the app fixes this. It needs to actually stop though, you can't just switch apps and reopen. Either wait for it to close on its own or force stop. I did not try the main menu method as suggested, though. It may be easier.

Cross posted from: https://feddit.uk/post/20469568

For context, "no hello website" is a term I'm using to describe websites like https://nohello.com/. The gist is that it's trying to get people to no only say "hello" but also ask whatever it is they're trying to ask you about. (In my opinion, this can even extend to generic conversations, like "hey, how are you?" versus just "hey!")

The problem is, many of these websites seem pretty rude. At the end of the day, I don't think it's possible to make one not seem at least a little rude because telling someone not to say hello just sounds rude lol. That said, even my favorite one (https://nohello.club/) has phrases like

1. Unnecessary pleasantries
2. useless phrase like "Hello"

But I like it because it doesn't say things like this that the original http://nohello.com/ says

please be prepared to be ignored if you only say "Hello!".

Some context, I'm not necessarily looking to include this on any corporate messaging app bio (unless it was 100% polite, which as I said I don't find possible). But the closer to something that polite, the more useful I think it is.

There is a promotion for new hams to get the Explorer QRZ-1 for $22 (along with some software and a cable, but I already have a cable and CHIRP is free). It is normally $60. Is this a good deal? Is this radio worthwhile?

I currently have a Baofeng UV-5R (Baofeng #1 radio! Wooo!) and a TIDRADIO TD-H3. I haven't really made contacts with either and don't know how well they perform. Is this QRZ-1 substantially better?

How poorly would an attic mounted antenna perform? Obviously worse than something outside, I'm guessing, but how much worse?

My office has one of those "side attics." It has a half sized door. Mounting a long antenna in there is very tempting because of how much easier it would be than doing anything outside. It's on the second floor as well.

I hear that a lot but, how bad is it really? Does it affect you (if you use Debian)? Aren't there ways to install newer versions of most things that actually matter?

Two different webs very close together. I like to imagine they'd chat about their days of they could!

Link to a (frustratingly) deleted question on Stack Overflow. Text and image copied below incase you don't have the ability to see it. (Not sure why the image shows multiple times.)

Is there any way to more granularly control IntelliJ IDEA's inspections' "Nullability and data flow problems" option "Treat non-annotated members and parameters as @Nullable"? Preferably for unboxing specifically?

I am aware I can use a variety of @Nullable annotations in a variety of places in the code to make the warnings appear. That's not always an option as the place the boxed primitives are coming from may be other libraries you don't have control over. (Imagine if the Holder record below was from a different project.) I included other examples below to illustrate my point.

public class Sample {

    private final Boolean value;

    public Sample(Boolean value) {
        this.value = value;
    }

    private boolean isValue() {
        return value; // I would like a warning here
    }

    private static Boolean boxedTrue() {
        return true;
    }

    private static boolean unboxedTrue() {
        return boxedTrue(); // No warning here, but that's understandable since never null
    }

    private static Boolean boxedNull() {
        return null;
    }
    
    private static boolean unboxedNull() {
        return boxedNull(); // Only warning in the file (by default)
        // "Unboxing of 'boxedNull()' may produce 'NullPointerException'
    }

    public record Holder(Boolean value) {}

    public boolean openHolder(Holder holder) {
        return holder.value(); // I would like a warning here
    }
}

When "Treat non-annotated members and parameters as @Nullable" is enabled, the following gives warnings. While that makes sense given the name of the option, there is code like this literally everywhere. It adds hundreds of warnings to my project. I'm trying to find more granular choices.

    public static ZonedDateTime timeStuff(LocalDateTime localDateTime, ZoneId zoneId) {
        return localDateTime.atZone(zoneId); // I do not want warnings for this
    }

I see that the Java Class Library has JetBrains annotations despite not actually being annotated. Is there perhaps some way to add these automatically to libraries if there is no better way to control the inspection?

Seeing that Uncle Bob is making a new version of Clean Code I decided to try and find this article about the original.