1 year later, why Nostr still resonates #Blog
nostr:naddr1qvzqqqr4gupzqpnrnguxe8qszsshvgkvhn6qjzxy7xsvx03rlrtddr62haj4lrm3qqnrzttev4shyttvv96x2u3dwa58jttwdaehgu3dwd6xjmrv94ex2um0deshgetnr9rmkn
If your Nostr client does not render this article, you can also read it at https://nostrver.se/blog/1-year-later-why-nostr-still-resonates
I recently had an idea to bring back my Hyves profile with Nostr (as I have a backup made by hvsbackup.nl desktop app I made back in the days).
Do you still have your Hyves profile? And do you think all data are really gone? It’s hard to imagine that TMG has deleted it..
As a library maintainer I take it as a serious job to use trustworthy other packages. Engaging with the authors is key there.
@nostrphp has not many dependency (which I like to keep it as low as possible)
```
"require": {
"php": ">=8.1 <8.4",
"ext-gmp": "*",
"ext-xml": "*",
"bitwasp/bech32": "^0.0.1",
"phrity/websocket": "^3.0",
"simplito/elliptic-php": "^1.0",
"uma/phpecc": "^0.1.3"
},
"require-dev": {
"friendsofphp/php-cs-fixer": "^3.51",
"phpunit/phpunit": "^10.5"
},
```
Thing is, there are already clients out there where we could integrate Nostr + Blossom to (re)distribute existing content (it would open up a nice copyright fight there)
https://github.com/kieraneglin/pinchflathttps://github.com/tubearchivist/tubearchivist (I'm running my own instance to download YT videos for my kids)
nostr:nevent1qvzqqqqqqypzpckv7l8jqspl8u4y54dn9rcduwlrs4v2040nxce0m2h0cunvrj8tqy2hwumn8ghj7un9d3shjtn4w3ux7tn0dejj7qgnwaehxw309amk7apww468smewdahx2tcqyqrry2uetvnxqu8duq3vrw29vhtrxq70w0y0ehz85qgqjpstyfxggedr2e2
HTML web components are okay
“Every new capability added to the web platform isn’t a limitation on your creativity – it’s an opportunity to express your creativity in ways that nobody imagined before.”
https://nolanlawson.com/2024/09/28/web-components-are-okay/
Thing is, there are already clients out there where we could integrate Nostr + Blossom to (re)distribute existing content (it would open up a nice copyright fight there)
https://github.com/kieraneglin/pinchflathttps://github.com/tubearchivist/tubearchivist (I'm running my own instance to download YT videos for my kids)
nostr:nevent1qvzqqqqqqypzpckv7l8jqspl8u4y54dn9rcduwlrs4v2040nxce0m2h0cunvrj8tqy2hwumn8ghj7un9d3shjtn4w3ux7tn0dejj7qgnwaehxw309amk7apww468smewdahx2tcqyqrry2uetvnxqu8duq3vrw29vhtrxq70w0y0ehz85qgqjpstyfxggedr2e2
@brugeman FYI, I couldn't find the Settings > Experimental menu item in my Brave browser on iOS. So as an alternative I opended up these settings by typing brave://flags in the address bar so enable the Content Push Notification setting. But it seems there is no 'Add to homescreen' option to install the site as a PWA (just like in Safari).
For what iOS version are these instructions? I'm on 17.3 😆
Do you think it's a Apple / iOS thing?
A while back I also went deep into the Push API stuff with integrating push notifications in a PWA site built with Drupal. Me and another dev made this contrib module for it: https://www.drupal.org/project/pf_notifications
Things work pretty well as expected, but not on iOS.. So I wonder if it's Apple who's acting bad trying to kill PWAs here with this story in your mind: https://open-web-advocacy.org/blog/apple-backs-off-killing-web-apps/
If we think Apple is still the bad actor, I can bring this up to the OWA which have direct connections to EU to put some pressure on Apple (for what's worth it).
It’s a funny story. Hard to say what the incentives are from each party involved into this. But the talks are all about the platform Bluesky and not about the protocol. So it’s noisy.
Oddbean new post about login | logout
Notes by Sebastix | export