waypoint

Thinking about /waypoint..

1. Hub subscriber one-copy to Redis, done ✅
2. Redis Streams/consumer groups, done ✅ 
3. 1s read/write, ⏳ 

4. We want an app-driven package/crate for getting events out of hubs, but ...
5. We need a sustainable project that rewards effort

6. North Star is batteries included

3, the bottleneck is tuning the database upserts. Considering a more jobs-based approach, but working with streams and consumer groups seem more powerful.

5, proposal to require a wallet passed as an env var with a valid @hypersub subscription in the app, which can be trivially removed if folks want to fork.

6, easy to setup = easy to use = easy to contribute.

how do you think about filtering? say I only care about a subset of FIDs or messages

Farcaster Development Boutique @ https://dTech.vision 💜 in love with tech 🤓decentralization, fitness and oldschool rap 😎

Hub subscribers/stream processors could trivially implement filters in memory, but a later problem.