spells are the simple, left curve approach to custom feeds that can follow you from one client to another. no relay dependency. no Rube Goldberg machine. nostry. comfy. catchy name. implementable in a single prompt if your client supports NIP-65. it's just a REQ, bro.

Replies (8)

It's just a way to create and publish custom relay filters. You say what your feed should contain, save it with a name, and then you can click that name in any spell-supporting client and see the same feed. I had done the same, in a GitRepublic prototype, but this publishes the filters as events, which means you stay client-independent.
multi content-type clients that treat every event kind as a first class citizen like Ditto and @Nostria are good candidates. the use case is user-created custom feeds or counts, filterable by you and your contacts' pubkeys (you can do not so common stuff like querying what your contacts are zapping, reacting to, etc.). spells solve the problem of feeds being hardcoded in clients and a closed system. by making REQ queries reusable we make clients open and expose ways to see the network that were not possible before unless client devs hard coded them. hope i answered all your questions, if not let me know. i read this by pure chance since it wasn't delivered to my inbox relays btw.
โ†‘