Shakedown Social

Free Software FoundationAssigning your copyright to the FSF helps defend the GPL and keep software free. Thanks to Rongzhao Yan, Paolo De Santis, and Maximilian Küffner for assigning their copyright to the FSF! More at: <a href="https://u.fsf.org/463" rel="nofollow noopener" translate="no" target="_blank">https://u.fsf.org/463</a> <a href="https://hostux.social/tags/Emacs" class="mention hashtag" rel="nofollow noopener" target="_blank">#Emacs</a> \<a href="https://hostux.social/tags/Wget" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wget</a> <a href="https://hostux.social/tags/CopyrightAssignments" class="mention hashtag" rel="nofollow noopener" target="_blank">#CopyrightAssignments</a>

Marcos Dione<a href="https://mastodon.sdf.org/@argv_minus_one" class="u-url mention" rel="nofollow noopener" target="_blank">@argv_minus_one</a> ... but why not <a href="https://en.osm.town/tags/curl" class="mention hashtag" rel="nofollow noopener" target="_blank">#curl</a> or <a href="https://en.osm.town/tags/wget" class="mention hashtag" rel="nofollow noopener" target="_blank">#wget</a>?

Dr Rockstar ♫ ㉆Octothorpe Y? In hopes that St NicholasSTEP1: CD to your <a href="https://social.vivaldi.net/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDevelopment</a> <a href="https://social.vivaldi.net/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#HTTP</a> server workspace.STEP2a: <a href="https://social.vivaldi.net/tags/curl" class="mention hashtag" rel="nofollow noopener" target="_blank">#curl</a> ``` curl -o- <a href="https://social.vivaldi.net/tags/https" class="mention hashtag" rel="nofollow noopener" target="_blank">#https</a>://gist.githubusercontent.com/ajaxStardust/674b5d86f1f4386e72937a607e263608/raw/install.sh > ~/install_adb_by_ajaxStardust.sh chmod 755 ~/install_adb_by_ajaxStardust.sh ``` Step2 alt: <a href="https://social.vivaldi.net/tags/wget" class="mention hashtag" rel="nofollow noopener" target="_blank">#wget</a> ``` wget -qO- <a href="https://social.vivaldi.net/tags/https" class="mention hashtag" rel="nofollow noopener" target="_blank">#https</a>://gist.githubusercontent.com/ajaxStardust/674b5d86f1f4386e72937a607e263608/raw/install.sh > ~/install_adb_by_ajaxStardust.sh chmod 755 $HOME/install_adb_by_ajaxStardust.sh ``` INSTRUCTIONS: a file saves to ~/home edit it to set 3 lines / $vars for your server name at line 40 <a href="https://github.com/ajaxStardust/AnnieDeBrowsa#description" rel="nofollow noopener" translate="no" target="_blank">https://github.com/ajaxStardust/AnnieDeBrowsa#description</a>

Preston Maness ☭I've mirrored a relatively simple website (redsails.org; it's mostly text, some images) for posterity via <a href="https://tenforward.social/tags/wget" class="mention hashtag" rel="nofollow noopener" target="_blank">#wget</a>. However, I also wanted to grab snapshots of any outlinks (of which there are many, as citations/references). By default, I couldn't figure out a configuration where wget would do that out of the box, without endlessly, recursively spidering the whole internet. I ended up making a kind-of poor man's <a href="https://tenforward.social/tags/ArchiveBox" class="mention hashtag" rel="nofollow noopener" target="_blank">#ArchiveBox</a> instead:for i in $(cat others.txt) ; do dirname=$(echo "$i" | sha256sum | cut -d' ' -f 1) ; mkdir -p $dirname ; wget --span-hosts --page-requisites --convert-links --backup-converted --adjust-extension --tries=5 --warc-file="$dirname/$dirname" --execute robots=off --wait 1 --waitretry 5 --timeout 60 -o "$dirname/wget-$dirname.log" --directory-prefix="$dirname/" $i ; doneBasically, there's a list of bookmarks^W URLs in others.txt that I grabbed from the initial mirror of the website with some <a href="https://tenforward.social/tags/grep" class="mention hashtag" rel="nofollow noopener" target="_blank">#grep</a> foo. I want to do as good of a mirror/snapshot of each specific URL as I can, without spidering/mirroring endlessly all over. So, I hash the URL, and kick off a specific wget job for it that will span hosts, but only for the purposes of making the specific URL as usable locally/offline as possible. I know from experience that this isn't perfect. But... it'll be good enough for my purposes. I'm also stashing a WARC file. Probably a bit overkill, but I figure it might be nice to have.<a href="https://tenforward.social/tags/RedSails" class="mention hashtag" rel="nofollow noopener" target="_blank">#RedSails</a> <a href="https://tenforward.social/tags/archive" class="mention hashtag" rel="nofollow noopener" target="_blank">#archive</a> <a href="https://tenforward.social/tags/archival" class="mention hashtag" rel="nofollow noopener" target="_blank">#archival</a> <a href="https://tenforward.social/tags/archiving" class="mention hashtag" rel="nofollow noopener" target="_blank">#archiving</a> <a href="https://tenforward.social/tags/warc" class="mention hashtag" rel="nofollow noopener" target="_blank">#warc</a>

