Not enough discussion here of the parts under "Our Optimization Strategies", which was the most interesting to me. Assorted reactions: > We found that react-icons had an issue that lead to everything being imported. This meant that we were including every single react-icon in our package whether we need it or not. Kudos to the Linen team for proactively finding this - I have a feeling tons of projects blindly trust t…
With icons, I've stopped using icon libraries a while back and now import just the SVG code that I need. I'm a big fan of Hero Icons[1] and they offer a way to quickly copy JSX or SVG code to the clipboard to faciliate this workflow. [1]: https://heroicons.com/
Linen.dev: A 500 kb Slack alternative
101–110 of 219 posts
Re: Linen.dev: A 500 kb Slack alternative
#102Wouldn't it be possible to make an IRC client+server that's a perfect clone of Slack? I guess you'd need a SIP plugin for huddles.
Re: Linen.dev: A 500 kb Slack alternative
#103Earlier quoted context omitted.
The UI package appears to use Rollup. And this looks like the PR for the icons update: https://github.com/Linen-dev/linen.dev/pull/1001
they had to change every import for an icon in 60 files. Wouldn’t it have been better if a PR was done against Rollup to fix this “bug”? probably much more difficult/not possible?
Unfortunately, the current state of ESM in Node is such a mess that you can't assume most packages are tree-shakeable. There is package.json metadata to do that.
It's more likely to be a "simple" bug (with far reaching consequences) in react-icons' package.json and/or build process.
Taking a quick glance at https://github.com/react-icons/react-icons/blob/master/packa...
Yeah, it's using the old non-standardized "module" field as opposed to the modern and mostly standard (now at least) "exports" field [1] or "type" field.
"exports" would be a quick fix of the existing package.json file with no other changes to the build process, but given this is a UI package intended primarily for browser usage I'm having a hard time understanding why it bothers to include CommonJS at all and isn't just `"type": "module"` and remove CommonJS from the build entirely.
That probably points to why this hasn't been done yet: it gets into a bikeshed argument and a lot of potential discussion on big changes to a presumably "not broke" build system.
[1] https://nodejs.org/api/packages.html#packages_exports
(ETA: Existing Issue on this subject in that repo: https://github.com/react-icons/react-icons/issues/717)
Re: Linen.dev: A 500 kb Slack alternative
#104We 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.
I've recently launched HN+ https://www.hn.plus For anyone interested in HN-type forums (with lots of other features we've built)
Obviously HN+ is missing the single most important thing about HN, the users.
Also, did you really have to steal the name too? Would probably been better off if you called it something different.
By the way, you should read your own terms of service and maybe start following it yourself if you ask others to follow it too?
> Your site is not getting advertised via unwanted electronic messages such as spam links on newsgroups, email lists, other forums and web sites, and similar unsolicited promotional methods;
> Your site is not named in a manner that misleads your readers into thinking that you are another person or company. For example, your site’s URL or name is not the name of a person other than yourself or company other than your own; and
Re: Linen.dev: A 500 kb Slack alternative
#105this is very cool! what things of slack does it NOT have - genuine question here. Like private channels, etc etc ? can it replace slack basically ? what will i have to do ?
Re: Linen.dev: A 500 kb Slack alternative
#106How does this compare to Ripcord[0]? Granted there haven't been any new releases of Ripcord in a couple of years, it's super lightweight and mostly perfect for my uses. [0]: https://cancel.fm/ripcord/
> Ripcord is a desktop chat client for group-centric service apples and oranges? Also, I seem to recall there was some drama about if one used Ripcord against a Discord server, it resulted in your account getting banned
Re: Linen.dev: A 500 kb Slack alternative
#107I won’t run any apps over 480 KB unfortunately.
Re: Linen.dev: A 500 kb Slack alternative
#108Earlier quoted context omitted.
I've recently launched HN+ https://www.hn.plus For anyone interested in HN-type forums (with lots of other features we've built)
Hmm, I feel like this could do with a different colored top bar. Making it look exactly like HN makes me feel more like ‘why not use HN then’?
Re: Linen.dev: A 500 kb Slack alternative
#109Earlier quoted context omitted.
I don't want to host a server and I want my messages to be synced between multiple devices including mobile ones. I want rich messages, images, links. I want threads.
> I don't want to host a server Given that we're talking about search-engine-visible logs - just use an existing, public server. > I want my messages to be synced between multiple devices including mobile ones. I actually believe it's better for people _not_ to have Slack on their mobile, so as not to be pestered, but if that's what you want, then you want the "fancy" alternative. Matrix clients can offer you that. >…
Re: Linen.dev: A 500 kb Slack alternative
#110Earlier quoted context omitted.
We do have a paid offering. Basically it's free on Linen's domain for public communities and we let you host on your domain like: https://archive.pulumi.com/ https://linen.prefect.io/ https://slack-chats.kotlinlang.org/
And you guarantee in writing that this pricing structure will never change?