Skip to content

Improve home server connection guidance#1148

Open
mcfnord wants to merge 2 commits into
jamulussoftware:next-releasefrom
mcfnord:next-release
Open

Improve home server connection guidance#1148
mcfnord wants to merge 2 commits into
jamulussoftware:next-releasefrom
mcfnord:next-release

Conversation

@mcfnord

@mcfnord mcfnord commented Jun 23, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Removes specific bandwidth numbers (10 Mbit/s down / 1 Mbit/s up)
  • Discourages wireless connections for home servers
  • Notes that fiber connections should work well

Test plan

  • Review the changed sentence in wiki/en/Running-a-Server.md for accuracy and tone

🤖 Generated with Claude Code

jrd and others added 2 commits June 23, 2026 17:42
Replace specific bandwidth numbers with clearer practical advice: discourages wireless connections and notes fiber works well.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@mcfnord

mcfnord commented Jun 23, 2026

Copy link
Copy Markdown
Contributor Author

a little confusing that all those other language files get added

@ignotus666

Copy link
Copy Markdown
Member

a little confusing that all those other language files get added

That shouldn't have happened. I think it's because you're making your PR from the next-release branch of your fork instead of creating a new one.

@mcfnord

mcfnord commented Jun 23, 2026

Copy link
Copy Markdown
Contributor Author

That shouldn't have happened. I think it's because you're making your PR from the next-release branch of your fork instead of creating a new one.

Would you like me to test this theory? If it's true, perhaps we'll update guidance. If we could instead just merge this and go on, I'd prefer doing that this time.

@ignotus666

Copy link
Copy Markdown
Member

A merge involving translatable files into next-release triggers a job (if actions are enabled) that updates the .po files. I had a look at your repo's actions and it's what happened. I don't think there'll be a problem merging this as it is.

Yeah, maybe we should recommend creating a new branch to make PRs from. It's recommended practice in general but no harm in spelling it out.

@mcfnord

mcfnord commented Jun 24, 2026

Copy link
Copy Markdown
Contributor Author

the same changes came in on PR 1150 just now, if that's easier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants