puck VS privaxy

A more reliable approach is to treat rich text as structured data instead of markup. Explicit content models give applications control over content creation, rendering, and extensibility, while aligning naturally with React’s declarative, state-driven model. In this article, we will explore why rich text editing is hard in React, how structured content helps address these challenges, and how extension-based editors enable safe customization. We will also walk through a step-by-step example using Puck’s rich text editor to demonstrate these concepts in practice.

All field types can now be extended using declaration merging. This is useful for adding strictly typed custom properties to your field configs, such as when using fieldTypes overrides.

You will find slices defined in puck/packages/core/store/slices folder. At the time of writing this article, Puck has the slices shown in the following image.

I run https://www.merklemap.com/ a certificate transparency / subdomain search engine.

I’d say that this kind of projects are not different than any entrepreneurial endeavor, and the biggest challenge is usually acquisition.

I am working on Merklemap, a CT search engine: https://www.merklemap.com/

Same for https://www.merklemap.com/

Biggest table is 27B records, a query that uses a btree index completes in a few microseconds…

    EXPLAIN ANALYZE SELECT * FROM table_name WHERE id = [ID_VALUE];

I thought this was a cool idea, so I looked around for existing implementations and found https://github.com/barre/privaxy

Been a while since the last commit, so I'm not sure if it's maintained, but I might try adding it (or something similar) to my pihole.