i am become linux user, juicer of tarballs
May 23, 2026 at 5:56 PM
i am become linux user, juicer of tarballs
javascript is stored in the tarballs
January 10, 2025 at 11:50 PM
javascript is stored in the tarballs
GNU developer be like "find my tarballs"
October 29, 2025 at 11:36 PM
GNU developer be like "find my tarballs"
correct we should be shipping tarballs compressed in xz instead
November 22, 2025 at 4:48 AM
correct we should be shipping tarballs compressed in xz instead
must be those tarballs i've heard so much about
May 4, 2026 at 5:13 PM
must be those tarballs i've heard so much about
Hate when my Linux nerd cat coughs up tarballs
February 4, 2025 at 3:57 PM
Hate when my Linux nerd cat coughs up tarballs
Sydney North Shore beach balls -
@unswchemistry.bsky.social
analysed them! TL,DR: filthy soap scum. Details below! #tarballs #grimeballs #ozchem
@unswchemistry.bsky.social
analysed them! TL,DR: filthy soap scum. Details below! #tarballs #grimeballs #ozchem
January 29, 2025 at 1:28 AM
Sydney North Shore beach balls -
@unswchemistry.bsky.social
analysed them! TL,DR: filthy soap scum. Details below! #tarballs #grimeballs #ozchem
@unswchemistry.bsky.social
analysed them! TL,DR: filthy soap scum. Details below! #tarballs #grimeballs #ozchem
Holding up a diagram is your package format zip files or tarballs
It’s a good package format sir
it’s tarballs
It’s a good package format sir
it’s tarballs
August 28, 2025 at 6:32 AM
Holding up a diagram is your package format zip files or tarballs
It’s a good package format sir
it’s tarballs
It’s a good package format sir
it’s tarballs
Initially, Google would usually provide access to the tarballs within a couple hours. Lately, they're often taking weeks to get back to us. They're the ones who chose to use this archaic system instead of pushing Git tags and it's their responsibility to handle requests promptly.
August 8, 2026 at 12:52 AM
Initially, Google would usually provide access to the tarballs within a couple hours. Lately, they're often taking weeks to get back to us. They're the ones who chose to use this archaic system instead of pushing Git tags and it's their responsibility to handle requests promptly.
Yet another attack where (part of) the payload is injected in final release tarballs.
Go definitely made the right choice by fetching git tags directly. Nowhere to hide extra code.
Go definitely made the right choice by fetching git tags directly. Nowhere to hide extra code.
March 29, 2024 at 9:38 PM
Yet another attack where (part of) the payload is injected in final release tarballs.
Go definitely made the right choice by fetching git tags directly. Nowhere to hide extra code.
Go definitely made the right choice by fetching git tags directly. Nowhere to hide extra code.
Been juicing my tarballs manually since 1993.
AI can find its own damn tarballs.
AI can find its own damn tarballs.
the final insult of AI is going to be forcing us all to become linux guys. we're all going to be like oh yeah downloading stuff on linux is super easy you just juice the tarball and compile the pulp in the sudo command line. not like windows where you have to click on things
May 3, 2026 at 1:51 PM
Been juicing my tarballs manually since 1993.
AI can find its own damn tarballs.
AI can find its own damn tarballs.
Prior to moving it to Google Drive, they started squashing the history into a single commit prior to pushing release tags. The tarballs provided via Google Drive have exactly the same source code. However, they went out of the way to make it more inconvenient in several ways.
August 8, 2026 at 12:45 AM
Prior to moving it to Google Drive, they started squashing the history into a single commit prior to pushing release tags. The tarballs provided via Google Drive have exactly the same source code. However, they went out of the way to make it more inconvenient in several ways.
so like why Do tarballs have 2 extensions . why are they so special
October 22, 2025 at 3:09 AM
so like why Do tarballs have 2 extensions . why are they so special
compressing all Rust release tarballs at very high compression settings takes over an hour on an 80-core server
September 22, 2025 at 6:55 PM
compressing all Rust release tarballs at very high compression settings takes over an hour on an 80-core server
basically:
- stop containers gracefully
- clone containers to *-backup
- tarball external data
- verify data tarballs
- tarball cloned containers
- verify container tarballs
- bzip2 the tarballs
- verify the bzip2'd files
- delete spare tarballs
- delete cloned containers
- restart the containers
- stop containers gracefully
- clone containers to *-backup
- tarball external data
- verify data tarballs
- tarball cloned containers
- verify container tarballs
- bzip2 the tarballs
- verify the bzip2'd files
- delete spare tarballs
- delete cloned containers
- restart the containers
October 4, 2025 at 4:57 AM
basically:
- stop containers gracefully
- clone containers to *-backup
- tarball external data
- verify data tarballs
- tarball cloned containers
- verify container tarballs
- bzip2 the tarballs
- verify the bzip2'd files
- delete spare tarballs
- delete cloned containers
- restart the containers
- stop containers gracefully
- clone containers to *-backup
- tarball external data
- verify data tarballs
- tarball cloned containers
- verify container tarballs
- bzip2 the tarballs
- verify the bzip2'd files
- delete spare tarballs
- delete cloned containers
- restart the containers
svelte.dev/playground now fetches package tarballs direct from npm (with an assist from jsdelivr.com) instead of individual modules from unpkg.com. grateful to unpkg for years of service but this is much faster and more resilient. if you hit issues, let us know
Hello world • Playground • Svelte
Web development for the rest of us
svelte.dev
April 4, 2025 at 12:36 PM
svelte.dev/playground now fetches package tarballs direct from npm (with an assist from jsdelivr.com) instead of individual modules from unpkg.com. grateful to unpkg for years of service but this is much faster and more resilient. if you hit issues, let us know
can atproto just return tarballs for repo exports i feel like it would've been better this way (streamed extraction/packing)
November 20, 2024 at 10:43 PM
can atproto just return tarballs for repo exports i feel like it would've been better this way (streamed extraction/packing)
Well that explains why they call them tarballs…
April 28, 2025 at 1:09 PM
Well that explains why they call them tarballs…
GNU developer be like "find my tarballs"
October 29, 2025 at 11:37 PM
GNU developer be like "find my tarballs"
All CRAN source packages (22749 tarballs as of today) contain 5.8Gb PNG images in total. Lossless compression via tinyimg::tinyping() can save 1.9Gb (32.0% savings), and lossy compression without noticeable differences can save 2.8Gb (48.2%): pkg.yihui.org/tinyimg/exam... (plot on the page is slow)
April 26, 2026 at 6:06 PM
All CRAN source packages (22749 tarballs as of today) contain 5.8Gb PNG images in total. Lossless compression via tinyimg::tinyping() can save 1.9Gb (32.0% savings), and lossy compression without noticeable differences can save 2.8Gb (48.2%): pkg.yihui.org/tinyimg/exam... (plot on the page is slow)