Earlier quoted context omitted.
It sounds like what should be brought back is NNTP or mailing list.
I think of Booklet as a better mailing list
Can Slack-mania be cured with systemized discipline?
111–120 of 205 posts
Re: Can Slack-mania be cured with systemized discipline?
#112I'm tired of constant chatting. Slack encourages quick, stream-of-consciousness, short responses. Plus, it's hard to find past discussion, and it's hard to jump in after being gone for a few days (or, even a few hours). Threads are absolutely the answer. But, the defaults matter - Slack isn't encouraging threaded, long-form messages. Instead, it makes all messages feel urgent - and it makes the cost of sending a mess…
Re: Can Slack-mania be cured with systemized discipline?
#113Re: Can Slack-mania be cured with systemized discipline?
#114Earlier quoted context omitted.
I’m interested in your idea, bringing what we’ve mastered in chat to the forum, but I don’t want to give my phone number or spin up a forum just to see. Is there an example forum?
I've been posting updates here, where you can see a demo: https://bookletupdates.substack.com I'm working on "public" groups, so that I can link directly to a meta group about the project from the homepage. It should be live early next week! -- I'm using phone number as primary login for these reasons: 1. I want passwordless login 2. Passwordless login with email is confusing because most people have multiple emails.…
Re: Can Slack-mania be cured with systemized discipline?
#115Earlier quoted context omitted.
I have tried Zulip but I think Twist has better UX & UI. https://twist.com/slack-alternative Supported by Doist which also supports Todoist which I am using
I've used Twist. It's a good piece of software, but I think it's too work-focused. Consumerization of Enterprise is real - people don't want work to feel like work. Even Slack is more of a social tool than a work tool [1]. So, I think that the key to building a great work-focused tool is to start on non-work use cases - such as social groups. Looking at Twist - I don't think it emphasizes usability, users in multiple…
I've been thinking about this as I build a slack-meets-twitter like chat platform for public discourse (https://sqwok.im) and have had a few ppl ask if they could use it for a work communication tool.
It isn't my primary vision but it is something I've been thinking about and def open to hearing if other people would be interested in that.
I'll have to check out twist, had never heard of it!
Re: Can Slack-mania be cured with systemized discipline?
#116I'm tired of constant chatting. Slack encourages quick, stream-of-consciousness, short responses. Plus, it's hard to find past discussion, and it's hard to jump in after being gone for a few days (or, even a few hours). Threads are absolutely the answer. But, the defaults matter - Slack isn't encouraging threaded, long-form messages. Instead, it makes all messages feel urgent - and it makes the cost of sending a mess…
The sign up flow is really not great. Pick one and stick with it, but having to do “Phone Number” click “Insert verification code” click “Email” click, “Enter verification code” click. Either defer email verification, or get rid of phones altogether. It’s a forum, I’m not expecting replies in texts hopefully.
Re: Can Slack-mania be cured with systemized discipline?
#117I'm tired of constant chatting. Slack encourages quick, stream-of-consciousness, short responses. Plus, it's hard to find past discussion, and it's hard to jump in after being gone for a few days (or, even a few hours). Threads are absolutely the answer. But, the defaults matter - Slack isn't encouraging threaded, long-form messages. Instead, it makes all messages feel urgent - and it makes the cost of sending a mess…
My friend works at a company that -- on orders from legal -- has set a 5-day "disappearing messages" policy for all of the corp Slack. Unfortunately nearly all technical discussions happen on Slack. He tells me that it's not unusual for messages to start disappearing before the issue being worked on has even been resolved, and everyone has to re-ask the same questions and re-post the answers at that point, and someti…
Re: Can Slack-mania be cured with systemized discipline?
#118I'm tired of constant chatting. Slack encourages quick, stream-of-consciousness, short responses. Plus, it's hard to find past discussion, and it's hard to jump in after being gone for a few days (or, even a few hours). Threads are absolutely the answer. But, the defaults matter - Slack isn't encouraging threaded, long-form messages. Instead, it makes all messages feel urgent - and it makes the cost of sending a mess…
My friend works at a company that -- on orders from legal -- has set a 5-day "disappearing messages" policy for all of the corp Slack. Unfortunately nearly all technical discussions happen on Slack. He tells me that it's not unusual for messages to start disappearing before the issue being worked on has even been resolved, and everyone has to re-ask the same questions and re-post the answers at that point, and someti…
In my office, Slack messages that live forever don't stop people from asking questions that have already been answered. The search tool is an afterthought.
Re: Can Slack-mania be cured with systemized discipline?
#119Slack is a pox. It's not just about endless notifications that kill your ability to focus, it's an environment that actively encourages organizational anti-patterns. If you have a question, first you ask your manager. If Slack makes it easy to reach out to someone directly, your manager will tell you to Slack them. If you don't have Slack, and you don't have people's phone numbers, instead you get directed to documentation / wiki / support ticketing.
Organizational choice architecture matters. Slack makes bad choices easy and good choices difficult. That's enough reason to ditch it.
Re: Can Slack-mania be cured with systemized discipline?
#120Earlier quoted context omitted.
I don't understand the love of email. It's little pieces of conversations that get sent around in an ad hoc way. Email doesn't have an easy way to add someone to a thread, or to manage a forked conversation. It's closed and non-discoverable by default.
> Email doesn't have an easy way to add someone to a thread You add them to the cc list. > or to manage a forked conversation. Your email client is at fault there, any decent email manages forked conversations. > It's closed and non-discoverable by default. Thats why you have mailing lists which are indexed and searchable. You may see 'closed and non discoverable' as a downside, I do not. Anything that should be disc…
I have very minimal experience using email, but doesn't this just add them to a new message as opposed to adding them to old messages?