| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| users:offline_messaging [2015/09/07 20:57] – [Pseudo-Offline messaging vs. Fully Offline messaging] cmotc | users:offline_messaging [2021/03/29 15:27] (current) – [Other currently available options] update ToxProxy link skeleton1 |
|---|
| ==== Pseudo-Offline messaging vs. Fully Offline messaging ==== | ==== Pseudo-Offline messaging vs. Fully Offline messaging ==== |
| |
| Some clients([[clients:qtox]] [[clients:antox]] [[clients:isotoxin]] [[clients:toxy]]) implement pseudo-offline messaging. Pseudo-offline messaging essentially schedules a message to be sent to a friend the next time you are both online. While this can be convenient at times, it still requires both clients to be online at the same time for one to message the other. Fully offline, asynchronous messages would not carry this requirement. | Most clients ([[clients:qtox|qTox]], [[clients:utox|µTox]], [[clients:toxygen|Toxygen]], [[clients:antox|Antox]], and [[:clients#features|others]]) implement pseudo-offline messaging. Pseudo-offline messaging essentially schedules a message to be sent to a friend the next time you are both online. While this can be convenient at times, it still requires both clients to be online at the same time for one to message the other. Fully offline, asynchronous messages would not carry this requirement. |
| |
| Pseudo-offline messages work similarly to the [[https://developer.pidgin.im/wiki/Using%20Pidgin#WhatisaBuddyPounce| "Pounce" feature some people may be familiar with from Pidgin]]. | Pseudo-offline messages work similarly to the [[https://developer.pidgin.im/wiki/Using%20Pidgin#WhatisaBuddyPounce| "Pounce" feature some people may be familiar with from Pidgin]]. More about [[http://gnewsense.org/Documentation/Pidgin#Buddy_Pounce| Pounce]]. |
| |
| ==== Using Pseudo-Offline messaging ==== | ==== Using Pseudo-Offline messaging ==== |
| |
| ==== Other currently available options ==== | ==== Other currently available options ==== |
| Some people have reported setting up computers they trust to relay messages to them when they are offline, often using single-board computers and ratox or toxbot to set up the relay. It is up to you to decide if these are appropriate for your needs. | Some people have reported setting up computers they trust to relay messages to them when they are offline, often using single-board computers and Ratox or ToxBot to set up the relay. It is up to you to decide if these are appropriate for your needs. Each of them have their own risks and benefits. |
| |
| | - [[https://github.com/zoff99/ToxProxy| ToxProxy]] by zoff99, made for [[clients:trifa|TRIfA]]. Example setup:((https://github.com/zoff99/ToxBlinkenwall_raspi_lite_image/blob/toxproxy_01/README.md)). |
| | - [[https://github.com/Astonex/MessageRelay| Astonex's Tox Message Relay]] Relays messages on behalf of a another Tox user. Only supports one client at a time and requires you to run it on a computer which is always online. |
| | - [[https://github.com/toxmail/toxmail| Toxmail's email to Tox Messaging Bridge]] Lets you create or authorize "Supernodes" to deliver messages on your behalf when you're offline, but compromises on decentralization. |
| | - Scripting an interface to Tox using Ratox could allow you to home-brew a message relay[[http://git.2f30.org/ratox-nuggets/tree/rat-autoanswer| Ratox AutoAnswer Nugget]] [[http://git.2f30.org/ratox-nuggets/tree/rat-autoapprove| Ratox AutoApprove Nugget]] [[http://git.2f30.org/ratox-nuggets/tree/rat-echo| Ratox Echo Script]] |
| | |
| | ==== Relationship to Multiple Devices Proposal ==== |
| | Some of the Multiple Devices proposals can also help users either simulate or achieve partial offline messaging. The multiple devices proposals can be found [[https://github.com/Quoturnix/ProjectTox-Core/wiki/Multiple-devices| here]]. |
| ==== Details ==== | ==== Details ==== |
| |
