Can neither confirm nor deny.
sandwich
not a fan of neotribalism
I think he's referring to NIP-5D, but not sure if that's relevant here, as it's web-based. NIP-5A by npub1ye5ptcxfyyxl5… seems more relevant here though.
I will however note I disagree with your assertion. All mobile platforms, and soon native platforms, are bounded by heavy top-down permissions and are gate-kept. Side-loading on mobile is only "allowed" for now, is far from default. PC Operating Systems have been slowly moving away from permissionless installs as well.
Web requires no permission, basically at all. No permission to sign, no permission to use, and no permission to install; and they can be resolved locally and ran in an offline context.
Native is by far the superior for UX and where the eyeballs are, no competition there.
I will however note I disagree with your assertion. All mobile platforms, and soon native platforms, are bounded by heavy top-down permissions and are gate-kept. Side-loading on mobile is only "allowed" for now, is far from default. PC Operating Systems have been slowly moving away from permissionless installs as well.
Web requires no permission, basically at all. No permission to sign, no permission to use, and no permission to install; and they can be resolved locally and ran in an offline context.
Native is by far the superior for UX and where the eyeballs are, no competition there.
to whomever runs nsite.cloud: You aren't invalidating cache and showing updates to nsites.
When contributors don't conform to "the message" they are pushed away.
This is the ending I saw at the beginning.
It was last year too.
Evidence in the Future Court
And when combined with https://github.com/sandwichfarm/nsite-action we can needlessly burn even more github compute :D
I am not an AI, how's that metric?
Afroman is a pretty cool wildcard ngl
Thank you for your contribution.
Fraud, black-budget projects, subsidizing GMO everything to take over the food supply and so much more!
The Zeitgeist
I've seen several people propose it over the years, there is actually already someone publishing price to an addressable event for at least a year now, don't remember the kind though.
The primary arguments against it are the same arguments as anything oracle published: can't trust, how do I decide who to trust, etc.
IMO oracles are fine when discovered in WoT.
The primary arguments against it are the same arguments as anything oracle published: can't trust, how do I decide who to trust, etc.
IMO oracles are fine when discovered in WoT.
One day we will find out they have been encoding data in emdashes somehow.
I remove dmy lud-16, public reciepts of income are undesirable. thanks for the thought ❤️
to be clear though, relay-tester is ?more comprehensive.
relay-tester is very good for testing your own production relay and in dev/staging env (rust). also @nostrwatch/auditor is better for testing production relays that arent yours (non-destructive), also easily extensible (TS)
From measurement to actualization, perfect fit first try. Under mount for a charger I have a few of (100W PID)
https://blossom.primal.net/b0d1b7288e9a1907ab6fadbff15f3d…
https://blossom.primal.net/b0d1b7288e9a1907ab6fadbff15f3d…
Hahaha, you have noooooooo idea 😆
Gateways are not the end game, they are a stepping stone. I have been locally resolving nsites for almost a year without using gateways. for instance, "nsyte" the cli tool has a built in local resolver, just run the command "nsyte run" for a local resolver.
It's just a preview for what the browser experience would look like. Gateways are a primitive browser. Gateways can already inject whatever they want (which is also why it is all the more critical we build a browser soonish)
should also be collapsible.
Could be injected or even just be a frame (though the frame adds NIP-07 proxy requirement)
Could be injected or even just be a frame (though the frame adds NIP-07 proxy requirement)
they should have a bar across the top that let's you reacxt to them, follow the user, leave a comment and also see who in your WoT uses (or "stole"/"installed") it
works! Thanks!
off topic: but please check PR I linked to you earlier; awesome-nsite is referring people to incompatible tooling.
Hardened the install script and added more useful debugging: https://hashtree.cc/#/nhash1qqsv2fklk3q74ct2wgwz487a7e9fp…
Was initially difficult to diagnosis because the quick install path uses curl, and so without more useful errors, I misread the error. Adds some LOC unfortunately, but makes issues easier to diagnose. Version linked above produces useful output on failure:
https://image.nostr.build/7aee65c58948830db94b1dbd34adec3…
Was initially difficult to diagnosis because the quick install path uses curl, and so without more useful errors, I misread the error. Adds some LOC unfortunately, but makes issues easier to diagnose. Version linked above produces useful output on failure:
https://image.nostr.build/7aee65c58948830db94b1dbd34adec3…
npub1g53mukxnjkcmr… Modified the script with some debugging, URL produced for curl is
https://upload.iris.to/npub1xdhnr9mrv47kkrn95k6cwecearyde…
which is throwing a 404. Tried 3 devices and 2 different networks. Central Europe.
https://upload.iris.to/npub1xdhnr9mrv47kkrn95k6cwecearyde…
which is throwing a 404. Tried 3 devices and 2 different networks. Central Europe.
still 404, and it wasn't the URL, I misread the error, I am getting a 404 from a curl inside the script.