Kevin Karhan :verified:<a href="https://mastodon.social/@bagder" class="u-url mention" rel="nofollow noopener" target="_blank">@bagder</a> Problem with that is (besides occasional bugfixes), most people including myself would see <a href="https://infosec.space/tags/curl" class="mention hashtag" rel="nofollow noopener" target="_blank">#curl</a> to be functionally complete and anything "nice to have" would be considered not worth the balooning in <a href="https://infosec.space/tags/complexity" class="mention hashtag" rel="nofollow noopener" target="_blank">#complexity</a> and <a href="https://infosec.space/tags/size" class="mention hashtag" rel="nofollow noopener" target="_blank">#size</a>. <ul><li>I mean, does <a href="https://curl.se/" rel="nofollow noopener" target="_blank">curl</a> need to be able to do <a href="https://infosec.space/tags/BitTorrent" class="mention hashtag" rel="nofollow noopener" target="_blank">#BitTorrent</a> (magnet:), <a href="https://infosec.space/tags/IPFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#IPFS</a> (ipfs://) or god forbid <a href="https://infosec.space/tags/blockchain" class="mention hashtag" rel="nofollow noopener" target="_blank">#blockchain</a> (i.e. <a href="https://infosec.space/tags/EVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#EVM</a>) support? </li><li>Do you really want to integrate <a href="https://mastodon.social/@torproject" class="u-url mention" rel="nofollow noopener" target="_blank">@torproject</a> / <a href="https://infosec.space/tags/Tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tor</a> support natively into curl when using <a href="https://infosec.space/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#HTTP</a> (localhost:8118) and <a href="https://infosec.space/tags/SOCKS5" class="mention hashtag" rel="nofollow noopener" target="_blank">#SOCKS5</a> (localhost:9050) <a href="https://infosec.space/tags/proxy" class="mention hashtag" rel="nofollow noopener" target="_blank">#proxy</a> allows for the same and doesn't necessitate having to handle and ingest Tor arguments as well??</li></ul>In fact if <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#toybox</a> didn't have a <a href="https://infosec.space/tags/wget" class="mention hashtag" rel="nofollow noopener" target="_blank">#wget</a> implementation that I could use for OS/1337 I would've merely chosen <a href="https://curl.se/tiny/" rel="nofollow noopener" target="_blank"><code>tiny-curl -o</code></a> as a <a href="https://stackoverflow.com/questions/30702803/set-aliases-globally-for-all-users" rel="nofollow noopener" target="_blank">global alias</a> or if <a href="https://infosec.space/tags/tinycurl" class="mention hashtag" rel="nofollow noopener" target="_blank">#tinycurl</a> wasn't an option, <a href="https://linux.die.net/man/1/curl" rel="nofollow noopener" target="_blank"><code>curl -o</code></a> instead.<ul><li>Maybe someone who wants to have said functionality like <code>tor</code> support built-in will go and IDK make i.e. <code>#neocurl</code> or sth. along those lines or build something like <code>#ethcurl</code> or <code>#torcurl</code>or <code>#ipfscurl</code> or whatever...</li></ul>That being said I am glad <code>curl</code> 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 "<a href="https://infosec.space/tags/TechIlliterate" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechIlliterate</a> <a href="https://infosec.space/tags/Normies" class="mention hashtag" rel="nofollow noopener" target="_blank">#Normies</a>" most likely never heard of but propably use on a daily basis as part of all the <a href="https://infosec.space/tags/tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#tech</a> they use to <a href="https://infosec.space/tags/consume" class="mention hashtag" rel="nofollow noopener" target="_blank">#consume</a> media with...<ul><li>I consider curl to be "the <a href="https://infosec.space/tags/vim" class="mention hashtag" rel="nofollow noopener" target="_blank">#vim</a> of downloaders" (tho that's kinda insulting and limiting since <code>curl</code> is more than just a downloader and more intuitive than <code>vim</code>) with wget being "the <a href="https://infosec.space/tags/vi" class="mention hashtag" rel="nofollow noopener" target="_blank">#vi</a> of downloaders" (tho <code>wget</code> is even simpler to use than <code>vi</code>)...</li></ul>Either way, curl is awesome... <a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#OS1337</a> <a href="https://infosec.space/tags/Enshittification" class="mention hashtag" rel="nofollow noopener" target="_blank">#Enshittification</a> <a href="https://infosec.space/tags/Bloat" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bloat</a> <a href="https://infosec.space/tags/Bloatware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bloatware</a>

