Yes, you're right. I heavily rely on NIP-50. I just didn't want to keep going down the custom query syntax route to prevent too much specialization, so I opted for data duplication
But as you note below that might be the case anyway, having custom relays in these scenarios
Would be interesting to see a breakdown of relay implementations, I'd guess most use strfry which had its latest commit last year
nostr:npub1uac67zc9er54ln0kl6e4qp2y6ta3enfcg7ywnayshvlw9r5w6ehsqq99rx
the roads... or who will build the roads?
What do you guys think of inheritance on nostr event kinds?
Composition is not the answer to everything. I recently splitted kind 32267 for apps, removing all the fields that correspond to a wiki entry and added an `a` pointer to it.
But if my kind 32267 *is a* compatible wiki entry, as it implements all fields from wikis kind 30818, it should be read by wiki clients.
Having to do multiple queries is also shit, and I will share my implementation to fix that. The problem is interoperability, relays are hard to change
Given the folllowing structure: apps -> releases -> file metadatas
User searches are performed on apps, once an app is selected we fetch latest release, and from there grab file metadatas.
It's easy when the search is done on one event kind (apps) but now I need to also start filtering on file metadatas (for platform/os/architecture). You don't want to be presented search results for which there's no app for your operating system.
Theres no way of doing joins or more expressive querying in nostr - unless copying the data I need onto one single event kind, which is the workaround I did and I hate it.
Uhm, no. It's an AND that needs to happen server-side. It would be ridiculous otherwise
Need to concurrently filter on conditions of 2 related event kinds (connected via "a" and "e" pointers) and there's no way of doing that.
There's not even a viable workaround, it's a fucking mess
The nostr relay query language needs an upgrade. Started to hit the limits
Not myself but heard multiple times from different sources that domains were revoked, experiences on reddit and trustpilot not looking good: https://www.trustpilot.com/review/njal.la
Very interesting
Built on https://harbor.social/
These idiots building yet another identity app
If we do it on open protocols we win
Yeah, really wish we had ecash UX with self custody. Hard tradeoff for now.
I don't think we'll rebuild the existing systems, imo it's worth a try
that's cool
The free market do its thing
we will eventually see mint insurance schemes pop up
we need something far more distributed and built on open protocols
Ecash is not bitcoin
Ecash is the smoothest bridge to bitcoin
Just like nostr, ecash will elevate orange pilling to new levels
Amazing work with nutzaps nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft
American non-profit #OCLC is mad at Annaās Archive for scraping their content and offering it as a torrent š They have left their .org domain now in favor for a .gs domain hosted by #Njalla.
https://torrentfreak.com/annas-archive-faces-millions-in-damages-and-a-permanent-injunction-240708/
njalla not good for domains
YouTube very recently started aggressively banning IPs, mostly non-residential and forcing sign-ins.
yt-dlp and many invidious, piped instances affected: 403 errors or "Sign in to confirm youāre not a bot. This helps protect our community"
Google's concept of community is wanting you to swallow their sludge advertisement and control your speech.
I take this as a challenge.
Piped is great but it was obvious that proxying would be shut down one day.
Even though I'm busy AF, I started prototyping something to take back great Youtube content. Involves nostr, blossom and ecash. More soon
Unfortunately not possible yet, I'm working on gitlab support but it's not ready
Not sure I see the connection with how it affected culture but appreciate your insight
Would be awesome if people could try out the examples and help me check it all works fine
Updated the NIP-39 linked cryptographic identities spec PR (and examples) to use binary format instead of hex/ASCII before converting to base64.
Space optimization appears to be significant.
Treating everybody as terrorists is the problem
Android users not using Google, hereās the most recent APK link for mobile beta šµš¤ https://github.com/wavlake/mobile/releases/download/v1.1.0-beta.17/application-c17c4e1b-3810-4363-b8c4-eb5ae2eb43d5.apk
Easiest install/update: nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8