I renewed my Apple developer account to keep Nostore on the App Store for another year. However I am not a heavy Nostr user these days so I will likely not renew again next year.
If anyone is interested in forking it at some point, I would support that.
I only have so much room in my life for social media apps. Twitter takes up most of my SM brain power.
Unlike most Nostr users, I actually like having a server and an algorithm. My entire Nostr feed is just stuff about Bitcoin and Nostr. I don’t even know if there is anything else on Nostr. Algorithms show me a wider variety of content, and I don’t want everything to be done in the client.
I am not quitting Nostr, it just doesn’t command a large amount of my attention and I haven’t maintained the same passion for it as I did early
One thing that I always wanted to add, but never did, was that I wanted to move the key management and storage out of the browser part and two the native part.
I did receive your email. Sorry, I'm a bit out of the loop on nostr these days. Can someone explain to me what's happening and how I can duplicate this problem?
My brother in Christ, base64-encoded JSON tokens is what the modern internet is built on.
If you want to talk derpy things, in Nostr we literally encode JSON blobs as strings inside other JSON strings
Yes that is what I mean. Instead of trying to squeeze group chats into the current way relays work, there would be a new relay structure focused on this use case.
In essence, a server is a meta-relay, and each channel is an individual relay (unique message stream). server.com/bitcoin, server.com/sports, etc are each technically a separate relay. Instead of amalgamating text notes from all relays into a one transparent feed, a client would segregate the feeds based on channel.
There would also be “admin” type events for channel creation, moderation, etc.
In summary, opinionated relays + a tweaked client experience to create a clean chat experience, while still allowing you to build with the Nostr ecosystem of libraries and extensions
If wallets implement this, it is nearly unstoppable. The event stores the money itself! It only redeemable by the owner of the public key. But there is a lock time condition, as well: if the owner doesn’t claim the ecash, you can refund to yourself after a time.
All of this happens without touching LN.
Cashu is Wallet of Satoshi on STERROIDS.
Risk profile is roughly the same. With Cashu, you can have offline payments and superior privacy as you said, but also a totally open transparent standard developed in the open, interoperable mints, etc
Ah, you mean it’s more complicated for the client developer? Yeah, it is. It is simpler for the user, though (it all stays in one app).
Most Nostr clients are JavaScript, and the typescript library is amazing.
We should rebalance our priorities to favor relays more.
Relays being transparent is a mistake for long-term sustainability. Relays should be communities. Relays should be invite only for posting, or have some membership requirements. Clients should obviously display which relay a note was from, and you should select destination relays when you make a post. Clients should also offer optional filters by relay to allow users to delve down into more specific communities.
The goal here is to be more like IRC, which maintains infrastructure for free for decades by being more “community-like” with regard to relays and making sure power users have a stake in the relay.
We should not be as siloed as IRC, however. Client integration with multiple relays should find a balance between making the seams between relays obvious but not a hindrance to UX. We should maintain the look and feel of global feeds while fostering per-relay communities.
There's a new, separate repo for Nomen specifications, and it's modeled after NIPs. They're called NOMs. I have opened a PR for a new NOM that allows indexers to publish their name data to relays, so that clients don't need to make external (or potentially proprietary) API calls to query names.
I would love feedback if any of you have interest in Nomen development: https://github.com/ursuscamp/noms/pull/1
If fees stay the same, should I implement Liquid support into Nomen? This thing will die if it can’t even get properly started because no one will buy a name because of fees!
It’s an extra output on top of any transaction. The size depends on the length of the name, but it’s quite small.
If you choose a 4 byte name “owen” then it would be 42 vbytes in total to register. That’s 4200 sats fee, or $1.54 at current prices + the cost for the rest of the transaction (it can be any transaction as I said).
I am attempting to bring global, unique names to Nostr via an open protocol.
I wanted to explain the new release of the protocol (and reference implementation), and why it needed a backward-compatible upgrade. nostr:note1r8s9ack6xmjv8x4vc7ucsgn9vzu9c3kt3eky3pj7nupx70crz9xq90ancn
What has blown me away are the sheer number of people that just absolutely do not care/excuse mass slaughter of innocent people, using the most paper thin of excuses.
Hamas is not an existential threat to Israel. This campaign is about revenge, pure and simple.
What is existential to Israel is bombing the population of Gaza to oblivion, committing non-stop terror and violence against the citizens of the West Bank, and uniting the entire Muslim world against them. THAT is an existential threat to Israel, and they have brought it on themselves.
That terror attack likely took them a year or two to plan and execute, and required Israel being historically negligent on their border security (to protect West Bank settlers). Hamas could not repeat it again if they wanted to.
Released 0.2.0 of the Nomen Explorer today. Disabled transfers temporarily. Transfers in protocol v0 were broken, they will be fixed soon and released with v1 of the protocol.
Fixed the issue that double-indexed @Freakoverse name 😉
https://github.com/ursuscamp/nomen/blob/master/CHANGELOG.md
I don’t suppose you would be willing to provide the PSBT so I can open a bug ticket? If not, can you provide an alternative PSBT which generated the error?
I am one of those mad fools that loves Safari and uses it for my personal web browsing. I know it’s not quite up to snuff on web standards, but it performs so well on macOS and integrates very nicely with all the Apple things.
Oddbean new post about login | logout
Notes by ursuscamp | export