u/FrogTalkXYZ

Been building a project called FrogTalk for the last while and it’s finally at the point where other people can actually use it.

The idea started because I was tired of needing 5 different apps just to chat with friends, post stuff, share music, hop in calls, etc. Everything felt fragmented and increasingly hostile to users.

So I built FrogTalk — kind of a mix of Discord, Telegram and a social platform in one app.

Current features:

• End-to-end encrypted DMs
• Group chats + channels
• Voice/video calls
• Social feed + reels
• Stories
• Music sharing/listening together
• Discord & Telegram bridges
• Self-hostable servers
• Web + Android + desktop support

One thing I cared a lot about was not requiring a phone number just to talk to people.

It’s still early and I’m a solo developer, but people are actively using it now and the feedback has been surprisingly good.

Would genuinely love feedback from people here, especially on:

• onboarding
• UI/UX
• what feels unnecessary
• performance issues

Website: https://frogtalk.xyz

Try instantly in browser: https://frogtalk.xyz/app

I'd love an honest read of my privacy policy before I keep growing this thing:

👉 https://frogtalk.xyz/privacy

I'm a solo dev and FrogTalk is a project I just shipped — it's an open, privacy-first chat + social platform. Think "encrypted DMs + voice/video calls + a small social feed with reels & stories + media-watch-together channels + Discord/Telegram bridges," all in one app, no ads, no tracking. Web app, PWA, Android (Play Store), and an iOS build in TestFlight prep.

Because it's brand-new I want to be upfront with users about exactly what hits my server, so I wrote the policy in plain English instead of legalese. Roast it.

TL;DR of what I actually collect:

Account: nickname, hashed password (Argon2), optional email/phone if you set them for recovery, and your public key.

DMs: stored E2E-encrypted (X25519 + AES-GCM, keys never leave your device). I can see who messaged whom and when — I cannot read the contents.

Public room messages: stored in plaintext on the server (they're public by design — like a Discord channel).

Connection logs: IP + user-agent, kept ≤30 days then discarded.

Push: routed via FCM/APNs; payloads do not include DM contents.

Bridges (Discord/Telegram): anything you send through a bridged channel leaves the encrypted boundary on purpose — clearly labeled in the UI.

No analytics. No ad SDKs. No selling data. No third-party trackers. Account deletion wipes everything from Settings → Account → Delete account.

What I want feedback on:

Is anything in the policy unclear, weasel-worded, or missing?

Anywhere I'm overpromising relative to what the architecture can actually deliver?

GDPR / CCPA gaps you'd flag if you were a privacy-conscious user about to sign up?

Format & navigation of the page itself — is it readable on mobile?

Try it if you want: https://frogtalk.xyz — feedback (and pitchforks) welcome.

Hey everyone, sharing something I've been working on for a while. It's called FrogTalk, live at frogtalk.xyz.

The short version: it's a chat app where messages are encrypted in your browser before they ever hit the server, but I kept piling features onto it until it turned into more of a small social platform. You can try the whole thing in a browser tab if you just want to poke at it.

What's actually in it:

• Channels with public rooms (key derived from the room name) and private rooms (passphrase based, server only ever sees ciphertext). Real time over WebSocket, typing indicators, reactions, file attachments up to 8 MB.
• DMs between any two users, also fully encrypted.
• FrogSocial, a profile and feed layer on top of chat. Posts, follows, stories, comments, the usual stuff, but it lives on the same node as your chat identity.
• Reels, a vertical short video feed with hot/new/top sorting, reactions, reposts and comments. It was a fun thing to bolt on and it ended up being one of my favorite tabs.
• Music channels where you can queue YouTube, Spotify and SoundCloud links. Everyone in the channel hears the same thing at the same offset because the server hands out a shared playback anchor. There's a "now playing" strip that follows you around the app and a mini dock so you can keep music going while you chat.
• Federation. Anyone can self host a node and it joins a global directory, replicating users, follows, posts, stories, rooms and DMs across nodes. So you don't have to use my node if you don't want to.
• Tor support. A node can run as an onion only service and clients can prefer onion endpoints, in which case federation traffic routes over Tor and the clearnet IP never leaks.
• Bridges for Discord and Telegram, so a room can be mirrored both ways.
• Bot API, full REST + WebSocket, docs here.
• Apps for Android (APK), Linux (AppImage / deb), Windows (portable exe / zip), or just open it in any browser.

Stack is FastAPI + SQLite on the server, vanilla JS on the frontend (no framework, no build step), Electron for desktop, native Kotlin for Android. Source is MIT on GitHub.

If you want to spin up your own node the node docs walk through it, takes about five minutes on a small VPS.

Happy to answer questions, take feature requests, or hear what breaks. Easiest place to try it is just frogtalk.xyz in your browser.

Hey everyone, sharing something I've been working on for a while. It's called FrogTalk, live at frogtalk.xyz.

The short version: it's a chat app where messages are encrypted in your browser before they ever hit the server, but I kept piling features onto it until it turned into more of a small social platform. You can try the whole thing in a browser tab if you just want to poke at it.

What's actually in it:

• Channels with public rooms (key derived from the room name) and private rooms (passphrase based, server only ever sees ciphertext). Real time over WebSocket, typing indicators, reactions, file attachments up to 8 MB.
• DMs between any two users, also fully encrypted.
• FrogSocial, a profile and feed layer on top of chat. Posts, follows, stories, comments, the usual stuff, but it lives on the same node as your chat identity.
• Reels, a vertical short video feed with hot/new/top sorting, reactions, reposts and comments. It was a fun thing to bolt on and it ended up being one of my favorite tabs.
• Music channels where you can queue YouTube, Spotify and SoundCloud links. Everyone in the channel hears the same thing at the same offset because the server hands out a shared playback anchor. There's a "now playing" strip that follows you around the app and a mini dock so you can keep music going while you chat.
• Federation. Anyone can self host a node and it joins a global directory, replicating users, follows, posts, stories, rooms and DMs across nodes. So you don't have to use my node if you don't want to.
• Tor support. A node can run as an onion only service and clients can prefer onion endpoints, in which case federation traffic routes over Tor and the clearnet IP never leaks.
• Bridges for Discord and Telegram, so a room can be mirrored both ways.
• Bot API, full REST + WebSocket, docs here.
• Apps for Android (APK), Linux (AppImage / deb), Windows (portable exe / zip), or just open it in any browser.

Stack is FastAPI + SQLite on the server, vanilla JS on the frontend (no framework, no build step), Electron for desktop, native Kotlin for Android. Source is MIT on GitHub.

If you want to spin up your own node the node docs walk through it, takes about five minutes on a small VPS.

Happy to answer questions, take feature requests, or hear what breaks. Easiest place to try it is just frogtalk.xyz in your browser.

Join in your browser now: https://frogtalk.xyz/invite/UqDf2n6w