patch sent (new category with its icon + new project that's not a nino, useful to the gaming scene).

Cool, though I hope full Silent Payment implementation is done sooner rather than later =3

nostr:note1dja9zfpxrgz9pjml0kf0recuge057gx9877mdtvf3494c05qh6ys4ewdyc

oh what do you know you damn lovable purple furball of the future!

Man... I think we've gotten used to Alby being there in the past , going through it now from the perspective of a new user that wants to create a nostr keypair using a nostr signing tool/manager (browser extension in this case), its, at least currently, a bad experience.

Password? Sure.

Register for an Alby account or use one of your Lighting hookups? wtf? As a new-user-pov, I'd go like "ok, let's create an alby account", then oh wait, no u can't, you have to get an invite code from x or y or z. WTF? all of this just to try and make a nostr account? I've been blinded and won't recommend, at least for now, Alby anymore to new users, unless the process becomes: install > password (skippable) > insert nsec or generate new pair > done / optional process of Alby LN service.

I had it as the first button for the 'registration' process on my project but yanked it out now.

Looking for alternatives and testing them, the best ones seem to be development-dead (Keys.Band, which as far as I'm concerned just needs an nsec extraction function/ui, and Flamingo, which is a bit slow).

The good options after that are the OG nos2x and Nostr Connect (a pretty version of it basically with a bit more nice additions like hex and nprofile key extraction).

I hope someone just forks keys.band and adds nsec extraction, and Flamingo's faster setup, plus Alby's opening of a browser tab to direct the user to setup (saves 2-4 clicks). Would also be nice to have finer permission control. That would be it.

Cashews 🤤

I think I'll be taking part in handling 4, half of 5, and a small percentage of 8, with my project.

Watched the new Aliens movie. It's nice. Kinda made me feel like I want to play the Aliens game again.

Wondering why Blue Wallet doesn't have full support/implementation of silent payments, and only send support...

Maniacs: "You have to break a few eggs to make an omelet"

Me: "You know what? Sure, though you and your pals will be the eggs, not the innocent, since you presented this idea."

Maniacs: "..."

Me: "Ah, not so enthusiastic to make that omelet now, are you?"

Imagine I went there and gave y'all a box of hummus x3

so a version where... nobody can truly follow you unless they've managed to know your xpub?

Delayed to Monday ~ Tuesday =/

nostr:note1gd5e6zpwhcgaqsedm3e8j2lp8s6qsykm6qpn88f0fzyve8dj0ggsjlejup

Want

https://video.nostr.build/20307d7f76a0c532d0f4b4552d4cf8ffa53ea513fa030a4dc723cc7294e1954b.mp4

Battle Queen

https://ix9.net/

Full vid:

https://www.youtube.com/watch?v=ORgxqzXtv64

#gaming #anime #fightinggame #gamestr

Yes, but aside from funding, I think there's the issue of designers who are new to FOSS and don't necessarily know how to step up and step in to even contribute for free.

Coders know git, hub/tea, know their way around the environment, submitting proposals, issues, committing PRs, etc.

"how do I come in and help? how do I use these things? Should I use these things? do i just hit up one of the devs and send them a .jpg on #nostr?"

These are the questions, at least for me as a designer and not as a coder, that go through my mind (and perhaps it's an introversion thing as well tbh), when someone wants designers for their FOSS project, or if a designer wants to help a #FOSS project.

A reply with "submit a PR" or "submit an issue" might make sense to a coder, but it's a blocking statement for someone else. They're lost on what exactly is the next step from that statement and don't have a clear picture of what to do.

That's why, I think, there should be a guide post (written or video) that should be shared always when attempting to lure in designers, explaining how designers (with and/or without basic coding skills) can contribute to a FOSS project. You'd write that yourself or find guides and share it (and even if you write or find a guide that outlines the steps, it might not even be detailed, well explained, or detailed enough, well encompassing, to have designers understand what to do and have them take action.

From the POV of a designer, from that side of me at least, I'm completely lost.

Perhaps I can work on that type of guide in the future, in written and in video form (and If I'm feeling ambitious about it, in a site form), like a really detailed, complete, and hand-holding one, and have it up online so that FOSS projects can link to it, on their project and whenever they post online or replying to someone asking how they can contribute (instead of "submit a PR". It'd be better if a post or reply is "submit a PR. And if you don't know what that means or how you can help, check out this useful guide for designers").

Finding designers isn't the issue, IMO, communicating with them and guiding them is.

Hopefully, a couple of coders and designers, who are more experienced in FOSS, can produce this (or maybe it is already out there, I'm not sure), where after some time has passed and there isn't one yet, and I can make it, then sure I'd make it (I'd hit up a bunch of coders for notes, thoughts, reviewers, feedback, etc).

nostr:note14aetjsek2nlru8y6zjucmjw3972tqgn5usal5yrtx90mq5p45kksu5sm58

https://nostrapps.com/ is the new PH.

Nostr Hunt.

ye i used WoS, i was determined to zap that post x3

I guess it's just alby, or my alby specially, having issues. Just zapped u with wos

You're zap-canceled apparently x3

(Tried to zap u)

"cool, i finished designing this thing for a #nostr client"

*Some new NIP comes out that kind of breaks the design

"fuck... hm... ok.. there's no need to scrap this.. ya ok I can adapt and add this... extra design to it.. ya this idea works. Great! There's no conflict anymore. The old and the new can stay."

Me today xD

(can't say what it is atm)