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

nostr:nevent1qqsxgqsmxjd4j8azrzswkrlclj43c88cztnem3nwvz8r0t7xy2l5p6qpz9mhxue69uhkummnw3ezuamfdejj7h36h5p

#dvm

Reply to this note

Please Login to reply.

Discussion

btw, this dvm is running on my laptop, so don't expect a whole lot of speed from it πŸ˜…

πŸ˜…

oh, is that why I keep getting "GET http://localhost/ net::ERR_CONNECTION_REFUSED"

Just kidding πŸ˜‰

Really? Where? Maybe I left a localhost relay?

πŸ˜‚

nostr://nevent1qqswensplsxwlxwz2p7c8z3cr4v3d5kp02snn48nytm6wnt2j45ttrspy4mhxue69uhhyetvv9ujuerpd46hxtnfduk8wumn8ghj7mn0wd68ytnhd9hx2efaltz

β€œRunning on my laptop”

This is the wayπŸ˜‚

Yes. Spinning forever.

reload?

You are incredible buddy πŸ₯‚

Why do you prefer to develop on nostr vs fediverse ?

Great work! And thanks for the TIL nostr:npub1hea99yd4xt5tjx8jmjvpfz2g5v7nurdqw7ydwst0ww6vw520prnq6fg9v2 provides Sparrow updates!

lmao epic flex

Very cool. Now put the output in an event that I can open on Amethyst :)

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

Right, but how does the app know what this is? There is no name for the resulting list. Do I just show all DVM results without any names to the result itself? How does the user parse what he wants out of all DVM results?

Interesting! I need to dive into DVM’s more some time.

Good job πŸ‘πŸ»πŸ€™πŸ»πŸ«‚

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.

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

I’m just joking πŸ˜†πŸ«‚

nostr:npub1el3mgvtdjpfntdkwq446pmprpdv85v6rs85zh7dq9gvy7tgx37xs2kl27r per our last conversation. Does this work for ya?

Thank you! That’s helpful one

Love it! And that's just the first. Thank god I will not be missing the next ones anymore πŸ˜‰.

How it works?

cool stuff nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft! I could really use this app. Keep on rockin 🎸

perfect name