daniel:// stenberg://I bet you don't remember when <a href="https://mastodon.social/tags/wget" class="mention hashtag" rel="nofollow noopener" target="_blank">#wget</a> briefly considered switching to using <a href="https://mastodon.social/tags/libcurl" class="mention hashtag" rel="nofollow noopener" target="_blank">#libcurl</a> back in 2007.<a href="https://daniel.haxx.se/blog/2007/10/27/wget-going-libcurl/" rel="nofollow noopener" translate="no" target="_blank">https://daniel.haxx.se/blog/2007/10/27/wget-going-libcurl/</a>

Kevin Karhan :verified:<a href="https://equestria.social/@SweetAIBelle" class="u-url mention" rel="nofollow noopener" target="_blank">@SweetAIBelle</a> I just hope that <a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@landley</a> can do <a href="https://infosec.space/tags/alias" class="mention hashtag" rel="nofollow noopener" target="_blank">#alias</a> support in <code>toysh</code> so I can supplement most stuff easily with a <code>.bash_aliases</code> <a href="https://github.com/kkarhan/misc-scripts/blob/master/bash/.bash_aliases" rel="nofollow noopener" target="_blank">file</a> to make it easy to use...Like I know I eon't be abke to ship most tools that I want to have at hand with like a 1440kB image but I can just yoink them with <a href="https://infosec.space/tags/wget" class="mention hashtag" rel="nofollow noopener" target="_blank">#wget</a> or <a href="https://infosec.space/tags/curl" class="mention hashtag" rel="nofollow noopener" target="_blank">#curl</a> or <a href="https://infosec.space/tags/tinycurl" class="mention hashtag" rel="nofollow noopener" target="_blank">#tinycurl</a> or whatever even before any <a href="https://github.com/os-1337/spm" rel="nofollow noopener" target="_blank">package manager</a> is up and running or available.<ul><li>Tho compared to most <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> distros and tools like <code>apt</code> and <code>yum</code>, <code>spm</code> isn't very advanced and at most will likely only offer to download/remove a binary or replace it...</li></ul>

Anton Ohorodnyk<a href="https://mastodon.gougere.fr/@bortzmeyer" class="u-url mention" rel="nofollow noopener" target="_blank">@bortzmeyer</a> <a href="https://mastodon.social/@bagder" class="u-url mention" rel="nofollow noopener" target="_blank">@bagder</a> it’s interesting point of view. I’d assume that <a href="https://fosstodon.org/tags/wget" class="mention hashtag" rel="nofollow noopener" target="_blank">#wget</a> can cover all use cases curl provides for more than half of people who use curl. I think people want to have wget alternative to not use two separate tools, but stay with <a href="https://fosstodon.org/tags/curl" class="mention hashtag" rel="nofollow noopener" target="_blank">#curl</a>. They may want to have it due to less installed tools (in some containers or minimalistic VMs or some IoT, etc). Why would you suggest to use wget instead?

