Hey Fiatjaf, I'm frequently receiving rate limit errors connecting to pyramid relays on apps like jumble and flotilla, which then limits my ability to get events. Sometimes it feels like having my ip address banned and i'd only be able to fix it by changing location on my vpn. not actually sure if that's the problem but that action seems to solve it more often than not. Could you make the request limit more lenient, or maybe make it configurable?

Yes, I can make it configurable, but I never hit that limit myself, so please ensure that if you are running behind a reverse proxy you are passing the X-Forwarded-For header to the relay.

That is a surprisingly hard problem, unless I make you adopt those users automatically when deleting their parent. Or what do I do instead? If you're inclined to adoption you can do that manually already, by the way. You can have the same user be invited by multiple users currently, so if it is deleted in one branch of the tree it's still alive on the other. On

Basspistol Relay

there is an example of that happening.

I'll see if I can learn & check around for that, because I'm not sure what it means. But, I use the default settings for my VPN

That’s good news, I can handle it manually for now, and of course it would be nicer if the process could be automated. But it’s not a big deal, no rush. By the way, I noticed that users added via the NIP-86 allowpubkey method don’t seem to get updated in the 13534 membership list event.

Are Pyramid Relays suitable for creating themed relays?

That is the idea. I don't know what exactly you mean by a themed relay, but you can invite like-minded people and get them to do manual themed curation using the /favorites sub-relay. Or you can get them to talk to each other either in groups or in the /internal relay about some theme, like a community. Or you can get them to curate public posts submitted to the /moderated relay, ensuring those meet some standards. If you are aiming for a curated experience you must be more selective with who you invite, as anyone invited will have the power to curate decide what goes in the thing. But if you're aiming for a community to live inside the relay you'll want to be more liberal and get more people. Let me know if you need some crazy feature that isn't implemented yet.

Thank you for spotting that.

This was about the server side setup, unrelated to your VPN. How are you hosting it?

Something like reddits communities, that's what i mean.

I ended up implementing a way to remove a user but keeping them in the tree, that should probably be the default action when deleting someone. I had to because I realized that @𝕾𝖊𝖗 𝕾𝖑𝖊𝖊𝖕𝖞 is flooding wss://pyramid.fiatjaf.com/ with a million notes with ugly images but he has invited a ton of people that I don't want to remove.

truly a badge of honor

Thanks ☺

😂🤣

Settings look like attached. Based on the video, that may not be quite correct. I get "success" when I try to post as the root member to wss://kumo.inkan.cc/ , wss://kumo.inkan.cc/popular/ and wss://kumo.inkan.cc/uppermost/, but for wss://kumo.inkan.cc/internal/ I get "blocked: we only accept events protected with the nip70 \"-\" tag", and for wss://kumo.inkan.cc/inbox/ I get "blocked: event must tag at least one pyramid relay member". Maybe I don't yet quite understand where I should be posting what. I'll keep trying for now ...

Figured it out - the pyramid looks much nicer now! I think I didn't use the release binary during the initial install. I can only publish to kumo.inkan.cc. As for /internal I get the nip-70 response, for /inbox I get the must-tag-one-member response, for /favorites I get a timeout, and for /popular and /uppermost I get "success" but then I can't see the relevant events on jumble and they don't show up in the stats. This is probably all intentional, but it's a bit hard to see what exactly is going on. It might be helpful to make clearer how each of the pre-configured relays expects to be talked to, i.e. what one has to do to publish on it, or how else one is supposed to interact with it if one isn't meant to publish on it.

🤣🤣🤣🤣