I recently reposted all my video content as kind 21 and kind 22 events, as it should be.
The reasons for the appropriate use of kinds is a video i never finished but will soon i think. But to get the point across, practical examples are the best.
Enter vutr.space a video client that is pretty decent despite some rough edges. The main issue:
Lack of content
Shitty slow media/blossom servers.
So how about we start that stupid vlogging trend again, but this time use the appropriate kind and a decent blossom server when uploading🧐.
I pay for mine at satellite.earth .
Nostr.
View quoted note →
Constant
Constant@techno-ethica.com
npub1t6jx...ksrw
Writing a book about Nostr
Ceterum censeo NIP-03 omnibus esse utendum
During my Nostr presentation at FOSDEM in 2025, i represented the query to relays as a lens, that provides a particular view on the big mist of events out there.
@grimoire turned that lens into a shareable thing, calling it a spell instead. Whatever its called, i am glad to see this development, and would encourage other clients to addopt this stuff. Perhaps not entire spellbooks at a time, because the UI of most apps wont work for that, but allowing you to 'cast' individual 'spells' on lets say amethyst or yakihonne would be very cool.
View quoted note →
Hey @Stuart Bowman love satellite, but i dont like the new content ''my files'' interface. The old one was way way better. If i were to guess the new one is more mobile friendly? Well, it sucks as a desktop user atleast; less tiles (only 2 tiles wide), no longer the credit info on that page, stuff like that. Things did not work, and i only now find out i was out of credits (not sure thats actually true, i thought i had more, but it whatever thats all fine you can have the money eitherway).
All and all its currently not a nice place/interface to manage my content :/
Last year at FOSDEM I had this slide where i briefly described how in Nostr problems could be solved in different ways. Unfortunately the bottom right is blocked, but it says *DVM.
I was reminded of that slide today discussing scheduled posts. @Pidgeon is a scheduling service that leverages DVMs, for those people that don't have 24/7 on and connected computers that run a client that could otherwise perform this task.
At the same time, i figured relays could handle scheduled posts rather easily by accepting future dated events, and only handing them out when the date/time has passed. Turned out @fiatjaf already implemented this in the #pyramid relays.
Depending on the method there are these trade-offs;
The DVM model can be used by anyone, and works regardless what relays are used, but it can't support ''protected'' events because relays only accept those if they are submitted by the author themselves.
The relay model does work for protected events, are also low threshold for users, but can only be used on relays that support this scheduling feature.
Lastly client-based scheduling works for everything, on every relay etc. but requires users to basically have a dedicated server running.
And depending on the type of user you are, and what it is you do, there will be a sensible solution for your among those three.
If you have not seen the presentation, here is the youtube link, its almost at 20k views👀
Nostr.
I was reminded of that slide today discussing scheduled posts. @Pidgeon is a scheduling service that leverages DVMs, for those people that don't have 24/7 on and connected computers that run a client that could otherwise perform this task.
At the same time, i figured relays could handle scheduled posts rather easily by accepting future dated events, and only handing them out when the date/time has passed. Turned out @fiatjaf already implemented this in the #pyramid relays.
Depending on the method there are these trade-offs;
The DVM model can be used by anyone, and works regardless what relays are used, but it can't support ''protected'' events because relays only accept those if they are submitted by the author themselves.
The relay model does work for protected events, are also low threshold for users, but can only be used on relays that support this scheduling feature.
Lastly client-based scheduling works for everything, on every relay etc. but requires users to basically have a dedicated server running.
And depending on the type of user you are, and what it is you do, there will be a sensible solution for your among those three.
If you have not seen the presentation, here is the youtube link, its almost at 20k views👀
Nostr.