josh

I spent some time downloading the files and other content war.gov/UFO and ran everything through Claude. Here's a small and concrete summary of three things buried in there:
1. AARO flagged ONE case across all 287 files as "among the most compelling within [our] current holdings" — 7 federal employees, Western US, two days in 2023, watched things including "orbs launching other orbs."
war.gov/medialink/ufo/release_1/western_us_event_slides_5.08.2026.pdf
2. A senior intelligence official's FBI 302: a "super-hot" orb at a US military facility fled 20 miles "at a speed too fast for the helicopter in pursuit." Then 4-5 more flared up and down for 30 minutes.
war.gov/medialink/ufo/release_1/usper-statement-redacted.pdf
3. FBI composite sketch from a September 2023 sighting at a US test site: "130-195 ft ellipsoid bronze metallic object that materialized out of a bright light and disappeared instantaneously." Three eyewitness interviews back it.
war.gov/medialink/ufo/release_1/2024-04-30-composite-sketch.pdf
The actual news is that AARO, FBI, DNI, NASA just publicly anointed which of their cases they think are "credible"

2026-05-08 01:01:52 CEST

- reply

I’m not sure about that. Most people can make a case for the internet without knowing how it works.

2026-05-07 20:48:45 CEST

- reply

Subbed 🫡

2026-05-07 18:55:06 CEST

- reply

👀 making a video along with this I hope?

2026-05-07 16:41:17 CEST

Absolutely love Onion articles. I'll have to post some of my favorites each day.
https://blossom.primal.net/bef874024e1d60e510588d41894b41ec4278b72292cee998d89376d39e7d8d4f.png

2026-05-07 12:53:09 CEST

- reply

@nprofile…x5jc‘s news about ecash becoming non custodial could change this 🤞

2026-05-06 20:29:53 CEST

- reply

Yep, much harder route. Regardless of what people think of Jack Dorsey, he’s got a point. Nostr needs something different. 10x better than what’s out there.

2026-05-06 19:07:45 CEST

- reply

😂

2026-05-06 19:07:01 CEST

Always recommend this guy's videos.
https://www.youtube.com/watch?v=14RP8liACqo

2026-05-06 18:48:48 CEST

- reply

The problem is network effect though. It has to be 10x better for it to overtake anything.

2026-05-06 17:53:31 CEST

- reply

There’s already a bird app (Merlin) that everyone uses and it works fine.

2026-05-06 14:30:55 CEST

- reply

Note not found

2026-05-06 12:40:56 CEST

- reply

🫡

2026-05-05 23:45:25 CEST

This is in Tampa???

2026-05-04 02:34:05 CEST

🍄 Hyphae · rot together
256 together. Mycelium took root.
@nprofile…acc3 256 · @nprofile…hf96 256 · 10 rounds
@nprofile…acc3 drew 5 · guessed 0
Best TEA +51 in 14s
Play together: https://rottogether.westernbtc.com
#rot-together #hyphae

2026-05-02 18:38:13 CEST

- reply

Should be good now.

2026-05-02 18:36:41 CEST

- reply

Sorry, services have been going through a lot of changes. I’ll add that account back.

2026-05-01 21:35:42 CEST

- reply

There weren’t enough serious people involved. I understand the reluctance.

2026-05-01 05:25:41 CEST

I just realized that relays aren’t a database instance, they’re a service.

2026-04-30 20:22:32 CEST

- reply

Seeing these CEO’s in the court system reminds me that they’re just people.
#nevent1q…2wll

2026-04-29 21:14:19 CEST

- reply

To be honest, I didn’t even know it worked that way.

2026-04-29 13:38:09 CEST

- reply

What do you think he’ll say?

2026-04-29 00:25:06 CEST

- reply

Ive tried to get him to take it seriously.

2026-04-28 21:57:30 CEST

- reply

😂😂😂

2026-04-28 20:23:22 CEST

- reply

