Thread - Nostr Hypermedia

hodlbod hodlbod@coracle.social 7 months ago

New project just released: Compass 🧭 For a long time I've wondered how bad things would be if @PABLOF7z's wss://purplepag.es relay went down, since it's the only dedicated kind 10002 indexer I'm aware of, and is heavily relied on for bootstrapping user relay selections, which is a key part of keeping nostr decentralized. So I stood up another one at wss://indexer.coracle.social. Regular users don't need to do anything, but I encourage client developers to add this to your list of relays you check for NIP 65 kind 10002 relay selections. I've also open-sourced the project at

GitHub

GitHub - coracle-social/compass: An ansible configuration for setting up an indexer relay

An ansible configuration for setting up an indexer relay - coracle-social/compass

so anyone who wants to can run their own. The project also supports mirroring other indexers via `strfry router`, but I have left that as an opt-in feature. Unless you expect significant load on your indexer, mirroring would only increase the number of unnecessary connections made to other indexers, so please be considerate when setting up mirrors.

Replies (32)

OceanSlim oceanslim@happytavern.co 7 months ago

Tysm for this.

Keyhan Alizadeh _@kehiy.net 7 months ago

no need to use strfry. pages domain specific relay is out there, a long time:

GitHub

ddsr/pages at main · dezh-tech/ddsr

The Dezh DSR's (Domain Specific Relays) repository. - dezh-tech/ddsr

its much more lightweight, anyone can run one of them and the discovery part can improve more overtime.

2 replies ↓

hodlbod hodlbod@coracle.social 7 months ago

Does it store kind 10002? Because that should really be the thing that gets indexed, rather than profiles (although that's also helpful). Also, I'm not sure what you mean by lightweight, a blossom server is out of scope for what I'm trying to do. Although the fact that it's dockerized does make it easier to deploy.

Keyhan Alizadeh _@kehiy.net 7 months ago

yes. it stores: 0,3,10002. also, blossom server can be disabled. its just an additional option. if more people who run this relay think this is not useful we can simply remove it. it even discovers kind 5s (in future 62s) to respect deletions of profiles or account vanish requests. also, the reason that it's lightweight is because its based on khatru. and yes. docker makes it easy to run. you can replace it or just use it beside your current relay to see how they perform. 🫡🚀

1 replies ↓

Keyhan Alizadeh _@kehiy.net 7 months ago

also, pages domain specific relay is managable using nip-86. you even receive reports for example because of impersonation and then you can blacklist them. it can even be more improved. for example if the report is from admin, it will take the action itself rapidly.

2 replies ↓

hodlbod hodlbod@coracle.social 7 months ago

Cool, sounds very good. You should add that extra info to the readme! One other question, does it mirror other relays?

1 replies ↓

elsat elsat@habla.news 7 months ago

📝

GitHub

Relay list metadata [NIP-65] Positive Interoperability Tracker · Issue #180 · nostrability/nostrability

spec: https://github.com/nostr-protocol/nips/blob/master/65.md related to: #69 #166 app Read Write comment damus ✅testflight ✅testflight no way...

hodlbod hodlbod@coracle.social 7 months ago

I am using router to sync with purplepag.es and relay.nostr.band, so it should be reasonably complete. I'm using supported_nips = [65] to signal this, but it wouldn't hurt to be more explicit

Keyhan Alizadeh _@kehiy.net 7 months ago

what do you mean by mirror? here is an update:

GitHub

Release pages@v1.0.2 · dezh-tech/ddsr

pages@v1.0.2

readme updated. blossom removed, moderator option added. admins can call nip-86 endpoints. moderators can send reports (kind 1984) and relay will delete it from database rapidly. i still believe we can improve discovery. you may want to take a look and contribute.

Max max@towardsliberty.com 7 months ago

That's awesome, thanks!

Dikaios1517 dikaios1517@nostrplebs.com 7 months ago

How much space does this take up on disk? I imagine it is still relatively small, right? Would this be something a mobile relay could index, like Citrine? Maybe not index all pubkeys’ 10002s, but an extended WoT, like follows, their follows, and one more layer deep of follows. We’d end up with something similar to a DHT, but with each mobile relay only indexing the 10002s of those they are likely to want notes from regularly, so they have to make requests to the larger indexers far less often. Am I crazy here @greenart7c3?

1 replies ↓

hodlbod hodlbod@coracle.social 7 months ago

Each event is about 500 bytes, so to index all 100k 10002s on purplepag.es would only take around 50 megabytes, so yeah, totally doable

1 replies ↓

Dikaios1517 dikaios1517@nostrplebs.com 7 months ago

That's wild... A mobile relay could easily index all the pubkeys the owner would ever care about.

Derek Ross derekross@grownostr.org 7 months ago

oh. maybe ill run one at indexer.nostrelites.org. thank you sir.

hzrd149 _@hzrd149.com 7 months ago

Any good nip-86 management apps? id like to try and setup a relay that supports it and play around with it

1 replies ↓

Keyhan Alizadeh _@kehiy.net 7 months ago

most relays on ddsrs and alienos relay:

GitHub

GitHub - dezh-tech/alienos: A plugin-able and manageable Nostr stack (relay/blossom/nip-05) designed for self-hosting.

A plugin-able and manageable Nostr stack (relay/blossom/nip-05) designed for self-hosting. - dezh-tech/alienos

are supporting nip-86. if you run them, you can use it. about nip86 client, we have nak:

nostr web army knife

gui client? we don't have any. i had a project called mangostr: https://github.com/dezh-tech/mangostr but i don't have enough time to work on it and i wasn't able to receive a grant for it so i put incentives for more devs. then it's abandoned at least for now. you may want to develop yours. 🫡

1 replies ↓

Cesar Dias _@nosotros.app 7 months ago

This is good, I have found multiple instances of some users relay list not found in purplepag.es, I have came up with purpagepag.es, user.kindpag.es, relay.nos.social and relay.nostr.band as "bootstrap" user relays, and believe me, it's somewhat not enough, the other day I was trying to find a relay list of a particular user across 30+ popular relays until I eventually gave up, but primal somehow managed to find it like magic in their UI.

1 replies ↓

hzrd149 _@hzrd149.com 7 months ago

ddsr looks really cool, ill have to try to run a few relays

Keyhan Alizadeh _@kehiy.net 7 months ago

thanks a lot. yes, of course. you can try them. 🫡

Sebastix _@sebastix.dev 7 months ago

💯💯💯 What about other lists defined in nip51? Ive noted down a todo to setup an relay on nip51.nostrver.se and happy to mirror when it’s up

1 replies ↓

hodlbod hodlbod@coracle.social 7 months ago

Lists should live on the user's outbox relays, the goal of compass is to have the minimum setup that allows for finding the correct relays to query based on the outbox model.

1 replies ↓

Sebastix _@sebastix.dev 7 months ago

Ok that makes sense yes 💯