Contact UnixTime
Contact UnixTime
Bring a concrete problem.
Share the system, control, deployment, or research decision that is blocked. Clear context produces a more useful response than a broad request for help.
Messages are reviewed directly by Hassan El-Masri. There is no automated sales queue.
Send a brief
Describe the decision you need to make.
Include the environment, constraints, expected outcome, and any evidence or implementation already available.
- contact@unixtime.com
- Phone
- +1 415 705 9169
- Response
- Direct review; complex requests may need a follow-up
US SMS program
Registration in progressGet UnixTime Dispatch by text.
Recurring UnixTime technical article and publication updates for US mobile numbers.
- Region
- US mobile numbers only
- Frequency
- Varies, up to 4 messages per month
- Controls
- Reply STOP to unsubscribe or HELP for help
SMS enrollment is not open while carrier campaign registration and the consent service are being completed. No mobile number or SMS consent is collected here.
What makes a useful brief
Reduce the back-and-forth.
Four pieces of context make technical inquiries easier to evaluate.
- 01
Current state
Name the platform, version, architecture, control scope, and what has already been attempted.
- 02
Decision
State the choice, review, implementation, or research question that needs an answer.
- 03
Constraints
Include trust boundaries, regulatory scope, operational ownership, timing, and acceptable risk.
- 04
Evidence
Link public references or describe redacted logs, diagrams, tests, and decisions that support the request.
Before you write
The answer may already be published.
Use the field notes for implementation depth or the research base for structured controls, risks, and evidence.