@5e7ae588d7d11eac4c25906e6da807e68c6498f49a38e4692be5a089616ceb18 Verifying My Public Key for mastodon: "https://mastodon.social/@melvincarvalho"
It says:
User has NOT signed their mastodon profile with their nostr private key.
https://mastodon.social/@melvincarvalho.json
My nostr is actually in my .json profile
See RHS
https://mastodon.social/@melvincarvalho
We could standardize this, though it's actually slightly nuanced in AP since all keys are actually URIs
And mastodon have done this is a complex way, which is actually broken ... sigh
Thanks. Legend! 🤙
Testing lightning network withdrawal link
100 sats to the lucky winner!
The new https://nostr.watch/ looking great!
Great video
Two android clients are in the works with .apks
arc: https://twitter.com/TheArcApp/status/1612240864637493248nostros: https://github.com/KoalaSat/nostros/releases/tag/v0.2.0.1-alpha
Lots more good web clients now incuding:
KUTGW!
nice idea!
Re subdomains i cant quite remember how, but we did it here:
https://github.com/nodeSolidServer/node-solid-server
You could have some kind of haproxy magic too
Starting up a new relay on demand is smart, imho
Lots of different communities or tribes reminds me of:
Nostr relay Setup on AWS
Multiple! 🙏
https://void.cat/ is on github
I hope we can get to the model where sites like this are self sustaining
I think low hanging fruit it turn on donations, as there will be some users wanting to support nostr infrastructure
Possibly even a nostr infrastructure open collective for relays and media, though open collective take 10%, it's not ideal, but maybe better than nothing...
Arc ⚡
📢 RELEASE: v0.0.1-alpha 🎉
Our first Android APK is now available for download! 💪
https://github.com/ArcadeLabsInc/arc/releases/tag/v0.0.1-alpha
Tested nostr on android ^^
It works!
Arc ⚡
📢 RELEASE: v0.0.1-alpha 🎉
Our first Android APK is now available for download! 💪
https://github.com/ArcadeLabsInc/arc/releases/tag/v0.0.1-alpha
🤙🏼
My favourite!
Got it. Im still unsure it compares to the whole REST surface
A friend of mine does market monitoring for the biggest exchange in europe. It's a few terabytes a month
Archive.org which is one site has 10,000 terabytes
REST has a proven track record to scale to billions of people with low resource intensity. Websockets are a newer technology, let's see how they get on.
What's interesting is most older web systems started with HTTP then added websockets for realtime. Nostr starts with realtime, and we can explore how to scale that with supporting NIPS.
Fun times! :)
That's interesting do you have some stats on that?
It would be interesting to compare the volume that goes through REST and the volume that goes through websockets, and also number of users serviced
And also compare the resource needed
Scaling to 1 billion users is still a big challenge for nostr, given that it's mainly grass roots
You can, but you might want to save resources when nostr gets to millions of users
In REST you would use GET if there are no side-effects
Lots of different ways to do this at scale, e.g. graphql type things