Well, then it should just be a very small mushroom-shaped carpet

Yeah, it’s like the copy of the copy from multiplicity.

I know…how to prompt?

Oh, he knows. It’s his middle name.

Gross absolutely

This is the way

That is…somethin’

RSS is really great, always has been. And many sites support RSS, not just for a main feed but also sub topic feeds.

I use NetNewsWire on iOS

I was in Vienna in late October and the people were marching in the streets to protest against the far right winning party. Glad it paid off for them in the end!

I’d vote for AOC in a heart beat, she’s awesome

Every time you speak it’s like an episode of Columbo

And McDonald’s is his fuel

Yeah, true. But that’s cool. Having choice like that is great!

But I suppose that’s the issue. Trying to keep signup simple to help drive user engagement. How much do you try to wrap someone’s head around such nuanced differences, and when do you say “just join me on my instance”?

I’m on three different instances and the sort by All-hot feed is nearly identical.

I’m not on Beehaw or Hexbear, but those instances make it pretty well known they block a lot of other instances.

I can taste the lower prices!

It’d be an improvement for sure

Very strange, but glad you worked it out!

I’ll keep this thread in mind if I ever run into something similar.

Well, dig is available also of course, but nearly all distros still include nslookup despite it getting deprecated. I like the simplicity of its interactive mode.

Host is also really great with more human-readable output.

Don’t get me wrong, when things are getting hairy, you’re going to make a lot of use of dig. I just find that most troubleshooting can be taken care of a lot simpler with host or nslookup.

nslookup is available on macOS and most Linux distros as well (and very helpful indeed).

Yeah if you can dig a record and received a response it’s not a routing issue.

But aren’t you on the same subnet as your DNS server? There’s no routing happening if you’re on the same subnet which I was assuming.

Even through dig defaults to outputting A records when no other options are specified, I would use the A option anyway just in case:

dig @192.168.0.249 study.lan A

If you use “ping study.lan” do you see it output the A record IP address in the first line of output?

Did you try using nslookup as I described?