In Brazil there are places that charge you money to install WhatsApp on your phone for you.
I've met multiple people that just buy an Android phone, register a random email address and start using the phone with that. Once they buy a new phone they just make a new account on everything.
I have never lost a password, but I have lost access to multiple accounts in my life due to poor management of domain names and phone numbers because these websites insist in using these things as second authentication factors when I no longer have access to them. And then when that happens there is no recourse. Why no one says the UX of these things is crap but everybody is super worried that people will lose Nostr keys?
Who can do an Excel plugin that fetches and subscribes to Nostr filters to get real-time updates and make calculations based on data published by other people elsewhere?
A do think a Nostr client inside an Excel spreadsheet would be interesting.
I think it is open-source and you can export the data easily and import it on your local instance, but most people are not really expected to do that.
It's a company, and not decentralized.
I think the best solution is to use an app that stores your stuff locally so you can republish in case shit happens.
I'm hoping Snort will make these by default in a distant future!
https://coracle.social/ does. I'm hoping Snort will make these by default soon!
https://www.getgrist.com/ is such an amazing thing. It solves all your problems and cures your diseases. Why doesn't it win but retarded stuff like Airtable does?
Turns out Gossip dark mode is actually better than light mode.
Good evening, I can't open your note because I have no idea of the relays it is in if you only give me a "note1" code.
What app people use to create and publish the badges?
If you really want it I can merge it as an experiment.
the thing is that even for that use case, which is exactly the use case I had in mind when I started looking at it (https://nostrit.com could be done much more elegantly if NIP-26 was better).
I think having a proper key delegation where user of both keys are the same person definitely needs to be solved,
but NIP-26, or something like it, where you can give *some* permissions to a 3rd party without giving out the full reigns to the kingdom, would be valuable.
I agree, but not all desirable things are practical. I am not convinced that NIP-26 is worth the cost, but if proven otherwise that will be good news. Maybe we need Nostr 2.0 that fixes all the bugs with Nostr 1.0.
That seems to be just an UI with no functionality.
It is never the case that most companies don't want to host your stuff, it always takes just 2 or 3 companies and you're effectively deplatformed, since your followers are all in these 2 or 3 and they can't move and they won't move.
If their clients made it easy for them to keep following you would wouldn't lose 99% of your followers as it is today, maybe about 5% due to logistics issues that we can't solve.
The fact that some clients do not allow you to do that because they just talk to their own servers, like Primal or Member.
If I am following A, but A is actually publishing events under A1, A2, A3, A4, A5 which are delegated keys, how am I supposed to ask relays for these events?
You are funny.
Apparently these people are looking into Nostr: https://techcrunch.com/2023/03/13/wordpress-com-owner-automattic-acquires-an-activitypub-plugin-so-blogs-can-join-the-fediverse/
Good point. It is a improvement. But it's more like a 10% improvement instead of 100% improvement that Nostr has originally promised. Maybe I am overthinking this.
I see. That was the initial design of NIP-26 before we switched to having different keys for backwards-compatibility. But your point makes sense. We might be able to come up with a magic cryptography trick that does that.
It would break backwards-compatibility, but, well, NIP-26, the way it is being pushed, also breaks backwards-compatibility, so we might as well do something better than NIP-26 for the purposes.
Well, my point was that no one thought about this question a single minute. Everybody just read NIP-26 and assumed it was the solution. NIP-26 is not a solution for this, it was made for temporarily delegating to third-party services because of the https://minds.com/ integration. And it was meant to be the least disruptive possible.
I can think of multiple other methods for doing delegation/revocation that would be better if the goal is to protect keys.
It's a very inelegant solution that adds a lot of complexity. It wasn't conceived with the goal of safeguarding people's keys at all. If it was done with that in mind I bet we could have made something better.
In any case, rushing into it feels misguided. For the sole purpose of keeping identities safe I believe NIP-41 is a superior solution, although not perfect either, of course.
Is the fact that the current state of things imperfect a justification for doing anything?