That about sums up my current state as well. following my intuition in these kinds of things has only ever led me to better states, however.
unclear exactly what the end goal is from here, but I think it has something to do with composability and marketplaces for software components (and will naturally involve WoT at some point, for all things must).
open source software is pretty far along the spectrum of "ownable" by the end-user, but there's a high technical barrier for simple stuff like "I want to change my client UI just a little". say you're a non-technical nostr user and you - for some inexplicable reason - want to add a "clock widget" to the upper-right corner your favorite client. you basically cannot do that without spending a month learning how to fork a repo, work with ai tools, learn how deploying code works, maybe figure out some devops, etc... In that sense, you don't "own" that UI.
consider the "ownership level" the user has over this UI:
https://npub19ma2w9dmk3kat0nt0k5dwuqzvmg3va9ezwup0zkakhpwv0vcwvcsg8axkl.blossom.band/b3cfe5e0f8ae24e11bc4650bba22c390e89a524c4a9ce7be47a84ad3bbc6793c.mp4
(_the user is already aware of a "note composer" element. asks for a new combined component with this and a clock_. this is now available to him in the future - or to anyone else, potentially)
Yes, they're still dependent upon a lot of systems outside of their control, but a picture is beginning to emerge. early days