What problem are you trying to solve?
Who has this problem?
Who feels so set back by this problem, that they would pay for a solution?
Who and what do they interact with, and how?
What are the typical routes and workflows they would use to enter, exit, and move through your application?
Why would they want to solve their problem with your application, rather than another (and don't mention Nostr in the answer!)?
If they are using another application, what might motivate them to switch (and don't mention Nostr in the answer!)?
Define the specific domain this application covers. Is it a global domain or some virtual space?
If it is a specific space, should you design it to occupy or surround an actual space, or should it still be completely distributed?
If it's a global domain, how private do the comms have to be?
If it's a space, how do you control access to the space? Does some part of the space need to have another layer of access or private comms? Is it okay for lurkers to see and/or hear all or some of the activity in the space? How do you find the space and gain/lose access to the space?
If it's global, how do the actors reliably find and recognize each other? How do they ensure mutual access to important data?
If it's a space, walk around that space. Decorate it, in your head or a drawing. Pick the objects up, examine them, put them down in a different place. Pick a notepad up and write on it. Put the notepad back down. Talk to the other people walking around. What are those people looking for? Can they still find the object you moved? Do they know you wrote something on the notepad?
Etc.
you need to think more abstractly about what a person might want to be notified about
an issue is a post, that is tied to an event that you created the root of, it tags the event and thus you would set up a filter that looks for events that tag roots (repos) that you want to monitor, and possibly, not ones of people you have muted
and mutes, they are so broad, you may not want to read someone's war and peace posts on demand in your issues but usually enjoy their long form posts, for example
so, notification engines need to be complex by nature, highly configurable, with sensible defaults that don't give you notification fatigue too quickly... and temporary ignores that can quickly be set up when you need to focus, generally, or just not see some particular thing
Showing page 1 of
1 pages
