Avatar
Lurking Cat
94e268f4aca4cc14613e1a6d50dab40882b9f08a31d7f6ba81604429b1bbba0e
Born as Cat. Curiosity feed the Cat. Sometimes, wandering a bit on Global feed. Non-Custodial ⚡: lurkingcat@longer-teddy-lined-truck.trycloudflare.com Custodial ⚡: lurkingcat@stacker.news

Oh, running from raspiblitz package? Yes, i'm not sure. Maybe new LNBits introduce some changes and raspiblitz doesn't package it correctly. Need to check the LNBits code and debug it manually 😅

Mmm, i bet some of them directly give a comment even before checking and read the links 😅

Replying to Avatar Lurking Cat

You can check list of paid relays here

https://relay.exchange

If you want some opinion, i think currently nostr.wine has offer more than other paid relays. They have multiple servers (Europe, Asia, US) which automatically choosen by your IP address. They also have extra features https://filter.nostr.wine . You can check their sites for more information. :)

There is similar question before, i will refer those below

Why Paid relays?

#[1]

Additonal opinion

#[2]

Maybe this can help some of your questions

I think the main culprit of this problem is your LNURL server gives html response instead of json. Seems there are some misconfiguration in LNBits.

Public group messages/chat is already available in Amethyst and Nostros. I'm not sure with other nostr clients.

Have you already set it with your nostr client? What is your nostr client?

Usually, we can enable it for home feed, private message, and global feed. We can disable free public relay setting in global feed to prevent seeing the spam

It's ok, it depends on whether it will become major issue or not for you #[5] :)

Friendly reminder, to those who concern of their privacy

#[0]

and probably try to minimize the identifiable eye-catching spot (unique monument, unique symbol) where the photos are taken. Google Lens, TinEye, and any reverse image search can easily dox the source place.

Ah i see what you mean.

Let's say you want to mention people that you've already followed, but sometimes Amethyst doesn't recognized it immediately, right?

Usually, i solve this by opening my profile page, click follow tabs, wait until the list of your follows fully loaded

Oh, why not?

This is example of how to mention people

#[1] #[2]

You just need to type "@" + "type a name, username, or public key (npub)" and it should be work

Replying to Avatar Cyph3rp9nk

Tips for Relays.

Forget about having a thousand and one relays.

The first option is to pay for nostr.wine, it allows you to use the filter.nostr.wine filter. The filter works both requesting events from other relays and sending events to other relays. In case you want to send events to other relays you have to add the relay with the following syntax:

wss://filter.nostr.wine/REPLACE_WITH_YOUR_NPUB?broadcast=true

Reading list:

wss://relay.damus.io

wss://nos.lol

wss://relay.current.fyi

wss://brb.io

wss://nostr.oxtr.dev

wss://relay.nostr.bg

wss://no.str.cr

wss://nostr.mom

wss://nostr.zebedee.cloud

wss://relay.plebstr.com

wss://offchain.pub

Writing list:

wss://relay.damus.io

wss://nos.lol

wss://relay.snort.social

wss://nostr.oxtr.dev

wss://relay.nostr.bg

wss://nostr.fmt.wiz.biz

wss://nostr.mom

wss://nostr.zebedee.cloud

wss://no.str.cr

wss://relay.plebstr.com

wss://offchain.pub

The next special relay is relay.nostr.band. This relay reads events from all relays and applies a spam filter, in the case of writing you only write to relay.nostr.band but it is a good complement to add content to relay filter.nostr.wine as it only requests events from your contacts and your contacts' contacts. It is not clear to me from which relay is requesting the events as the code is not available.

And finally the relay nostr.mutinywallet.com. This relay uses blastr which is a nostr cloudfare worker proxy that publishes to all known relays. Basically what it does is to read the list of online relays from nostr.watch and all events are queued to be executed in batches by another worker that rotates every 30s if there is an event queued, or once a certain amount of events are queued. In this case the relay is write-only.

In short, your relays could be reduced to 4:

wss://nostr.wine

wss://filter.nostr.wine/REPLACE_WITH_YOUR_NPUB?broadcast=true

wss://relay.nostr.band

wss://nostr.mutinywallet.com

With them you save bandwidth and battery, actually filter.nostr.wine in write mode and nostr.mutinywallet are redundant, but I put the two because nostr.mutinywallet.com has more amplitude because it publishes in all the online relays of nostr.watch and also because it has high availability in case of failure of any of the two relays mentioned above.

The same case is applicable in the case of reading for filter.nostr.wine and relay.nostr.band.

Been using this relay combo for a while. Agree with your points 😄

Now i wonder, is it possible with Parameterized Replaceable Events (NIP-33)? Currently, Latest Amethyst already support this 🤔

Currently, latest Amethyst has some support for basic Markdown. You can check regular updates from https://github.com/vitorpamplona/amethyst

or follow #[2] to get his notes update about Amethyst

What is your nostr client now? Is it Damus?

If you like video tutorial then you can start with this

https://m.youtube.com/watch?v=fG1IDm-lQek

Additionally, you can start with this guide, someone has made this. Hopefully, this can help some of your questions.

https://uselessshit.co/resources/nostr/

and

https://nostr.how

If you want to know which wallet supporting zaps (NIP-57) then you can check this

#[1]

Is that relay aggregator that also filter the spam? If so then it is gladly accepted.

Like how #[2] have done with nostr.mom