sandwich

This is fantastic. The ability to reference an nostr entities in a human readable and communicable way enables many new use cases in the physical world.
One of the complaints about nostr I often get from the uninitiated are that the links are too long and it makes thepeople they share it with suspicious.

2025-05-06 22:35:44

nsyte v0.5.0 release
- nostrconnect
- .nsite-ignore file support
- @npub1ye5…knpr implemented applesauce signer (more reliable, huge code reduction)
https://image.nostr.build/15fcab62d77baa2ddc9c578e34b312b7dc9f6559cb1976eaa56f1922483e54a4.png
https://github.com/sandwichfarm/nsyte/releases/tag/v0.5.0
https://github.com/hzrd149/applesauce

2025-05-05 17:58:02

- reply

this is the first time I haven't involuntarily and violently puked after seeing "FinCEN"

2025-05-05 13:56:19

- reply

Not that I am aware of.

2025-05-04 11:38:41

nsyte v0.3.1
- fixed secrets management
- output cleanup
- various bugfixes
- tested in production CI/CD flow
I am done with this for now, as it satiates all the deficiencies that led me to fork this to begin with. glhf.
@npub1ye5…knpr
@npub1klr…7gxc
@npub1hw6…65gr
@npub1equ…hkj6
https://image.nostr.build/3be3c85e0568ea94ef797fe4df4f846e2fd225611fbca7e2b4d7ae76e3cdc47a.gif
https://github.com/sandwichfarm/nsyte/releases/latest

2025-05-03 13:19:51

- reply

don't think so, but when I was setting up knots I didn't try that hard.

2025-05-03 01:04:10

- reply

datum

2025-05-03 00:12:08

knot +12th/s

2025-05-02 14:55:38

I ported `nsite-cli` by @nprofile…kfet to deno and added bunker support. Had a little help from my assigned agent. Alpha. Binaries available for Linux, MacOS and Windows.
https://github.com/sandwichfarm/nsyte

2025-05-01 16:08:02

- reply

Haha, might have been me, I was debugging https://nadar.sandwich.farm.

2025-05-01 15:26:42

@nprofile…d3rp Was I removed from whitelist on wheat?

2025-05-01 13:45:51

- reply

I buy from a few sources.
EU
https://bitcoinbrabant.com/ These ship with the cheapo heatsinks and cheapo PSUS, so both must be upgraded if you want to overclock as well.
CN
`solobitcoinminer` on aliexpress, these are very well constructed, and they come with upgraded heatsinks and VERY stable PSUs. Only con is shipping time and they use the larger fan connector which I don't like.

2025-04-29 22:47:13

- reply

I don't know, ask a nostr developer 😂

2025-04-29 22:43:05

- reply

Someone else can do it 😊

2025-04-28 11:45:27

- reply

One way to do it I suppose, but since clients don't necessarily have an endpoint (native clients for example) this doesn't work universally. it would probably have to be an event.

2025-04-26 18:10:01

- reply

tracking client capabiltiies protocol level would be difficult but well worth the effort.

2025-04-23 07:58:43

- reply

It is not possible to prevent your note from being stored somewhere. f
Formulating notation for something that is impossible to implement can only result in bad UX because users could falsely believe it is possible when it is not.

2025-04-20 17:46:00

- reply

Is this still using NIP-66?

2025-04-20 15:06:44

- reply

2025-04-20 11:53:25

- reply

Added fan for this voltage regulator, adds some noise, but more stable.
https://blossom.primal.net/85a057be012e9bc90402966b06703a44bb6bcb74407d600aee3f57ed157f132e.jpg

2025-04-20 11:22:19

- reply

... And an 8cm radiator.

2025-04-20 11:15:09

- reply

...and an 80cm radiator.

2025-04-20 11:14:52

- reply

It's a 12v pump, with approx 30cm of 14mm OD PMMA hard line, and a waterblock made for a Northbridge with custom 3d printed mounts to fix the Bitaxe.

2025-04-20 11:03:31

- reply

8cm raditator

2025-04-20 10:56:57

- reply

After tuning and rise in ambient temperature (took the photo in the morning), hash-rate is ~2TH/s @ 63C, still no radiator fans.
https://image.nostr.build/f7615d732c4ad651c34657acd315793359eaa1998833082a21fb93dea0e4e42a.png
https://image.nostr.build/954ce4c6b67f4028114276bca73bb5fb35f8dface2bf142e3544ea1385287d1e.png

2025-04-20 10:09:37

900mhz @ 1300CV thermal test w/ steady 5V supply. Warm loop running at 44C. Passively cooled voltage regulator is crying. No rad fan; silent. Untuned OC. #bitaxe #gamma #oc #overclock
https://blossom.primal.net/b7172e56c021fd628638877f6efe94ea1d152b23305f8cdc0f2a971396a5a8a2.jpg

