add multibyte FAQ, reference awesome-meshcore community projects, minor changes#2172
add multibyte FAQ, reference awesome-meshcore community projects, minor changes#2172liamcottle merged 3 commits intomeshcore-dev:mainfrom
Conversation
LitBomb
commented
Mar 27, 2026
LitBomb
commented
- Add multi byte FAQ
- Reword amped radio output setting numbers
- Clarify repeater ID collision including distance, supercede docs: clarify first byte key collision behavior in FAQ #1478
- Reference awesome meshcore for community projects. Supercede docs/faq.md: Removed explicit listing of external projects, and instead refer to ressources which specialise on that. #1893
…or changes - Add multi byte FAQ - Reword amped radio output setting numbers - Clarify repeater ID collision including distance, supercede meshcore-dev#1478 - Reference awesome meshcore for community projects. Supercede meshcore-dev#1893
|
According to the diff, you introduce a bogous table of contents item - [⚠️ **WARNING: Set these values at your own risk. Incorrect power settings can permanently damage your radio hardware.**](#️-warning-set-these-values-at-your-own-risk-incorrect-power-settings-can-permanently-damage-your-radio-hardware)(Anyway, naming this "frequently asked questions" seems a bit confusing, most of the things more seem like "further information and ressources", not questions that emipirically were asked often, or?) |
|
I am not seeing the bogus table content item that you are referring. this is what I see in the diff: 
And the table renders fine: This is definitely a frequently asked question on multiple discord servers, and that is why I added it a couple months ago. More and more users are getting these 1W+ radios and they often ask what dbm to set to for these radios. It is just further information rand resources to you if you don't have one of these 1W+ radios. It is a question every new 1W+ radio owner ask the first time they need to configure one for MeshCore. |
When I open https://github.com/meshcore-dev/MeshCore/pull/2172/changes#diff-57cdcc6b6701a7ce3b3a8f8c0366e0e611e6fb1a1b8dd7cd29e3263b3e064c8bR84#:~:text=**WARNING:, i.e. the same as when in this pull request #2172 click on "Files Changed", then 
I did not mean that specific item, but the general information that is in the Regards! |
Fixed an extra TOC jump link inserted by VSCode Markdown All in One VS Code extension.
|
with the line number this time, I see the markdown all in one VSCode extension inserted an extra jump link to the table of content. I have fixed that in this PR. Thanks for the report! |
If you generate the table of contents automatically (you actually did change the whole table of content, because you indented all entries one time -- why?), I think the whole document should have a rule that no stuff is within it that can confuse automatic generators. I think here heading-formatting is misused to highlight some text. Thiis is wrong semantics. i think if Regards! |
|
FYI, the new docs site automatically generates it's own table of contents. |
|
@liamcottle can you approve and merge this PR? It is ready to go. Thanks! |
Have reviewed, looks good. There's a bunch of spelling mistakes and grammar issues though. I won't comment on each of those. Please revise and then I can merge :) |
fixed typos and refined multibyte sections.
|
I found and fixed 2 typos. I reworded some sentences in the multibyte sections. I always use double spaces after a period between two sentences. :) Thanks! |
|
I always use double spaces after a period between two
sentences. :)
i think what @liamcottle wants here is one consistent way of doing
it in the repository, regardless of personal typographic aesthetics.
If some people use double spaces, other single spaces, then it becomes
a typographic mess.
|
|
I wrote 99% of this faq for over a year now since the start of the project. There are double spaces between every two sentences in this faq. Double spaces is the consistent way in this faq so far. |
3 participants
