One Time Share (1ts.dev)

GameRaccoon

The service allows sending self-destructing messages.

It can be useful when you want to share content-sensitive information in a conversation with someone, and you don't want this information to persist there after being read.

Disclaimer

Disclaimer of Warranties and Limitation of Liability

This service is provided "as is" and without warranties of any kind, either express or implied. No representations or warranties are made regarding the operation or availability of the service, the accuracy or completeness of the information provided herein, or the reliability of any service descriptions. The contents of this page are not legally binding and may be subject to change without notice.

The provider expressly disclaims any and all liability for damages arising out of or in connection with the use of this service or the information provided, including but not limited to direct, indirect, incidental, punitive, and consequential damages. Users assume full responsibility for their use of the service and any information obtained through it.

The important parts first

Don't send any context to your secret information in your 1ts's

OK:

Hi, can you unlock my PC so I can remote-login into it, my login is User123, my pin is here: [link to 1ts]

Not OK:

Hi, can you unlock my PC so I can remote-login into it, I've sent you all the instructions how to do it here: [link to 1ts]

Why:

There's always a possibility that this service can be hacked. If that happens, the hackers will be left with only contents of the 1ts's in the flight without any information about who sent it, who is supposed to read it, and where it can be applied. You don't want to give them this information by including it in 1ts.

If you have a separate trusted end-to-end encrypted messenger with your recipient, prefer using it over 1ts

The example above but even better:

Hi, can you unlock my PC so I can remote-login into it, my login is User123, I've sent you my pin in our encrypted chat in Telegram.

Unfortunately, this is not always possible, that's why this service exists.

Telegram is used as an example, you choose what you trust.

Use end-to-end encrypted communication to send any information you don't want to disclose publicly

Not only relevant to 1ts, but if you care about your information, use end-to-end encrypted messengers. Most messengers and means of online communication as of 2024 are not end-to-end encrypted.

If your conversation is not end-to-end encrypted it means that all your messages can be read by 3rd parties and be leaked to malicious users. Not only that, but the messages can be modified without you knowing (e.g. in theory while your message is being delivered someone who has access to your conversation can intercept the 1ts link, read it, create a new link, and give it to your recipient).

Never share your private keys or their recovery codes over the internet, nor with 1ts, nor even with end-to-end encrypted messengers.

Also avoid sharing access passwords and similar information, if you absolutely need to do so, change them quickly after.

What can this server do?

The messages that you send over 1ts.dev can be accessed by the link only once
The message is removed from the server even before it receives the recipient
The message will be removed after the time you've chosen if it is not read by that time
After the message is removed the service doesn't track whether the message even existed

What information does the service store?

The message (assume it is stored in plain text)
The expiry time of the message
The token associated with the message

What are the limitations?

Since the message is removed from the server before sending it to the recipient, delivery is not guaranteed. If the recipient has a poor internet connection, the message may not be delivered and will need to be resent.
The service does not make a distinction between read, expired, and non-existing messages
Only text messages are supported
To avoid spam and overuse, there is a strict limit on how often messages can be created, and this limit is shared among all users
The size of the message is restricted
The maximum possible message storage time is 30 days

One Time Share - 1ts.dev