Problem with that is (besides occasional bugfixes), most people including myself would see #curl to be functionally complete and anything "nice to have" would be considered not worth the balooning in #complexity and #size.

• I mean, does curl need to be able to do #BitTorrent (magnet:), #IPFS (ipfs://) or god forbid #blockchain (i.e. #EVM) support?
• Do you really want to integrate @torproject / #Tor support natively into curl when using #HTTP (localhost:8118) and #SOCKS5 (localhost:9050) #proxy allows for the same and doesn't necessitate having to handle and ingest Tor arguments as well??

In fact if #toybox didn't have a #wget implementation that I could use for OS/1337 I would've merely chosen tiny-curl -o as a global alias or if #tinycurl wasn't an option, curl -o instead.

• Maybe someone who wants to have said functionality like tor support built-in will go and IDK make i.e. #[url=https://infosec.space/tags/neocurl]neocurl[/url] or sth. along those lines or build something like #[url=https://infosec.space/tags/ethcurl]ethcurl[/url] or #[url=https://infosec.space/tags/tor]tor[/url]curlor #[url=https://infosec.space/tags/ipfs]ipfs[/url]curl or whatever...

That being said I am glad curl isn't solely maintained by you but has other contributors (give them a shoutout!) but I also am glad you maintain that vital software that most "#TechIlliterate #Normies" most likely never heard of but propably use on a daily basis as part of all the #tech they use to #consume media with...

• I consider curl to be "the #vim of downloaders" (tho that's kinda insulting and limiting since curl is more than just a downloader and more intuitive than vim) with wget being "the #vi of downloaders" (tho wget is even simpler to use than vi)...

Either way, curl is awesome...

#OS1337 #Enshittification #Bloat #Bloatware

Set aliases globally for all users

I have certain paths, which are too long to type, so I need to wrap all those in one script as alias and source that script to my existing package code. These should set alias permanently over that

^{Stack Overflow}

A proposal to add #IPFS support to #libcurl

curl.se/mail/lib-2023-10/0073.…

I'm not convinced:
curl.se/mail/lib-2023-10/0074.…

Let the discussion flow!

We're heading into the weekend by announcing our intent to add #IPFS support to #Mastodon

This means that media attachments can also be collectively shared across the fediverse, just like messages already are.

Initial funding page up on @opencollective if you want to support, and we'll dig in more on this next week! opencollective.com/fission/con…

Fission - IPFS Media Support for Mastodon - Open Collective

While ActivityPub federates messages and accounts, media attachments of images, audio, video, and other file attachments don't move in the same way.

^{opencollective.com}

✨ HELLO FEDIVERSE ✨

I'm working on an introductory #book about #decentralisation protocols. 🦄

It serves as a taster for different technologies, and provides you with a path forward to deepen your studies if you're so inclined.

I'll cover #ActivityPub, #Hyper, #IPFS, and #SSB. Each chapter is a brief intro and a hands-on project using #JavaScript.

The book will be CC licensed. If that sounded interesting, add yourself to the interested readers list at:

leanpub.com/four-decentralisat…

transferfile.io - #Decentralized #Filesharing over the #IPFS #network.

Info
Up to 32 GB per upload and no registration needed.

Website
transferfile.io/