mathstodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance for maths people. We have LaTeX rendering in the web interface!

Server stats:

2.7K
active users

#udp

2 posts2 participants0 posts today
Replied in thread

@mimir

This may not fit the 90% same machine situation but:

A few years ago, I looked around for IPC that would reliably scale to more than 1000 connections doing about 1 message/second with a few hundred bytes/message, and with forward secrecy.

The only thing that still fits that is #UDP (not TCP) over #wireguard.

For #rustlang udp means: do it yourself, no existing crates, allow for missing data, and #serde for the udp packet contents.

Continued thread

A friend tested this for 2 VMs with #ubuntu & simply set a #UDP interface in the settings file on #meshchat on each #VM & it works. The spreading factor (SF) 10 #rnode end point meshchat GUI sees the messages arriving at the lora SF 5 rnode via UDP, & vice versa. So the #proxmox setup has both lora SF settings for messaging images & data. The SF 5 rnode is ace for messages of about 60 KB & the SF 10 for longer range text. Both arrive at each VM. reticulum.network/manual/inter
#reticulum is sensational.

reticulum.networkConfiguring Interfaces - Reticulum Network Stack 0.9.4 beta documentation

Just wanted to share some thoughts on #RFC9715 - an #RFC that defines standards on reducing the #DNS issue of IP fragmentation over #UDP. It's not a long read, but a good one for everyone who understands the issues of large UDP responses on the #Internet. A great leap forward to (hopefully) reduce the reflection/amplification #DDoS potential of DNS.

Just today I learned that #Google will share their public DNS resolvers to limit to ~1400 bytes (smaller adjustments expected while figuring out the sweet spot in production). From now on, DNS responses which exceed this limit will have the truncated flag set instructing the client to resolve back to #TCP.

In the actor model, actors need to communicate. On different machines, they need a protocol that supports this, either on LAN or WAN, e.g. UDP. CCE has a UDP server and client module available for qjs on linux, including rpi.

#linux #udp

sha256sum
5578f4afa9a19c5f64fb13e7d5193599a95f4e79d733b512e987a62689f1769a dist-qjs-udp-RPi-0.2.1.tgz

464d2aa65aee4492565bd34d3887e3a9cdf553012c26aca19066906a8096c7cd dist-qjs-udp-x64-0.2.1.tgz

wget cce.citiwise.eu/downloads/dist-qjs-udp-x64-0.2.1.tgz

GitHub - trzsz/trzsz-ssh: trzsz-ssh ( tssh ) is an ssh client designed as a drop-in replacement for the openssh client. It aims to provide complete compatibility with openssh, mirroring all its features, while also offering additional useful features. Such as login prompt, batch login, remember password, automated interaction, trzsz, zmodem(rz/sz), udp mode like mosh, etc. github.com/trzsz/trzsz-ssh #alternative #OpenSource #password #GitHub #prompt #batch #login #mosh #ssh #udp

any application needing to communicate large messages with UDP must implement packetization, retransmission, reordering, etc-- the same things that TCP already implements for us. Many applications that have 'rolled their own TCP' in userspace have ended up with exploitable bugs in them, so it isn't something that should be done without good cause.

also has the issue of traversal: Getting bidirectional communication across a NAT with UDP is not a simple matter. Crossing anything more complicated than a full cone nat requires considerable amounts of special code but without it there will be a many hosts that just can't talk to other peers with UDP.
bitcoin.stackexchange.com/ques

Bitcoin Stack ExchangeCan someone please explain FIBRE to me like I'm 5 and why is it useful?I read the website but they imply you already know why this is valuable. Can someone please illuminate me on this issue?