I can't agree more. Even if the protocol is perfect, which it's not, a malicious person can always implement a bug into the client or relay.
Pick your client carefully.
wss://blowater.nostr1.com will be our new community relay for Blowater users.
This is an invitation only relay. Everybody can read, but only invited can write.
If you want to join this relay, please comment on this note. I will add your npub.
relay.tools is amazing! nostr:nprofile1qy88wumn8ghj7mn0wvhxcmmv9uq3vamnwvaz7tmzv4mx7tnwdaehgu339e3k7mf0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpq0npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qf04dgf deserves more credit.
I don’t want to train today. So I cleaned some tech debt in the codebase. Body and mind, one of them has to work every day.
Then renew it. iPhone lasts. No Android can last 7 years.
The new version of Blowater has more features, less code. How ironic! Please wait for another 2 weeks.
Quite a journey
Iphone15 is great
More than 3000 lines of code will be added to the next release of Blowater. Stay tuned. I’m not just doing bjj. After the release, maybe I will operate a BJJ relay.
We will see more startups doing self funding and earn money the traditional way. One time pay for a piece of software.
It really depends on how client developers treat relays.
The real question is: Should a user has a unified view of data over the Nostr network or just over separate relays?
Developers has long been discussing the problem of data inconsistency among relays.
For example, your follow-list might be different in various relays. Your profiles might be different.
At the beginning, I, just like many other developers, thought it's a design shortcome of Nostr, if not a flaw and we spent much time solving it.
But, what if, we fully embrace the inconsistency? Then it's a design advantage.
Imaging that you can have different subscription/follow/block list in different relays.
How client developers design the product will vastly change how users experience Nostr.
Hey nostr:npub1dww6jgxykmkt7tqjqx985tg58dxlm7v83sa743578xa4j7zpe3hql6pdnf, saw you made an invoice, did the system/invoicing screw up or just checking things out? In theory you can still get that relay name, on the (newly designed) invoices page. Feedback is appreciated. I'm in the process of making a nostr native support portal too, till then you can just @ me.
The upcoming design of Blowater will encourage users to operate their own relays. We can potentially collaborate on this. I don't want to implement my own Relay as a Service. If Blowater links to nostr.tools, the experience will be smooth. What do you think?
Sooner people will chat around a calendar event
Hey nostr:npub1dww6jgxykmkt7tqjqx985tg58dxlm7v83sa743578xa4j7zpe3hql6pdnf, saw you made an invoice, did the system/invoicing screw up or just checking things out? In theory you can still get that relay name, on the (newly designed) invoices page. Feedback is appreciated. I'm in the process of making a nostr native support portal too, till then you can just @ me.
Just checking things out
Who is the author of nostr1.com？
A serverless platform for people to spin up their own relays and writing plugins will be useful.
