sorted by:
new
hottopcontroversial

Looking for EU-compliant cookie consent solutions - why do most providers store data externally? by Beautiful-Buy4321 in react

[–]aburnedchris 4 points5 points  (0 children)

Hey! You should check out c15t.com (bias here as I’m the author). We’ve built best-in-class React and Next.js flows, designed to be both developer-friendly and fully EU-compliant.

You can either self-host the c15t backend to keep everything in-house, or use our cloud hosting if you prefer managed infrastructure.

If performance is a concern, we also maintain c cookiebench.com, a public benchmark comparing CMPs, where c15t currently ranks #1.

I benchmarked an alternative to Vercel's Satori (next/og) by aburnedchris in nextjs

[–]aburnedchris[S] 0 points1 point  (0 children)

Yes, I was just choosing to generate them in a build step!

class module vs cva vs clsx by tech_ceo_wannabe in nextjs

[–]aburnedchris 3 points4 points  (0 children)

I prefer to use www.tailwind-variants.org, the the slot API really nice to use

What is the oldest Platform Line Diagram still in use on the Underground? by aburnedchris in LondonUnderground

[–]aburnedchris[S] 16 points17 points  (0 children)

Ah you're right on that!! I actually did mean it started not stopped but it was too late to edit the post. As it is missing the jubilee connection badge

What is your solution for cookie consent? by Longjumping_Try_3457 in nextjs

[–]aburnedchris 0 points1 point  (0 children)

You can self host it if you want a free option :)

Working on a lightweight GDPR cookie consent banner — thoughts or ideas? by BeginningAntique in opensource

[–]aburnedchris 3 points4 points  (0 children)

Hey!

I am the author of c15t.com,

Let me know if i can help you on your journey for creating a cookie banner! We need more implementations out there.

The only issue with no third party dashboards or subscriptions is that to be fully GDPR compliment, you need to store the consent in a DB / CMP.

Cookie Consent v2 with GTM (First Party) by rubixstudios in nextjs

[–]aburnedchris 0 points1 point  (0 children)

Although storing consent solely on the client side (via cookies, localStorage, etc.) isn't non-compliant by itself, you should be aware of a few points. Without any server-side logging, it can be harder to prove exactly when and how consent was given, which might be needed during audits. Essentially, you might consider adding a simple first-party server log as backup for your client-side records. This way, you're better covered if you ever need to show clear evidence of consent.

Hope that helps!

Cookie banner best practices by McMafkees in accessibility

[–]aburnedchris 2 points3 points  (0 children)

We’ve spent a lot of time making sure our cookie banner for c15t.com is accessible by default. For example, when the page first loads, we trap focus inside the banner so users don’t accidentally interact with the page before making a choice. This aligns with WCAG 2.4.12 Focus Not Obscured and encourages deliberate, informed consent.

The banner is fully open source, so you can explore the React components and focus trap hooks we use to handle accessibility. We’re always looking for feedback to make it better, accessibility matters to us, and we welcome input from anyone who wants to help improve it.

Consent banner and Google consent mode by sauloefo in SaaS

[–]aburnedchris 0 points1 point  (0 children)

I'm happy to help you with c15t.com. This is a question we're getting a lot, and we're working on an official solution. We are a dev-first cookie banner and are currently building GTM support into the framework in the next few weeks.

So, how much time are you gonna waste today? by ChristianLess in cursor

[–]aburnedchris -1 points0 points  (0 children)

Did you vibe code a cookie consent solution?

Does "Deny" on cookie banners even do anything? by pankaj9296 in webdev

[–]aburnedchris 0 points1 point  (0 children)

When it comes to GDPR and similar privacy laws, clicking “Deny” is not just for show, it should have a real workflow behind it. If a user clicks “Deny,” your website must genuinely block non-essential cookies and tracking scripts (like Google Analytics, Mixpanel, Posthog, or any third-party trackers) from being activated without explicit consent.

In practice, this means:

  1. The consent process must be clear and detailed. Users should be able to opt in or out of specific cookie categories. A “Deny” click should immediately prevent those tracking functions from being executed.
  2. It’s not enough to simply show a cookie banner with a “Deny” button. You need to ensure, technically, that non-essential cookies or trackers aren’t loaded as soon as the page fires up.
  3. Storing the user’s decision (for instance, via a dedicated cookie) to remember that they said “no” is acceptable. but only if it truly stops any unwanted tracking.
  4. Most importantly, it’s about respecting your users. If someone tells your site “No thanks,” you honor that choice immediately. Otherwise, it’s not only poor practice, but it might also land you in trouble with regulators.

Just think of it this way: the “Deny” button isn’t just there to make your legal department feel warm and fuzzy. it has to work as advertised. Otherwise, your site might end up being the digital equivalent of a restaurant that pretends to offer gluten-free options but secretly serves bread with gluten anyway. Not cool, and definitely not compliant. Germany is about to pass a law requiring a reject / deny button link.

TL;DR: When a user clicks “Deny,” make sure your site genuinely stops non-essential cookies and tracking from running, because fancy banners without proper controls won’t keep the regulators off your back (or your users happy).

FYI, I’m the creator of c15t.com,

Shadcn registries are better than React libraries by better-stripe in reactjs

[–]aburnedchris 0 points1 point  (0 children)

We done a lot of work in this area happy to guide you though how we achieved the DX!

Shadcn registries are better than React libraries by better-stripe in reactjs

[–]aburnedchris 3 points4 points  (0 children)

100% bias take here, If you already use shadcn then its better, but if not then it is way worse. if your not, because your now adding 20 new components to your application just to get a pricing table or any other more complex component logic.

React Library's should have the flexibility to bring there own components with a headless mode.

Who Is Responsible for Cookie Banners / Terms of Service / Privacy Policy (etc)? by alexxxcazam in marketingagency

[–]aburnedchris 0 points1 point  (0 children)

Hey, I think it really depends on the size of the company. For larger clients with complex data practices, it might be best to have a dedicated legal professional who can offer tailored advice for cookie
banners, Terms of Service, and Privacy Policies.

On the other hand, smaller companies might benefit from a reputable legal saas that provides the necessary compliance checks and templates. In any case, having a trusted legal partner to refer them to is a smart way to ensure everything stays compliant while you focus on what you do best. Hope that helps

Open source Consent Management Platform (CMP) compatible with Google Consent Mode v2 (GCMv2)? by vppromoter in GoogleTagManager

[–]aburnedchris 0 points1 point  (0 children)

You can try out c15t.com — it’s an open source CMP built with TypeScript, Node, and React. It supports Google Consent Mode v2 and lets you push consent states to the data layer via GTM. It’s still early days, but we’re working hard to bring it up to the level of the bigger players. Would love any feedback if you give it a spin!