if I wanted to make a slack bot for this channel, what would be the most Future of Code Compliant ™️ way to do it?

What would be its purpose?

reply to messages that contain links with a list of previous conversations that contained the same link

Interconnecting conversations seems very useful. I'm new here so I do not dare to answer technical requests concerning the community.

the question doesn't concern the community, it's just a "request for future of code adjacent technologies that may be useful to solve this problem" 🙂

Love the idea of resurfacing previous conversations automatically. I wonder if we could somehow implement a backlinking system. Wiki links like this [[syntax]] could cause the bit to auto-reply with… something. 🤔

I could index wiki links in my archive (example https://marianoguerra.github.io/future-of-coding-weekly/history/weekly/2022/05/W5/share-your-work.html#2022-05-23T15:49:14.120Z)

Interesting. I already use the archive fairly often. Would be pretty cool to build index pages for each wikilink with all relevant messages.

If the idea is to use "Futuristic" technologies, I'm tempted to say it would be plenty cool if it was written in Smalltalk or something. Maybe Pharo? :D

if it was easy and cheap to deploy as a server I would, I'm not sure it is 😕

I suspected as much. I like the options you listed, too. :)

I recently built a simple system like this at work. I use Slack’s extension system to get messages as they come in, which are sent to a web endpoint where some basic python parses the event and (in my case) forwards it on to the rest of the system. It shouldn’t need much more than the slack extension, web endpoint, and access to slack history data.

The idea is to try some future of coding related tool

In that case I’d second Unison, you’ll need a Slack extension regardless afaik, but Unison is so fun to work with.

I have a twitter bot made with the precursor to webcode https://observablehq.com/@endpointservices/twitter-bot thats a serverless tech so its exceedingly cheap to do event driven stuff (and it supports live debugging which you will quickly realise you will want when doing webhook stuff). Happy to twitch it too, observable supports multiplayer coding.

I'd be curious to see how @Tom Larkworthy's approach does with something I'd use 🙂

I forgot I just used zapier to do the tweeting for that bot, I am able to do a full low level API integration too but I just didn't bother. I once did a production slack bot using BPMN workflows: https://futurice.com/blog/a-detailed-look-at-camunda-bpmn-application-development too. It was that experience that made me decide it was far quicker using zapier.