Avatar
Sebastix
06639a386c9c1014217622ccbcf40908c4f1a0c33e23f8d6d68f4abf655f8f71
Web of Trust foundation board member | Kubo.watch developer | Nostr-PHP library maintainer https://github.com/nostrver-se/nostr-php | OpenSats grantee | Check all my Nostr contributions and services on https://nostrver.se | Solopreneur as a creative / fullstack webdeveloper from πŸ‡³πŸ‡± #PHP #Drupal #Javascript #Vuejs #InteractionDesign | What we need more #FOSS #Privacy #Selfhosting #DigitalWellbeing #Family | Hobbies #Cycling #Gravel #HondaCivic #Circuit

πŸ€™πŸ» I’m with you πŸ€“

Replying to Avatar jonb

🚨 Hey y'all; very excited to introduce a new Nostr experiment my friend nostr:npub15q5a7j3vfgzz7jer5rtpjl7edqyq2vn7qgltzuzuwrgnmwvzrg7svz0rem and I have been working on: zeum.space !

#Zeum enables you to turn any Nostr note into a shareable 3d gallery.

It's early days, but we'd love to hear feedback especially from the #art #artstr #photography communities to see how y'all might use something like this 😁. Thank you!

That’s an insane number πŸ§πŸ€·β€β™‚οΈ

What nostr:npub136jg2fnty2z5vwcnh7p4jpckrs3tk0dpueftgs7mznuuaenjpfps6tjnxf shared πŸ‘ŒπŸ»

I bootstrapped something familiar with Nuxt (Vue) and NDK: https://github.com/Sebastix/nuxstr

But it’s far from a first release ready for building clients with different kind of components.

How Developers Can Mitigate the Risks of User Data Being Exposed on Nostr

https://www.psacramento.com/how-developers-can-mitigate-the-risks-of-user-data-being-exposed-on-nostr/

πŸ”‚ crossposted from https://ccns.sebastix.dev

In iOS 17.4 all WebApp and PWAs features are disabled only for those in EU countries. Besides using these features as a develoepr in Drupal/webprojects I'm also using some PWAs on a daily base. I'm slightly frustrated...so I just wrote down my opinion on this decision by Apple.

Apple is killing WebApps and PWAs in their power-play against the EU: https://sebastix.nl/blog/apple-is-killing-webapps-pwas-power-play-against-the-eu/

GM!

Having really angry feelings against Apple. With their PWA nonsense…

Nostr is a giant shit show. The fact that our software interoperates at all is a miracle and probably just a temporary anomaly. Given enough time, the relentless breaking changes being made to published NIPs will eventually break everything.

Linux succeeded because "WE DO NOT BREAK USERSPACE". For nostr to succeed, changes must "NOT BREAK EXISTING IMPLEMENTATIONS". There shouldn't be any exceptions to that EVEN IF THE IMPLEMENTATION WAS NON-COMPLIANT.

Pay close attention to Linus right here:

> Are you saying that pulseaudio is entering on some weird loop if the

> returned value is not -EINVAL? That seems a bug at pulseaudio.

Mauro, SHUT THE FUCK UP!

It's a bug alright - in the kernel. How long have you been a

maintainer? And you *still* haven't learnt the first rule of kernel

maintenance?

If a change results in user programs breaking, it's a bug in the

kernel. We never EVER blame the user programs. How hard can this be to

understand?

Linus doesn't want to break pulseaudio EVEN THOUGH pulseaudio was doing the wrong thing.

It seems like every week I find a NIP that I've coded for has changed. This last week I think it happened three times already. Sometimes it's a small change and I quickly update my code. But I can't read all the PRs, and I'm afraid dozens of small changes have slipped past my notice. Gossip is probably now incompatible with multiple other implementations which happen to have implemented different versions of the same NIPs (some older, some newer).

Even if we didn't have any breaking changes, the simple fact that different software implements different optional NIPs itself presents to end users like broken software. Why does it work in Damus but not Amethyst? Why does it work in Amethyst but not Coracle? That is an even harder problem to solve.

But let's at least solve the easier problem and stop changing NIPs. If you don't like a NIP make a new one, don't break the current one. Even if you think the current one sucks balls and should have never happened. Even if you think there aren't many implementations out there.

https://njump.me/nevent1qvzqqqqqqypzqpnrnguxe8qszsshvgkvhn6qjzxy7xsvx03rlrtddr62haj4lrm3qy88wumn8ghj7mn0wvhxcmmv9uq32amnwvaz7tmjv4kxz7fwdehhxarj9emkvtcqypewl2znt6s982vhuurxuadeurn6her6qn25pnpnuag4ct6ltxvly8ndwsw

Coracle and Nostur both haved stopped working with my account.

When I use another account, everything works fine. So I make the assumption there is some related data to my account which is breaking things in those clients...it's not fun when you suddenly you can't use two of your favorite Nostr clients anymore. 😒 For now...

