Remove Korean language from DigiByte .org

[DGBNOOB]

Greetings everyone,
I was contacted by Rudy Bouwman via DM, asking if I could create a pull request to remove the Korean language from DigiByte .org due to regulatory implications in the listing process with big Korean exchanges.

I'm raising the issue since I'm not 100% sure if this is a simple deletion of the ko/index.html or if it requires additional changes to the website such as in the language menu. I have DM'd DennisPitallano who has helped us in the past with making improvements to the website to ask if it's just a simple deletion or if it requires additional changes to the website. I will also consult with AI to get its feedback. Any comments, questions or concerns?

[DGBNOOB]

Grok response to my question about deleting the ko/index.html:

The ko/index.html file (and likely the entire /ko/ directory) serves as the Korean-language version of the DigiByte website, which is still live and accessible at https://digibyte.org/ko/. It provides a full translation promoting the blockchain, DGB coin, features like DigiAssets and Digi-ID, security aspects, and community involvement.

Why this request might be happening

South Korean crypto regulations are notoriously strict, especially around investor protection, market manipulation prevention, and compliance for virtual assets. Major Korean exchanges (e.g., Upbit, Bithumb, Coinone) have historically delisted many altcoins — sometimes in large batches — due to:

• Low liquidity/volume
• Insufficient utility or risk of price manipulation
• Failure to meet internal or regulatory standards

DigiByte (DGB) has never been a top-tier listed asset on the biggest Korean exchanges in recent years, and the community has faced challenges with listings/delisting on various platforms globally (e.g., past incidents like Poloniex). Having an official Korean site could theoretically be interpreted by regulators or exchanges as actively targeting or soliciting Korean users/investors, which might raise compliance flags — especially if the project lacks formal registration, local presence, or specific disclosures required under laws like the Virtual Asset User Protection Act.

Some global exchanges (Binance, Bybit, BitMEX) have preemptively removed Korean language support from their platforms ahead of regulatory deadlines to avoid being seen as offering services to Korean residents without proper licensing.

Can you simply delete the ko/index.html file?

No, probably not — a simple deletion of just that one file is unlikely to be sufficient or clean.

The DigiByte website (hosted from the GitHub repo DigiByte-Core/DigiByte.org) is multilingual, with directories for various languages (e.g., /id/ for Indonesian, /pl/ for Polish, /af/ for Afrikaans, etc.). Removing only ko/index.html would likely:

• Leave broken links or navigation (e.g., if the language switcher still points to /ko/)
• Cause 404 errors for users who land there via bookmarks, search engines, or old links
• Leave other Korean files (CSS, JS, images, or sub-pages) orphaned

Recommended changes for a proper removal

To fully and cleanly remove the Korean version, you should aim for something like this (ideally discuss/confirm with the DigiByte-Core team or maintainers first):

1. Delete the entire /ko/ directory (not just index.html)
   → This removes all Korean-specific assets.

2. Update the language selector / navigation
   → Remove any Korean option from the dropdown/menu on the main site (likely in the header or footer HTML/JS).
   → Check files like index.html, header partials, or any JS handling language switching.

