Replying to Avatar AU9913

I submitted an nostr:nprofile1qqs8suecw4luyht9ekff89x4uacneapk8r5dyk0gmn6uwwurf6u9ruspzpmhxue69uhkumewwd68ytnrwghszxthwden5te0wfjkccte9eekummjwsh8xmmrd9skctcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhs2juazd grant for interoperability testing. Denied. No one is going to be the janitor of nostr for fun, it's a pretty much the worst kind of coding work, even though it'd super needed, they don't want it.

On super apps, checkout the browser in nostr:nprofile1qqsth7fr42fyvpjl3rzqclvm7cwves8l8l8lqedgevhlfnamvgyg78spz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qnse3k pretty epic. Built in wallet and secure chats. once they get notifications working on graphene without Google services, probably will use it way more

I dont believe music on nostr actually happens on nostr. It happens on rss and is distributed and discovered over nostr.

We dont need a nostr janitor as its downstream from RSS. RSS has been a standard thats been reliable for decades. No need to recreate the wheel. They've already got plenty of janitors.

We simply need bots and other programmatic triggers so when things happen in the RSS world, they get automatically noted and bridged to nostr. Plenty ofnpeople have been making music kinds - use those by parsing the rss feeds for metadata. Its a goldmine, seriously. From there people can pull endless other automation and integrations.

Reply to this note

Please Login to reply.

Discussion

No replies yet.