You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would enable access to the secret only when the sender literally has the tab open in fugacious where they entered it.
The data would never be stored in fugacious' database, and it would never be transmitted through fugacious' servers. Instead, fugacious' JavaScript would be responsible for establishing the peer-to-peer connection and transferring the data directly from the sender to the receiver.
This is a non-trivial feature addition, but I wanted to get it down while I was thinking about it. Because it eliminates the need for a database (at the cost of forcing transfers to be mostly synchronous/coordinated) it might even be a better fit for another tinier app entirely. But if this project is interested in it, it'd be a fun, useful feature.
The text was updated successfully, but these errors were encountered:
This would enable access to the secret only when the sender literally has the tab open in fugacious where they entered it.
The data would never be stored in fugacious' database, and it would never be transmitted through fugacious' servers. Instead, fugacious' JavaScript would be responsible for establishing the peer-to-peer connection and transferring the data directly from the sender to the receiver.
This is a non-trivial feature addition, but I wanted to get it down while I was thinking about it. Because it eliminates the need for a database (at the cost of forcing transfers to be mostly synchronous/coordinated) it might even be a better fit for another tinier app entirely. But if this project is interested in it, it'd be a fun, useful feature.
The text was updated successfully, but these errors were encountered: