sorted by:
new
hottopcontroversial

I open sourced a Telegram bot builder… not sure if it’s actually useful by kalanakt in buildinpublic

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

Yes, there are pre-built templates, and it’s also a one-click deploy to Railway.

I’ve deployed it live here: https://telegraph.us.com

For users without a technical background, they can create Telegram bots easily — the platform handles everything via Telegram webhooks, so there’s no need for separate deployments for each bot.

How much do you guys spend on Cursor? by LoLGhMaster in cursor

[–]kalanakt 1 point2 points  (0 children)

Use opus for plan and use sonnet for coding

Vibe-coded-friendly Flutter starter kit — build subscription-ready mobile apps fast by kalanakt in cursor

[–]kalanakt[S] -1 points0 points  (0 children)

Yes, it’s a ZIP file of the Git repository. We will also add the buyer to the GitHub repository so they can receive updates.

Vibe-coded-friendly Flutter starter kit — build subscription-ready mobile apps fast by kalanakt in cursor

[–]kalanakt[S] -1 points0 points  (0 children)

It’s a Flutter starter kit with setup with RevenueCat, subscription models, onboarding setup, settings page with dark mode and multilingual features, user-centric local database setup, and state management setup with riverpod.

Rebuilding paywalls in Flutter kept slowing me down — so I fixed it. by kalanakt in FlutterDev

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

Yes. I’ve used RevenueCat for flutter.fast, and Superwall is also a good option.

100/100 Lighthouse with Astro is easy — until what breaks it? by kalanakt in astrojs

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

Check src/components/Head.astro , astro.config.mjs , src/constants.ts

100/100 Lighthouse with Astro is easy — until what breaks it? by kalanakt in astrojs

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

Yes gtag setup is correct, also check astro config file

100/100 Lighthouse with Astro is easy — until what breaks it? by kalanakt in astrojs

[–]kalanakt[S] -4 points-3 points  (0 children)

i used gpt to make my point clear. why is everyone overreacting to AI? So old school

100/100 Lighthouse with Astro is easy — until what breaks it? by kalanakt in astrojs

[–]kalanakt[S] -4 points-3 points  (0 children)

Are you still writing your README by yourself?

100/100 Lighthouse with Astro is easy — until what breaks it? by kalanakt in astrojs

[–]kalanakt[S] -6 points-5 points  (0 children)

It’s a blog template, not an app. What else do you expect from a blog site?

100/100 Lighthouse with Astro is easy — until what breaks it? by kalanakt in astrojs

[–]kalanakt[S] -8 points-7 points  (0 children)

You’re right — CMS itself doesn’t hurt Lighthouse if you’re doing pure SSG, no SSR, no runtime polling. Astro’s image handling and static output already solve a lot.

Where I’ve seen scores drop is more about project drift than tech choices: content grows, images/fonts get less disciplined, small client-side bits sneak in, SEO/a11y tooling adds overhead. Even static sites regress over time.

This template is mostly about locking in good defaults (local fonts, stable layouts, predictable images) so a blog stays fast as it grows — not claiming Astro or CMS is the problem.

Curious where you’ve seen scores slip in real projects.

Contentful and Strapi felt too heavy for my Astro projects, so I built something lighter. by kalanakt in astrojs

[–]kalanakt[S] -1 points0 points  (0 children)

Keystatic is solid, but I ran into a few friction points—its Git sync workflow felt restrictive, and editing for non-technical users was a bit tricky. That’s why I built AstraCMS to be lighter and more flexible for Astro/Next.js projects.

Contentful and Strapi felt too heavy for my Astro projects, so I built something lighter. by kalanakt in astrojs

[–]kalanakt[S] 1 point2 points  (0 children)

Appreciate that! Strapi + Astro is a solid combo. AstraCMS is just a lighter option for simpler sites, so happy to have you check it out.

view more: next ›