You want to stop by at Bar in Montenegro? Let me know if you visit here 🤙
Now compare this to the original nostr description of nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhkcmmrdd3x77pwve5kzar2v9nzucm0d5hszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0qydhwumn8ghj7un9d3shjtnhv4ehgetjde38gcewvdhk6tc4rdlnm from November 9, 2020:
https://github.com/nostr-protocol/nostr/commit/bdeb03aeaf2d44db954e0eb1356a3f585ee7c50d
Interesting, I did a quick read on it and will read it again later. Perhaps there are some good ideas I can adopt in Nostria.
Get one, they come with Bluetooth as well now. Can connect to soundbars, headset, etc. Fairly cheap as well.
Here is my former setup, massive desk. I love that desk, I still have it. Inherited it from my father, painted it red to match the scheme of the basement I renovated. Red accent in chair, headset, mouse, keyboard, etc.
Had a vinal record player (visible in right corner) and proper speakers.
nevent1qqsqdlgphnhgm328cu3cdkvmey9dpw8vjdzkltf0vk9fzyf9af0u88cvqslvk
Here is my setup, unfortunately I can't use my secondary monitor due to the tiny desk. It's an 38" ultra wide, it's so much better than those 34" ultra wide.
I'm sure I'm ranking high in the competition of Nostr devs with the best view 🪟
NTAG 424 DNA card? I got a couple of hundred of them, using for FreeID (Liberstad identities).
It stores each ecash individually and can only perform transfer of the full value, or is there a way we could do payments of smaller amount this way? Maybe by dividing it up into smaller units, similar to physical cash?
Anyone written an Nostr Implementation Guide yet, or maybe want to do it? With AI you can do it fairly quickly, it would be a good source for reference for Nostr client developers.
For example, there are two competing file media protocols, should developers care about NIP-96 or go with Blossom?
Many other questions that are not really answered in the NIPs themselves, but this guide could explain how different clients have understood and implemented the protocol.
"Mentioned event not found"
I presume perhaps that the "p" tag in this event is the author of the note?
Will make sure that these kinds of posts will work in my new app (doesn't work on Primal) by discovering the user and then grabbing the note you mentioned.
Great comment, want to add that "owning data" doesn't mean "restricting access". Nostr clients could potentially backup locally all the events that are published by the user as an extra "home relay". Then if I decide to move to another relay, perhaps I purchased a paid one, the Nostr client could re-publish my entire archive to this new relay.
Clients should also do outbox model, only publishing profile and other events to a small set of relays, except from the Relay List, which should be published on "Discovery Relays" so everyone can be discovered.
It doesn't request signing on just browsing, but yes it does sign app settings at intervals which is annoying, especially when what is signed is actually an empty JSON. Interactions such as posting, reactions, etc. always has to be signed.
Coracle just released an update with a bug fix for Nostr Connect, it now works perfectly with my new Nostria Signer app! Thanks for fixing 💜
- Posted using Coracle and remote signed with Nostria Signer.
Thanks fiatjaf! I can do that, I just need a decent article editor for Nostr that does remote signing. I could capitulate and use extension or nsec though. I'll look more into that later.
To respond to the last part first, the DM part is not that important, though I still believe it's the right way to go: Publish DMs to me to my full relay list, then my relays should have auth implemented to only return DMs to me, nobody else. That simplifies a lot for implementors and users, it simplifies backups, data management and great deal of other things. This is one of the best parts of NIP-17:
"It's advisable that relays do not serve kind:1059 to clients other than the ones tagged in them.". Maybe I will implement support for kind 10050, but I doubt it. I seriously think it's a really bad idea to have separate relays for DMs and Group Chats.
My thoughts is based of the outbox model, but removing the more too complex ideas in NIP-65 and the current discussions around changes to the standard. I'm taking the ideas from DWN and Solid (pods) to Nostr, attempting to solve the scaling issue (avoiding large popular relays), and also the discovery part, where resolving DID Documents to get the services of the identifier (public key), which is the most important aspect to ensure scaling.
My next chapter in Scaling Nostr:
You should see what I've built the last few days! 
Maybe there are other? I tried all the web clients and desktop clients I found on a list, noStrudle doesn't work because they don't do it correctly. Didn't try any of the mobile apps.
I'll elaborate in more details on a future post, the general idea is to rely on the Relay List event to get Profile and other data of all individual accounts. As long as the Relay List is discovered, the user's profile will be found on those relays. No need to spread profile, following list and other events everywhere. To be able to "bootstrap" any profile, we could have a few relays that holds these lists and nothing more. It will be similar to the DID (Decentralized Identifier) resolves. My suggestion does not involve DID at all, my DID Resolver that I implemented was simply utilizing my suggested pattern.
Build, build, build. It's what I do all the time, nobody is going to stop me.
Coming soon: Brand new Nostr client built to help Nostr scale globally and an accompanied remote signer app.
Working on a new remote signer for Nostr, here is the first published post. Unfortunately there are only one web client that currently implements remote signing correctly, Coracle: 