Avatar
β‚Ώ/πŸˆβ€β¬›
a514ab3befb752faaeb536192d04941dc25b88458e89407f9539bb89f39daf78

nostr:nprofile1qqsfnw64j8y3zesqlpz3qlf3lx6eutmu0cy6rluq96z0r4pa54tu5eqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9thwden5te0dehhxarj9ehhsarj9ejx2a30qyghwumn8ghj7mn0wd68ytnhd9hx2tcwzkxek the One per follow dvm is a great feed improvement. I find myself using it more than the regular time feed as the follows engagement inreases (especially with big follow list), as the visibility of notes also does, instead of drowning in the bots. Something similar for one per hashtag? Of course catstr excluded πŸ€£πŸ€™

nostr:nprofile1qqszeug0lpyaya5m9vpphkf6qfcdq0hvl52pymg8l9xxeg3xnjel8vgpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3gamnwvaz7tmwdaehgu3wdau8gu3wv3jhvqg5waehxw309aex2mrp0yhxummnw3ezucn89rl4ph

Well I know that supertestnet said it is not practical for zaps but I wanted to spin a nutshell mint on the phone to test between amethyst and oxchat and then bankify it to zap some catstr content. Not bad at all. Apart from the extentions concern, at least the mint can rugpull only if the backend goes bye.

Replying to Avatar Cocktus 🌡

the nostr:npub1gv069u6q7zkl393ad47xutpqmyfj0rrfrlnqnlfc2ld38k8nnl4st9wa6q widget πŸ”₯

naddr1qqgxvce3xajnjwf4xcekxdejxesk2qguwaehxw309ahx7um5wgknqvfw09skk6tgdahxuefwvdhk6qguwaehxw309ahx7um5wgknqv3w09skk6tgdahxuefwvdhk6qg7waehxw309ahx7um5wgknqvewv3hhyctxv93hgmmj0yhx7un8qgsf24pnp9hu5g3l9xkl654qct0q0g7996mgp7d5m84kc3ker9k9grsrqsqqqa20fwq7j4

Nice. Other clients may adopt πŸ€™

You can get the online ones at the moment from https://api.nostr.watch/v1/online clean up the list a bit and use something like :

```

#!/bin/bash

input_file="cleaned_relays.txt"

output_file="relay_nips_output.txt"

specific_nip=45

> "$output_file"

while IFS= read -r relay; do echo "Querying $relay"

relay_name=$(echo "$relay" | awk -F[/:] '{print $4}')

response=$(curl -s --max-time 10 -H "Accept: application/nostr+json" "$relay")

nips=$(echo "$response" | jq '.supported_nips | @csv' | tr -d '"')

if echo "$nips" | grep -q "\b$specific_nip\b"; then echo "Supported NIPs for $relay_name ($relay): $nips"

echo "Relay Name: $relay_name" >> "$output_file" echo "Relay URL: $relay" >> "$output_file" echo "Supported NIPs: $nips" >> "$output_file" echo "" >> "$output_file"

fi done < "$input_file"

```

Takes awhile but will give you something like this:

No no need for local, I can see the get req to damus. Was just wondering about the nostr settings are for as it does not seem to ask anything on the user side.