tatterdemalion

Sadly the Android app is no longer maintained, and it hasn't been released for newer versions of Android.

~~There's an unmaintained Windows client.~~

Actually here is one that's still active: https://github.com/IJHack/QtPass

This person is no superstar.

Sounds a lot like the AT Protocol.

Monster

74 episodes. Psychological thriller. Serial murder mystery, but instead of "whodunit?" it's "whydunit?". Dramatic as an opera. No weird tropes. Superb character development. I love Magnificent Steiner.

What are you talking about? BlueSky has absolutely nothing to do with Facebook. It's a different company using the open AT Protocol.

Technically it's an open protocol. Whether or not any other implementations will surface remains to be seen.

Being eternally trapped in a mental prison. Imagine having a panic attack that never ends. I'm pretty sure that type of prolonged stress would cause a psychotic break where your psyche fractures and you become a despondent shell. You would become deathly afraid of everything, even the people you love, because of an unceasing paranoia. That basically sounds like hell to me.

I'm not really afraid of the idea of nothingness after death, because at least then I am released from the torment of living.

My point wasn't so much that I think RED is shady but that exposing my IP seems like an unnecessary requirement to join. Why can I not have my membership tracked via an anonymous account? If they are concerned about account harvesting or something, then the interview already seems like a good enough measure, accompanied by seed ratio minimums.

Thanks for all the info. This makes me want to try it even more now!

There are plenty of good resources online. Here are some topics you probably wouldn't see in an intro algos course (which I've actually used in my career). And I highly recommend finding the motivation for each of these in application rather than just learning them abstractly.

• bloom filter
• btree
• b+ tree
• consensus algos (PAXOS, RAFT, VSR, etc)
• error correction codes (Hamming, Reed Solomon, etc)
• garbage collection (mark+sweep, generational, etc)
• generational arena allocator
• lease (i.e. distributed lock)
• log-structured merge trees
• min-cost + max-flow
• request caching and coalescing
• reservoir sampling
• spatial partition (BVH, kd-tree, etc)
• trie
• write-ahead log

That's good to hear. Is it as easy to navigate and customize as Sway/i3?