Mon, 28 Nov 2022 01:26
RSS support has been updated to handle substreams properly. Like everything in product development any new feature brings a lot of questions that need to be answered in order to integrate the feature into the current system.
Current logic is pretty simple - RSS is available only for public streams, substreams are not available. One may argue that both points could be different. That's true! However any branching brings initial complexity and rather then solving all of it before moving on to other features, the plan is to implement other essential features before starting iterating on them.
Now, what features am I talking about?
- First of all some landing page + waiting list needs to be there
- Since a stream can have fields, the dream is to make them actively impact the stream page. For example, if you're recording temperature in your stream, I'd like to show you a graph.
- The streaming nature of the notes becomes clear if the events are put into timeline and that feature needs to be built as well.
- Another concept to play with - sharing. Simple way would be to have one link for all, however I'd like to play with a concept of unique sharing links. Why is it useful? It allows me to apply different sharing criteria for every single one of them. E.g. you can grant a temporary access to your stream like temporary location share in whatsapp or telegram. In this case one can imagine this coud enable paid streams in the futue
- API: Current plan is to build dabdab as an open platform. Actually I think it's completely fine to have some streams generated by the services or apps. Just imagine, how cool it would be if your training sessions get into one of the streams and you don't need a separate app for that!
All features will be implemented at some point, stay tuned.