Cartero 📩

84 Followers
6 Following
72 Posts

Cartero is the lightweight HTTP client that you can use to test your APIs. Avoid bloat, respect your privacy, reject cloud; that's the motto.

Written in Rust, powered by GTK and libadwaita. If you run GNOME, you will love it. Made in Spain 🇪🇸, with contributions from 🌐 all around the world! Technically made in Europe 🇪🇺

This is our fediverse account. Follow for announcements, tips and some occasional shitpost.

Websitehttps://cartero.danirod.es
Source codehttps://github.com/danirod/cartero
Bloghttps://cartero.danirod.es/blog
Oh boy, here it comes.

Cartero 26.0 has been released!

This version adds a theme picker that you can use to choose the color palette for the application. Text editors and windows will use the chosen colors.

Also, bugs have been fixed, translations to Basque, Indonesian and Brazilian Portuguese have been updated, and a new translation to Simplified Chinese has been added.

📰 Release notes: https://github.com/danirod/cartero/releases/tag/v26.0
📝 Blog post: https://cartero.danirod.es/blog/cartero-26-0-released/
💾 Download: https://cartero.danirod.es/download/

With the current prices of RAM memory, it is important to squeeze like an orange every byte available in the system in order to save money.
Themes have landed in nightly. Now, where is the VSCode to SourceView theme converter?
Another satisfied customer, I guess. 🔥

The settings window is being rewritten because it has to fit new options and the old design made it too hard.

I'm adding some settings to configure the HTTP proxy, to test drive the new system and check that it's easy to extend.

(Cartero has always supported proxies using the env variables http_proxy, https_proxy and no_proxy; but this has never been disclosed and it's a side effect of how curl works rather than a real feature.)

In fact, Cartero will now refrain from rendering images or binary files by default. If you try to request something that is not text, it will suggest you to save the response contents into a file instead. (You can still render the response in the view, if you really want to view all the � characters or other Unicode garbage.)

The "Export as cURL" tab has moved into a menu, basically because there are more export formats now!

You can still export as cURL, of course. But there is initial support for JetBrains HTTP (it was easier to write, but imagine having Bru or OpenAPI in the future).

You can also export the response body right from the menu. For instance, to save an image, a big file or a payload that you need to consume from another app.

It is now possible to attach the payload for a request straight from a file.

(This is NOT adding a file as a multipart field. I'm working on that yet. This is a raw request, but instead of writing the payload inside Cartero, you load the raw content from a file.)

There are a few security restrictions in place at the moment, but they might be relaxed in the future. (Mainly, you cannot attach any file from your system, I don't know yet if this is a good idea or not. Feedback appreciated!)

Now merged: the export tab will be moved to a dropdown menu in the toolbar. Choosing an export format will open a dialog to review, copy or save the data to a file.

Currently only the original "export as cURL" is available, but additional exporters are going to be added as the refactor advances: export the response body (only sane way to deal with octet-stream requests), export entire interaction as HAR...

Available in nightly, and tomorrow in the Snap Store, channel latest/edge.