2025-04-20 08:13:48

- reply

Clients could expose the TOS and PP via NIP-11, which is how users could see it.

2025-04-19 22:09:52

- reply

Probably. Someone should PR NIP-11, would propagate changes faster than a note

2025-04-17 16:22:27

- reply

@nprofile…pxlr

2025-04-17 15:25:07

- reply

Every single web client will have these errors from time to time (if not always), unless they route every connection through a proxy.

2025-04-12 11:46:39

- reply

These terms are acceptable.

2025-04-12 11:14:23

- reply

that would be insanely stressful.

2025-04-12 10:46:18

Opened a PR for an alternative AxeOS OC interface with named presets. https://github.com/bitaxeorg/ESP-Miner/pull/840#issue-2990399888
https://i.nostr.build/fydGh7wwNBasOkWH.png

2025-04-11 16:51:28

- reply

Secret?

2025-04-10 18:52:26

- reply

"enter your nsec" :D

2025-04-07 11:14:33

- reply

What do you mean by "relay overlap" ?

2025-04-07 08:47:51

- reply

And to be clear, they are complimentary and so is relevant. Just wanted to clarify the functionality.

2025-04-07 08:46:23

- reply

They are conceptually much different 😂
Both useful on different ways. Randomness is great in fuzz testing and finding edge cases that are difficult to find without randomness, the auditor I wrote is better for unit testing known vectors to validate expected behaviors.

2025-04-07 08:04:06

- reply

The tests I have aren't random because then its difficult to meaningfully communicate the outcome. Instead it each NIP had a test suite, and then each test in the suite attempts to obtain samples from relays and then uses the uses those samples to construct filters than satisfy the respective test.

2025-04-05 15:55:57

- reply

What is the challenge resolvers face when attempting to resolve the most recent hash?

2025-04-01 14:42:16

- reply

Hahaha

2025-04-01 14:41:12

- reply

😂😂😂

2025-03-28 18:18:36

- reply

All of them.

2025-03-28 14:19:54

- reply

I used coracle I think.

2025-03-28 14:09:56

- reply

Yes, completely rewritten from scratch. There's a link to the original in the GUI.

2025-03-28 11:03:38

- reply

The state is constantly changing, to publish events NIP-66 style would be burdensome in its own way. When I considered publishing events for a similar purpose, I backtracked and landed at a DVM as well.

2025-03-28 10:52:43

- reply

I deployed it.
http://nadar.sandwich.farm/
https://npub1nadarndr8f0fra505suk85xhvgksqer2vnuqsjkvt2tfm7d0wakqhwlpf5.nsite.lol/
(when it decides to work @nprofile…59pa , all events published)
@nprofile…c7nk

2025-03-28 08:56:51

Updated NADAR to use NIP-66 and to also support naddr @nprofile…62gt @nprofile…qyu3
Maybe I will deploy it eventually, otherwise, go for it.
https://github.com/sandwichfarm/nadar

2025-03-28 07:25:29

- reply

Also, I think this is using the legacy API, and since I cannot find a git, I cannot patch it, and thus, it will soon die.

2025-03-28 07:12:59

- reply

No, and I don't plan on adding it.

2025-03-27 12:35:07

- reply

Yes, a long time ago.
https://github.com/SamSamskies/nostr-zap

2025-03-26 20:14:07

- reply

I wish your headphones a long life. I will never buy headphones from Sony because they wouldn't cover the failure under the warranty, despite them breaking inside of the case, and showing them a photo that clearly demonstrated that the part was defective (it had air-pockets where the breakage occurred, shoddy injection modling)

2025-03-26 20:10:48

- reply

Not sure, I was just primarily responding to @nprofile…k94x since he linked to the nostrability repo that hasn't been updated in almost 6 months. Wanted to clarify.
If Client A puiblishes a NIP-22 events without a root event tag, then Client B (and perhaps event Client A) won't be able to find it. Schemas can catch this error either in production or in a CI/CD pipeline. It can also detect these issues by fuzz testing events.
I would personally consider that QA, but maybe not?

2025-03-26 20:07:27

- reply

They sound good but break easily and are near impossible to fix. Mine broke after a year, meanwhile my PXC-550's from 2017 are still going strong, cost $100 less and only needed a battery replacement.

2025-03-26 20:04:26

- reply

It's for validating data, in general. A huge percentage of interoperability issues between clients relates to missing tags or missing data within tags.

2025-03-26 19:58:10

- reply

These are up to date, with some known inaccuracies (and in production use)
Schema: https://github.com/sandwichfarm/nostr-watch/tree/next/libraries/schemata
TS/JS Validators: https://github.com/sandwichfarm/nostr-watch/tree/next/libraries/schemata-js-ajv

2025-03-26 19:55:19

- reply

This one is out of date, I will soon update it.

2025-03-25 11:58:49

- reply

Buidl

2025-03-25 11:47:21

- reply

And why?

2025-03-20 16:19:19

- reply

#nevent1q…79pq

2025-03-19 15:50:06

GM @npub180c…h6w6

2025-03-15 14:07:29

- reply

Happens

2025-03-11 09:06:45

- reply

Very cool

2025-03-09 19:45:57

🥜🥜🥜🥜🥜🥜🥜󠅓󠅑󠅣󠅘󠅥󠄲󠅟󠄢󠄶󠅤󠅕󠄳󠄺󠅟󠅔󠄸󠅂󠅧󠅓󠅪󠅟󠅦󠄼󠄢󠄡󠅠󠅒󠅞󠅁󠅥󠅒󠅇󠅜󠅥󠅑󠅇󠄺󠅠󠅔󠄸󠄽󠅥󠅉󠄢󠄶󠅪󠅑󠄳󠄩󠄳󠅑󠅈󠅂󠅚󠅒󠄢󠅜󠅥󠅉󠅈󠅆󠅚󠅓󠄢󠄶󠄠󠅉󠅈󠅃󠄲󠅟󠅝󠄶󠅠󠅃󠄱󠄲󠅁󠄲󠅆󠄴󠅧󠅃󠅅󠄶󠄷󠅉󠅈󠄳󠄴󠅟󠄢󠄶󠅘󠄱󠅇󠄶󠅪󠅕󠄵󠄲󠅚󠅊󠄴󠅅󠄣󠄽󠅚󠅊󠅚󠄾󠄢󠄵󠅨󠅊󠄷󠅂󠅜󠄽󠅪󠄵󠄡󠄽󠅇󠅁󠅧󠅉󠅚󠅘󠅚󠄿󠅇󠅉󠄤󠅉󠅪󠅜󠅘󠅉󠅝󠄽󠄠󠅊󠅄󠅅󠅧󠄽󠅝󠄽󠅩󠄽󠅪󠅜󠅘󠄽󠅪󠄵󠄡󠄽󠄷󠄾󠅘󠄽󠅪󠅛󠅪󠅊󠅄󠅘󠅝󠅉󠄢󠅊󠅝󠅊󠄴󠅘󠅘󠄾󠅚󠄽󠄠󠄽󠅝󠅁󠄣󠅉󠅇󠄾󠅉󠄹󠅁󠄿󠄤󠅢󠄩󠄧󠄤󠄨󠅔󠄦󠅜󠄴󠄹󠅁󠅁󠄴󠅙󠄥󠅄󠄩󠅢󠅝󠅞󠅨󠅖󠅨󠅉󠄣󠅈󠄼󠄻󠄩󠅆󠅊󠅊󠅁󠅤󠄩󠄾󠅞󠅁󠅠󠅇󠅀󠄦󠄾󠅘󠅉󠅁󠅂󠅘󠅓󠄣󠅘󠄱󠅉󠅚󠅓󠄣󠄿󠅄󠅓󠅪󠄽󠅇󠅁󠅪󠄽󠄷󠄹󠄤󠅉󠅝󠅅󠄠󠅊󠄷󠅊󠅚󠄾󠅪󠄹󠄢󠅉󠅇󠄽󠄡󠅊󠅚󠅜󠅜󠄿󠅇󠄺󠅙󠅊󠄴󠅂󠅚󠄾󠅚󠅛󠄥󠄾󠅝󠅆󠅝󠅉󠅪󠅉󠅨󠅉󠅪󠄹󠄤󠄾󠅄󠄽󠄡󠄿󠄴󠄾󠅛󠄿󠅇󠅉󠄣󠅊󠄷󠅆󠅛󠅊󠅝󠄵󠄤󠄽󠄷󠅊󠅛󠅉󠄢󠄶󠅚󠅇󠄳󠄵󠄳󠅃󠄹󠄾󠅔󠅠󠅈󠄶󠅏󠅠󠅠󠄩󠅈󠅁󠄹󠄥󠅉󠅏󠅙󠅒󠅝󠅁󠄸󠅁󠅝󠅚󠅏󠅜󠄵󠄹󠅂󠅂󠅏󠄩󠅈󠅪󠄾󠅝󠅇󠅙󠄾󠅈󠅖󠅩󠅚󠅉󠅇󠄵󠅁󠅉󠅈󠄾󠄤󠅁󠄴󠅔󠅛󠄾󠅚󠄱󠄤󠅊󠄴󠄵󠄤󠄽󠅄󠅘󠅙󠅊󠄴󠄽󠄣󠅊󠅇󠅂󠅜󠄽󠄷󠅆󠅘󠅉󠅪󠅛󠅪󠅉󠅚󠅉󠄠󠅊󠄴󠄹󠄤󠅊󠄷󠄵󠄤󠅉󠅇󠅊󠅝󠄾󠅚󠅔󠅛󠅉󠅪󠅂󠅜󠅊󠅚󠅅󠄥󠄾󠅚󠄽󠅨󠅊󠅄󠅘󠅚󠄽󠄴󠄱󠅩󠄿󠄴󠅓󠄤󠄾󠄴󠄹󠅧󠄽󠅪󠅔󠅝󠅊󠄴󠄲󠅘󠅉󠄡󠅗󠅘󠄱󠅏󠅆󠅆󠄨󠄾󠄦󠅅󠄲󠅊󠄳󠅝󠄸󠄡󠅚󠄱󠅊󠅟󠅆󠅑󠅂󠅊󠄶󠅥󠅘󠅃󠄧󠅝󠅆󠅊󠅖󠄸󠄡󠅡󠅉󠄩󠄶󠄣󠄾󠅥󠅅󠅚󠄤󠅧🥜🥜🥜🥜🥜🥜🥜🥜🥜🥜🥜🥜🥜🥜

