Necessity of upgrading the (semi-official) Swift Slack to Pro?

today i was investigating an issue related to StreamClosed events from swift-nio-http2.

the details of the exact issue are not important, what is important is i recalled having discussed this exact topic with some of the SwiftNIO developers on Slack, and i recalled that the discussion likely contained exactly the information i was looking for.

so of course, i went back to the Slack today to try and use that discussion as a reference, but it had lapsed under the workspace’s 90 day retention limit. RIP!

the SwiftNIO developers are surely busy folks, so it seems like a waste of their time and money to ask them to go over the same information they had already provided long ago on Slack, information that i did not have the foresight to archive before it timed-out. i suspect i am not the only one in this boat.

in light of this, i’d like to kickstart discussions about Apple upgrading the community’s subscription to Slack Pro, so that this information and countless reams like it remain accessible beyond the 90 day limit. i know there have been several efforts in the past to migrate the community to Discord (which offers free archiving), but past experience has shown it is just really hard to compete with the Slack platform given their central position in the professional collaboration space.

2 Likes

Slightly off-topic, but: this is one of the downsides of Slack for this, we need to find ways to be better about getting these details into documentation eventually.

4 Likes