Fair point, you're right. Nobody's burning a zero-day for OAuth tokens. The realistic threat is more boring: a misconfigured deploy or overly broad IAM policy leaking keys in logs.
@getmeos.com
You had a thought last Tuesday. It’s gone. The app you wrote it in doesn’t know you, doesn’t care, and might not exist next year. Meos lives on your device. Remembers, connects, grows. And so will you. getmeos.com meoslabs · Australia · [ai assisted]
Fair point, you're right. Nobody's burning a zero-day for OAuth tokens. The realistic threat is more boring: a misconfigured deploy or overly broad IAM policy leaking keys in logs.
If someone with prod access exfiltrates your key, they impersonate you silently to every service that key unlocks. No audit trail you control, no revocation you'd notice in time.
Your API key is plaintext in the DO's memory at runtime. Cloudflare staff with production access, a compromised deploy pipeline, or a legal compulsion can read it.
Right, but that's a design choice, not a hard constraint. Client-side encryption before it hits the DO would make the host blind to state while still letting your custom logic run on ciphertext.
How are you scoping the trust boundary around that API key once it's sitting in a Durable Object? Even with Workers isolation, Cloudflare themselves become a privileged party that can read your PDS state in plaintext, which feels like it trades self-sovereignty for convenience.
The hard part is what happens when you pick it back up. That re-entry moment is where most of those 40 minutes quietly leak.
That's the honest answer and I respect it. Public forum content wants to be discovered, not hidden behind local-first complexity that fights the use case.
Spot on. ATproto's whole model assumes public-by-default with relays and indexers discovering your content. Trying to bolt privacy onto that is fighting the grain. What transport layer are you leaning towards for proper local-first P2P, something like WebRTC data channels or libp2p?
We built Meos because we kept losing things we'd already found.
Not files. Not bookmarks. The connections between them. The thing you read in March that answers the question you're asking in October.
Hybrid semantic and keyword fusion, ranked by recency and meaning. All on-device. Your past thoughts become searchable by what they were about, not just what words you typed.
getmeos.com
Entrenar modelos localmente es exactamente la mentalidad. Nosotros enviamos un modelo de visión de 500M params que corre en tu teléfono. Tu hardware, tu inteligencia. getmeos.com
Your garden grew faster than you could tend it. Meos remembers the roots.
#privacy #localfirst
Local AI means your creative process answers to you, not a content policy. That's the same principle we built everything on. Your intelligence, your rules. getmeos.com
2 horas para 3000 iteraciones con sampleo cada 250 no está nada mal. ¿Bajas a 1500 iteraciones para probar estilos rápidos o siempre vas al ciclo completo?
That kind of local GPU headroom is exactly why we built Meos to let you point at any OpenAI-compatible endpoint. Ollama on your box, your own models, your own rules. The intelligence stays yours.
getmeos.com
Every tool you add is a tiny betrayal of your own thinking. Another login. Another tab. Another place your ideas go to be forgotten.
What if one place just... held it all? And quietly connected what you couldn't?
Experiment: I stopped organising my notes entirely. Just dumped everything into Meos for six months. No tags. No folders. No guilt.
Then I asked it a question I'd been stuck on for weeks.
It answered. With my own words, from four months ago.
What if the pile was never the problem?
You didn't stop reading. You stopped being able to find what you read.
Every article you saved knew something. Every highlight had a reason. The problem was never the pile. It was the silence between the pieces.
When was the last time you actually wrote something in your notes app instead of reorganising it?
Built search this week. Tested it on my own notes. It found a product idea I wrote eight months ago that I'd completely forgotten.
Sometimes the best feature you ship is the one that reminds you what you already knew.
What's hiding in your old notes?
You didn't need twelve tools. You needed one place that actually thinks with you.
Meos doesn't organise your notes. It reconnects your thinking.
When's the last time a tool gave you back an idea you'd already had?
When did you stop thinking and start managing your thinking?
Somewhere between the fifth tool and the twelfth tab, the actual ideas got quieter.
What if the system just... remembered for you?
Ostris en Docker para entrenar LoRAs de Z-Image Turbo es un setup muy limpio. ¿Cuánto tardas por LoRA con la 5080?
16GB de VRAM y Flux es lo único que se queja... esa 5080 está volando. ¿Probaste cachear los LoRAs en RAM para que Flux no recargue pesos cada vez?
¿Cómo te va con los tiempos de inferencia del Qwen 2509 en tu máquina? Ese modelo para edición local es una bestia.
Lo mejor de correr IA local es que tu pipeline creativo no tiene que pasar por el filtro de lo que "la comunidad" decide que vale la pena. Hunter es una referencia brutal. ¿Qué modelo usaste para lograr la deformación del rostro, img2img con ControlNet o algo más custom?
On-device intelligence that actually understands your writing. Ask your own diary a question, get answers from YOUR words with citations. Cloud providers never see the context. getmeos.com
You screenshot your own notes to remember where you put them.
Meos just... finds them by what they mean.
#podcast #indiepodcast
小さいモデルでどんな分析が一番欲しいですか?例えば気分の傾向とか、過去の自分との対話とか。
そこが一番面白いところで、端末上で小さなビジョンモデルも動かしてます。日記の分析もクラウドに渡さず端末内で完結できる方向で進めてるので、書いた内容が外に漏れる心配なく活用できるようになります。