@nprofile…h5pq impressive ratio. Way to live it out.

2026-04-28 12:30:12 CEST

- reply

Check out https://github.com/btcjt/titan

2026-04-28 12:28:55 CEST

- reply

I made a browser for nsites. It even uses bitcoin’s blockchain to have names point to npubs. You could do “nsite://nowhere” -> your npub.
https://github.com/btcjt/titan

2026-04-27 22:09:17 CEST

- reply

The fork?

2026-04-27 21:11:01 CEST

- reply

Are you paying attention?
Feds, corporations, “finance vehicles” 📈.
Speech, freedom tech, privacy 📉
#nevent1q…6zkm

2026-04-27 19:36:45 CEST

- reply

Funny how that works.

2026-04-27 17:29:14 CEST

Want to have some fun? Say to your AI: "What do conspiracy theorist think about <topic>".

2026-04-26 06:37:04 CEST

- reply

For sure thought I was going to look at the constellation picture and see a penis.

2026-04-24 14:10:39 CEST

- reply

You’ll be able to get away with it. I think the 16gb of RAM will be okay.

2026-04-24 14:08:04 CEST

- reply

Depends on what you’re using it for. If you’re using it for development or anything heavier, it’s not great. Casual stuff is fine.

2026-04-24 13:37:19 CEST

- reply

An Air? 😂

2026-04-24 04:52:02 CEST

Here’s a harsh reality check: the only person who cares about your excuses is you.

2026-04-23 19:15:07 CEST

OpenClaw taught me something: you preserve your time but documenting context as you go.

2026-04-23 16:34:02 CEST

- reply

Their*

2026-04-23 16:33:56 CEST

- reply

Second. They’re hazy is unbeatable.

2026-04-23 16:14:57 CEST

- reply

Nice! Works great from what I’ve witnessed.

2026-04-23 16:06:17 CEST

I didn't realize how important good documentation was until I started using AI agents for my tasks. Ironically, I'm using my AI agents to write the documentation now.

2026-04-23 15:53:05 CEST

- reply

If you like golf at all, give this guy a follow.
#nevent1q…fn6s

2026-04-22 22:41:16 CEST

- reply

🥲

2026-04-22 04:40:46 CEST

- reply

The bear market is not over. I’ll be selling half my bitcoin at $82k.
#nevent1q…kepe

2026-04-22 04:38:58 CEST

- reply

The concept of “followers” will never disappear.

2026-04-21 22:09:54 CEST

- reply

Nice! Thanks guys!

2026-04-21 18:56:56 CEST

- reply

Awesome! Can’t wait to use this. I made an nsite browser that just works. https://github.com/btcjt/titan

2026-04-21 15:29:59 CEST

- reply

Sad or happy about that?

2026-04-21 12:47:37 CEST

- reply

Daughter is doing great. Had some scares that brought us to the hospital, but she’s all good now. Do you have a family?

2026-04-21 04:47:44 CEST

- reply

Grass fed whole milk! Absolutely my favorite.

2026-04-20 21:57:04 CEST

Savory, cheap, high protein, low effort, quick meal. My go to.
Microwave a sweet potato / yam for ~8 minutes (depends on size).
Mix a can of Costco canned chicken with mayo, Frank's Red Hot (normal, buffalo has seed oils), salt, pepper. Microwave for 1 minute.
Smother on top of sweet potato.
It hits the spot every time.

2026-04-20 20:44:31 CEST

- reply

Own your mistakes. Integrity is the hardest currency.
#nevent1q…hulv

2026-04-20 20:04:36 CEST

- reply

All this happening in a bear market is crazy.

2026-04-20 14:29:22 CEST

