Friendly reminder (since we've had a few instances of this in the past few days) — When replying, please always reply in a thread. This makes it easier to follow discussions, avoids new discussion prompts being lost in the noise, and makes it easier to link back to discussions down the road. Addenda: As @Kartik Agaram points out in this thread, when starting a new discussion at the top level, type out your entire thought in one message. If you want to add additional details after sharing, edit your original message (use the

...

hover menu on desktop, or tap-and-hold the message on mobile) rather than posting additional top-level messages.

Corollary: when starting a new thread, type out your entire comment all at once. (To create new paragraphs without submitting, type

shift-return

on a laptop. My Android keyboard uses the

⏎

key to insert newlines without submitting the comment.)

this week there's an interesting conversation that I can't share because I can't link to any part of it, I would have to copy paste it all and edit it in the newsletter itself, just because it was spread across messages (and I was part of the problem🤦🏽‍♂️)

I've wished in the past that the newsletter included comments and not just links.

you mean highlight the best comments?

Not to totally derail absolutely everything, but since we'll probably be sticking with Slack (spoiler for the upcoming, much delayed podcast episode and survey results), we'll want to get some sort of nice searchable archive of messages and replies set up. Which might make it easier to call out good thread comments in the newsletter.

I'm growing some basic tools to create the newsletter, I could create a script that scraps the slack threads in the newsletter and creates a static site with them so non slack users can easily open the threads in tabs and read

A wiki hosted on GitHub to distill interesting conversations would be a good timeless complement to Slack's eternal present.

yep, I could dump each thread to a new wiki page

It'd be nice if any direction we go with this could eventually cover the entire public Slack. It'd be a shame to only capture the things we think are relevant to the newsletter. (Not that this newsletter thread archiving idea needs to be that. Just.. thinking about the broader problem.)

will start with the threads on the newsletter and when done (if it's possible) may extend it to the whole slack

@Ivan Reese this is doable. If Mariano just spun up a wiki page for every single thread, then most pages would be fallow, but we could easily start editing any page at any time. The newsletter would become the frontpage, the tip of a much larger iceberg of cross-linked threads.

I think this sounds like two separate things. It'd be nice to have (A) a wiki of the ideas we self-select as being worth citing, revisiting, interconnecting, tagging, etc., and (B) an automatic archive of everything everyone ever shares or says, so that we can query the hell out of it.

If someone volunteers to host it, yes. My idea was that GitHub could be a poor sophont's database in the absence of something better.

ok, managed to dump this week's content of general and feedback channels, we could run it weekly and dump the content on the repo as json and let people build tools, I can do an online viewer quickly to get the links from the newsletter working

Is it going to be at https://github.com/marianoguerra/future-of-coding-weekly?

probably to start with unless there's a better idea

Hah, sorry I did this a couple of times when I decided to post links and follow up with more info, my thoughts are I wanted people to see top level context of the link, next time I'll edit the post if I want to add instead of following up

Posting definitely preferable to not posting.