Welcome to #C5U3SEW6A! If you found a blog post, article, talk, book, podcast, paper, or other item of external media (collectively referred to as "links") that is in some way relevant to the future of computing, this is the place to share and discuss it. If you're going to add some commentary about your link, please include that as part of the same post as the link itself — if you split it across two or more messages, it'll be much harder to reference the link and discussion in the future, search for it, etc. • Links about the programming / world of the present should go to #C01932BJGE8, unless they are framed with an eye to how the future will unfold. • Links about history are welcome here, since any view of history incorporates a sense of how things have evolved, which is one of the most powerful ways to understand how things will continue evolving. • Discussions that might include a link as supporting material, but center on your own thoughts or questions, should go in #C5T9GPWFL. • Feel free to post multiple links in the same post if they are directly related and should be discussed together. • If your link generates a rich preview, the preview may be removed by an admin if it doesn't offer meaningful value. Inline videos are meaningfully valuable. Good summaries of an article are meaningfully valuable. A generic image of some code text or a mountain scene accompanied by the name of the article... not valuable, will be removed without notice. Please provide adequate context in your post, explaining why we might be interested in the link, rather than relying on the rich preview. (After all, rich previews aren't searchable)

This should be pinned. I think it’s possible to pin messages in slack right?

center on your thoughts should go in

@Ivan Reese is this a typo?

Thanks @opeispo. Good idea. I don't believe that's a typo, @Nick Smith. Here's a rephrasing: Posts that might include a link as supporting material, but that are mostly based on your own thoughts or questions, should go in #thinking-together.

Ah, I see. Another parsing error of mine. The extra comma helps.