Worst Possible Airdrop and Wasted Dev Time

[NirajBhattarai]

Description:

I am writing to express my frustration with the airdrop process, which has proven to be an incredibly poor experience and a significant waste of valuable time. The complications and limitations surrounding the SSH key requirements and the validation process are exceedingly cumbersome and have hindered my ability to participate effectively.

Steps to Reproduce:

1. Generate an RSA SSH key as instructed.
2. Attempt to link the key with GitHub and run the provided Docker script.
3. Encounter multiple issues with key recognition and eligibility.

Observed Behavior:

• The script fails to recognize valid SSH keys, despite following all the instructions correctly.
• Additional requirements and constraints (e.g., specific key types and pre-snapshot additions) are not clearly communicated upfront.
• The process demands excessive effort with little to no clear guidance or support.

Expected Behavior:

• A streamlined, straightforward airdrop process that does not require extensive troubleshooting or technical maneuvers.
• Clear, upfront communication about all requirements and constraints.
• Support and documentation to guide through potential issues.
• Simply use OAuth2 to Claim AirDrop Same as StarkNet

Impact:

This process has been a massive waste of time. Instead of focusing on building and contributing to projects, I have spent hours attempting to navigate a convoluted airdrop system. This is not a sustainable or attractive way to onboard developers. If this level of difficulty and inefficiency continues, it will undoubtedly deter many developers from engaging with the platform or participating in future airdrops.

Recommendation:

• Simplify the airdrop process and remove unnecessary barriers.
• Provide clear, comprehensive documentation and support.
• Ensure the system reliably recognizes valid SSH keys and other required credentials.

If this approach to developer engagement and airdrop distribution continues, it will be impossible to onboard and retain developers. The current process is counterproductive and undermines the overall objective of fostering a thriving developer community.

[hems]

My SSH keys on Github are no longer accessible because I used them on an old computer that I no longer have access to.

It would be easier if it were just like StarkNet: Connect to Github via oAuth and sign a message with the wallet or something along those lines.

[NirajBhattarai]

My SSH keys on Github are no longer accessible because I used them on an old computer that I no longer have access to.

It would be easier if it were just like StarkNet: Connect to Github via oAuth and sign a message with the wallet or something along those lines.

They are not bothered on anything. It should have been done with oauth2 to onboard new developers. I don't know who thought of this. This selection from dev was horrible. Good luck for their project