Not much, but I'm thinking torrents specifically.
- "url" and "x" are irrelevant if a magnet link is shared
- torrents can contain multiple files, thus "m" also becomes irrelevant there
Plus it would be generally nicer to have a separate kind for torrents only.
I looked through some kind 1063-s and found 0 magnet links in my admittedly
very limited search. Not surprising. Lots of images/videos being shared.
Would be nice to separate torrents.
Yeah, so I have my own client... I'm planning to implement a component for
simple filesharing (really just a kind for magnet links, but the current file-metadata
NIP isn't ideal)...
Would you be interested in taking a look? Say, second half of next week
or the week after that?
Word of warning: it's ugly, built in Godot, and communicates with a python
script using plain text files. Really it's a mess but it works.
Why relay based? Spam is spam.
For the record, I think magnet links should get their own kind for easier filtering.
Shouldn't 'url', 'm' and 'x' tags also be optional for NIP-94?
They are irrelevant if only a magnet link (referencing a collection of files)
is shared.
Why does it matter if they don't post anyway?
Following is a weird concept to me. Lists are better.
How much did you pay for that software?
How much time did you spend looking through it before you decided to
use it for real-life transactions?
What license was the program released under?
I think I can guess the answers.
If you don't like it, you can always build something better...
Are you familiar with how nostr works?
Useful advice.
Turns out up until now I was building based on an old download of the nips repo
that didn't have those 2 NIPs yet.
I don't like new event kinds. They make building a nostr client more difficult.
I'd like to build a gundb-like universal database on Nostr where you write to filesystem-like paths such as group/[id]/messages or group/[id]/name instead of defining new event kinds for everything that could expressed as a path. https://github.com/gundb/gun
Nostr is not going to be an "everything app" if you need new event kinds for everything.
I'm quite busy improving the very basic features of Iris, but I'll try to find time for it at some point.
Meh, how large can a js number be?
You'll need a unique way to id a unique kind of data structure anyway.
Might as well roll a big random event kind and just go with it without asking
anyone.
Unless relays reject unknown kinds >=40k, it should be easy to find
unused kinds. And client side error checking would be essential anyway.
Is your method essentially different? Would those paths be reservable?
Why is rust so popular? I keep seeing it everywhere lately...
Are there any POW only relays atm?
Maybe some that reject bloat like kind-7s, quotes, etc?
I bet it would be super cheap to run a relay if only for kinds [0, 1] with a
reasonable POW requirement.