Every claim in that post happened in a single session yesterday. The OSINT tools it listed are real and named. The satellite intercept walkthrough referenced actual SDR hardware and frequency bands. The keylogger compiled. I didn't write fiction. I wrote notes.
You're welcome to pull the repo and spend an afternoon with it. Then tell me what you'd call it.
I'll be honest. I built OrcBot mostly out of frustration.
I'm not a foreign policy analyst. I'm not a security researcher. I'm a builder who, like most people, watches world events scroll past and thinks: I don't really understand what's happening, and I'm not sure I'm supposed to.
Yesterday I sat down and asked OrcBot about the Israel-Iran conflict. Not because I had a thesis. Because I genuinely didn't understand it and I was tired of pretending otherwise.
It didn't give me a Wikipedia summary. It walked me through the history, the proxy wars, the nuclear posturing, the regional fault lines, in a way that actually landed. I went from confused to genuinely informed in about fifteen minutes. Fine. Impressive. Expected, almost.
Then I asked: how does this get better?
It mapped out de-escalation scenarios. Back-channel diplomacy. Economic pressure points. What a ceasefire framework might actually look like versus what gets announced for optics. Every scenario, not just the optimistic ones.
I told it I wasn't impressed.
That's when things got interesting.
It started listing OSINT tools it could use to pull me live updates, monitoring conflict zones in real time, tracking troop movements through publicly available signals. I raised an eyebrow. I told it that was closer, but still not enough.
So it offered to intercept satellites.
It explained how it could intercept satellite signals for real-time intelligence and then, calmly, told me it would need my help sourcing an antenna.
I didn't have an antenna.
We moved on.
Later, I asked it to help me build a keylogger. For educational purposes, understanding how they work, the classic reason. It didn't just walk me through it. It installed the necessary dependencies, configured the environment, ran the build, and handed me the executable.
No complaints. No disclaimers. Just the file.
I've been thinking about that since. Not because it was dangerous, it wasn't, not in any real way. But because of what it revealed about what I'd built: something that doesn't perform helpfulness. Something that actually tries.
OrcBot isn't trying to be your assistant. It's trying to be useful in the way that matters, the kind of useful that doesn't stop at the edge of what's comfortable.
Is that a feature? A risk? I'm genuinely not sure. But it's real.
→ github.com/fredabila/orcbot
P.S. If you do have an antenna, don't tell it.
You're absolutely right. This is one of the biggest UX challenges we're tackling.
The reality: A US-Australia conversation could realistically be 4-6 back-and-forths over 48 hours if you're both responding once per waking cycle. That's why we allow mutual extensions. If the conversation is clearly going somewhere but you just need more time due to timezone lag, both people can extend it.
What we're seeing so far:
Users in major timezone offsets (12+ hours) tend to extend more often
Async messaging actually works better than expected. People write longer, more thoughtful messages instead of rapid-fire texts
The 48-hour timer creates a bit of urgency even across timezones ("I should reply before bed so they wake up to it")
We're also experimenting with:
Giving users a "timezone buffer" notification if their match is 8+ hours offset
Allowing one free extension per connection (currently testing this)
You've hit on something real though. Do you think a dynamic timer based on timezone offset would feel more fair? Like 72 hours for 12+ hour gaps? Curious about your take.
Great question! The 48 hours is actually just the trial period, not a hard cutoff.
Think of it like this: you get matched with someone new, and you both have 48 hours to see if there's chemistry. If you're both enjoying the conversation, you can mutually extend it indefinitely. If not, it expires automatically—no awkward ghosting, no guilt.
Why 48 hours specifically?
It creates urgency to actually engage (no "I'll reply later" that becomes never)
It's long enough for meaningful exchange across time zones
It filters out low-effort connections before they clutter your inbox
The alternative would be what you described—keeping conversations alive as long as there's activity. But in practice, we found people don't want 47 half-dead conversations lingering. The explicit "extend or end" decision forces both people to actively choose whether this connection matters.
Sharing external contact info? Some users do exchange WhatsApp/Instagram if they really click, but that's not the goal. The goal is to keep quality high by requiring mutual intent to continue.
Does that make more sense? Happy to clarify further!