Should Nostr have statuses? nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6

Maybe one string field on profiles and perhaps a date for expiration?

Reply to this note

Please Login to reply.

Discussion

Sure

We want Buddy Lists! 🫂🤣🏃

What are buddy lists?

Well, whether someone is online/active can be deduced by their actions cause it’s all public. Perhaps clients could show a green solid circle when someone is on.

Right, that’s the thought. Someone could be scrolling but not posting or reacting, but they could set a status, as well as an “away” message. And I’m sure we’d find a way to get creative with it. NIP incoming?

Wanna try writing a NIP? Would this be a first?

Actually no NIP needed

This could be simple enough, just query relay for any event by the author and use that as the last active time

Oh, nice…so maybe status could be color coded based on how recently the user was active.

What about the ability for a user to set a custom status? That would probably need a NIP, right?

You can set a "mood" or "status" on profile I guess, that event already has the created timestamp so the same logic can apply

An `expiration` tag could be used so it can be set for some time

This could help in the updates to the LiveStream as well.

How?

We could use another update from the user to identify that the stream is still live so that zap.stream doesn't need to keep updating the event to sustain its status.

That is for the view counter

A way to know which of our fellow Nostriches are online, on an opt-in basis of course.