Feature request: Smaller codes

[NotNite]

Coming from croc, I'm not used to the very big codes. As an example, a croc code I just got is 5615-eclipse-select-liter. sendme codes are, in comparison, very large. Even when specifying --ticket-type id (as indicated in the help menu by being the smallest ticket type), the receive code is over 100 characters long.

croc codes use a randomly generated PIN and a forked version of mnemonicode (which seems to have a Rust port on crates.io). croc codes are easy to read out over the phone because they're mostly words, but I will always have to provide the sendme ticket over text. I'm not entirely sure what data is contained in the ticket, but would it be possible to represent easier?

[matheus23]

This comes with trade-offs.
Sendme tickets contain quite a bit of information (making them somewhat large), sometimes including IP addresses, making it possible to send files in the local network, even if you don't have internet (though at that point, getting the ticket across form device A to device B is questionable).

The way magic-wormhole (and likely croc, too) solve this is via rendezvous servers and PAKEs. We don't run that kind of infrastructure at the moment, and we probably won't do so soon.

[peacefulotter]

I am surprised there isn't an option for a short and easy-to-type id. I would like to share files between two computers on the same private network which makes writing the whole ticket id complicated. Maybe a special flag (for local network file sharing only?) could allow for shorter ids ?
Thanks!

[matheus23]

On the local network, it would technically be possible to enable the LocalNetworkDiscovery service and in conjunction with user-data added to the discovery service publishing, you allow for a sort of "listening for sendme instances on your network" flow on the receiving end.

[peacefulotter]

Thanks for your comment!
Are you saying this as an explanation on how to solve this for my use case or is it rather a thought about how this could be implemented in sendme?
I really feel like something like this should be implemented in sendme out of the box

[matheus23]

This is something that can be implemented in sendme, or someone who wants to write a tool like sendme.

FWIW, sendme keeps being stuck between being a single-file demo/example for how to write things using iroh.
I think we'd be happy to take contributions like that though (and have accepted contributions to improve UX in the past).