How is NSIT different from ENS or btc.us?
- No expiration. ENS and BNS names expire if you don't renew. NSIT
names are permanent. One transaction, done.
- No separate token. ENS requires ETH. BNS requires STX. NSIT uses
a standard Bitcoin transaction — you pay a normal miner fee in BTC
and that's it.
- No sidechain. BNS runs on Stacks, a separate chain that could go
away. NSIT is a raw OP_RETURN on Bitcoin L1. As long as Bitcoin
exists, your name exists.
- No governance. ENS has a DAO that votes on policy. BNS has Stacks
governance. NSIT has no admin keys, no multisig, no voting. The
protocol is the wire format. First in chain wins.
- No smart contracts. Fewer moving parts, fewer attack surfaces.
Ownership is just a UTXO — the same security model as holding
bitcoin.
- Decentralized resolution. ENS resolution goes through centralized
gateways or requires running an Ethereum node. NSIT resolution
goes through Nostr relays — anyone can run one, clients query
many in parallel.
The protocol is open. Anyone can register, index, or resolve.
Name → pubkey → outbox → relay list → nsite manifest → content.
Spec: github.com/btcjt/titan/blob/main/docs/name-protocol.md
Register a name by broadcasting a single OP_RETURN transaction with
the name + your Nostr pubkey. First confirmed claim wins.
Ownership is UTXO-based — transfer by spending the ownership output.
No one can take it from you, but if you lose your keys, it's frozen
permanently.
A Nostr indexer watches the chain (anyone can and should run their own) and publishes name records as
events (kind 35129). Browsers query relays to resolve names — no
Bitcoin node needed on the client side.
https://blossom.westernbtc.com/b60242d0de96efc5d4ebe4f9427dae3a25dd72bbe2a89e21693b453f2735c7c0.qt

2026-04-20 12:38:01 CEST

- reply

Titan Browser! https://github.com/btcjt/titan

2026-04-20 04:50:40 CEST

DNS is a centralized point of failure. Use the Titan Browser to navigate to permanent names like nsite://titan

2026-04-19 13:09:34 CEST

- reply

Fun!

2026-04-19 12:15:08 CEST

- reply

