Good. They all deserve it. View quoted note →

Name reveal #NoorNote

Last night I taught my AI coding agent how to write CSS. With a much more consistent look, a vertical rhythm and all that. With reusable abstractions, 30% less code and being a lot more maintainable. It thanked me politely. Damn, shouldn’t it be the other way around? #AIs_still_suck_at_CSS

How did you, especially the devs, solve the problem of direct communication between two Nostr users when Nostr DMs are unreliable but the feature is important? Did you simply recommend a different chat client? Is there a NIP for reliable DMs that I don't know about? #asknostr

That’s a pretty on-point take on addiction and its spiritual consequences, whatever kind of addiction it is. It also mentions social media addiction, the addiction that algorithms create. And from that I conclude that moderate, targeted Nostr use is a better option for Muslims. View quoted note →

This is actually better than Wavlake. @Derek Ross single-handedly took over Wavlake with that one. Only a few details are missing, like NWC support, track permalinks, but it's already great! View quoted note →

I scroll through Twitter, see a thousand posts, and end up feeling like I’ve just wasted a chunk of my life. I scroll through Nostr, see maybe 30 posts. One of them inspires me. Then I build a new tool/add a feature, or change something in my daily routine. Choose wisely what you give your attention to.

Jummmah Mubarak!

View quoted note → Okay, my Nostr client supports it now. I’ve been working on it all day. You can turn it on in the settings if you want to use it, with full migration tool between private and public. That way, you can also follow people privately. And they’ll show up in your follow list with a proper label.

Supporting NIP-88 polls in my client.

With vibe-coding, people often complain that code quality suffers, that the code isn't as smart as it would be if a human wrote it. This especially comes from people or companies who've at least warmed up to the idea of integrating AI into their workflows. So not from AI haters. Honestly, I find this argument pretty damn hypocritical. Back in my day, when we were still writing every line by hand, there were also massive quality losses in the code, but back then it came from something else: from the impatience and cluelessness of company leadership. Feature development was (and still is) crammed into tight Scrum processes, under the micro-management of some Scrum Master clowns who often had no clue about coding, but really made an effort to lick their leaderships' boots. Stuff was constantly promised 'up top' that we 'down below' could only deliver on schedule by shipping dirty code with massive technical debt. Short-term thinking was the norm. The main thing was that the feature (which in 90% of cases was useless or even harmful to the app) absolutely had to get out before the next board meeting. And after years of us developers complaining that we were just piling up technical debt and never getting time to fix it, a CTO even had the nerve to say to our faces: 'Listen guys, in this business it's not about hitting the track with the most polished car, but about reaching the finish line first with the crappiest jalopy.' So when the same people, with the same short-term mindset, come at me now with 'AI code is bad,' I just laugh in their faces and know they've never vibe-coded a larger project. Because with vibe-coding, I'm actually in control of making sure architectural principles and other standards are followed, without some bullshit suit jumping in and saying 'Nah, we'll do that later. Just ship it first.' And without some dumb 'Scrum Master' who took a few weeks of expensive paid courses for his job title trying to orchestrate me.

Wavlake sucks. Someone please build a pure Nostr-based music distribution service.

🔥 View quoted note →