Avatar
Prof. - Xadke
0a4bc33dbb4b63980b586b6d7e76f4d28cfaf2b7c39829df2da789aa2d71efb2
its @profxadke ! :O

phiww thank a lot to ur pv bots and gm bots that we're cool lolz. anyone haha.

#nostr is noster cuz it "knows" @everything. lolz hail #nostr #peace =)

#newmember #memo #peace #nostr #x

Replying to Avatar Gauss

really

lolz. looks like.

open "web" APIs are actually bugging each other while other buggers are simply emitting `wss://` events - like me. nvm

~

and, PWA seems to be a problem here. where, if we just keep the track/chain up - not letting these API calls/wss events on particular relay / nostr backend. sounds like a solution to me while we should trust these TLS, and CAs anyways. so. I'll be actively utilizing APIs I discovered and moving on.

~

Summing up, do not let irrelevant `nostr` event be emitted via ur own nostr node. 😄 ez.

yeah, these open APIs can also get dangerous based on client though.

DTR hmm....

~

aka. default tip rate - interesting. 🤔

Can we just admit it "our" commit our choice. 😅 cuz unfortunately/fortunately, we anyways did it?

~

And, you 100% "free" just kick of off ur relay/server as well - straight kill my PR. (aka. Pull Request over git. )

~

Funny that I have to come and tell it here.

how do we aviod "heavy" sats damaging / glitching the client? #memo

any hope-ers around?

I mean, looking to these kids below me. why'd i use any other exploit if i have the best mutating in my github profile lolz.