<!here> Itโ€™s not often that we use notifications o...
# announcements
h
<!here> Itโ€™s not often that we use notifications on #C0922A726, but today calls for a celebration. If you havenโ€™t noticed, you now have history in Slack! Weโ€™re extremely grateful to Slack and specifically to @sam for helping put this in motion.
๐Ÿ‚ 16
๐Ÿ‘ 12
๐Ÿ•ด๏ธ 16
๐ŸŽ‰ 249
G 23
๐Ÿ‘ 40
๐Ÿ‘ป 16
๐Ÿบ 21
๐Ÿค˜ 14
๐Ÿ‘Œ 8
๐Ÿ˜ 6
๐Ÿ‘™ 1
๐ŸŽ 3
โฌ†๏ธ 1
๐Ÿ”ฅ 38
K 95
๐Ÿ˜ฏ 16
๐Ÿ’ฅ 16
๐Ÿพ 16
๐Ÿค  4
๐ŸŽ–๏ธ 3
๐Ÿ” 3
๐ŸงŒ 2
๐Ÿ˜ป 1
๐Ÿ“– 20
๐Ÿฅ‚ 19
๐ŸŽ‡ 15
๐Ÿš€ 6
๐Ÿ˜บ 2
๐Ÿ•ถ๏ธ 2
metal 1
S 132
โค๏ธ 102
K 11
๐Ÿ’ฏ 40
๐ŸŽŠ 32
๐Ÿ‘ 74
๐Ÿ‘Œ 37
To be clear History is just one of the benefits!
r
Standard plan with 17k users !?
๐Ÿ˜… 2
n
To put this into context. Thatโ€™s ~$2.5M right there
e
I hope JB managed to knock out a discount
๐Ÿ‘๐Ÿผ 1
n
So we can use calls too?
l
Why do we need history here?) I think slack for kotlin could be free.
h
@lewik there are quite a few Kotlin OSS projects that use this slack for their development and would appreciate keeping a history of discussions theyโ€™ve had.
@nish I think youโ€™re mistaken in terms of how Slack calculates users. Itโ€™s active users, not all users.
n
Ah good point ^ I forgot about that.
g
Well, clicking at a random user gives me the "Call" option, so there's that.
h
@gabrielfv I believe that was always there
g
You might be right, as I've never tried that before actually ๐Ÿ˜…
e
I'm glad they changed idea
I wonder, though, what made them do that
k
So we get access to the existing history too now? Awesome!