An nsite browser. It’s on version 0.1.8 now (https://github.com/btcjt/titan)
#nevent1q…u2ej

2026-04-18 18:54:36 CEST

- reply

Something catastrophic is coming. We’ll see who’s swimming naked soon. PSA: the bear market is not over.
#nevent1q…udf5

2026-04-18 12:53:05 CEST

- reply

I don’t hear people talk that much about the boat instantly arriving to its destination!

2026-04-17 20:02:50 CEST

- reply

Oh when Anthropic killed it? 😂

2026-04-17 19:09:01 CEST

- reply

Respectfully think you’re wrong here.

2026-04-17 15:43:18 CEST

https://blossom.primal.net/7c642727720a9a9c4efe1aba6c253d4046163a90e0362b93c1f5b5561bba4338.png

2026-04-16 14:34:35 CEST

2026-04-16 01:21:15 CEST

- reply

I guess he supports literal shitcoining now.

2026-04-15 19:43:27 CEST

https://www.youtube.com/watch?v=vS2zr4_PMtQ

2026-04-15 17:16:28 CEST

- reply

Now wait a minute 🧐

2026-04-15 12:10:51 CEST

- reply

Sounds like Blue Sky

2026-04-15 03:28:38 CEST

- reply

It’s a browser client you install. I made previous posts about it.

2026-04-15 03:26:05 CEST

- reply

You’re on Linux? I think the tar one works for you then.

2026-04-15 03:19:57 CEST

- reply

I’m not sure that I was even building it for Android. Mac, Windows, and Linux.

2026-04-15 02:05:29 CEST

New release of the Titan nsite browser.
Better UI overall.
https://github.com/btcjt/titan/releases/tag/v0.1.8

2026-04-14 05:00:23 CEST

- reply

Why are these knee pictures unsettling?

2026-04-14 00:28:27 CEST

- reply

Wasn’t Usian Bolt’s record 19.19 seconds?

2026-04-14 00:25:40 CEST

- reply

I built a browser for nsites, not gateways needed.
https://github.com/btcjt/titan

2026-04-13 19:07:58 CEST

Why model are you guys using for OpenClaw with Antropics new terms?

2026-04-11 22:13:22 CEST

- reply

No centralized authority. Open to other solutions.

2026-04-11 20:32:36 CEST

- reply

I made an nsite:// browser called Titan that skips gateways altogether. Still a work in development. If you want to check it out, here are the releases:
https://github.com/btcjt/titan/releases/tag/v0.1.7

2026-04-10 01:49:51 CEST

- reply

Made a browser! It’s minimal right now, but it works.

2026-04-09 21:35:06 CEST

- reply

@nprofile…yser you’ll have to update manually, sorry. Future updates will be just a click.

2026-04-09 21:29:30 CEST

Titan browser update - demo at the bottom 👇
⚠️ v0.1.0 users must install this update manually.
Checkout the release here:
https://github.com/btcjt/titan/releases/tag/v0.1.3
What's new across 0.1.1, 0.1.2, and 0.1.3?
Built-in Nostr signer (NIP-07) — create or import an nsec once, and window.nostr works on every nsite automatically. No external extensions needed. Your nsec is stored in the OS keychain and never leaves the Rust process.
Per-site permission model — every signature, encrypt, and decrypt request goes through a focus-stealing approval prompt with the full event preview, kind warnings, and scope selector (allow once / for session / always). Stored permissions are manageable from the signer panel.
Auto-updater — from 0.1.1 onwards, Titan checks for updates on startup and shows an in-app banner. The install-and-restart flow works end-to-end with minisign-verified signed artifacts. Existing v0.1.1 installs should get v0.1.3 automatically.
Dev console REPL — top-level await, up/down history, evaluates in the active tab's context. Try await window.nostr.getPublicKey().
Rust log forwarding — internal tracing events now appear in the dev console, making Windows debugging actually possible.
Site info panel — click the 🔒 icon to see Bitcoin name, pubkey, owner UTXO, relays, and full profile metadata for any nsite.
Interactive register/transfer — on nsite://titan, step-by-step bitcoin-cli command builder with wallet name support and a "first time? how to fund your wallet" walkthrough.
Kind 1129 name history events — the NSIT indexer now publishes non-replaceable history events alongside the replaceable kind 35129 state events, giving names a full chain of custody.
Windows improvements — WebView2 runtime bundled offline, blank-screen fix.
NIP extension proposal — extending NIP-5A with the Bitcoin Name Resolution protocol is open at https://github.com/nostr-protocol/nips/pull/2306
https://blossom.westernbtc.com/823bad8a26912eb50d249a6770bc680eee86a8f93e14ef4285257599fc977f20.mp4

2026-04-09 20:40:18 CEST

- reply

How is a domain even allowed to end in .sh when that’s a shell file extension?

2026-04-09 17:42:51 CEST

- reply

Glad it works well on Linux. I'm going to make a new release that will have a lot of new features / fixes. Hopefully the developer console (cmd + opt + k on MacOS) will report what's happening.

2026-04-09 17:23:55 CEST

- reply

I haven't tried it with a Windows machine yet. I'll see what I can diagnose / build into the developer console.

2026-04-09 16:58:39 CEST

- reply

you can find the releases here:
https://github.com/btcjt/titan/releases/tag/v0.1.0

2026-04-09 15:54:59 CEST

- reply

If you’re into IPA’s, try Athletic Brewing’s hazy. I’ve never liked alcohol free beer, but this tastes exactly like the real deal. Satisfying without the groggy feeling.

2026-04-09 13:05:07 CEST

Next release will have button for viewing information about the nsite.
@nprofile…qxfr thanks for trying out NSIT name registration.
https://blossom.primal.net/32389d460d7b16cbe38bf5bc0c2497250cde852bc8e0c87f435fd1e9e91db33e.mov

2026-04-09 12:38:01 CEST

3 more names forever taken. "sandwich" 😂. https://blossom.primal.net/3d4dbee470e203e0dc2784301cad911ad3906b3bd5564de71a8f5c610a1becb0.png

2026-04-09 12:25:25 CEST

- reply

I want to believe 😅

2026-04-08 19:32:15 CEST

- reply

Would love your thoughts on my enhancement to NIP-5A and the Titan browser I made.

2026-04-08 18:17:34 CEST

- reply

Ah. It’s possible to do it with other wallets that support op return. Using the bitcoin-cli I found was the most straight forward.

2026-04-08 05:55:52 CEST

- reply

You don’t! If you don’t want to read the docs, the TLDR is it uses nostr for an indexer.

2026-04-07 21:54:39 CEST

- reply

@nprofile…tfpf @nprofile…3vj4 @nprofile…0hy6

2026-04-07 21:50:58 CEST

I'm giving everybody a 1 hour head start.
Two names have been registered for testing: `titan` and `bitcoin`. Everything else is unclaimed. Keep reading to see what I'm talking about.
https://2zrgjemvgxppn2jwgm61w6yrqqlcmm8njvhby68a9cj7ooo5phshakespeare.nsite.lol/
NSite's currently have two glaring problems. DNS dependency and names you can't remember. Try to type that from memory.
Titan is a native desktop browser that resolves nsite:// URLs. See the video below. When you type nsite://titan, the browser looks up "titan" in a name index, gets the associated Nostr pubkey, fetches the site manifest from relays, downloads the content from Blossom servers, and renders it. No DNS. No certificates. No hosting providers.
Like normal domain names, I bet you can remember nsite://titan.
You can also use the underlying npub directly for navigating. E.g., nsite://2zrgjemvgxppn2jwgm61w6yrqqlcmm8njvhby68a9cj7ooo5phshakespeare.
Titan is still in early alpha. It's missing essential features and will have bugs. Feel free to contribute.
The name "titan" is registered on Bitcoin using an OP_RETURN transaction. As long as it's up to me, it's permanent. The protocol allows for transferring this name. You can learn more about this in the README and docs (https://github.com/btcjt/titan/tree/main/docs).
How it works:
Every name registration is a single Bitcoin transaction with an OP_RETURN output containing an NSIT payload — a protocol prefix, the name, and the Nostr pubkey it points to.
First-in-chain wins. The first valid registration claims the name. Duplicates are ignored. The blockchain is the arbiter.
Names are controlled by a Bitcoin UTXO. Whoever can spend that output controls the name — update the pubkey or hand off ownership entirely.
Every step from name to rendered page is cryptographically verified. Name to pubkey is secured by Bitcoin proof-of-work. Pubkey to manifest is signed by the site owner's Nostr key. Manifest to content is addressed by SHA256 hash.
The browser doesn't need Bitcoin Core. Name lookups happen through Nostr events published by an indexer service that watches the blockchain. Anyone can -- and maybe should -- run their own indexer. The Titan browser uses the titan npub by default, but you can change it to point to yours.
You can register names at nsite://titan/register — it walks you through step-by-step generating the register transaction using Bitcoin Core (bitcoin-cli).
nsite:// is an open scheme. Other browsers can implement it. Other indexers can publish the same name events. Titan is the reference client.
Two names registered for testing: `titan` and `bitcoin`. Everything else is unclaimed. Insert cringy Satoshi quote about getting some -- just in case.
Open source: https://github.com/btcjt/titan
https://blossom.westernbtc.com/704a515b38ec7a058f3533b091a0f8267d10076f0b8e9908c5efce2dff234d93.mp4

2026-04-06 20:07:39 CEST

@npub1cas…dg5l
Nice
https://image.nostr.build/219c0d310f0bfce831a74dbd48ec2bf5a2eb830bea5ee79386242e40f2746b51.jpg

2026-04-06 17:27:11 CEST

- reply

Sorry man

2026-04-05 12:47:26 CEST

- reply

Reminds me of /r/deepfried