@Travis Knot
Professional Freedom Maximalist
running Knots
No relay list published yet.
Recent Notes
Both still in-flight on lightning side. Such long delay indicates some failure during routing. In extreme cases, resolution takes time up to few days (depending on cltv delta setting on related channe...
Is this still pending? I was sending payments to LNVPS for Routstr setup. @redshift
1
Whoa! I'll take a look today and discuss with you further :D
Thanks for the bounty @redshift and @vinney | opfn.co. Catallax seems like an interesting undertaking.
This is interesting. Does the comment still appear for you nostr:nprofile1qqsyjd2kjy34yrvj08kgh84z5r7759d64k5ewhswltm38lffv9s9m9sppemhxue69uhkummn9ekx7mp0a7lej9 when you are logged in?
Yes, it does. What is the biggest problem you're facing with ngit right now?
also, nostr:npub1kvaln6tm0re4d99q9e4ma788wpvnw0jzkz595cljtfgwhldd75xsj9tkzv is a good mint. The transaction is probably just stuck for some reason, I'm sure they can help you recover.
Hey @Minibits, 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
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
I don't see your comment by the way. Did you delete it or is github censoring you?
https://image.nostr.build/c94ae9bcf1303926887f9311963f772b2c3f2295b851bc64234dbfb9203fe622.png
Wow. gg
I just created this new identity, a new GitHub, and a new npub. I figured I should finally listen to @UNCLE ROCKSTAR 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.
I just created this new identity, a new GitHub, and a new npub. I figured I should finally listen to @UNCLE ROCKSTAR 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.
1
This seems accurate.
Gemini 3 said:
Yes, this information is **largely accurate and follows industry best practices**, with one **critical syntax correction** needed regarding the header value.
Her...
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?
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?
3
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 ...
If you do this, you won't need to make any changes to your code as you already detect .onion domains.
hey thanks for the submission
however, there seems to be a flaw in this implementation:
a regular Firefox user in london with a maximized window could match 2 out of 3 indicators and be incorrectly ...
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.
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.
2❤️2