sandwich

404

Public Key

npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx

NIP-05 Address

bread@sandwich.farm

NIP-57 Address

bread@sandwich.farm

Profile Code

nprofile1qqswwud0pvzu362lehm0av6sq4zd97cue5uy0z8f7jgtk0hz368dvmcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqjyamnwvaz7tmwdaehgu3dwejhy6txd9jkgtnhv4kxcmmjv3jhytnwv46q60txrm

Publishing to

relay.damus.io

nostr-verified.wellorder.net

wheat.happytavern.co

Author Public Key

npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx

Show more details

Last Notes

2025-05-07 22:12:26

- reply

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-04-29 22:43:05

- reply

Someone else can do it 😊

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 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: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-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-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-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:23:23

gn.

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?

2025-02-10 23:49:48

- reply

Half of it a sandbox still. Im working out a few more kinks before wrapping everything up.

2025-02-07 10:00:01

- reply

Then you're doing it right 😊❤️

2025-02-07 09:46:26

- reply

You're doing it right

2025-02-07 09:38:50

Despite not being particularly invested in US politics, other than taxation and foreign policy, I will say this is the most entertaining show I've ever witnessed. Nothing short of hilarious with a perceptible dose of catharsis.

2025-02-05 05:46:03

- reply

Could just be a reposter, this is why we need to start using `i` tags from @nprofile…u7te 's NIP (forget the number of the NIP 😅)

2025-02-05 02:45:55

- reply

NIP-01

2025-02-01 07:18:26

shoutout hypertuna 😂

2025-02-01 03:02:42

- reply

Yep.

2025-01-31 12:04:06

- reply

Probably not, buds are for blossom, this would be nostr discovery.

2025-01-31 12:02:09

- reply

they're useful .... until you do something you're not supposed to.

2025-01-30 13:48:36

- reply

Would be a new NIP, completely different t criteria and ttest vector. Could reference NIP-66 though.

2025-01-30 13:31:08

- reply

Someone else can do it, I'll aggregate it 😂

2025-01-28 14:37:02

- reply

And yes, many problems with NIP-11s, it's one of many reasons why I wrote @nostrwatch/schemata; not on npm yet, need to fix NPM publishing in my CI.

2025-01-28 14:35:43

- reply

I used my personal relay, many relays ignore empty filters.

2025-01-28 13:06:10

- reply

Submitted PR.

2025-01-28 12:43:12

- reply

Ah, wrong branch

2025-01-28 12:38:43

- reply

Forget to commit that component?

2025-01-28 12:20:58

- reply

Sure.

2025-01-28 12:20:38

- reply

Yes. Let me know if you have any questions.

2025-01-28 11:54:59

- reply

BTW the link to the banner broke on jellyfish, it was the only relay that I could test banners against 😂

2025-01-28 11:53:25

- reply

Yeah, its totally possible. I've refrained from doing it myself because I like the separation of concerns.
...my agents are separate processes and they publish to relays.

2025-01-28 11:49:45

- reply

(testing a wiki implementation)

2025-01-28 08:47:58

- reply

You can aggregate NIP-66 events from relaypag.es and relay.nostr.watch instead.
https://github.com/nostr-protocol/nips/pull/230

2025-01-28 08:47:18

- reply

https://next.nostr.watch

2025-01-27 14:47:46

- reply

🤔
https://i.nostr.build/ZO9GolTDQ58xebw5.png

2025-01-27 14:25:58

- reply

How so? I've shared my data and fulfilled over 100m requests 😂

2025-01-27 13:05:54

- reply

Also, will eventually release an API that aggregates NIP-66 data, but I won't be hosting it, I don't want to contribute to centralization, and it's a largely fruitless endeavour that recieves little thanks and bucketloads of complaints.

2025-01-27 10:52:29

- reply

NIP-66

2025-01-27 05:53:24

This is something I've wanted to do since the day it was released 2 years ago....
This is the sunset notice for api.nostr.watch
If for some dumb reason you're using it, you have one monthfrom now before it goes offline forever.
If you're interested in alternatives, please inquire.

2025-01-26 08:36:25

- reply

Migration should probably be done via DVMs

2025-01-26 00:04:53

- reply

Just go to preferences and click wipe if you have any problems.