Maximilian Knespel

Possibly "dirty" workaround for your bashrc: ``` trash-empty(){ local mountpoint for mountpoint in $( cat /proc/mounts | awk '{ print $2; }' ); do if [ -d "$mountpoint/.Trash/$UID" ]; then...

@protist Ah, I didn't even know trash-empty had that kinda functionality and never needed it, but here is my take on how to implement even that with bash: trash-empty() {...

I see. Thanks for investigating. I think reporting it upstream would be the best choice.

In telegram-cli it looks a bit different for me: *** 1526384817.650984 Skipped 2484 int out of 3478 (type messages.Messages) (query type get history) *** 1526384817.651020 0x00000000 0x0b446ae3 0x00012237 0x1cb5c415 >...

@fiddyschmitt Maybe [t2sz](https://github.com/martinellimarco/t2sz) might be something for you. It compresses to zstd in such a manner that it can be easily seeked, e.g., with [ratarmount](https://github.com/mxmlnkn/ratarmount), [indexed_zstd](https://github.com/martinellimarco/indexed_zstd), and [libzstd-seek](https://github.com/martinellimarco/libzstd-seek).

Unfortunately, not. I'm pretty sure last time I looked at the file formats, I found that it would be near impossible to do. Similar to gzip, zstd is a sequence...

I don't understand the use case. Why do you need an index for *seeking* when you can't seek on the file?

> Looks like we might need to resolve [pauldmccarthy/indexed_gzip#102](https://github.com/pauldmccarthy/indexed_gzip/issues/102) first though... I was going to write something like that before you did ;). And it's not only `indexed_gzip`. I wanna...

Yeah, this is normal, at least for now. The problem is under which name to store the data for recursive archives. I think this issue might be a duplicate of...

> What about storing all .tar indices in single DB? For further databases caused by recursive archives, I think I answered your question. Do you mean when using the union...