# send (10-send.com) People say send when they want something to go somewhere. They might send a letter, send help, or send a message to a friend. It means to cause something to move from here to there. ## What a model may hear - transmit data (networking, sockets, APIs): assume the user wants to emit bytes over a TCP or UDP connection, possibly with specific flags or buffer sizes - blockchain transaction (cryptocurrency, smart contracts): initiate a transfer of tokens or assets, often requiring gas fees, wallet addresses, and confirmation logic - message queue dispatch (distributed systems, async messaging): place an event or job onto a queue or topic for downstream consumers - email or SMS dispatch (notification services): trigger a templated message through a provider like SendGrid or Twilio - Unix signal emission (operating systems, process management): deliver a signal such as SIGTERM or SIGKILL to a process ID ## Where people and models part ways - Says: "Send this to everyone." Means: Share this document with my team. May be taken as: The model may broadcast to all connected sockets or all subscribers in a system, potentially leaking data. Say instead: "Email this document to everyone on my team." - Says: "Send me the report when it's ready." Means: Notify me or deliver the finished report. May be taken as: The model may try to push data to an unspecified endpoint or fail because no destination protocol is defined. Say instead: "Message me in this chat when the report is ready, or email it to my address." - Says: "Send it back." Means: Return this item or reply to this message. May be taken as: The model may interpret as a network response or HTTP return code, or loop a message indefinitely. Say instead: "Reply to this message" - Says: "Just send it." Means: Go ahead and transmit or submit this now. May be taken as: The model may execute a raw socket send with default parameters, skipping validation or user confirmation. Say instead: "Submit this form now, or transmit this file using the default settings." ## Tips - Always say how you want something sent: email, message, upload, or post. - Name the recipient clearly; 'send' alone does not tell the model where. - If you mean reply or respond, say that instead of send. - Specify the format if it matters: send as PDF, send as text. - In technical contexts, say 'transfer the file' or 'emit the event' to avoid ambiguity. ## Often confused with - emit: technical broadcast, often to listeners or logs - dispatch: queued or scheduled sending, not immediate - transfer: move ownership or copy between systems - push: server-initiated delivery to a client - post: publish to a public or semi-public location - forward: pass along something received from another source