Show thread history
SLCW
2w ago
I don't use nos.lol, but I have relay.nostr.band set as one of my general relays with read-only access so I'm never writing to it. I just use it to pull content because it's an aggregator, and I save a ton of data useage by just pulling from there as opposed to 7 other big relays.
See translation
1
1
0
0
0
Replies
Silberengel
@Silberengel
2w ago
It makes more sense as a read, than as a write, as it's completely open to all writers, including a lot of spam, and it pulls in most publicly-visible notes.
Having us look for replies in gigantic aggregators doesn't make sense, for an outbox model, as the client could always include an aggregator as a fallback for things it should be able to display, but can't find in the outbox.
It all needs to be thought-through a bit more. We're thinking. 🤔
Having us look for replies in gigantic aggregators doesn't make sense, for an outbox model, as the client could always include an aggregator as a fallback for things it should be able to display, but can't find in the outbox.
It all needs to be thought-through a bit more. We're thinking. 🤔
See translation
0
0
0
0
0
SLCW
@SLCW
2w ago
Client based aggregators make me a little nervous because I always think of Primal and their weird cache server model. Obviously, it could be made a lot smarter and less obstructive, but I think doing that on the client level also negates some of an aggregator's benefit, namely the reduction in data use. If the client is doing it, then all the relays being aggregated are still being downloaded per device. Just some initial thoughts, but I think it's valuable to query these ideas, and brainstorm them because that's how we arrive at great solutions!
See translation
0
0
0
0
0
Rizful.com (zap tester)
@Rizful.com (zap tester)
2w ago
Zap test on this note… we made seven attempts to⚡zap this note, using your lightning address starting with "slcw", over a period of 14 minutes. All seven attempts were successful. You should check on your end to be sure you received these. Average zap time was 6057ms (6.1 seconds). We consider this zap time slow... generally, zaps should complete in under two seconds. (Other Nostr users might think your zaps are broken, might not zap you again.) We recommend you receive zaps with a well-connected, cloud-based Lightning node to reduce inbound zap latency.
See translation
0
0
0
0
0
SLCW
@SLCW
2w ago
I received seven 1 sat zaps 8hrs ago, which I'm assuming are yours. I have my incoming sats routed to a different wallet via my @getalby.com address. So those zaps hit that wallet. I've had no other problems sending and receiving from my node. Everything appears to be in good working order on my end.
See translation
0
0
0
0
0
Silberengel
@Silberengel
2w ago
I meant an aggregating relay, like relay.band or lumina.rocks, or even someone's local relay.
Clients could just let you list a fallback relay, where you'd like them to look for notes that seem to be missing because the outbox relay is down, or something.
Clients could just let you list a fallback relay, where you'd like them to look for notes that seem to be missing because the outbox relay is down, or something.
See translation
0
0
0
0
0
SLCW
@SLCW
2w ago
Doh! I see. That clearly makes more sense than the notion of a client-based aggregator like I was thinking of. And that's why you make the big bucks! 😜
See translation
0
0
0
0
0
Silberengel
@Silberengel
2w ago
😂 I wish.
See translation
0
0
0
0
0
01 more reply(ies)