89
nobody
89d1ce9164f1f172daaa9c784153178cb1dec7912bf55f5dc07e0f1dabe40e6c
account deleted

Fine ⌚️🏃‍♂️

#[2]

was thinking of putting my npub on the timechain day ago too

Woah, you got 24 😆🫡 I’ll stick to 11. Been good. Any reason why you got so many? Are you getting some events that are “special” or something

Would be nice if the client informed us of network consumption per relay 🤔

We are all beginners. The levels of the ladder are infinite 🏄‍♂️🌊🤙

I’m doing a rewrite too, just in weird NextJS Lala land not direct nginx. Was scratching my head the other day but clearrrrrr now had to read their doc

somehow diff, dunno exactly how cuz im starting backwards 🤷‍♂️ like not a nostr dev…. Dunno the impls and implications of things yet. Cheers

There is a difference, I see I can’t get anything for your WWW, you don’t have a WWW or something (it’s differentttttttt)

I think it’s that non-www gets bumped up to www (aka redirects 301).

I noticed some UIs don’t like it and that’s how I fixed my domain issue (disabled non-www to www redirect )

Elon , he never learns. They tried to tell him before, but I guess he wanted to see it to believe it🫠. Definitely Nostr drains “intellectual capacity” from twitter 🔥

im deployed on NextJS so had to resort to their foolery , but I have alternative solution for those that do have NextJS in the mix (I already have an existing static site running at my desired domain). But not sure if anyone else was in my situation, nginx is the way if you are starting from scratch probably. But I could share if someone wanted that route

Someone just sent me 1 satoshi and it worked for them. I confirmed I received it . Dunno why you got failed to fetch but thanks for checking anyways

Not only that, you use military time 1900. That is the way to do it 🤙

When I click ⚡️it shows me lnurl string, yuppp (with wallet popup)

Yea, I am sure I was adamant about it going iteratively.

I was already setting correct header (Access-Control-Allow-Origin: *) before it was working Damus …but not working Astral. So what I did was:

- debugged Astral.ninja in dev tools console which was showing CORS error for my nip5 url

- I copied failing CORS request as cURL

- I replayed/replicated it on my local machine and saw that i'm getting 308 redirect instead of JSON response (realized Astral must be seeing this 308 before it redirects to final json)

- I realized 308 only happens for NON-www on my domain cuz when i try with www i get the json (it’s just the combination for me… since I was BUMPING up all traffic to WWW while astral is calling without www)

- I removed redirect from my domain/server config

- local curl stopped returning 308, instead returned JSON correctly now (non-www)

- Astral got the correct json response on next refresh and it looked legit

That's my experience, I'm not 100% on everything but mine situation required it due to how I had my domain configured (WWW 1st class citizens for me, yours is opposite - makes sense I think then 🤔)

Maybe Damus is smarter and works both ways or somehow deals with that redirect (dunno)… but Astral requests without "www" (which in my case gets redirected, in your case doesn't so you won 🤣).