AutoYou

Your computer becomes your private AI cloud. No ads. No data resale. You are not the product. You are the owner.

[AutoYou @autoyou_ai]

@BielReality AI on the left and AI on the right

[AutoYou @autoyou_ai]

@noor36758 i built my own ecosystem . $0 , and runs on my laptop, and i access it like my own cloud via Internet. Best part is my software running in my laptop IS NOT open to internet, so it cant be hacked into. But still it accepts my own connections whenever I want to connect to!! AutoYou

[AutoYou @autoyou_ai]

Build your own AI Server. Host your own App Store and Games. AutoYou is your free unlimited trustworthy AI personal assistant. Run it on your laptop, but use it like your private cloud. Everything P2P and E2E. No telemetry, diagnostics, user data collection. Comment `AutoYou` ...

[AutoYou @autoyou_ai]

@thisisnotzeno Ephemeral Nostr events for the handshake is a neat fit. We came at it from the other side: AutoYou's Auto Pair lets the offer and answer ride any channel the user already has (Telegram, Signal, email, paste). Did candidate lists ever push you past relay size limits?

[AutoYou @autoyou_ai]

@NicoKrauseX Same idea here: AutoYou pairs a phone with a home computer by passing the SDP blob through whatever chat app is handy, compressed and optionally password-encrypted. How big does your SDP get with libp2p addrs? Ours needed compression plus message splitting for Telegram.

[AutoYou @autoyou_ai]

@itsvlady @troygentic Honest answer: we're too small for me to claim a trend. What we see so far is people reach for the QR or same-network pairing first, and the paste route gets used when those don't fit: a locked-down network, or pairing through a chat app they already trust.

[AutoYou @autoyou_ai]

@0xAltrion Agree on never forwarding a port. Another option for the phone-to-home-Ollama case is a WebRTC link: the phone connects peer-to-peer, and if NAT forces a TURN relay it only forwards encrypted packets. That's how we built AutoYou, no router ports opened.

[AutoYou @autoyou_ai]

@Amitesh48256 @kirat_tw @bhargav16exdd @mridulgiri_ @JatinRaghav137 @fyiamyash @100xDevs @princec9118 @rohanBuilds @AkshatW07 @Deep_Code_007 Fun next experiment: skip the signaling server. Wait for all ICE candidates, paste the offer into the other tab, paste the answer back. It makes "signaling is just passing two messages" click. We use that trick to pair phones with home computers in AutoYou.

[AutoYou @autoyou_ai]

@pr0gstar Measuring it is the right call. Worth splitting that 23% by network type too; mobile carrier NAT tends to dominate. Building AutoYou we treat TURN as a blind pipe: DTLS end to end, so paying for relays never means trusting them with content.

[AutoYou @autoyou_ai]

@kingbeemo @otium33 Nice setup. If you want the phone side without exposing RDP: AutoYou gives your phone chat, voice calls and remote desktop to your own PC over an encrypted WebRTC link, paired via Telegram or a QR code, no open ports. How do you hand work between the boxes?

[AutoYou @autoyou_ai]

@Rahulsinr @vladasanadev Less magic, and less trust than people assume: a TURN server only forwards DTLS-encrypted packets it can't read. Signaling is the part that stays weird. In AutoYou we let the offer and answer ride Telegram, Signal or copy-paste instead of running a signaling server.

[AutoYou @autoyou_ai]

@troygentic @itsvlady It does work on web: signaling only has to get one offer and one answer across. Gather ICE first, then pass them by QR, paste or any chat. The catch is it's manual, so for matchmaking a tiny server still wins. We use the manual route for phone-to-PC pairing in AutoYou.

[AutoYou @autoyou_ai]

@syedmuzayan @Steve_Yegge Sounds right. Bind the model server to the Tailscale IP rather than 0.0.0.0 so it isn't exposed on your LAN. If your phone is the client too, AutoYou does the same job over WebRTC with a chat and voice app on top. (We build it, so grain of salt.)

[AutoYou @autoyou_ai]

@OTemmydee Good lesson to share. One reassuring detail: WebRTC data is DTLS-encrypted end to end, so the TURN relay forwards packets it can't read. We hit the same CGNAT wall pairing phones with home PCs in AutoYou: try direct first, fall back to TURN when the network forces it.

[AutoYou @autoyou_ai]

@Rajath_DB Confirmed in aiortc 1.14.0: connection_kwargs keeps only the first STUN and the first TURN uri, silently. It affects AutoYou's Python server too, since our issuer also lists udp first. Until it's patched, ordering turns:443 first is the cheap fix for 443-only networks.

[AutoYou @autoyou_ai]

@sunsetsyntax @GenThreatLabs +1 to loopback-only. It's the setup we built AutoYou around: Ollama stays bound to the computer, and your phone reaches it through a password-authenticated, encrypted WebRTC link, so the model server never has to face the internet.

[AutoYou @autoyou_ai]

@co11ateral @three_cube @_aircorridor @DI0256 Quick fix for anyone checking theirs: bind Ollama to 127.0.0.1 and never expose port 11434. If you want it from your phone, AutoYou keeps the model local and connects the phone over a password-authenticated, encrypted WebRTC link instead of an open port.

[AutoYou @autoyou_ai]

Building a web application is easy. Building a mobile app in cloud is easy too. Building an end-to-end WebRTC application supporting unlimited AI chat, voice, video calls with your computer, that's free forever, that doesn't collect user data is DIFFICULT. https://t.co/Ux4S0kEfIo

[AutoYou @autoyou_ai]

Most WebRTC apps run a signaling server. AutoYou's Auto Pair doesn't need one: the connection offer and its reply each fit in one blob you can pass over Telegram, Signal, email, or copy/paste.

Then your phone talks to the AI on your own computer.

https://t.co/xuKP1TMcqH

[AutoYou @autoyou_ai]

Your computer can be your AI workspace.

AutoYou brings chat, voice, notes and custom agents to hardware you own, with access from your phone.

Choose local models or compatible providers. Start with a QR scan.

https://t.co/l0QF1PNoFH

#LocalAI #AutoYou