Oddbean new post about | logout
▲ ▼
Vitor Pamplona | 2 months ago (raw) | root | parent | reply | flag 
 Yeah, that's a problem. The phone is getting the same check, but can't answer it.
▲ ▼
TheWayHome | 2 months ago (raw) | root | parent | reply | flag 
 I wonder if it would be any diff if on cloudfare nip-05 is done via a cloudfare worker app returning the json package for that url and not a static text file? Out of my element here but was just looking at today when setting up my own domain to test.  Stupid gatekeeper mentality is ruining the whole privacy / security model.  I'm also seeing more websites that absolutely won't work with good VPNs.
▲ ▼
Vitor Pamplona | 2 months ago (raw) | root | parent | reply | flag 
 Yep, standard cloud flare stuff. They do have an option somewhere to enable Tor. I just don't know where it is.
▲ ▼
sudocarlos | 2 months ago (raw) | root | parent | reply | flag +1 
 https://github.com/sudocarlos/on-cloudflare
▲ ▼
TheWayHome | 2 months ago (raw) | root | parent | reply | flag 
 Thanks Carlos.  I'll give that a try in a bit. If it works for mine...I'll drop a not to the verified-nostr.com team to see if that's my issue from their site setup as well.
▲ ▼
TheWayHome | 2 months ago (raw) | root | parent | reply | flag 
 Well that's a no go...that WAF config option is at the enterprise plan level.  Ugh. They have some tor cloudfare onion vs exit nodes  related switch at my plan that's suppose to help bit already on.  The enterprise WAF rule is suppose to allow lowering the captcha trigger level.
▲ ▼
sudocarlos | 2 months ago (raw) | root | parent | reply | flag 
 Hmmm i did this with a free account but that was almost a year ago. Not sure what is going on with cloudflare now. Private vps proxy ftw
▲ ▼
TheWayHome | 2 months ago (raw) | root | parent | reply | flag 
 up front...a big thanks for both of the responses on this to help guide me in this 'nu user' kind of stuff.
 
my TL;DR answer...What I have found so far is that by reverting to only my phone's VPN network and not using Tor/Orbot setting within #Amethyst, Amethyst does work better for the #NIP-05 verification and Search function part of the app.  All the ones I was having Tor/#cloudfare issues, now was much faster and now getting the verify check icon on these cloudfare hosted nostr.json files like verified-nostr.com   See thoughts below as the Search function of this has it's own UI dilemma of 'still searching'.

my thoughts/feedback...I think somehow having this kind of info from within the app would be best to reduce a nu nostr&Ametheyst user wondering why some user's id "works" and some don't.  I'm not solutioning, just giving nu user thoughts.  I also noticed during this specific exercise that the app's Search function doesn't let the user know that it is still actively searching relay's (not the NIP-05 referenced server it seems) and when the app is no longer searching.  At one point during Tor based I thought there were no results put the phone down and then about a full minute or so later....a user seaarch result just showed up.  Same thing under VPN but it was in about 15 sec or so before the result showed up.  In both...had no idea the app was actually still searching.  

summary...These are very common nu nostr/app user kinds of activities where they are creating account, want to have a NIP-05 id and are likely to start with a free service, add it to their profile and looks like they did something wrong (blaming Tor here).  While exploring nostr network, trying out the search feature, for other users' NIP-05 ids or trying to search for their newly created NIP-05.  I'll concede that the 'common' internet user will see the app's question about using Tor...and just select 'no' because they have no idea what it is or their previous experience will have been ultimately...negative.  If they at least have a good VPN...better than nuttin.