Avatar
PABLOF7z
fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52
Magical Other Stuff Maximalist

πŸ‘‹πŸ‘‹πŸ‘‹πŸ‘‹

trying to subscribe even harder

every nostr client needs to implement the same 3-very-complex things, 17-mildly-complex things and 89-simple-but-annoying things

that, on top of naming the client which is it's own massively complex undertaking πŸ˜‚

ndk.fyi aims to provide this functionality transparently to make writing well-behaved/performant clients easier

Adam would zap this

#nevent1qqsfw8fknuclvn56wywp0fwc63v8lu9kdrfgm8aq2gaa72y5rng7jvqc8wy9f

🀝🀝🀝🀝

would be so cool! it'll get gossip-style behavior for free πŸ˜‰

with google

they do the same job TSA does:

security theater; they pretend to be keeping you safe while really just unleashing gatekeeping/snooping powers

when you ask NDK to subscribe to a bunch of similar-ish things, it will, by default, aggregate your queries and only send the relevant query to the relevant relays

this way I can have an component that tries to fetch the profile picture and it doesn't need to care what other components in the same page are requesting

here I'm rendering 14 components but only two have different pubkeys.

yeah, probably, I want my extension to be able to talk to alby or other nip-07 extension

can you help me with this?

1M sat bounty, and something that will be broadly useful πŸ˜…

another hour wasted trying to make a stupid chrome extension work within the guidelines of what google allows

what a shitshow; chrome in non-dev mode means you are not fully sovereign

this paternalistic software patterns is an absolute fiat aberration

πŸ€”

interesting approach, nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s; this does mean that you can't query for the quote reposts of a note though

not sure how I feel about that, maybe it's a feature not a bug? πŸ€·β€β™‚οΈ

Testing quote repost nostr:note1x3kgmcf5gda46937u3ef82p22ts2l8yjtlewkvr67ahzfun39ams74ex4v

Do you know if it’s possible to side load an extension in chrome; I mean, distributing the extension and allowing people to easily install it without it, being published on the store

Today I woke up scratching the cut where I had surgery last week.

It’s still covered with bandages but I ripped part of it in my sleep and woke up from the pain of pulling on the stitches πŸ˜…πŸ˜…

Follow this account for more post-surgery tips πŸ€™

who wants to help me publish a google chrome extension today?

it's already written but using manifest version 2 and apparently google rugged people using manifest version 2 (as in, you cannot publish it...)

250k sat bounty that expires end of day 2023-04-19 UTC.

please repost for visibility

I think NIP-18 (reposts) having the JSON of the repost in the content as a `MAY` and not a `MUST` is a mistake.

It only works when kind 6 is used for a single event kind; which is the case now but hopefully it won't continue to be.

I'm making a non-kind-1 app, but I do want the ability of reposting.

For me now that means that if I support the `MAY` I will need to fetch every single event reposted to discern if my app should care about this repost or not.

nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s

holly shit, this is so cool I'm blowing my own mind πŸ˜‚

I'm keeping this screenshot to commemorate this moment πŸ˜‚

sorry for the tease, I'm pretty sure I'll be ready in the next couple hours despite google sucking balls

This.

But without the constant threat of having the thing lost.

My wife is starting another one for our baby boy.