Kevin Karhan :verified:<a href="https://social.treehouse.systems/@ariadne" class="u-url mention" rel="nofollow noopener" target="_blank">@ariadne</a> makes sense espechally if you don't want to delegate that to tools like <a href="https://infosec.space/tags/curl" class="mention hashtag" rel="nofollow noopener" target="_blank">#curl</a> or <a href="https://infosec.space/tags/wget" class="mention hashtag" rel="nofollow noopener" target="_blank">#wget</a> to handle...<ul><li>In fact, were it not for the minimalist wget in <a href="https://infosec.space/tags/toybox" class="mention hashtag" rel="nofollow noopener" target="_blank">#toybox</a> [without <a href="https://infosec.space/tags/HTTPS" class="mention hashtag" rel="nofollow noopener" target="_blank">#HTTPS</a>!] I would've to figure out a different way to make the <a href="https://github.com/OS-1337/spm" rel="nofollow noopener" target="_blank">package manager</a> for OS/1337, <a href="https://infosec.space/tags/spm" class="mention hashtag" rel="nofollow noopener" target="_blank">#spm</a>, work.</li></ul>OFC it's not operational yet but I know that <a href="https://infosec.space/tags/KissPrinciple" class="mention hashtag" rel="nofollow noopener" target="_blank">#KissPrinciple</a> is good... And I do intent <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a> to do that with as well...<a href="https://infosec.space/tags/OS1337" class="mention hashtag" rel="nofollow noopener" target="_blank">#OS1337</a>

daniel:// stenberg://"Wget can be typed in using only the left hand on a qwerty keyboard!"Still my favorite difference between <a href="https://mastodon.social/tags/wget" class="mention hashtag" rel="nofollow noopener" target="_blank">#wget</a> and <a href="https://mastodon.social/tags/curl" class="mention hashtag" rel="nofollow noopener" target="_blank">#curl</a> <a href="https://daniel.haxx.se/docs/curl-vs-wget.html" rel="nofollow noopener" translate="no" target="_blank">https://daniel.haxx.se/docs/curl-vs-wget.html</a>

Mateng<a href="https://mastodon.social/@gruber" class="u-url mention" rel="nofollow noopener" target="_blank">@gruber</a> <a href="https://mastodon.social/@bagder" class="u-url mention" rel="nofollow noopener" target="_blank">@bagder</a> This might be the killer feature of <a href="https://nrw.social/tags/wget" class="mention hashtag" rel="nofollow noopener" target="_blank">#wget</a>: "Wget can be typed in using only the left hand on a qwerty keyboard" 😉

daniel:// stenberg://<a href="https://mastodon.social/tags/wget" class="mention hashtag" rel="nofollow noopener" target="_blank">#wget</a> 1.24.5 has been released: <a href="https://www.gnu.org/software/wget/" rel="nofollow noopener" translate="no" target="_blank">https://www.gnu.org/software/wget/</a>43 weeks since the previous release.

Aral BalkanIt’s bloody 2024, think we can agree on either wget or curl being installed by default on every freaking operating system by now so shell scripts can have a guaranteed way of carrying out http requests?I mean it’s been about 35 years. I think it’s about time.<a href="https://mastodon.ar.al/tags/http" class="mention hashtag" rel="nofollow noopener" target="_blank">#http</a> <a href="https://mastodon.ar.al/tags/shell" class="mention hashtag" rel="nofollow noopener" target="_blank">#shell</a> <a href="https://mastodon.ar.al/tags/cli" class="mention hashtag" rel="nofollow noopener" target="_blank">#cli</a> <a href="https://mastodon.ar.al/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.ar.al/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a> <a href="https://mastodon.ar.al/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#macOS</a> <a href="https://mastodon.ar.al/tags/curl" class="mention hashtag" rel="nofollow noopener" target="_blank">#curl</a> <a href="https://mastodon.ar.al/tags/wget" class="mention hashtag" rel="nofollow noopener" target="_blank">#wget</a>

Recent searches

Search options

Administered by:

Server stats:

#wget