I hope so, but that was not my point. Also I don't believe in a solely individual path. One does not operate in isolation. Even the great jd Vance did not accomplish this entirely by himself alone, he had mentors and role models for example, but I am impressed by his path (on wikipedia, fwiw) to this position. I can only hope he has the love and wisdom, gathered in is life, within him to be a great leader and make your country whole again.
How is that special to the US? Also a harsh childhood does not make you great fit for a leader, per se ;)
Yeah, you could only do with get or post, it just that these two cause the browser to act differently. The other methods are (more or less) degrees of freedom expression. I'd say the nips are not much different technically, may be semantically there is some difference dunno, but to go religic about it goes a bit far.
Meh, GET|POST /path is bare minimum, possibly with an host header for virtual hosts. There rest is pretty much optional sugercoating. Your reasoning goes the same for all nips beside 01. No need for the rest in essence and it is the same for http. And then devs start adding features 🤣
You can that sort of do with nostr too by embedding an url to an image. Later on you can change that image. To prevent that, nostr should add something like etags (sha256 checksum) to an event for links to static elements. Clients can then check their validity. Also relays could prefetch these static files and provide them to clients in additional http requests. Clients can verify them by the etags. This would make nostr safer and easier to scale,.since static content is distributed.
You can that sort of do with nostr too by embedding an url to an image. Later on you can change that image. To prevent that, nostr should add something like etags (sha256 checksum) to an event for links to static elements. Clients can then check their validity. Also relays could prefetch these static files and provide them to clients in additional http requests. Clients can verify them by the etags. This would make nostr safer and easier to scale,.since static content is distributed.
It almost reads as supercreepy
Europe, let’s FINALLY stand on our own feet as of now.
I created a note 😔
And the crazy thing is, this "leader of the free world" is now some third world oligarchy 😔
It's just a term I sometimes use since I wrote this article in 2011: https://sebastix.nl/blog/jouw-personal-graph/ around this proof of concept app: https://personalgraph.me/
Yes, I ran into that article. Am I correct to summarize it as: the overview of your personal relationships/information online?
That would be the case if this was a country like somewhere on the other side of the planet. Unfortunately Europe is quite the ally of the US, so whoever is in charge there does effect us here. Culturally, politically, financially, military... the list goes on. 😔 And yes, that's also on ourselves, but this is the situation we are in. Hope you choose wisely and with your heart 🙏
What do you mean with "personal graph" and where can I learn more about this?
Ah yes a NIP46 helper library would be very welcome by many! 💯
Just like how this bunker stuff is being written in nostr:npub10qdp2fc9ta6vraczxrcs8prqnv69fru2k6s2dj48gqjcylulmtjsg9arpj: https://docs.soapbox.pub/ditto/signing
note1059c6pz784zkfukjkwe86ttcnc0fyh9qaf36nxkavml6w69p4ucq5h0lxc
That triggered this idea with me🔥
It’s mostly just client-side stuff
But for the php ecosystem there is not many buid (yet)
For Drupal I made https://www.drupal.org/project/nostr_dev_kit as a bridge
You can try it out here: https//ccns.nostrver.se where you can connect with a Nostr browser extension
I see that it mostly client stuff, but there is some back-end work required. At least providing nip46 php library would help devs connecting their apps to the nostr ecosystem. Perhaps integrating these is too specific and should be done by the app devs themselves...
Yes and I want to bring it to php/wordpress/laravel apps. Any work done there?