But you said Wikistr is infected with global view syndrome. That was offensive.
I just added you, but now please start sending your notes there. Pyramid is so empty these days. Most people allowed there are not publishing to it.
Oh, I see what you mean.
Well, that is problematic because there is no way to "query the world" for notes, i.e. there is no "global firehose", so we can't do something like "for all notes that exist check if they will expire". Of course we could cheat and just "get all notes from the top 5 big relays" but that is a bad idea, expensive and against my principles, so I can't do that.
I'm more interested in crazy ideas that might incentivize people to willingly go to a specific relay, like using Jumble, and post a note exclusive to that relay, like, I don't know, "if you reply to notes published on this relay 5 times and your comment gets a like from the author you get the chance to post a note to this relay that is certain to receive some attention".
That is one thing you shouldn't do: add it to your "relay list".
Unless you mean you've added the relay as a standalone feed. I think you can do that on Nostur, right? nostr:npub1n0sturny6w9zn2wwexju3m6asu7zh7jnv2jt2kx6tlmfhs7thq0qnflahe
I'm totally willing to do any crazy relay ideas you might have.
But how do we know a note will disappear? Do notes ever disappear?
If you have nothing better to do in this fine day of August I would like some help to test https://impromptu.relays.land/.
You can do so by going on wss://imp.relays.land/ using Jumble or Nostur (I'm not sure what other clients allow publishing to a single relay using "-") and replying to a note you can see or writing some very important note there.
If you don't understand anything that's expected.
There is also this simple validation method in Go: https://gitworkshop.dev/fiatjaf.com/nostrlib/tree/master/schema/schema.go
By the way, nostr:npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr GitWorkshop doesn't display the latest commit for that repo on my browser, but it does if I open a new incognito browser window.
I started working on this generic schema that could be used for that: nostr:nevent1qvzqqqqqqypzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qydhwumn8ghj7un9d3shjtnhv4ehgetjde38gcewvdhk6tcqyz5a04nmem34nh3jd88g5vhv0ww2pu4l6l4xtphyqa9eartnn4u2k5z9a5u
It would be great if you took a look and helped fix the AI bugs.
There is also this simple validation method in Go: https://gitworkshop.dev/fiatjaf.com/nostrlib/tree/master/schema/schema.go
I started working on this generic schema that could be used for that: nostr:nevent1qvzqqqqqqypzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqythwumn8ghj7un9d3shjtnwdaehgu3wvfskuep0qydhwumn8ghj7un9d3shjtnhv4ehgetjde38gcewvdhk6tcqyz5a04nmem34nh3jd88g5vhv0ww2pu4l6l4xtphyqa9eartnn4u2k5z9a5u
It would be great if you took a look and helped fix the AI bugs.
I would have never expected this from you, but I'm glad that you did it.
Well, except for the fact that it doesn't work (and that there are no relay-based communities anywhere in sight, but that's another issue).
What about something like this: https://github.com/nostr-protocol/registry-of-kinds/blob/master/schema.yaml (mostly broken and vastly incomplete)?
With an accompanying stupid website for easier reading:
What is the difference between dev.nosotros.app and nosotros.app? Is "dev" merged into the main domain very often?
You read this note, so there is still some reading going on.
Specs don't have to be long, and I hope they won't be.
I agree and I think this is a move that improves, if only slightly, the issues you mention.
Except I don't agree there is anything that is fully ownerless like Nostr and is larger but still manages to get "official standards" done or follow some "governance" rules. These things only work when someone controls the project. The control often takes the form of control over the canonical software implementation that 99% of people use. That cannot happen on Nostr.
Talking often helps, but is far from a panacea. In any case, my hope is that in the new proposed mechanism more talk and more publishing of guides will be encouraged, such that the need for reverse-engineering will be minimized.
I just saw many worthwhile pictures by accident on the "media" feed while carelessly browsing through https://dev.nosotros.app/ (it's weird how fast this app is, and seems to have all the good features presented in a nice way).
Yes. Probably because NIPs are the wrong abstraction. But also because we're stretched too thin trying to make all the things "on Nostr" at the same time.
I think you're combining many different problems in one big rant:
- NIP-29 clients are buggy: yes, because we don't have enough users testing them nor enough developer time working on them.
- Some people are more famous than others: yes, that's how the world works, there is no "governance mechanism" that can fix it.
Well, it was only two problems.
I agree, that's why I want to get rid of them.
The way they exist now gives too many wrong impressions. People see a central registry of NIPs and think that is "the Nostr protocol", when in fact many of those NIPs are not used already (or most people agree they shouldn't be used) and we can't touch anything on the list because it is a very serious list. At the same time there are many kinds being actively used with multiple implementations that aren't merged on the repo, and, most importantly, the way in which each kind is or should be used is not in the repo either.
Once the "official NIPs" aren't a thing anymore someone (or actually many people) can create independent registries that track implementations or do the job the current NIPs repo is doing, but much better and in a more fluid, opinionated way.
You mean if kinds were strings instead of numbers? Yeah, maybe, but essentially it would be the same thing (just from the name you can't get all the context regardless, like the schema, the ecosystem around it, the expected UXetc) and even if what you cite is a minor advantage there are also minor disadvantages (more bytes used, slower to parse, people still have to check some registry to see if they're typing the correct strings, names don't really correspond to anything so one would still have to check guides, names can actually give people the illusion that they understood or can be deceiving etc).
nostr:nprofile1qythwumn8ghj7anfw3hhytnwdaehgu339e3k7mf0qyg8wumn8ghj7mn0wd68ytnddakj7qg3waehxw309ahx7um5wgh8w6twv5hsqgzxpsj7dqha57pjk5k37gkn6g4nzakewtmqmnwryyhd3jfwlpgxtsnyw5n2 nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qgwwaehxw309ahx7uewd3hkctcpz9mhxue69uhkummnw3ezumrpdejz7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qg3waehxw309ahx7um5wgh8w6twv5hsqgpjuxp8vd29p6ancknaztql3eajk52y8xkppfn7au7elkw9c68zg5w6awvc nostr:nprofile1qyghwumn8ghj7mn0wd68ytnvv9hxgtcpz9mhxue69uhkummnw3ezuamfdejj7qgmwaehxw309a6xsetxdaex2um59ehx7um5wgcjucm0d5hsz9nhwden5te0wfjkccte9ekkcettw5hxgetk9uqzphtxf40yq9jr82xdd8cqtts5szqyx5tcndvaukhsvfmduetr85ce4znfpm your considerations would be appreciated.
Contact cards are great: https://github.com/nostr-protocol/nips/pull/761
But as you can see the entire "NIP" is actually just an event schema definition. It doesn't say what relays to use or give any implementation examples or UX suggestions.
Another argument for doing this:
nostr:naddr1qqyrxvf3vgunjwt9qyghwumn8ghj7enfv96x5ctx9e3k7mgzyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze6qcyqqq823czkn5qp
But these things you are saying are the same things that serve as the basis for my article and against which I argue. Now you're just restating then as an answer to the article?
Well, except for "guides suck and get outdated", to which I reply that NIPs suck and get outdated too, in fact they may not get outdated because they're horribly incomplete from the start in most cases.
Why is there a "Global"? It should have specific relay feeds instead.
Oh, also .Find() now already checks if len() >= 2, so you if you use that you are safe.
The new Amethyst is great and if you are complaining you are wrong.
No, I didn't try it.
Somewhat, yes. But this is like a v2 of go-nostr with too many (but small) breaking changes it wasn't worth keeping the same name.
Please let me know what you think about this (but only if you agree):
nostr:naddr1qqyrxvf3vgunjwt9qyghwumn8ghj7enfv96x5ctx9e3k7mgzyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze6qcyqqq823czkn5qp
Honestly, if you are a programmer and you like Nostr, what is preventing you from trying out https://ngit.dev/ in your next project?
Why do English speakers waste so much time on these pronunciation quibbles? English must be a uniquely stupid language.
nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9us2xuyp ...since more people are using nostr:nprofile1qqs0f6uwv2kazdqtnjkumxrpue5m96g8e6jnfc8h7wkfwnq3cav22xspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9u34c34r now and some other things moving towards outbox, do you think it would be a good idea if I were to start referring people towards https://zapbox.relays.land again?
Yes, I think it's a good idea to experiment with it. The code didn't change and hopefully it still works. I just moved it to that other place.
I agree, and also subjectivity and hardcoded constants > self-described schemas.
It's too unfinished still. The best thing you can possibly do to help now is to create articles with links to other articles and so on. Having more content would probably incentivize the creation of better clients.
I believe https://wikistr.com/ favors linking to articles that were liked by the author of the current article or by yourself, or that are in the preferred wiki relays of the current article author or yours. But aside from that it doesn't do much currently.
You can't, you have to trust the archiver, as with anything in Nostr.
I don't think we have the technology to create a mesh that big, it doesn't scale. We need smarter decentralized routing.
Lately when I click to delete messages on Gmail the interface acts as if they were deleted but when I reload the page the messages are still there.
Gmail is pretty successful, so maybe that's the normie UX we're missing for Nostr to be successful.
We can't fix all the broken things Nostr is trying to fix while at the same time being afraid of offending some misguided prejudices of so-called "normies" (who are never actually called into the debate themselves, by the way -- and of course they can't be, since at the time they get to the point where they can have an opinion they're by definition not "normies" anymore).
I still don't get it. Who is trying to feed you? And what do you want instead?
I do not understand what you mean. What is the "feed" problem?
> In that regard, a "trust" button would never EVER be used.
Yes, I don't think there should be a "trust" button. "Trust" is too vague, too generic, not a good word. I would never click that one either.
But perhaps you have a list of uber drivers you like, or a list of wiki authors you favor over others, a list of people with music tastes you endorse etc. I don't know.
Important message:
See my comment for more nuance if you like nuance.
ngit init
OK, here's the web scrobbler extension with Nostr support:
https://github.com/fiatjaf/web-scrobbler/releases/tag/nostr
It's a browser extension that can scrobble from YouTube, Soundcloud, Spotify, Bandcamp and a ton of other sites I never heard of directly into Nostr.
It will also update your "status". I couldn't find any app that displays music status, but I think Damus used to, right? Someone please test it for me.
Anyway, you can browse your scrobbles on https://trackstr.netlify.app/npub1eer3xzy76k8tqr2w40804d07qxyzq4ypfv0vv70kj3xnuukcdhts35cfkg (use your npub) (if people use this I'll finish and improve it).
Let me know if the extension works well. Once it does I'll open a pull request to the upstream project.
Of course if you use the most evil Spotify you can also scrobble using this (remember to see full thread, painfully): nostr:nevent1qvzqqqqqqypzqwlsccluhy6xxsr6l9a9uhhxf75g85g8a709tprjcn4e42h053vaqyd8wumn8ghj7urewfsk66ty9enxjct5dfskvtnrdakj7qgmwaehxw309aex2mrp0yh8wetnw3jhymnzw33jucm0d5hsqgplfzyjwwpcs4twavfsj8lutf3fa5mftfskv980m3emkvpw90tymsq9rd6w
OK, here's the web scrobbler extension with Nostr support:
https://github.com/fiatjaf/web-scrobbler/releases/tag/nostr
It's a browser extension that can scrobble from YouTube, Soundcloud, Spotify, Bandcamp and a ton of other sites I never heard of directly into Nostr.
It will also update your "status". I couldn't find any app that displays music status, but I think Damus used to, right? Someone please test it for me.
Anyway, you can browse your scrobbles on https://trackstr.netlify.app/npub1eer3xzy76k8tqr2w40804d07qxyzq4ypfv0vv70kj3xnuukcdhts35cfkg (use your npub) (if people use this I'll finish and improve it).
Let me know if the extension works well. Once it does I'll open a pull request to the upstream project.
It's easy to come up with your own relay policy and logic without having to rebuild everything from scratch.
You can reuse Nostr identities and clients. You can natively refer to and be referred from the external Nostr network.
https://jumble.social/ is the best for now, but we're still early.
https://coracle.social, https://yakihonne.com and others can also be used to just browse.
You don't have to be a rich go developer to build a high end nostr relay. You can host your nostr relay in a cheap, shared host with a ordinary mysql/sqlite database.
Now it is possible with Phatru, a new library to build customized nostr relays in PHP, architecture is inspired by Khatru (https://github.com/fiatjaf/khatru).
Go (no puns intended) check it out at https://github.com/dhalsim/phatru and give some comments.
nostr:nprofile1qydhwumn8ghj7un9d3shjtnhv4ehgetjde38gcewvdhk6tcprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsqgpm7rrrljungc6q0tuh5hj7ue863q73qlheu4vywtzwhx42a7j9n5qnvvze
How much does a shared PHP host cost? Is it less than $3.50/mo?
I don't understand why people want to use these instead of a cheap VPS that can execute any code instead, but I'm glad this option exists anyway.
Nostr relays are just websites, so they must work even if you have a bad server and inefficient code. Otherwise Nostr is a failure. Clients must be mindful of this (of course evil clients won't be, but that is also true for normal websites).