Martin Kleppmann (known for the Building Data-Intensive Applications book) gave a lecture on Raft a year ago [0], it remains my absolute favorite explanation of the algorithm.
I think it does way too much "all in one shot" v.s. a layered abstraction approach you have to do with Paxos where you build up from the basics of consensus.
The evidence that raft is more "understandable" rest on IIRC a multiple choice question test not on actually implementing the thing working correctly. But (without having seen the test, but being familiar with both algorithms) it is easier to answer questions about what raft is supposed to be doing than paxos, but paxos actually confronts you with the edge cases more explicitly that are still present in raft.
Granted, both are hard to implement correctly! I just think that learning Paxos does lead to a more detailed understanding of consensus than raft.
As someone who TA'd 6.824 (Distributed Systems) twice, I 100% agree. It's easier to halfway understand Raft than to halfway understand Paxos, but implementing a consensus algorithm correctly requires understanding it fully. Once you start talking about e.g. the "election restriction", Raft becomes a bit hairy.
I took 6.824 under Paxos (I think we took it at the same time maybe? not sure if you were TA at that point) and then helped a friend when it switched to raft and good lord that seemed to be a worse for them.
It replicates all data everywhere in real-time asynchronously over HTTP. The id of each node is a hash of the key each node uses as privilege to edit. A user node can edit child nodes with it's key. link is used for 1-to-many and word search. meta is used for 3-way many-to-many x-ref values, so for example user-type-item etc. The user management uses this for security: https://datatracker.ietf.org/doc/html/rfc2289
