tiptap VS realtime

Hey HN, Philip here, Co-founder at Tiptap (https://tiptap.dev/).

We just shipped an upgrade to our DOCX import and export capabilities, including new extensions, new endpoints, better formatting handling, and custom node support. This may be for you if your product deals with Microsoft Word files in any way.

We rebuilt our DOCX handling pipeline to give developers more control and flexibility:

- Import endpoint: Converts .docx to Tiptap JSON, accurately handles complex formatting (lists, tables, inline styles).

- Export extension: Generates .docx from your editor content, including custom nodes.

- Custom node support: Map internal components (e.g. callouts, embeds) to standard DOCX structures.

- Style control: Define exactly how DOCX output should look to match your app’s UI.

- Frontend or backend: Run conversion wherever it makes sense for your setup.

- Image upload handling: We give you hooks to manage storage your way.

What's still on the roadmap:

1) Import and export of DOCX headers and footers

2) Import and export DOCX pagination

3) Import and export comments, version history, and suggestions

Developer Docs: https://tiptap.dev/docs/conversion/import-export/docx

Product Website: https://tiptap.dev/product/conversion

We’d love your feedback! If you’ve struggled with document conversion (or just want to nerd out a bit), let us know your thoughts and experiences.

Show HN: Tiptap Editor 3.0 Beta is out.

Hi HN! Philip here from Tiptap (https://tiptap.dev/). We're excited to announce Tiptap 3.0 Beta, a major upgrade built with and for the open source community. It's still extension-based, still unopinionated, but we've tackled some of the biggest developer headaches:

Enhanced TypeScript support:

Hi, Philip here from Tiptap. We just released a new set of open source UI components for [Tiptap](https://tiptap.dev/), our headless text editor framework.

These are handcrafted React components that integrate directly with Tiptap’s headless core, things like toolbars, dropdowns, formatting buttons, upload controls, etc. They’re MIT licensed and fully optional. You can use them as-is or customize every part.

There’s also a CLI that sets everything up for you: project scaffolding, recommended defaults, and a working example.

This is for folks who like the flexibility of Tiptap but don’t want to start from zero every time they need an editor UI. It doesn’t change how Tiptap works – just gives you a faster way to build on top of it.

Start here:

Thanks! I built the editor using Tiptap (https://tiptap.dev/) which doesn't support Markdown out of the box. However, since it can detect Markdown shortcuts (#, ##, >, etc.), it should be possible to convert a markdown file into rich text, and then when done writing and editing convert it back into markdown, while limiting formatting options only to ones that are available for both. I think Joplin (https://joplinapp.org/) does something similar.

I'll think about this for sure, especially since I've been thinking of making it possible to save and read local files. If you'd like to try Gorby, send me an email and I'll be happy to give you a free license code :)

While Storyblok and Builder.io offer full-page editing experiences with structured CMS capabilities, Tiptap takes a different approach. It’s not a traditional page builder but rather an embeddable headless editor built on ProseMirror. This means that instead of giving you a predefined UI to work with, it provides the underlying logic, leaving you in full control of the interface, interaction and level of functionality you want to provide in your page builder.

There are paid tools available. For example, the Tiptap rich text editor is free to use, but some advanced features and APIs are paid for. For example, the cursor editor heavily relies on AI capabilities, so it requires payment for use.

Novel is an open-source Notion-style WYSIWYG editor with AI-powered autocompletion. This built on top of TipTap. Tiptap is the headless and open source editor framework. Integrate over 100+ extensions and paid features like collaboration and AI agents to create the UX you want.

For more, visit the official TipTap website. Did you learn something new from this article? Let me know in the comments! 🎉

Tip Tap Library

We are starting to add OpenTelemetry support to all our core products and our Telemetry server. OpenTelemetry (OTel) standardizes logs, metrics, and traces in a vendor-agnostic format, so you can ingest data into tools like Datadog, Honeycomb, or any monitoring solution you already use. While you'll still have the freedom to bring your own observability stack, we're preparing to surface this data natively in the Supabase dashboard.

Discover use cases for Supabase Realtime Read the Supabase Realtime documentation to learn more Sign up for Supabase and get started today

Supabase | Senior Elixir Engineer | APAC | Remote | https://supabase.com/

We're hiring to grow our Elixir teams mainly on Supavisor and Realtime projects. You will be using Elixir and also help build new client libs mainly in TS. We work in an opensource manner so you can check our code in https://github.com/supabase/realtime and https://github.com/supabase/supavisor.

* Senior Elixir Engineer: https://jobs.ashbyhq.com/supabase/46ffc00b-b9a7-4b45-a6f2-1a...

Any question, email me at [email protected]

supabase/realtime

Supabase has a feature called Postgres Changes, which is part of their realtime product offering. It allows you to listen to changes that happen in a single table, and send those changes to clients that are allowed to receive them.

So this cool low-code no-code platform provides a realtime feature that lets you do a bunch of stuffs:

You can LISTEN/NOTIFY. Or you can use logical replication and a custom subscriber.[1] Supabase uses the latter.[2]

[1]: https://www.postgresql.org/docs/current/logical-replication....

[2]: https://github.com/supabase/realtime

Supabase Realtime is great for building collaborative applications. You can receive database changes over websockets, store and synchronize data about user presence, and broadcast any data to clients via "channels".

We use :telemetry to collect usage data per tenant for Supabase Realtime.

We do this for rate limiting but it also makes it very easy for us to attach a listener (https://github.com/supabase/realtime/blob/main/lib/realtime/...) which ships these (per second) aggregates to BigQuery (via Logflare), which then the billing team can aggregate further to display and actually bill people with.