Dan Gohman (Dec 13 2019 at 18:45): Dan Gohman (Dec 13 2019 at 18:45):If you had asked me for what one thing about chat I'd change, adding titles to threads probably wouldn't have been it, but I'm willing to give it a try.
fitzgen (he/him) (Dec 13 2019 at 22:50):I do enjoy the threading, but I find the UI a little hard to visually parse quickly
Benjamin Bouvier (Dec 16 2019 at 17:12):Can we have several levels deep within a thread? (stream > thread > thread > thread...)
Dan Gohman (Dec 16 2019 at 17:13):I think replies within a thread just extend that thread
Sean Stangl (Dec 16 2019 at 17:41):The topics are analogous to email subjects. They don't nest.
Sean Stangl (Dec 16 2019 at 17:43):They're intended to be cheap and disposable. It's easy to create a new topic, and easy for people to ignore it, so you don't worry about getting the topic right or anything like that.
Sean Stangl (Dec 16 2019 at 21:16):Related to GitHub being kind of hard to find out about new issues/review requests/updates/etc., it is possible to connect that via webhooks to post into Zulip.
Sean Stangl (Dec 16 2019 at 21:17):You could give each project its own channel like #git-cranelift. Every update to the project would then be reported into that channel. On my other project, it means that we never have to check email anymore, we never miss anything, and everyone knows what's happening in the project.
Sean Stangl (Dec 16 2019 at 21:18):Each issue and merge request is automatically given its own Zulip topic. So by pressing Shift+S, you can see the whole change history of the issue/request right from chat, to get immediate context.
Sean Stangl (Dec 16 2019 at 21:18):At least for me it has been a very effective way of working. Without it I miss basically everything.
Dan Gohman (Dec 16 2019 at 21:20):#git-cranelift here in zulip sounds like something worth trying
Sean Stangl (Dec 16 2019 at 21:22):The instructions for doing that are here: https://bytecodealliance.zulipchat.com/integrations/doc/github
It would require a Zulip administrator to set up an incoming webhook bot. (Ours was just named the equivalent of "GitHub.") That generates an incoming URL.
The Admin then hands that URL to a Cranelift repo maintainer, who follows the rest of the instructions in GitHub, by going to Settings -> Webhooks.
Dan Gohman (Dec 16 2019 at 21:40):I'm not a zulip admin here, so I'll ping @Till Schneidereit who can hopefully look into this
Benjamin Bouvier (Dec 17 2019 at 09:43):Note that Escape followed by "?" will show you many (so many!) keyboard shortcuts one can use to navigate between streams and topics.
Akshat Agarwal (Feb 28 2020 at 11:12):Hello everyone I am Akshat Agarwal (@humancalico). I have been interested in WebAssembly for a while now and understand why it's needed. But what I don't understand is why do we need it to run outside of the browser. Is the similar like the Node's JavaScript everywhere paradigm or is there a greater reason behind it? Thank you in advance
Till Schneidereit (Feb 28 2020 at 12:08):Hi Akshat, and welcome! The announcement post for the Bytecode Alliance gives a good overview of some of the most important reasons for doing all this: https://bytecodealliance.org/articles/announcing-the-bytecode-alliance
Last updated: Dec 23 2024 at 12:05 UTC