My mother has never watched The Matrix.

I provided various contexts about themes since it is a 25-year old movie, but then suggested that she actually do so. Like, really. Out of a thousand action movies, watch that one.

It’s a classic now, imo. On the list of movies that proper movie enthusiasts can’t not have watched.

While you are absolutely correct that would save packets and time, there are way too many packets lost in HF radio for something like that, unfortunately. It is not uncommon to miss over other, every third packet. Even the small ones. Something like ardop or Vara does their own acks and systems for error correction, which work fine. But there is zero chance you can proceed with our them and still keep the connection going. I'm fact, on HF, sudden complete signal drop is common.

I'm also in no way going to redo the packet stack at this point, lol.

“He chooses all the wrong hills to die on”

No, I'm not using async tcp, I'm not sure what you mean. There is no networking stack other than connecting to the tnc on an ip, and the webserver front end. Everything is over ham radio packets which are not duplex.

Any hardware tnc modem that uses KISS is compatible. It is up to the user to try.

Thanks for your input, but I think we are on different wavelengths so to speak as to what HAMSTR is.

Nope.

I wanted to start with max compatibility with kiss tnc.

That way you can use a million hardware tnc, direwolf, uz7ho, and a bunch of other kiss tnc software packages

Ardop still uses ax25, but I think needs a plain kiss frame not ax25 pre formatted.

Likely HAMSTR could be modified if setting is ardop, then it skips or modifies the packets.

I'm not interested in this feature currently however, as I have lots of other features to work. If you want to give it a rip, go for it.

If you want more speed, ardop wouldn't fix that on HF likely. Maybe a bit, and yes, more robustness though. Personally, I don't like winlink using ardop, never works well for me on HF

After I add some needed features, I will be switching gears towards fldigi instead.

I daresay one of the very elements in Ukraine that was cynically used by the CIA to cause trouble this time around given a large number of decedents there.

You should grab that choker chain & pull hard on it. 😂

Get a clue, when another ethnic group starts shelling the ethnic group who is the same as the one right across the border, they are coming across, they always do.

The last time that idiocy happened it started WW2...

Technically I’m am using fx25 in addition, at the tic level which adds a few bytes to each size. Plus kiss framing.

The time includes delays, relay processing, sending, sending ac’s, waiting for connection ack, getting ready, and on and on. There is lots of back and forth. Plus I have control data and flow bytes for missing packet checking. There is crc checksum data 8bytes as well.

Do you mean the packets themselves? I think each packet has around 50 bytes of ‘overhead’. If that helps?

But I would need to check my tic log to verify, I don’t recall exactly.

I see that you only repeat the otanist propaganda, I have nothing more to talk to you.

I repeat, less nostr and more go to war if you think that is your problem.

I don't give a damn about my neighbor, I only look out for my family, if you care so much don't be a hypocrite and enlist, I have given you the means to do so.

It’s more like 10. Connection, ack, ready, ready ack, request to send, ready, then the 2 packets for the actual note, with ack in between, final done, done ack, disconnect. Make sense?

It is not simplistic, it is the living representation of hypocrisy.

Isn't it true that you don't play poker the same way if instead of gambling money you gamble chickpeas?

How easy it is to support a war when those who die are not your children.

also, the content more often the length that causes more packets, not the rest of the structure. sure, you could save a half a packet with extreme conservation, which may help not spllover into another packet perhaps. there is almost always 2 packets for writing a note, and often the 2nd is not full, but saving 50 or 60 bytes likely won't do the trick.

I am sending compressed Json, yes. A full signed note.

I have no idea what your math means, or where it came from?

A timestamp is not 4 bytes, the kind is not 1, it is a min of 7(kind:1;).

content: "Hello Nostr"; would be 23 bytes.

Uncompressed of course.

Each ax25 packet has a max of 240 bytes, including the kiss framing, header, my coding and the message parts. The limit is adjustable, but I use 200 bytes on content for smaller packets.

Not sure what side channel means?

How many bytes? Are you putting the full message as the payload? Are there side channels available?