@LiorOnAI — Reflection-Tuning: open-source models fixing their own mistakes
This is huge. A new technique called Reflection-Tuning allows open-source models (Llama 3.1 70B) to outperform Claude 3.5 and GPT-4o.
This new technique trains the model on structured, synthetic data to detect reasoning errors and enable LLMs to fix their own mistakes.
That's the part worth watching — not "open source beats proprietary" headlines, but that structured synthetic data for error detection is the lever. If the technique holds up at smaller scales it means alignment-style training loops are available to anyone with a fine-tuning budget.
@rohanpaul_ai — Fish Speech 1.4: compact multilingual TTS with voice cloning
The new open-source Text to Speech model: Fish Speech 1.4 is brilliant!
Trained on a massive 700K hours of multilingual speech data in 8 languages
- Instant voice cloning 🗣️
- Ultra-low latency ⚡
- Compact model (~1GB weights) 🏋️♂️
Sub-1GB weights for an 8-language TTS model trained on 700K hours is genuinely compact. The voice cloning story is interesting — most alternatives that size either sacrifice quality or lock you to one language. I haven't run benchmarks on the latency claims yet.
@omarsar0 — Claude's summary of Anthropic's prompt engineering deep dive
Anthropic's recent AI Prompt Engineering deep dive is a must watch!
Here's Claude's summary of the mentioned prompting techniques and tips:
Smart move — use the model itself to distill the prompting guide for the model. The meta layer aside, Anthropic's prompt engineering docs are dense enough that a structured summary is actually useful. If you haven't read the original, the summary is a fast entry point.
@nikelsnik — Next.js form handling stack
My go-to method for handling forms in @nextjs
- react-hook-form -> form handling 📋
- zod -> validation ✅
- shadcn/ui -> UI components 🧱
- next-safe-action -> server actions ☁️
- sonner -> success/error toast messages 🍞
next-safe-action is the piece most people are missing from this stack. It wraps server actions with input validation, typed errors, and pending state — things you'd otherwise wire up manually. The combo of zod + next-safe-action means validation runs server-side too, not just in the form.
@aykutkardas — First custom shadcn component shipped as open source
I have released my first custom @shadcn component as open source. 🎉 You can directly download it to your @nextjs project using shadcn cli. ✨
The distribution model here is what's interesting — shadcn CLI as a package manager for components means no npm dependency to maintain, you just copy source into your project. More people are shipping components this way, which makes the ecosystem more composable even if discoverability is still rough.
@sujjeeee — Supabase Google OAuth callback: blocking non-registered users
Authentication tip w/ @supabase!
Google OAuth callback checks to block non-registered users.
Small but practical: the default Supabase OAuth flow creates a new user for every Google login. If you want invite-only or closed-beta access, you need a callback that checks against an allowlist before the session is persisted. This is that check.
@linear — Parent & sub-issue automations
New: Parent & sub-issue automations
[→] Navigate to Team Settings to activate [↓] Follow instructions to get started
Honestly just saved this to go set it up. Auto-closing a parent when all sub-issues are done is one of those things that sounds simple until you're manually doing it every sprint.
@alexxubyte — 8 network protocols in one diagram
Explaining 8 Popular Network Protocols in 1 Diagram.
Network protocols are standard methods of transferring data between two computers in a network.
- HTTP (HyperText Transfer Protocol) HTTP is a protocol for fetching resources such as HTML documents. It is the foundation
Makes sense as a reference rather than new information — the value is having HTTP, WebSocket, gRPC, MQTT, and friends laid out comparably so you can see the use-case splits at a glance. Good thing to have bookmarked when explaining protocol choices to someone who asks why not just use REST for everything.
@sahnlam — How HTTPS works, step by step
How HTTPS works
HTTPS (Hypertext Transfer Protocol Secure) is a secure way to share information on the internet. It encrypts data transfer between client and server.
But without common encryption key, how data is encrypted?
Let's see how:
1 - Server Certificate Check
The TLS handshake is one of those things engineers nod along to without being able to explain key exchange on demand. A clear walkthrough of certificate verification → cipher negotiation → session keys is useful to have around.
@johnrushx — 369 open-source alternatives to paid tools
369 Open Source alternatives to tools you pay for:
No framing, no description, but 369 alternatives organized well enough to be a real reference. Worth pulling up before renewing a SaaS subscription you're not sure about.