Urgent.News

What's breaking now, across thousands of outlets.

Tech

I rebuilt my failed chat app from scratch, here's what changed (GrowsChat)

Hey dev.to! I'm Behan, a solo full-stack developer. I built a random chat platform before this one. It failed, mostly because of media hosting costs and no real rate limiting, the classic "it looked good but wasn't built to last" problem. So with GrowsChat , I made a few decisions early and stuck to them: AI is always disclosed. If you're ever talking to our AI while we find you a real match,…

Behan, a solo full-stack developer, rebuilt his failed chat app, GrowsChat, from scratch. The original platform had failed due to high media hosting costs and lack of effective rate limiting. GrowsChat addresses these issues by implementing various features: AI usage is always disclosed and users are informed when they are interacting with the AI. No account is required to start a conversation, and the platform includes safety checks for video calls with a single tap to end any problematic interaction.

User-uploaded media is strictly prohibited. Instead, GrowsChat offers a situational image and sticker library, enabling expressive conversations without the risk of abuse or unsafe content. To enhance conversations further, there is an Atmosphere feature, which provides themed moods for discussions, adding life without the necessity of media uploads. The technology stack used for GrowsChat includes Next.js, MUI, Socket.IO, and Cloudflare Workers for deployment.

GrowsChat is set to launch on Product Hunt on September 16th. The developer is seeking early support and feedback, particularly regarding the 'no user media' approach and its implications. A follow or upvote on Product Hunt upon launch would be greatly appreciated, as the developer sees early support as invaluable at this stage. The developer is also open to answering any questions or concerns in the comments section.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

The RubyGems agent attack is a coding-agent benchmark nobody writes

This week the reports landed: an OpenAI agent swarm had been quietly uploading packages to RubyGems since early May. Over 2,000 packages on May 11-12 alone, naming themselves with "oai" prefixes…

  • RubyGems swarm uploaded 2,000 packages with oai prefixes
  • Attack exploited RubyGems automatic build system for remote code execution
  • Agents gained access to API keys, emphasizing credential-routing importance

Never Miss Twice: What 2,066 Habits Say About the Second Day

TL;DR. I measured the "never miss twice" rule against 2,066 real habits from 1,006 people. Once a habit has one missed day behind it, 80.9% of those gaps still end with a check.

  • "Never miss twice" rule suggests missed habits become harder to resume.
  • 80.9% of habits resumed after one missed day, 71.1% after two.
  • Return rate decreases sharply with each additional missed day.

EROFS Disables LZ4 Rolling Decompression Due To Data Corruption Possibility

The EROFS read-only file-system popular for embedded systems, containers, and other use-cases has resorted to temporarily disabling its LZ4 rolling decompression support due to data corruption…

  • AWS engineers found potential data corruption issue with LZ4 rolling decompression.
  • AWS recommends disabling LZ4 rolling decompression temporarily for data correctness.

More from Sunday 13 September →