erre

There's pretty active communities on other instances too:

• https://lemmy.world/c/nfl
• https://lemmy.ml/c/nfl

You could subscribe to those.

I requested one for r/soccer. The community here is small and I don't have the time to spend all day on Twitter looking for the latest news to post it while it grows. So this bot fetches latest posts from there and I crosspost to a Lemmy community of real users on the rare occasion that it's interesting to me. The bot lives in its own instance so it isn't spamming any real user community.

Listen to this person, this is the temporary solution.

Hilariously posted in the wrong thread I believe. 😄

Same here, forced me out of my lurker shell. 😅

I feel like I'm missing something here. I've never needed to worry about docker container IPs.

I wonder why you want them to have fixed IPs. I guess I want to understand the problem it would solve.

If all you want to do is have the other containers use the pihole as DNS.. they'd already be doing so if the server is using it as the DNS server.

At worst you'd need to provide

dns:
  - <server IP where pihole is>

property to the services.

I liked Connect! But I didn't stick with it because ~~it doesn't collapse comments~~.

EDIT: Turns out it does collapse comments by long-pressing them. 😅

Gonna give it another chance.

I'm using Thunder. It's pretty stable but not feature complete.

Same and on thunder too now 🫠

So glad it's not just me. I've had to use another client because Jerboa is useless due to this bug.

Or Telegram, unless you're a confirmed terrorist.

I keep it simple and cheap, Zest or Irish Spring.