My #Nostriga nostr:npub1nstrcu63lzpjkz94djajuz2evrgu2psd66cwgc0gz0c0qazezx0q9urg5l Shirt is here βοΈ Say hi if you see me in Riga π€ #artstr #art #nostr #bitcoin 
Very nice. When a purple one with a Nostr theme? π
Well yes, the theme does not seem to be very well optimized for mobile screensizes:

Running Drupal / PHP with WebAssembly π
https://piped.yt/watch?v=SkKdDmg9K2o
Demo: https://wasm-drupal.mglaman.dev/
#Drupal #PHP #WASM
Wellβ¦we need stronger incentives for running small relays and improve the UX how to manage them from clients.
My opinion. π€
I'm posting weekly updates on what I've worked on for nostr:npub1phpdev2d38u5hzs4jrsh360mevh0rjctu9669quy97wu23u8sqdqpfha0j and other Nostr stuff at https://nostrver.se
This website is still a pretty basic Drupal powered one, but it uses some modules I'm building for crossposting notes and long-form content.
I just posted this nostr:naddr1qvzqqqr4gupzqrwzmjc5mz0efw9pty8p0r5lhjew789shct452pcgtuac4rc0qq6qyvhwumn8ghj7mn0wd68ytnnv43xzum5d9uzuer9wchsqxthv4jkktfjxukh2uryv96x2ueddehhxarj94cxsuqkgu8s7
which is also displayed on https://nostrver.se/blog/week-27-updates-nostr-php
This is how it currently looks like in the cms/admin UI of Drupal:

I'm also working on a feature to have multiple Nostr keypairs (users) configured so you can choose which user should broadcast the event to Nostr.

#NostrPHP #PHP #Drupal #POSSE
I'm posting weekly updates on what I've worked on for nostr:npub1phpdev2d38u5hzs4jrsh360mevh0rjctu9669quy97wu23u8sqdqpfha0j and other Nostr stuff at https://nostrver.se
This website is still a pretty basic Drupal powered one, but it uses some modules I'm building for crossposting notes and long-form content.
I just posted this nostr:naddr1qvzqqqr4gupzqrwzmjc5mz0efw9pty8p0r5lhjew789shct452pcgtuac4rc0qq6qyvhwumn8ghj7mn0wd68ytnnv43xzum5d9uzuer9wchsqxthv4jkktfjxukh2uryv96x2ueddehhxarj94cxsuqkgu8s7
which is also displayed on https://nostrver.se/blog/week-27-updates-nostr-php
This is how it currently looks like in the cms/admin UI of Drupal:

I'm also working on a feature to have multiple Nostr keypairs (users) configured so you can choose which user should broadcast the event to Nostr.

#NostrPHP #PHP #Drupal #POSSE
Really interesting to discuss this more.
All the encryption / decrypting stuff is done in PHP at this moment (which I didn't write fyi). To do all these things on C level in a package would be a nice feature (it requires the ability to install this on the server I assume?)
βThe reason you can't buy a car is the same reason that your health insurer let hackers dox youβ
https://pluralistic.net/2024/06/28/dealer-management-software/#antonin-scalia-stole-your-car
How to Embrace the STR:
Most of the time, devs are aware of bugs and issues. If they're not, submit an issue on the project's GitHub or tag them on Nostr.
It helps to provide as much information as possible. That said, I've been guilty of just taking a screenshot and tagging nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug π₯Ή Sorry!
If the devs aren't fixing your issues, it could be because of several reasons. They could not want to fix it simply because other issues exist and they're working on those instead. And sometimes it's because a new shiny object has their attention and priorities have shifted. If this happens, you could try asking them how much it's going to cost to motivate them to fix it and Zap them to get it resolved. Devs like money too.
What if your favorite app doesn't have the feature that you'd like to see? Well, following the same path as the above for issues, you can ask developers, talk to them on Nostr and submit feature requests on GitHub. You can also put up a bounty for it too. Again, devs like to be paid for their work. I remember paying a bounty sometime last year to get a feature added to Amethyst. It worked well.
Now, not every feature will get added to every app. From a user standpoint, this may seem like it sucks, but remember that Nostr is open and anyone can build whatever they'd like to see. That means we'll have many different apps and use cases and not all of them will be the same. That would be boring. The most popular and most useful ones will probably be replicated across all major clients. And if it not, well, there's always the opportunity for you to build it yourself or again submit a bounty to get someone to build it for you.
If all of this sounds very disorganized and hard to navigate, then you're absolutely right! Nostr is decentralized, meaning no one is in charge - but it does work! Somehow, with everyone essentially doing their own things, all of this works and is interoperable.
You see, Nostr has no development team or design time, but we do have various freelance developers and designers working for themselves or very small teams, where most of them are hacking away on Nostr in their spare time. While some do work on Nostr full time, it's still a lot of work for one person to do non stop, without getting burnt out.
Nostr is very far along and improving all of the time across many clients, considering how early we are in the whole process and Nostr's inevitable future. Embrace the STR. No one said it was going to be smooth and easy.
π«‘π
Show them your passion how you can solve their problem with onboarding friends to Nostr
Happy with this #NostrPHP shirt. Thx nostr:npub1gwa27rpgum8mr9d30msg8cv7kwj2lhav2nvmdwh3wqnsa5vnudxqlta2sz !

#Dutch
Vanavond om 20:00 organiseert stichting nostr:npub1ch54x83rf6jly58hrkpvk03jfywtl5n8st24w2jmhfusl939gj6qhkl7kk een webinar 'Vergroot je privacy op social media'.
Tijdens deze webinar zal ik een kort introductie geven over Nostr.
Mocht iemand de webinar vanavond bij willen wonen, met de kortingscode / waardebon code WEBSOCLID107 krijg je 100% korting als je je aanmeld via https://welkom.keuzevrijbijmij.nl/product/ticket-live-webinar-vergroot-je-privacy-op-social-media-10-juli/
I want nostr to be known for something good!
π cross-posted from https://ccns.nostrver.se
For nostr:npub1nstrcu63lzpjkz94djajuz2evrgu2psd66cwgc0gz0c0qazezx0q9urg5l and for all other dev meetups π
https://nostr.guide/ is not resolving
Who is the domain owner?
Tomorrow I'll do a short 5-minute introduction about Nostr in Dutch in a webinar about Social media and privacy. The people who're attending will see and hear about Nostr for the first time, so what are the three most important topics I should highlight to them?
What I currently worked out is to show them:
1. How it's censorship resistent
2. Data ownership with signatures
3. Data portability between clients