Live data from Hacker News

Linen.dev: A 500 kb Slack alternative

linen.dev

1–10 of 219 posts

Re: Linen.dev: A 500 kb Slack alternative

#3
post #2

The size is only one of the factors, it can be small but slow, especially when the history grows.

Definitely. This is why we also do things like optimistic updates, setting query performance alerts, and when possible reducing as much DOM elements.

Re: Linen.dev: A 500 kb Slack alternative

#4
A lot of people already "live" in Slack (i.e., slack has a 'network effect', same with Discord) and so naturally I think people are more likely to engage with my community on a tool they are using because of work (their company is on slack). How does Linen think about addressing that concern?

disclaimer: OSS founder here that cares a lot about managing community!

Re: Linen.dev: A 500 kb Slack alternative

#5
the Show HN: https://news.ycombinator.com/item?id=33248488 and there was another thread last year for their main domain https://news.ycombinator.com/item?id=31494908

I wish all the locked away Slack communities would use Linen[1] because there are so many nuggets of bug-fixery buried in Slack that will age off or never be found in the horrors of Slack search

1: I really wish they'd just stop using Slack entirely since Zulip is open source and bundles this "allow search engine indexing" built-in, but I think that ship has sailed

Re: Linen.dev: A 500 kb Slack alternative

#6
We actively evaluated Linen in launching our community. Although, we went with discourse as we are going for a forum type community platform but Linen certainly has fantastic potential.

One very minor friction point with Linen was, it needs to be a bit transparent about their pricing for business tier. I don't think "contact us" pricing strategy is the perfect fit Linen's target audience.

Re: Linen.dev: A 500 kb Slack alternative

#7

A lot of people already "live" in Slack (i.e., slack has a 'network effect', same with Discord) and so naturally I think people are more likely to engage with my community on a tool they are using because of work (their company is on slack). How does Linen think about addressing that concern? disclaimer: OSS founder here that cares a lot about managing community!

Sure thing! We support a two way sync between Slack and Discord so using Linen doesn't mean you have to migrate off of either. The end goal here is that we eventually build enough features that more and more people would prefer Linen in the long term.

We think that there is a better chat app out there that isn't built yet that handles things like: 1. A non chaotic notification system. Slack and Discord stresses me out. We want to introduce things like !mentions which sends you a push notification and @mention notifies you but doesn't interrupt you. 2. Better thread and content management. Things can get messy in Slack and that you can't find information. We give you ability to move threads and messages around to help organize that and we want to do more to help people find content. 3. More power user features: Slack is probably the most used app for a lot of us and I don't think it is optimized for individual productivity. We want to build something that is designed for our productivity. Something along the lines of Linear or Superhuman.

Re: Linen.dev: A 500 kb Slack alternative

#10

We actively evaluated Linen in launching our community. Although, we went with discourse as we are going for a forum type community platform but Linen certainly has fantastic potential. One very minor friction point with Linen was, it needs to be a bit transparent about their pricing for business tier. I don't think "contact us" pricing strategy is the perfect fit Linen's target audience.

Sorry about that. It was a vestige of Linen's first version being very Enterpise sales heavy and we haven't updated it. At the moment it is 150/month for 5000 members for our paid tier and 50/month more for every 5000. Will update it this week!

We just shipped our self checkout flow last week: https://github.com/Linen-dev/linen.dev/commit/61c482cab5d5aa...

Just hadn't got the chance to update it on the landing page yet

Post reply on HN