Robin Linus
Robin Linus
It's a good idea to report this confusing feature to Microsoft
@rmpasswd do you have a link?
@Bellisario looks like the fix made it worse, no?
@svenjacobs looks like the server breaks whenever there is too much load. Also someone keeps trying to DoS the Snapdrop server. We started to port it to Rust for better...
Maybe [Snapdrop for Android](https://play.google.com/store/apps/details?id=com.fmsys.snapdrop) causes a problem because there are about a Million clients permanently connecting to the server and thus dos'ing it?
> @RobinLinus, what do you think about these changes? Sorry that it took me so long to respond to your PR. This is a tough decision. I've been thinking about...
Another question: How do we communicate this feature to users? Maybe that previous sketch using a dialog is better UX? I remember I said we should always minimize the number...
Looks like this is already quite close to the Snapdrop server. https://github.com/seanmonstar/warp/blob/master/examples/websockets_chat.rs Is someone here familiar with warp and knows how to get a client's ip? I dug into it...
Thank you @crapStone ! [tokio-tungstenite](https://github.com/snapview/tokio-tungstenite) looks like a good alternative to warp. Looks like you [can simply access the client's IP](https://stackoverflow.com/questions/63024046/how-to-access-the-peer-ip-address-in-tokio-tungstenite-0-10) from the TcpStream object.