Travis Knot / Travis Knot is on Nostr

Yes. Pay for it. Everything is slow in Nostr because we aren't paying for convenience and speed. I'd definitely pay a few sats if it means its faster and more reliable.

2026-02-21 16:12:58 CET

I wrote something
cc: @npub1gzu…a5ds @npub1dvm…3jdm
#naddr1qv…9am7

2026-02-21 16:08:45 CET

It was surprisingly hard to write an article on Nostr.
Apps that worked:
1. Yakihonne
Apps that didn't work:
1. Hable.News
2. Highlighter
3. Untype
4. Decentnewsroom
https://media1.giphy.com/media/oxFDq4E9CHb7W/giphy.gif?cid=4ea4f8d5yd7ea86nzl6ypgy6wk0hjwmta0qv4errqvhs4u7b&ep=v1_gifs_search&rid=giphy.gif&ct=g

2026-02-15 08:14:53 CET

- reply

Is this still pending? I was sending payments to LNVPS for Routstr setup. @npub1ftt…edsh

2026-02-15 08:12:07 CET

- reply

Thanks for the bounty @npub1ftt…edsh and @npub19ma…axkl. Catallax seems like an interesting undertaking.

2026-02-12 07:43:28 CET

- reply

Yes, it does. What is the biggest problem you're facing with ngit right now?
https://image.nostr.build/61ec486c30daf66ef9d0ea8cf4e1d322ec2f280fdf21841bc0f25a5ad0a42066.png

2026-02-11 10:56:57 CET

- reply

Hey @npub1kva…tkzv, what do you need from me to help me recover my funds?
Here are the two invoices that are pending:
lnbc66182890p1p5cs4hwpp56k4d75nu2m7q00tmu20j2c26ea9qlqfx2e2ancxedfun4ysk6utsdzz2exjqun9dejhwctvyqunjveqw3hjqv3sxgmz6vpn95crsgps8yaryd36x5mjq425gvcqzzsxqzjcsp56fzp9r5adjg2jeqxw2uayfk33pp4x7esathhcmuaetwgwleqvhys9qxpqysgq6385jycth2zvyh9yltvcxvnw99t2llqw26xr7gwn867jz7j4fpd865lewukhec46hmlwk6x56vad2pyhmjd5ww65lvqrh79kgvmxnccqssdj06 with amount 6,619
and
I only have a quote id for this one: H2Szi5DITQebTeoy4xOpZOn7BPT-G2bD-eQTBXI2V with amount 6717 sats

2026-02-11 10:50:58 CET

- reply

Wow. gg
I just created this new identity, a new GitHub, and a new npub. I figured I should finally listen to @npub1j8y…vrvg and go nym. It's a good thing Nostr is more tolerant, but I reckon we'll soon have a WoT based system locking new nyms out.
https://image.nostr.build/10a045afd4fd8f0157cc9af3d929d4fbbcf984b0879cd8f7c73d9627333d5d9c.png

2026-02-10 16:15:35 CET

- reply

If this satisfies you, could you help me claim the bounty? I commented here: https://github.com/Routstr/routstr-chat/issues/159#issuecomment-3871457272
Also, I was setting up Routstr with Openclaw but lost around 14,000 sats paying Lightning using Minibits (pending transactions). Have you had such instances?

2026-02-09 09:45:21 CET

- reply

If you do this, you won't need to make any changes to your code as you already detect .onion domains.

2026-02-09 09:42:14 CET

- reply

Either way, detecting the Tor browser isn't enough. Since most Tor nodes lack TLS, you'll encounter CORS and mixed content issues when trying to request .onion endpoints. The best solution is to host your frontend on Tor itself, this is the industry standard, as you've likely seen on many websites that display an ".onion available" option. Here's how to implement it, since you seem to be hosting your pages on Cloudflare:
Implement Onion-Location Header on Cloudflare
Context: We need to configure the server to return an `Onion-Location` header. Since we are on Cloudflare, we cannot edit a standard Nginx/Apache config file directly. Please choose Option A (if using Cloudflare Pages) or Option B (if using standard Cloudflare proxy/CDN) below.
Option A: If using Cloudflare Pages (Static Site Deployment)
1. Navigate to the local project repository.
2. Create a new file named `_headers` inside the **output directory** (often called `public`, `dist`, or `build`).
* *Note: It must be placed in the root of the folder that gets uploaded to Cloudflare, not necessarily the root of the source code.*
3. Add the following code block to the `_headers` file:
```text
/*
Onion-Location: http://YOUR-ONION-ADDRESS.onion
```
4. Commit and push the changes to trigger a new deployment.
Option B: If using Standard Cloudflare CDN (DNS Proxy)
1. Log in to the Cloudflare Dashboard.
2. Select the specific website/domain.
3. Go to **Rules** > **Transform Rules**.
4. Click **Modify Response Header** and then **Create Rule**.
5. **Rule Name:** Enter "Onion Location Redirect".
6. **Incoming Request:** Match when:
* Field: `Hostname`
* Operator: `equals`
* Value: `www.your-domain.com` (or the specific domain being used).
7. **Outgoing Response:** Set **Static**:
* Header Name: `Onion-Location`
* Value: `http://YOUR-ONION-ADDRESS.onion`
8. Click **Deploy**.
---
### Verification (Required)
Once the deployment or rule is live, please verify the setup:
1. Open the **Tor Browser**.
2. Navigate to our standard website (`https://...`).
3. Check the address bar for a small, purple/green "onion" icon on the right side.
4. Click the icon and confirm it offers to switch to the `.onion` version.