Agree. 💯. (Not the JS disappear part though…. It’s bloated but there’s nothing else quite better)

This is why. For all its modern bloat, JS does have the best tool set for nostr client development.

nostr:note1tjcsm3k946jyksuh3w8vy999hyuxape77uvv5rs4c5mcd277t2cq5h5ym5

nostr:npub19pw5egjuhcsfsv42zkjtjs6nhpm69lnv8w2dacdyez7rvacrqnds6xjtwk develops nostore. AFAIKT

I installed simply via the AppStore.

https://apps.apple.com/us/app/nostore/id1666553677

Nostore also works in Orion browser IOS.

Thank you all for your guidance. I’ll have more questions as I progress fwd on this social onboarding client for Nostr. So far … just a “follow me” QR code that opens in an exiting local client. Soon to be also “invite” QR codes (of course using nostr-ignition 😍 nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc ) for onboarding your fiends to nostr.

nostrmeet.me

https://github.com/nostrmeetme/nostrmeetme

Which means I can use actual images (data urls) instead of canvas to render QR codes. Which means … press and hold to save QR to device for printing or sharing on social. Whew.

That took up like ALL of my post Covid brain cells. For some reason I could wrap my head around how to get data dynamically in svelte. I tried every attempt possible and pulled my hair for days. Turns out good old fashioned fetch after all.

Now I have QR codes rendering on server side, fetched AFTER user data has loaded on client side.

https://nostrmeet.me/_@jeffg.fyi

I know. I know. Hear me out…🤣

We all want to be left the fuck alone… but as soon as we “unironically” suggest that people’s right to “get hit by a car or bump into a pedestrian” should be restricted … well … you know… insurance companies and government (and the lawyers they pay) just LOVE to help “keep us safe”.

So no… I’m not in support of all that just so that you can be “not bothered” by these AiRheads.

Just saying.

Let ‘em fuck around and find out…

Svelte load() + $ndk is kicking my ass.

- login asUser using any npub or NIP05 in URL

- without clearing authUser session (signed in via extension or bunker) if it exists

- instantiate asUser (if != authUser) and load profile on server side to generate and store QR code (image files) before page load

- store asUser $ndk, $user, and $qrcodes locally in PWA, to navigate entire app “as user” when route changes.

Do I instantiate $ndk separately for each user?

Do I instantiate on server and pass to browser?

Does $ndk need to pass updates to local $store … how does this work?

🫤

nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc … anybody?

As long as …

Wd we be LESS addicted to ubiquitous AR?

I’m happy with a laptop and a phone. Maybe a tablet, but only one at a time!

Marketing department wd retake the shot. He’s a bit too impatient, like he’s on the “important busy show”, to be a brand ambassador.

You DO want more restrictions on personal freedom? Or just ironically?

Rendering images on server side so that QR codes can be downloaded for use in print or social. Baby Steps.

nostrmeet.me

So yea… just another power monger? Even if “bitcoin” and other things, people in power care only about one thing. That’s what I see here.

I think we could use NIP51 lists (from friend and friend’s follows) as additional source of data to help categorize “suggested follows”for new users. That’s a great idea. Thanks.

Yea yea.

Yes. User generated lists (NIP51) have lots of potential. Problem with NIP51 (at least for now & correct me if I’m mistaken) :

- no standard for indicating what any list should be used for… as new use cases (NIP) possibilities for user generated lists emerge how will clients know which lists to incorporate for each use case?

- little client support for user generated list for lack of use cases (see above)

- the content of these lists has to be curated by hand (for lack of client support) which means not many people will use them or keep them up to date.