GUIDES · BETSLIP DOCTOR
Does a text conversation guarantee that binary attachments are supported?
No. A conversation that supports text does not automatically support image, document, or other binary attachments. The recorded BSD message adapter accepts text with an empty media list and rejects non-empty media IDs rather than silently treating them as supported. Use only attachment controls that the current product actually offers; do not assume a text-message result confirms that a file was uploaded or delivered.
For BSD community members deciding whether to send a file in a conversation · Updated
Text support does not prove attachment support
The current adapter's message request is defined around text and a media ID list. In the recorded implementation, that list must be empty; a non-empty list fails instead of being accepted as an attachment.
A successful text conversation therefore does not establish that a binary file can be uploaded, stored, opened, or delivered.
Rely only on attachment controls offered by the current client
If your current BSD client visibly provides a supported file-sharing control, follow its displayed limits. The backend README alone does not establish an upload flow, storage policy, file type support, or attachment delivery.
Do not paste a private file into another service or assume that a message body can safely contain its contents.
Check the message result instead of assuming a file went through
A message receipt for text is not proof that a binary attachment was accepted. If the current client does not show an explicit supported attachment and its result, treat file support as unconfirmed.
The recorded source rejects non-empty media IDs, so do not infer that an unsupported file was attached or delivered.
Hypothetical: a text message with a file expectation
Imagine a member sends text in a private conversation and expects a document to travel with it. The recorded adapter only accepts an empty media list, so the text result does not confirm that a document was attached. The member relies on an explicit file control in the current product rather than assuming attachment support.
Related questions
If a text message sends, does that confirm my file was attached?
No. The recorded adapter's text result does not establish binary attachment support or file delivery.
Does the current adapter accept media IDs?
The README specifies an empty media list for message sends and says non-empty media IDs fail rather than being silently dropped.