rallycall VS ht

Link to Source Code: (https://github.com/chrsstrm/rallycall)

I built a small voice communication portal I'm calling Rally Call [0] that will be submitted to the Digital Ocean/Dev hackathon tomorrow [1]. Rally Call is intended to be a backup group communication portal that can be used in emergencies and situations where use of cell phones is lost. It is essentially a group voicemail-box that runs on Twilio. If you and your group had the foresight to sign up for an account, you could use Rally Call to let others in your group know your status ("Hey everyone, I'm OK. I made it out and am staying at a friend's house") or to organize ("Let's all group up and meet at uncle John's house in two days."). You dial in from any touch tone phone and enter your Crew's Account PIN to access the account where you can listen to or record messages for the group. Only one Crew member needs to register for an account and can share the dial-in number and account PIN with anyone they want in their Crew.

While the project's intent is a backup comm system for emergencies, it could obviously be used for any number of purposes. I still have a couple things to button up before submitting, but it's mostly done and should be a solid MVP by this time tomorrow.

[0] - https://github.com/chrsstrm/rallycall

No need to use curl, make HTTP requests great again with https://github.com/ducaale/xh

Except when you actually enjoy things being fast. For example, HTTPie easily adds 0.5-1s delay to every request because it's written in Python, especially on the first invocation. xh (https://github.com/ducaale/xh), on the other hand, starts immediately because it's written in Rust. I very much like this trend.

HTTPie is great and was a big improvement for me over cURL.

However, I ended up switching to xh[1] as it's significantly faster and I prefer its output.

https://github.com/ducaale/xh

No, but unless portability is a concern or you're massively familiar with curl, you might want to consider xh. It's much more intuitive.

https://github.com/ducaale/xh

xh

wget on the other hand, automatically converts the ñ to UTF-8 hex and resolves the link perfectly.

I've searched the curl manpage and couldn't find a way to solve this. Please help.

I'm having to use `xh --curl` [1] to "fix" the links before I pass them to curl.

[1] https://github.com/ducaale/xh

Very nice, you should add xh to the User-Agents though.

While not a rewrite - one recent tool for making http requests which i quite enjoy is:

https://github.com/ducaale/xh

It's basically python httpie rewritten in rust. my only gripe is that i keep forgetting that it exists - and that "xh" is for http and "xhs" is for https.

So i frequently end up with curl anyway:)