2025-03-07 21:07:05

meat good.

2025-03-06 13:14:03

- reply

Clearly the correct answer

2025-03-03 21:05:11

- reply

Thank you.

2025-02-27 09:24:06

- reply

It* not I

2025-02-27 09:23:35

- reply

I will not deprecate manual relay lists. NIP-66 enables returning only online relays, by design, with the ability to filter relays based on a number of factors. In 2022 nostr.watch also manually maintained relay lists.
IMO manually curated relay sets are still useful, for example, this tor list of yours could instead be a relay set, and then people could use them in clients like nostrudel, without manually copying/pasting or relying on github.

2025-02-27 09:16:59

- reply

jfc, 2 years 😂

2025-02-27 09:16:36

- reply

NIP-66 is what does and has been the dataset behind nostr.watch for 12 years. It's implemented in many clients: snort, nostrudel, jumble, etc.

2025-02-26 12:30:17

- reply

I can generate a lost of around 500+ that are online if you need them, but they will also be available via NIP-66 soon as well.

2025-02-25 17:12:25

- reply

thanks, means a lot. Especially considering how broken that version is. I'm pushing a release within the next few days.

2025-02-24 14:58:17

- reply

There is much to unpack here, and I'm all for it.

2025-02-21 12:31:20

- reply

And if all keys are compromised via a swift, coordinated attack?

2025-02-21 12:21:28

- reply

Sure. What are you more interested in:
1. learning technique, applying the technique in nature and getting better (very good knowledge in there can be applied to different things), and maybe working up to astrophotography over time.
2. astrophotography and ability to share the experience with those who may or may not have ADHD?

2025-02-18 14:03:42

- reply

Until a key is compromised.

2025-02-13 01:24:46

- reply

😂

2025-02-13 01:14:47

- reply

Clean af

2025-02-12 02:20:15

- reply

My mind immediately went to using timers to hotfix race condtions. I should probably go outside.

2025-02-11 10:45:53

- reply

One step at a time...

2025-02-11 09:03:22

- reply

Recommend to use relay.nostr.watch or relaypag.es instead or in addition to

2025-02-11 08:58:01

- reply

NIP-66?

2025-02-11 05:14:49

- reply

Well, I just figured it out. The changes weren't being deployed :D

2025-02-11 03:57:31

- reply

Thanks for the help btw, it's difficult to rapidly develop + test every possible case in every possible browser :D

2025-02-11 03:07:02

- reply

handles serviceWorkers in a secureContext differently*

2025-02-11 03:06:40

- reply

Should have it this time. I'm assuming you're using Firefox in a private tab. It handles serviceWorkers in a secureContext, and I wasn't accounting for this case. ~10 minutes.

2025-02-11 02:31:52

- reply

CDN cache has been purged.

2025-02-11 02:31:11

- reply

It might be a CDN caching issue, with the change that was added, it would be impossible for that error to occur.

2025-02-11 02:03:38

- reply

hotfix will be deployed in roughly ~10 minutes. It's possible the error caused you to have breaking state. lmk if the error persists.

2025-02-11 01:57:05

- reply

Ah, ok. See the issue. Other than livereload for some reason being in the production build (oops), looks like the service worker deregister implementation was naive. Many thanks, will patch it today.

2025-02-11 01:46:39

- reply

Interesting. Could you send me console log?