Jakub Fišer

ok, the last paragraph isn't entirely true. When I sent a few messages from another client, things "caught up" somehow, without any action taken on either Gomuks or server side

I'd like to see Vault as st2kv backend as well but I can also see tha the feature parity doesn't align. I see another option here - do not use...

interesting, I must say that lately (weeks, maybe a month) I don't actually remember this happening... (I'm on v1.8 currently) Something else happens though - when I switch workspaces, the...

@teto added

I believe [this](https://github.com/charmbracelet/bubbletea/blob/d1a16bd88370daba01ea34b9007e050f56adc97c/standard_renderer.go#L225]) is the reason why `chafa` and similar approaches don't work for some people. The standard renderer truncates all the lines to the available terminal width regardless their...

Being a total Go n00b, I can only theorize about a solution that could be made on `slides` side - a custom renderer which overrides the standard renderer's `flush()` to...

This is a selling (or rather _unselling_) point for me. Implementing zrepl as my backup backend but I have a hard time explaining how the _restore_ part is gonna work...

> Especially for the untrusted remote/encrypted ZFS scenarios - since that requires special consideration for managing/backing up the encryption keys. That is imho exactly why encrypted scenarios should _not_ fall...

well, as they say in the docs: > zrepl is a one-stop, integrated solution for ZFS *replication*. It doesn't say "backup" but imho backups are the most common use case...

then there is a bug in the docs :) either in README or on zrepl.github.io Even then though, it says _backup_, not _backup&restore_. Beyond this the discussion would be philosophical...