-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
primal-caching-service
Primal’s caching service for Nostr connects to the specified set of relays, collects all events in real time, stores them locally, and makes them available to nostr clients through a web socket-based API.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
There is no "zaps balance". Zaps are just receipts of lightning payments.
The basic idea is that a lightning node will detect when the invoice with a nostr note inside is paid, and then send the receipt to nostr as a nostr note, with the original bolt11 invoice inside with the signature from the user who sent the zap.
It's all describe by NIP-57, a spec I put together to support this:
https://github.com/nostr-protocol/nips/blob/master/57.md
I was working on c-lightning at the time and I thought it would be really cool to replace the "like" button with an instant bitcoin micro-payment. I think it worked out quite well! There are many sites utilizing zaps in all aspects of the protocol, such as a decentralized market for AI job requests (data vending machines), zapgoals and zap fundraisers. All built on this note type. protocol synergy!
Hey, author of https://damus.io here (ios twitter-like nostr client)
> First, I want a replication strategy. Nostr messages get lost in time, and many of the clients end up just blasting an entire message history at your client. Because there's no clue in the protocol how messages are related other than a timestamp this also means you can fake timestamps and write fake messages in the future or back in time
You can do this with email or git too and it doesn't make it any less useful. I actually like the backdating feature as it allows you to copy your account to a new key.
As for replication, at damus I am working on https://github.com/damus-io/nostrdb which is intended to be a "sqlite for nostr". I plan on implementing set-reconciliation based syncing with strfry relays (using a technique called negentropy), so that replication is very efficient.
> Second, I don't like that many Nostr clients are using the same signing key for messages as they do for lightning transactions.
This is simply not true.
> Third, someone needs to delete some of these NIPS. The arms race to make Nostr as complex and difficult as possible to implement is not going to do much for the ecosystem in the long run. In the beginning Nostr was simple to implement from scratch, they should get back to that!
All nips are optional except for nip01, you can ignore them all for the most part.
> Fourth, it needs a dedicated blob store protocol. Yah, I know IPFS isn't great but someone should come up with something that is simple and works.
It does not, in the same way email or git or any text-based protocol doesn't need a dedicated blob store. These are separate concerns and they should be a separate protocol. nostr clients can of course integrate and link to any blob store it wants via new NIPs that describe this. I believe there are a few already in the nips repo.
Cheers!
Damus has come a long way since this article was written.
Android also has a great client, Amethyst: https://github.com/vitorpamplona/amethyst
Strfry is used by most of the large relays: https://github.com/hoytech/strfry Doug Hoyte is a wizard.
Damus has come a long way since this article was written.
Android also has a great client, Amethyst: https://github.com/vitorpamplona/amethyst
Strfry is used by most of the large relays: https://github.com/hoytech/strfry Doug Hoyte is a wizard.
Nostr's very cool tech and I'm excited to see where it ends up. But I'm not sure it'll make for good social networks/apps that I'll care about. ActivityPub and Matrix.org get flak on the account portability issue and it's a valid one but it (and their design in general) provide a pressure on their communities to be very "cozy-web"[0] despite the few leviathan instances. Nostr's more than flexible (almost under-specified) that you can build your cozy spaces on top of it but I'm convinced its design allows it to be a real decentralized contender for the big social and I fear that's where its custodians are headed. It won't be long before we see Nostr service providers that replace all the core functionalities of Twitter like a good algorithm and moderation[1] But personally, I don't want Twitter with pki, I don't want Twitter at all. I really hope Nostr keeps it cozy but hey, at least you'll get to personally choose your algorithm.
[0]: https://maggieappleton.com/cozy-web
[1]: https://primal.net has a great start