So, they need to be encrypted, then converted into base64 before sending to the address. However, the messages will likely be decrypted at the other end, and will very likely be stored unencrypted. Then you can chop up the file into multiple messages. Due to the limitation of BM sending up to 256KB messages, your file can be no bigger than 256K, unless you setup a striped RAID array. Intrigued, I started thinking about this. The random blurb ensures the server always hears you." If you send multiple LIST commands to the server in a short period of time the Bitmessage client see's your requests as duplicate messages and ignores them. When sending the LIST command, type some random blurb into the message. REMOVE - Removes a file saved to your account. e.g "UPDATE a567f My even more top secret file" The new_file_name is optional and is only used to rename your file.
#Bitmessage echo server update
UPDATE - Update an existing file saved to your account. e.g "NEW my top secret file", put the contents of your file into the message body. LIST - Lists all the files you currently have saved to your account.
You are authenticated via the address you send from, so be sure to keep it safe.
"You send commands to the service via messages, the message subject is used to tell the server what you want to do. When you send 'help' to the address, you get the following information: No doubt should you call into question a faceless storage provider, but I thought I would play around with it.
For instructions please send a message to BM-2cUqBbiJhTCQsTeocfocNP5WCRcH28saPU with the subject 'help'." While hanging out on the "privacy" channel on Bitmessage, someone sent the following:
0 kommentar(er)
