few understand this flex

I must have missed that. I don’t love the interface but it does implement nip42 auth correctly which is apparently the hill I die on now. I still only use 1 relay, my proxy, and it requires auth. damus is totally unusable after latest update. primal doesn’t work either. was at a loss when someone recommended nostur so I tried and to my surprise it actually works.

although it says my zaps fail. did you get my zap?

moving kind 1 out of the original spec is confusing and a mistake.

https://github.com/nostr-protocol/nips/pull/1076

📣 impress your friends by sending #nostr notes straight from #vim using vim-nostr!



https://github.com/bndw/vim-nostr

@nevent1qqs...

I’ve been building an experimental nostr relay with the goal of improving bandwidth efficiency and performance of nostr clients.

the idea is simple: instead of connecting the phone to a dozen relays and deduplicating events locally, push that logic into a “proxy relay” in the cloud.

- duplicate events are never sent to the client, improving both bandwidth usage and performance
- the proxy maintains a local database of events to further speed up queries
- your client IP address is only visible to your proxy, not the upstream relays
- you can define separate upstream read and write relays
- nip-42 + allowlist auth to optionally restrict access

if you look at my set of relays you’ll see I’m only connected to one - that’s my private relay proxy. I’ve been using this setup with damus for the better part of a week and so far so good.

the code is free and open source at https://github.com/bndw/nostr-relay-proxy

don’t forget to consider how many watts/amps you’re drawing. it’s common to have 15 amp cabling in walls and I don’t think it’s recommended to exceed 80% capacity, especially continuous load.

I’m not an electrician, but let me try to do the math.

Amps = Watts / Volts

assuming you’re using 120v power and running the s9 at 1400W, you’d be pulling about roughly 12 amps:
11.7 = 1400 / 120

assuming a 15A circuit, your utilization is probably right at 80%:
80 % = (12 \ 15) * 100

I have some old wiring and things started smelling funny after running an aisc for a day. be careful.

notes are visible from the profile “replies” tab, but not on timeline. I assume it’s related to caching based on my understanding of your architecture.

could damus use an LRU and expose a slider for the user to choose cache size?

trending: some kind of damus secret-sauce algorithm. show me cool stuff based on past zaps, likes, follows, etc.

api/store: don’t be the gatekeeper for algorithms. allow others to publish algorithms and users to use them. provide some kind of api for making that possible

@npub1zafcm... latest testflight of @npub18m76a... has persistent notifications for me.
- open app
- notification alert
- look at them
- close app
- open app
- notification alert

been experiencing this jumping behavior in damus testflight 1.5 for a while. attempting to click into a thread and the viewport jumps up and seems to navigate back.

here’s an example of trying to read some replies before eventually giving up.

cc: @npub1xtscy... @npub1zafcm...