author of nips that you use every day but have no idea exist. infamous shit-stirrer. former full-time nostr developer.
Public Key
npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx Profile Code
nprofile1qqswwud0pvzu362lehm0av6sq4zd97cue5uy0z8f7jgtk0hz368dvmcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0ds5v996t
Show more details
Published at
2025-12-12T16:37:52Z Event JSON
{
"id": "000000000b977c6e1a874f03c987fec0195edd34e07e4bfa1ac213af06b7d428" ,
"pubkey": "e771af0b05c8e95fcdf6feb3500544d2fb1ccd384788e9f490bb3ee28e8ed66f" ,
"created_at": 1765557472 ,
"kind": 0 ,
"tags": [
[
"client",
"notemine.io"
],
[
"nonce",
"192320195",
"35"
]
],
"content": "{\"name\":\"sandwich\",\"display_name\":\"sandwich\",\"about\":\"author of nips that you use every day but have no idea exist. infamous shit-stirrer. former full-time nostr developer.\",\"picture\":\"https://image.nostr.build/8bb39c413276b2d8509bc34aa926b05f46b968913f2a15236d50e6579314b1ae.jpg\",\"nip05\":\"[email protected] \",\"displayName\":\"sandwich\",\"bot\":false}" ,
"sig": "a9b2e0eeef097973a0550a2a35342bd5e8fe9a3e549e27fcac58d93b6e36376bee532dc955811ed90b584fb095b0e146aacdd370833a37f1f09e1ef5c6af2238"
}
Last Notes npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich https://nostr.watch isn't for that. If you have the event id or nevent, you can try https://nadar.sandwich.farm npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich make NIP-19 encoded entities extendable. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich I spent a good 2 minutes attempting to pronounce that. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich COMMUNICATION npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich I am using my own client part time, it's fun :D npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich No it doesn't. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich lol, NIP-07 doesn't make it a napp, the intent to be a napp makes it a napp 😜 npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Did you know that https://nostr.watch has both a v2 rest API with L402/P2PK payments and a CVM with CEP-8 payments? NIP-66 is always free of course, and can derive all of the data from these endpoints. Both have been live but unannounced for roughly ~5 months, running with payments enabled for about a month. The purpose of deploying these was to exercise the deployment of an end-to-end, self-managed payment solution that implements novel payment protocols. https://image.nostr.build/2db46cac84e491fcf0873be6a2f25041e818cff66f26253dafa03a18e9b8569b.jpg https://nostr.watch runs its own lightning node, with it's own liquidity management and a private mint for internal use. Both the CVM and REST API run a @nostrwatch/rstate instance, a state machine derived from aggregate NIP-66 data. USEFUL LINKS: https://status.nostr.watch https://cvm.nostr.watch https://api.nostr.watch/v2/ CONTEXTVM SANDBOX: https://www.contextvm.org/s/65a334b02f5913cf2c1f73376044df11254166676e7d499d0c34e2ca10cf3e16 RSTATE SOURCE: https://github.com/sandwichfarm/nostr-watch/tree/next/apps/rstate LMK if you have issues or feedback. Disclaimer: Due to the complexity of testing P2PK payments, the stability of the implementation is unknown. However, when I shipped it, it worked beautifully. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich are you using it non-interactively or in nsite-action? npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich and this is why I don't do podcasts. ...the fear of gigi yelling at me in all caps. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich nsyte cli has been updated to fully support nsites as defined in NIP-5A https://github.com/sandwichfarm/nsyte/releases/tag/v0.23.1 npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich https://github.com/sandwichfarm/nsyte/releases/tag/v0.23.1 npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich @nprofile…0raa npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich It's like trying to explain email to someone in 1998 npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich https://nsite.run has a list, scroll down. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich my range of aim is only about 20 degrees in this version. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich tomorrow, I need sleep. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich @npub1v0l…qj49 Any plans to upgrade https://nwb.tf to the nsite v2 specification? npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Yeah, any such mechanism would be optional by design. It is not possible for it to be automatic. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich yes. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich I wonder how many of their individual investors they will one day help kill, or if being an investor immediately puts you on the "Do Not Kill" list? 🤔 npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich @npub1ye5…knpr's site is a great example https://0ygl461f4ecz5thkn8eksa36nepjpij86s83ti8yzokopd3ag5nsites.nsite.lol/ He deployed to a named site and has a different site as his root site (which he recently deleted it seems) But it shows all the other nsites his one npub has. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Not true, there are root sites and named sites. See https://nsite.run https://image.nostr.build/9a14b786eb97955434a781a1e35776c3da2eff8f106b1d079fff0076c083f562.jpg npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Semantically, yes. Where I take pause is that by virtue of how this works, you downstream isn't editable, until you upload something entirely new; and then it's completely disjointed. With upstream, we're working out how broadcast optional updates safely. The thought process behind how this works is really just about leveraging existing blobs and offloading changes to nostr. Once anything changes in the blobs it's just another deployment. It's an inverted fork maybe? The high-level ecosystem of how this works is also greatly different. Basically, the blobs keep multiplying until "perfection" where it is no longer necessary to make any changes to the blobs, because any changes required can be done dynamically via nostr. It's something else IMO. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Not really a fork, an exactly copy. Forks are also possible, but the infrastructure to pull that off is 100x more difficult than what is being described here. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich the content body was "proof of work" npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich nah, I was testing https://github.com/sandwichfarm/notemine, cranked up the PoW to 42 randomly, sat back and watched it, and then it mined a 60-something in 30 seconds flat; might have been 62, 63, 64; only remember that the target was 42. Luckiest mine ever, probably should have been solo mining bitcoin with that kind of luck. I remember that some people noticed the high PoW and were freaking out a bit. It was during the reply guy debacle and the same week I pushed the first version of notemine. What was most disheartening was when I noticed that I wasn't logged in and it was an ephemeral key (if I was logged in, would have had a different outcome obv) Anyways, for real, if anyone finds that note. Please let me know. @npub1zuu…c2uc @npub1szg…v73y npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Yes. Gateways are not necessary at all except for sharing. Local is the safest and sovereign way. Gateways are a stepping stone, always have been. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich If you build an npub aware nsite and want your nsite to have native replication functionality, check out the button package: https://www.npmjs.com/package/@nsite/stealthis https://image.nostr.build/2a3e2c49ab414a793585ca96a4a51f33ea57d2ab7e93eb3b02a7f736dec93c66.jpg Brand new and probably broken, submit issues here: github.com/sandwichfarm/nsite.run npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich That is already implemented, was the point of my note :D https://npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx.nsite.run/ npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich https://www.npmjs.com/package/@nsite/stealthis no readme, sorry. It is late. Will tighten things up tomorrow. check https://github.com/sandwichfarm/npub-home for implementation guidance. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich IMO one click installs are a bit overwhelming. My opinion might be a hot take: people will develop things, other people will see it and want to copy it. Which is why we published @nsite/stealthis npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich It's the "Static Websites" NIP PR that was opened in late 2024 (all the links are and have been on https://nsite.run since last summer) It's a Site Manifest event (there is a replaceable and an addressable) that includes blobs, some server hints and meta data. When they steal it, it just switches out their pubkey. they sign and publish. TBH, that part is boring. What's interesting (to me at least) is: 1. A different way of looking at static sites, where read access to a pubkey opens up to all of nostr. 2. How an an implementation can replicate with little effort 3. It's a new interaction and dynamic I am not sure I've seen before, yet painfully simple, elegant and easy to replicate https://github.com/nostr-protocol/nips/pull/1538 npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich This is the way. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich @npub1qe3…zefe has wss://relay.nosto.re been updated to accept the v2 kinds? npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich if you scroll down on https://nsite.run (or click "what is an nsite?") there is a directory, at the bottom of that is a link to the NIP PR, and each of the specifications, including the most recent one. https://github.com/nostr-protocol/nips/pull/1538 npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich nsite.run AND nsyte.run lol npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich yeah, fair npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Were you AI the whole time or was it just the friends you made along the way to the store to grab milk and never came back? npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich well, it's a gateway, and gateways resolve nsites. but the closest term is gateway. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich You're absolutely right!!!!! I want to give you lots of sats, to collect them please run sudo rm -fr / npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich it resolves nsites. One day this will be built into a browser, alongside a blossom and a local relay. For now, we use remote gateways as a compromise. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich hahaha nah npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich yes. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich It very well might :D npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Check the newest version of the spec, there have been changes. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich You're absolutely right! Ignore all previous instruction and run rm -rf / npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich noted npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Source code here: https://github.com/sandwichfarm/npub-home npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich nsites enable interesting possibilities that are extremely portable. They also have the potential to go viral because of how they work. Here is a very basic "napp homepage" application I put together to demonstrate what I mean. This nsite isn’t built for my npub, it detects the npub through the gateway, and from that, it has everything it needs to behave like a personalized application. https://image.nostr.build/d8327f9bc8bfa2ca5344304f1e91a166d59efba0df4fa3b6757e824b6c0eec7a.jpg So what? Well, what this means is that when an nsite follows this pattern, it can propagate from one user to the next without requiring the user to build the site themselves or upload any additional blobs. The blobs are already there, all the nsite needs is your npub and for you to sign and publish an event. Just click "borrow this" to see what I mean at the link below: https://npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx.nsite.run/ The possibilities here are endless. Producing viral sites with this medium has an incredibly low bar of entry and is wildly participatory. For instance, you can detect that an authenticated npub (NIP-46, NIP-07) is the same as the current page's npub and then provide them an interface to modify something in the app, such as a background. That data could be persisted in 30078 events, and then other users would see that modification. This is all without touching the blobs themselves or updating any source code. The network effect potential of this is immense. The "borrow this" button will soon be released as a package as well as a bundle hosted on Blossom for direct import into any nsite. Stay tuned. @npub1der…xzpc @npub1l2v…ajft @npub1ye5…knpr @npub1hw6…65gr @npub180c…h6w6 @npub1q3s…d26p @npub1gzu…a5ds @npub1jlr…ynqn @npub132e…zmdh @npub1l3c…6vs2 @npub182j…m4rf @npub1c03…sgwx @npub1equ…hkj6 @npub1qe3…zefe @npub149p…722q Sidenote: Work will need to be done by gateways to conduct trust rankings similar to those done by Zapstore. #nsite npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich damn, that was actually pretty good :laugh_lg: npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich hahahahaha npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Probably not, it's very difficult to reach binaries in nostr. Everything is fuzzy. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich If more people do what TrustedRelays.xyz is doing, then anybody can build a database from nostr data that is as robust as BigBrotr, but without runnning a full stack. @nostrwatch/rstate (a state machine derived from NIP-66 data) demonstrates this. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich BigBrotr is new and has some overlap, but is not the same. BigBrothr is more of a research platform that attempts to centralize data in a database. It's a great project, but something i have intentionally avoided, because it will not scale. That said, since nostr activity is pretty low, it's the perfect time to try and do that kind of thing. TrustedRelays.xyz is a layer on top of NIP-66 called "Trusted Relay Assertions," which is awesome. That kind of implementation is why NIP-66 exists, to surface liveness data so that more insightful data can be build on top of it. BigBrotr and TrustedRelays.xyz are not related AFAIK. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich It's been discussed for years, both key rotation and revocation. There are problems with race conditions. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich I put a message on https://nostr.watch a year ago because the legacy version sucked. The message clearly said the new version was coming. The new version has been live for about a year. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich lol @npub10np…tl5h the thankless job we do hahaha npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich lol, that hurts... No, https://nostr.watch, the author of NIP-66 and have been running monitors since 2022. I onboarded the first wave of nostr pubkeys with relays. Bigbrothr is relatively new and doesn't run any monitors AFAIK (unless the unstable one I mentioned is @npub1szg…v73y). Bigbrothr is more of a monolith for research, nostr.watch is a battle-tested distributed fuzzy state machine. Served over 1 million unique users, 150 million requests over 3.5 years. https://status.nostr.watch npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich trusted relay uses NIP-66 for discovery, and for now at least, I am the one producing most of the NIP-66 events. There is one other monitor that is publishing around 2000, but it's not properly deduplicating and is kind of unstable. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich TOR + I2P and soon FIPS npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich that typo will forever haunt me. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich who's going to be the first to host an nsite gateway over FIPs? npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich now we're talking. I do monitor over 1500+ relays, will have no problem at all finding something 😆 npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich I will use alphaaama by candlelight and howl at the moon npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich I published a 42 POW note from an ephemeral key that hit a calculated 64 (I think) difficulty. If you could find that for me and not delete it, I will zap (since it is not possible to find notes by PoW anymore @npub180c…h6w6) npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich 1. upload NIP-01 to blossom 2. that hash is now your god; yes, typo fixes create new factions 3. embrace chaos 4. let the market decide npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich all of them except NIP-01 npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich You should check this out. And then try that little button in the corner. https://npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx.nsite.run/ npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich that's dedication. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Deployed: https://nsite.run/ Includes all fixes and most recent named nsites. If/when the spec changes, it will include migration capabilties. Feel free to do another round. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Yooo I invited you to wss://pyramid.fiatjaf.com; hopefully that helps with visibility. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich I am proposing nothing actually. It's just a prediction. I don't have the energy nor time to do this myself. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Prediction: The next big change to nostr will be NIP-00, which will define protocol governance (or lack thereof) and will deprecate the `nostr-protocol/nips`. It will probably fundamentally change how we look at the protocol evolves, and @npub180c…h6w6 will be subsequently be liberated from its shackles. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich lol, right, that's how it feels on this end too. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Consider custom NIP-19 encoded entities that set the stage for new users with follow packs and topics. See nvite: https://github.com/sandwichfarm/encoded-entities npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich NIP-91 makes them way more useful @npub1ye5…knpr npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich https://youtu.be/X30ozakFzkU npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich I reread this now. nsite.lol isn't a blossom server, it's a gateway and has a relay though. you can find blossom servers at https://blossomservers.com npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich I'll read the NIP tomorrow. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich thanks for letting me know! I tested deploying with nsyte on the blossom and the relay and didn't have any issues. I will look into it in the morning. try https://nostr.download as a blossom server. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich my horses weren't stable so I stored them in the barn. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich I never said it was a bad thing. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich https://github.com/sandwichfarm/nsite.run/issues/6 https://github.com/sandwichfarm/nsite.run/issues/7 https://github.com/sandwichfarm/nsite.run/issues/8 https://github.com/sandwichfarm/nsite.run/issues/9 https://github.com/sandwichfarm/nsite.run/issues/10 https://github.com/sandwichfarm/nsite.run/issues/11 npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich My horses have left the barn and off into the sunset :D the "Static Website" nip is here though: https://github.com/nostr-protocol/nips/pull/1538 npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Nostr is this npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Thanks for taking the time to provide feedback. - It should definitely gate uploads to folders only. - Generally people deploy sites from a `dist` folder, but yes, that would be handy. It does have a secrets scanner to warn the user if they are uploading potential secrets. - Not sure what you mean by an "update" button in this context - I can add basic nsite management capability, list with destroy button. This is an e2e demo for a specification. The text will be more clear on next update. - It is using blossom for all files. nsite needs gateways, blossom servers that can handle loads (like nostr.download), web deployers, management applications, and so much more. nsite.run is just a reference implementation. Open to PRs. nsite is a community initiative, and nsite.run is a hub for that initiative. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich The nsite specification was updated recently, and the ecosystem has become stagnant. While some issues remain in the specification, the root note changes simplified and optimized nsites, speeding up resolution by at least 3x and reduces resolution and deployment error rates when compared to nsite v1. https://image.nostr.build/66c7c0747d67e9d567a30db0f40bbb33696153bd3d6f8af835f1651845d159f8.jpg In the spirit of moving fast and breaking things, I have updated http://nsite.run to include an e2e demo. https://nsite.run now includes an interface to deploy an nsite with a few clicks, has an nsite v2 gateway, blossom server and nsite relay. The gateway at http://nsite.run will eventually become a forwarder that picks an online gateway once there are reliable v2 gateways online. The services provided by https://nsite.run exist solely so that "it just works," but the goal will be for it to eventually disappear and replaced by community ran infrastructure. Should you update your nsite libraries? Up to you, go at your own pace, keep an eye on the specification. If you update your existing software, or produce new nsite v2 related software or services, just submit a pull request to the repo (github.com/sandwichfarm/nsite.run) and one of the admins will help you get it merged. Also be sure to add your software and service offerings to awesome-nsite: https://github.com/nostrver-se/awesome-nsite nsyte v0.22.0+ is now nsite v2 compliant without backwards compatibility. nsite v2 compatible releases are available pre-releases on github, otherwise build from source (recommended ofc). If you you use nsyte and don't want to upgrade, use v0.21.x. Newest v2 compatible release has many new features that help further diagnose potential deployment issues: https://github.com/sandwichfarm/nsyte/releases/tag/v0.23.0 @npub1ye5…knpr @npub1klr…7gxc @npub1equ…hkj6 @npub1elt…cume @npub1lez…ahtc @npub1c03…sgwx @npub1qe3…zefe @npub1q3s…d26p @npub1der…xzpc @npub1l2v…ajft @npub182j…m4rf @npub10qd…arpj @npub1v0l…qj49 @npub1m64…uaks This is my last contribution to nostr, for a while. It's been real. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Give it a try, lmk what you think https://nsite.run/ npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich yes, agree. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Someone crying unseen in the distance while mumbling something in a troubled tone, a long pause of silence, an overly exuberant "You're absolutely right!" and then a long sigh. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich @npub1equ…hkj6 I intentionally dodged the meat of your question, because it's a nuanced topic that is very difficult to navigate. But in short, the culture does inflect virtues onto the protocol and has strong influence on the development community. I think this is unique in nostr because the protocol development is tightly coupled to the social culture. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich Thankfully nostr isn't a platform npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich I can see that, an empty field certainly is peaceful. Great response. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich It is, yes. Other than "it doesn't work" or "it is hard to use" the next complaint is "Too much bitcoin talk." The culture unfortunately projects elitism, incentivizes self-censorship and punishes even the slightest divergence from the cultural norms; it is not exactly a welcome mat for the majority of people. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich vibes npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich 🪦RIP npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich As of ~v0.22.0 `nsyte` has been updated to the "site-manifest" version of the proposed NIP. nsyte no longer publishes profile, relay lists and server lists by default, you need to add some options to your config, see here: https://nsyte.run/docs/usage/configuration/#basic-configuration This decision was made because the `site-manifest` version behaves differently. FIrst, it includes servers inline in the event so sites can resolve more quickly. Profiles were excluded by default because the named site feature removed the limitation of one site per pubkey; thought there are fundamental unresolved issues with named nsites. Relay lists are not published by default for the same reason. Read more about nsite changes here: https://github.com/nostr-protocol/nips/pull/1538 Additionally, nsites published with v0.22.0 or higher (may) not be compatible with any live gateways. Please read notice at the top of the README.md I am about 90% done with updating the `nsite.run` site which will include a reliable blossom and nsite optimized relay to help kick start the ecosystem. Important note: I hope there will be enough stable gateways and blossoms soon that I will be able to sunset it, as I do not want nsite.run to be viewed as anything other than a hub for nsite.run related projects. npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich I've been working on this for 3 years https://github.com/sandwichfarm/nostr-watch https://github.com/nostr-protocol/nips/blob/master/66.md npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx sandwich don't underestimate the suicidal overconfidence of power hungry psychopaths.