3. Handle redirects (optional but recommended)
   → Add a 301 redirect from /ko/* → / (English/default) or a notice page explaining the change. This preserves SEO and user experience.
   → Or simply let it 404 if the goal is complete removal.

4. Check for any hardcoded Korean references
   → Search the repo for strings like "ko", "Korean", "한국어", or links to /ko/.

5. Update any sitemap.xml or robots.txt if they reference /ko/.

6. Test thoroughly after the changes
   → Ensure the site loads correctly in other languages, no broken assets, and the language switcher behaves.

If this is a sensitive regulatory-driven change, it would be wise to:

• Get explicit approval/confirmation from core maintainers or the person who requested it
• Document the reason in the PR description (without revealing sensitive details if needed)
• Possibly add a comment in the code/commit message like "Remove Korean localization due to regulatory considerations"

If you're unsure about the repo structure, check the live site and GitHub repo (DigiByte-Core/DigiByte.org) to see how languages are implemented — it's a static HTML site, so changes are straightforward but need to be comprehensive to avoid half-measures.

Let me know if you share more context (like the exact repo or who requested it), and I can refine this further!

[ycagel]

Thanks for putting this together @DGBNOOB. Can you create a PR?

[DGBNOOB]

Thanks for putting this together @DGBNOOB. Can you create a PR?

I contacted Dennis for assistance and I'm waiting for a response, however, it is a little more technical than anything I've done in my limited experience. I created a Todo list and can give it a try if Dennis isn't available.

Here is a clear, step-by-step TODO list to make the removal of the Korean language version (/ko/) from the DigiByte.org website sufficient, clean, and professional. This assumes the site is a static HTML-based setup (with separate directories per language), as is standard for this repo.

TODO List: Remove Korean Localization (/ko/)

1. Confirm approval & document the reason

   • Get explicit written confirmation from the requester (or DigiByte-Core maintainers) to proceed.
   • In the PR description, clearly state the purpose (e.g., "Remove Korean language support due to regulatory considerations related to major exchanges and listings in South Korea"). Keep it factual and non-sensitive.
   • (Optional) Add a commit message note or code comment referencing the regulatory context.

2. Delete the entire /ko/ directory

   • Remove the full /ko/ folder and all its contents (index.html + any sub-files like CSS, JS, images, or additional pages if they exist).
   • Do not delete just index.html — partial removal will leave broken links or 404s on assets.

3. Remove Korean from the language selector / menu

   • Locate the language switcher code (likely in the header, footer, or a shared partial — check files like index.html, any header.html, langmenu/ directory files, or JS files handling language switching).
   • Delete or comment out the Korean option (e.g., any <option value="ko">한국어</option>, link like <a href="/ko/">한국어</a>, or JS array entry for "ko").
   • Ensure the selector still works correctly for remaining languages.

4. Search & clean up any remaining Korean references

   • Use repo-wide search (GitHub search or git grep) for terms like:
     • "ko"
     • "Korean"
     • "한국어"
     • "/ko/"
   • Remove or update any hardcoded links, meta tags, or references found outside the /ko/ folder.

5. Handle redirects (strongly recommended)

   • Add a 301 permanent redirect from /ko/ (and /ko/*) → root / (English default) or to a notice page.
     • If the site is deployed via GitHub Pages, add this to a _redirects file (Netlify-style) or use a meta refresh/JavaScript redirect as fallback.
     • Example in _redirects:

       /ko/*    /    301
       /ko      /    301
       

   • This preserves SEO, prevents bad user experience, and avoids crawl errors.

6. Update sitemap.xml (if present)

   • Remove any <url> entries that start with https://digibyte.org/ko/.
   • If the sitemap is auto-generated, regenerate it after deletion (or manually edit).

7. Check robots.txt (minor, but good practice)

   • Ensure no lingering Allow: /ko/ or similar lines exist (unlikely, but verify).

8. Test the changes locally & on a preview

   • Build/serve the site locally (e.g., using a simple HTTP server or GitHub Pages preview).
   • Verify:
     • Language selector no longer shows Korean.
     • No broken links or console errors related to /ko/.
     • Visiting /ko/ (or old bookmarks) redirects properly or 404s cleanly (depending on your choice).
     • All other languages still function normally.

9. Create the Pull Request

   • Title: e.g., "Remove Korean language support (/ko/) due to regulatory considerations"
   • Description: Summarize the changes, list the steps taken, mention testing, and explain the reason briefly.
   • Request review from maintainers or the person who asked for this.
   • (Optional) Add "BREAKING: Korean version removed" if you want to flag it.

10. Post-merge follow-up (after approval)

    • Monitor for 1–2 weeks: Check Google Search Console (if you have access) for crawl errors on /ko/ paths.
    • If any community members ask about the Korean site, point to the regulatory explanation (if appropriate).

This approach ensures the change is thorough, avoids half-broken states, and minimizes user impact. If you discover the language switcher is handled differently (e.g., via JS config file), adjust step 3 accordingly.

Let me know once you've started or if you run into repo-specific quirks — happy to refine!