I think I've broke Nostr in someway in my case: both Coracle (desktop) and Nostur (iOS) have stopped loading my feed. Damus (iOS) and noStrudel (desktop) seems to work fine.

On Coracle I'm getting a lot of errors which look related to reading out events from relays. When I use an other Nostr account, everything just works fine.

and I already poked nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn about this πŸ€“

Earlier this week I've used https://delete.nostr.com/ to delete some events with short text notes. Could there be a correlation between those actions and the issues I'm facing in Coracle and Nostur?

/cc nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr

Replying to Avatar PABLOF7z

πŸ“’ Collaborative document editing over nostr: Proof-of-concept

@naddr1qqhyxmmvd3skymmjv96xjmmw94hkut2wdaehgu3d2pex7mmx94hkvttrdahxxetswskh5df5v9exzqgdwaehxw309ahx7uewd3hkcq3ql2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqxpqqqzzmk8q5num

So today I called nostr:npub1zuuajd7u3sx8xu92yav9jwxpr839cs0kc3q6t56vd5u9q033xmhsk6c2uc and we were talking about collaboratively editing documents on nostr; I had this very left-side of the curve idea on how to do this, so after kids' bedtime I implemented it to see what it would feel like.

How it works:

A user can invite other users to edit a document (i.e. a long-form, or any other kind of document)

* The invitees can be added/removed at will by the owner of the document.

* The users send ephemeral events while live editing and can hit "save" to propose a new version of the document.

* Everybody sees what the others are doing in real time

* The document's owner chooses which version to make "official".

* Documents can be forked so any of the invitees (or anybody else if the document is allowed to be public) can fork the document and continue working on their own version.

https://flare.pub/w/naddr1qqhyxmmvd3skymmjv96xjmmw94hkut2wdaehgu3d2pex7mmx94hkvttrdahxxetswskh5df5v9exzqgdwaehxw309ahx7uewd3hkcq3ql2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqxpqqqzzmk8q5num

This would be really, really cool to integrate in Drupal or any other CMS.

Collaboration on Nostr Proof-of-concept

https://highlighter.com/npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft/Collaboration-on-Nostr-Proof-of-concept-z54ara

A quick and dirty proof of concept, trying collaboratively writing a document over nostr. By nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft (PABLOF7z)

πŸ”‚ crossposted from https://ccns.sebastix.dev

Replying to Avatar Sebastix

Nostr login library for remote signing with NIP-46

https://github.com/nostrband/nostr-login

This library enables NIP-46 Nostr Connect in your app. It installs a custom window.nostr object that will proxy your NIP-07 calls to the NIP-46 calls for remote signing. The library provides several UI screens to let users set up the NIP-46 connection, it also supports the new OAuth-like flow that is very smooth.

πŸ”‚ crossposted from https://ccns.sebastix.dev

Nostr login library for remote signing with NIP-46

https://github.com/nostrband/nostr-login

This library enables NIP-46 Nostr Connect in your app. It installs a custom window.nostr object that will proxy your NIP-07 calls to the NIP-46 calls for remote signing. The library provides several UI screens to let users set up the NIP-46 connection, it also supports the new OAuth-like flow that is very smooth.

πŸ”‚ crossposted from https://ccns.sebastix.dev

Replying to Avatar Bert

I will give a presentation to https://www.betaalvereniging.nl/en/

and would like to know if anyone has some great Nostr slides / ideas I could include?

It will be attended by, banks, payment processors, regulators and CASPS (crypto asset service providers).

I will mostly cover payments now vs payments in the near future. I also would like to cover nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg his work on chaumian ecash, or do you believe this is too early?

On the 26th of march 11.00 CET I would like to do a live post on primal and show my wallet when zaps ⚑️ flow in. If the zaps are just one Satoshi it's ok, I just want to show live what this tech means. I currently think I'll use nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg because it's the easiest flow for the noobs, any other advice you plebs can give me?

Besides that I think the most important with Nostr is the signing component. You can demo this with a signing extension where you can manage your keys and sign events with it (using a client/app).

Replying to Avatar Bert

I will give a presentation to https://www.betaalvereniging.nl/en/

and would like to know if anyone has some great Nostr slides / ideas I could include?

It will be attended by, banks, payment processors, regulators and CASPS (crypto asset service providers).

I will mostly cover payments now vs payments in the near future. I also would like to cover nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg his work on chaumian ecash, or do you believe this is too early?

On the 26th of march 11.00 CET I would like to do a live post on primal and show my wallet when zaps ⚑️ flow in. If the zaps are just one Satoshi it's ok, I just want to show live what this tech means. I currently think I'll use nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg because it's the easiest flow for the noobs, any other advice you plebs can give me?

You could explain why Nostr is the most sovereign identity layer just like bitcoin is the most sovereign money layer (and lightning as a payments layer). Have a look at wallets which are integrating Nostr or look at https://nwc.dev