TMCIT student (Japan) seeking assistance: Paper ID rejection on Student Developer Pack

[ghost]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Verification Help & Guidance

Hi everyone,

Hi there,

I am writing to seek assistance regarding my Student Developer Pack application, which has been rejected 4 times now.

I am a student at Tokyo Metropolitan College of Industrial Technology (TMCIT) in Japan. Despite using my official school email address (.ac.jp) and matching my profile information, the automated system keeps failing to verify my status.

The issues I'm facing:

Paper-based ID: My student ID is paper-based, not a plastic card. The in-browser camera system has difficulty reading Japanese characters (Kanji) from this type of ID due to low image quality and potential glare.

Japanese Characters: My name on the ID is in Kanji. I have updated my GitHub billing and profile name to match the ID exactly (both in Kanji and English), but the system still errors with "name mismatch."

In-browser Camera Constraints: Since I am required to use the webcam, I cannot upload a high-quality scan or photo, leading to continuous verification failures.

I've already tried clearing my cache, re-logging, and matching my profile information perfectly, but the automated system continues to reject me. Since the manual support ticket system is currently unavailable, I am posting here hoping a moderator can help me with a manual review.

My GitHub Username: Neutron42
School: Tokyo Metropolitan College of Industrial Technology (TMCIT)

Attached is the screenshot of my latest rejection. I can provide the physical student ID for manual verification.

Best regards,

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[ghost]

thank you very much. Ill try.