Product / source
Artifact, source snapshot, build or format question.
blue@… ↗Contact / two doors, routed by subject
Send the signal
with a useful subject.
Use blue@okcompressor.com for products, licensing, funding and collaboration. green@okcompressor.com is reserved for private research and technical transfer.
blue@okcompressor.com [product]
blue@okcompressor.com [licensing]
blue@okcompressor.com [funding]
blue@okcompressor.com [collaboration]
green@okcompressor.com [private research]
routing intent → subject line
Routes
Pick the closest door.
No account system, ticket portal or CRM required.
Licensing
Commercial use, integration, resale, internal deployment or source rights.
blue@… ↗Funding
Fund a benchmark, drop, research sprint or defined experiment.
blue@… ↗Collaboration
Independent reproduction, technical question or joint experiment.
blue@… ↗Research
Private dossier, deeper architecture or scoped research transfer.
green@… ↗Public fallback
The organization profile keeps a Proton contact trail if the custom-domain route is ever unavailable.
Check current GitHub profile ↗Minimum useful first message
Three lines beat a pitch deck.
What are you trying to test or buy? Which artifact/research area? What outcome would make the thread useful?