0x0 VS emacs-request

http://0x0.st works for me

Minimal file hosts like https://catbox.moe or http://0x0.st work nice in my opinion, here's an example link: https://files.catbox.moe/zamm2d.jpg

The only catch is most of them set a time limit on uploads, but you might be able to (ab)use archive.org if you want the files to stay online forever.

Looks similar to 0x0.st

major OOPS here, ( I feel like the sorcerer's apprentice)expression "curl -F'[email protected]' https://0x0.st" returns message that "-F" is badly used, and trying it without the "-F" results in failure . . . oops!

I dont use go$hit drive so I use 0x0.st to upload files for sharing (it uses curl).

curl -F'[email protected]' https://0x0.st

# censor usernames from log sed -iE "s/$USER/$(printf "%${#USER}s")/g" mem.log` # upload curl -F'[email protected]' https://0x0.st

> It was purely decorative, but ugly decoration that only appealed to other brutalist architects, meant to trick people into thinking it was some "raw" construction element sticking out.

That's really funny, because I've seen websites that tries to appeal to "hacker"/"minimalist" aesthetics doing the same thing.

An example: the file-hosting service https://0x0.st. When you try to visit a link to a non-existing file, it will crash with a trace message that exposes the offending code block from `fhost.c`.

Wow, so RAW and BRUTAL. It's even written in C, so hacker-ish! Until you find out that the error message is _fake_: https://git.0x0.st/mia/0x0/src/branch/master/templates/404.h...

The server is actually written in Python and it generates a randomized, fake C-looking trace message for its 404 page.

I'm going to go on a limb and say it's automod because of my file host ( https://0x0.st ) also testing if this comment gets removed or not

First cd into the log directory and run the following command. curl -F '[email protected]' https://0x0.st

That is quite normal thing to do. Have you not seen Emacs Async? Take, a look, it is a useful thing. Or Emacs Request. Since Emacs does not have proper thread scheduler, that is the best next thing you can do.

Exciting! I've been using request.el for my own projects mostly out of habit. Could you outline some of the relative advantages of plz?

Instead of shelling out to curl, use url.el or request.el.

You mean, John Wigley's async package? Maybe it isn't used so often, however async processes are used in Emacs. Check for example functions 'native-async-compile' or 'async-byte-compile-file'. There is another package, request.el that uses async processes to do the network I/O (via curl).

This? https://github.com/tkf/emacs-request

You can already use emacs-request, it offers very nice asynchronous API and uses curl by default if present and falls back on Emacs url if curl is not found.

Have you tried (package! emacs-request), since that’s the name of the source repository (https://github.com/tkf/emacs-request)?

It's possible that I'm brain dead but I'm struggling to wrap my head around the emacs-request code found here: https://github.com/tkf/emacs-request