So many cool relays, so few people.

Does it still work with people who haven't set up NIP-4E keys? Because I'm trying it from scratch and it doesn't show any chats for me whatsoever.

There was a small sign. I think it wasn't there a month before.

Also, if a relay represents a niche group or more-or-less semi-closed community and is often browsed like such, searching inside of it becomes trivial for all the moments when you want to recall something you know you saw there. This is equivalent to searching a Discourse or a Reddit.

NIP-50 can also be used in specific NIP-29 groups and even for searching multiple groups that you belong to at once. That's basically all the search functionality that Telegram, Slack and Discord offer.

Search on outbox relays directly fixes 80% or more of all generic "search" use cases. We almost can live without big centralized search indexers if we can do full-text search directly from the source of people we're interested in.

1. If I want to search for something specifically said by someone (on Twitter there existed a "by:" special directive when searching, I basically always used that) I can search their outbox relays directly.
2. If I want to search for something and I'm not sure who said it: it goes a long way to search each of my follows' relays, as that thing that I saw is likely to having been said by someone I follow.
3. The point above can be expanded to follows-of-follows: it may take more time, but such cases of search are rare enough that the user can be expected to endure through a "loading" bar while the client tries to search some hundreds of relays.

@nevent1qvz...

https://github.com/fiatjaf/window.nostr.js now supports the "scan QR code" flow.

The easiest way to make a web client compatible with mobile signers like Amber and Primal and Aegis and Nowser and others I forgot.

You just write your app assuming that the user has an extension that provides NIP-07 (`window.nostr`) capabilities and include the <script>. If the user actually has an extension nothing happens, if he doesn't then the script is activated and everything is handled in the background.

I've recently found a small store that accepts Bitcoin close to my house.

(And it's not even on that BTCMap thing.)

Hyperbitcoinization is happening, finally!

I'm also looking for it.

The new #pyramid release v1.0.21 includes, among other things:

- a new (very simple) sub-relay "personal" that each member can use to store their own stuff others can't read (well, the pyramid owner can), like a personal note-taking service:


- NIP-50 full-text search support:

It tries to be good about it. Like it will allow you to choose the language used for analyzing and stemming note contents (more than one language can be selected, in which case a magical system will select one for each incoming note automatically).

It will also act smartly about indexing mentions, quotes and URL references in notes. For example if you index something that has a "nostr:npub1..." in it then later search for "nostr:nprofile1..." with the same npub you'll find that first note (and vice-versa). If your query includes a reference to the npub of the note author that will also work (although using {"authors": ["<pubkey>"]} also works the same).

And the query language supports basic stuff like "banana OR mango" or even "apple AND NOT strawberry". Exact matches enclosed with double quotes are also supported.

@nevent1qvz...

Pidgeon could do the scheduling directly on the relay if it found out that the person doing the scheduling has a relay that supported scheduling in their list, then fall back to the DVM in other cases.

I don't understand what you mean by a Postgres adaptor. You mean like using Postgres as the database for a relay? That has been done on day 1.

DVMs (as they exist today) are just a much worse way of doing ad-hoc HTTP APIs.