CommentBox.io VS Kitemaker

Could you embed a web object? Maybe use something like this: https://devilpenakut.medium.com/free-comment-widget-for-websites-and-blogs-574aca4341f (free) or this: https://commentbox.io/ (not free but fairly cheap and more control). Source: about 1 year ago

Ooo, you even added in comment boxes, nice! It's the free Comment Box thing, right? I'm thinking of using that for my own neocities site once I get it started up. Source: over 1 year ago

You can use embed pages from community softwares like Discourse or Flarum or you can use HTML Commentbox or you can just build your own commenting system (it's not that hard). Another option can be Commentbox but it requires external login but only allows third-party auth and has lots of options like Twitter, FB, Google, Github etc. Source: almost 2 years ago

For regular comments (and not like a guestbook/chat or something) I see a lot of people using commentbox https://commentbox.io/. Source: almost 2 years ago

- Not familiar with n8n.io, looks like it's similar to Zapier. We don't have any integration like this yet, but most functional components that you can add to your Typedream site (like forms, waitlist, etc) can be done using HTML embeds. For example, to add a form, you can embed an Airtable form in your Typedream site. This means that any automation supported by those tools can be used. With that said,... - Source: Hacker News / over 2 years ago

When we built Kitemaker [0] we elected to not use CRDTs. We built our sync engine after reading the blog article Figma wrote about they didn't need CRDTs because they have the server arbitrating any conflicts. We ended up taking the same approach. It's worked out very well for us though in a tool like our "last one in wins" generally works fine and doesn't lead to a lot of surprises. For documents, we had to do... - Source: Hacker News / about 2 months ago

There is no one-size-fits-all approach to writing descriptions, so you need to figure out what works best for you and your team. However, seeing real-world examples might inspire you to find new ways to write them. Here are some examples from descriptions we have written for Kitemaker. - Source: dev.to / over 1 year ago

Kitemaker.co - Collaborate through all phases of the product development process and keep track of work across Slack, Discord, Figma, and Github. Unlimited users, unlimited spaces. Free plan up to 250 work items. - Source: dev.to / over 1 year ago

At Kitemaker, we recently made the leap to Recoil.js for our React state management needs. Before using Recoil, Kitemaker used a simple state management solution built upon useReducer(). We built Kitemaker to be super fast, responding to every user interaction instantly. However, in organizations with lots of data, we sometimes had a difficult time achieving this due to unnecessary re-renders. Kitemaker has a sync... - Source: dev.to / over 1 year ago

Definitely feel your pain. We did a full OT implementation for our startup [0] and it was a beast. We based it on Slate.js which has a nice concept of operations that maps nicely to OT, but it was still a lot of work to get it working well (and there are still rough edges we try to improve all of the time). We did base it on Postgres in the backend so really looking forward to what the Supabase team comes up with... - Source: Hacker News / over 1 year ago