ouroboros-network VS xmonad

I'm one of the consensus team members at IOG. We maintain and extend the consensus layer of the Cardano blockchain, which provides a rich set of challenges related to distributed computing, type level programming, networking, concurrency, among others.

According to a document on pipelining I saw on Github they might be building a whole new Ouroboros protocol called Leios (https://github.com/input-output-hk/ouroboros-network/pull/3579/files) so there might be something we don't know yet

• cardano-node - top level integration code • ouroboros-network & ouroboros-consensus - network code & consensus (which integrates network, consensus and the ledger) • ledger - ledger(s) specifications and implementation • plutus - the smart contract language and related infrastructure

Check out cardano-ping.

This is non trivial, you can check an example how we generate valid subset of Haskell to check that our implementation of orElse is corect: https://github.com/input-output-hk/ouroboros-network/blob/master/io-sim/test/Test/STM.hs

So from what I gather the transaction fee is a fixed protocol parameter. I like how fees are distributed amongst the epoch, If I had to design a blockchain system I'd also have chosen this approach TBH. It addresses some of the issues and misaligned incentives if you only have to rely on fees for block rewards. However if the demand for transactions constantly outweighs the available space you get into other issues. I tried to find details on how Cardano handles transactions and manages its mempool. I believe somewhere here is the code? (https://github.com/input-output-hk/ouroboros-network/blob/master/ouroboros-consensus/src/Ouroboros/Consensus/Mempool/Impl.hs)

Ouroboros(the consensus algorithm's formal specification): https://github.com/input-output-hk/ouroboros-network

The official guide and the archwiki do say that it's okay to just install it via pacman, but I've also found some issues on the official repo that strongly suggest against installing via pacman and to use stack instead, as sometimes pacman breaks dependencies.

Especially Haskell tools often live in proximity to nix as well, e.g., pandoc or xmonad.

Hey everyone 👋 ! I'm currently working on a rust library for building and configuring your own shell! It's inspired by projects like xmonad and penrose where the configuration of the program is done in code. This means that for example, instead of using Bash's arcane syntax for configuring the prompt, it can be configured instead using a rust builder pattern! The project itself is still at a very young stage, so there are plenty of bugs and unimplemented features. However, some things that are (partially) implemented are:

Daily, because xmonad

If the problem is as described in the reply linked below, then this isn't a fundamental issue, but just a matter of how sendMessage is written. In fact, the fix already exists in xmonad/432:2fff2a0.

There are a few other things I could mention, but there are more like side issues, and not relevant to my actual LaTeX setup. First and foremost—and thus perhaps noteworthy after all—is bibliography management with arxiv-citation (see here for more words). This is integrated very well with the XMonad window manager, which makes it even more of a joy to use.

The tl;dr is that this is a bug in steam, see https://github.com/xmonad/xmonad/issues/423

And here is my Xmonad configuration