Thread

🛡️
Second release of the day: 🚀 Releasing FOMOstr 1.0 A very simple client to talk to "What you missed" DVMs What does that mean? You can use this simple app to see what you've missed in nostr, as calculated by any number of DVMs that implement whatever algorithm they choose to serve this function. 👉 fomostr.com View quoted note → image #dvm

Replies (21)

🛡️
↩ replying to Vitor Pamplona
the result is just a content of stringified JSON e tags, would take a few hours to implement for any capable nostr dev and around 12 minutes for you to implement 😂 nevent1qqsz802vnaqt943fcdcfg6uth6u08wqarsyyujfhs5rcp47p23mrvucpzfmhxue69uhhyetvv9ujue3h0ghxjmczyp4n04wu3rquh5edwkm38ak5ctmhvcnk75wfxda0n5ev34c4esdexn0wkz9 is a response note15lg60u5qrwd2zq8p3qug4x4dy8yz5p5llyhzfcdn4lhjh2snznpqg85zr8 is a request
🛡️
just tried. this idea is so cool. while i didnt miss most of the result i think make a new nip, which start calculation the time the mouse is moving on the screen, stop tracking when it release, publish an event(maybe kind 8086) about how much time user A spending on event B and fomostr will eat all kind 8086 events and generate the result. image
🛡️
↩ replying to Sherry
just needs a better algorithm, this one I coded today very quickly and there's a loooot of room for improvement (like right now I'm not clustering your activity when determining the times you were active at) also, the window size I'm using is very short because I wanted to find more events that would fit in the "inactive window", right now it's set at 30 seconds or something like that