(Creators here:) We are excited to talk about the architectural and design principles that underpin the development of the Capture SDK. While the ideas behind the Capture SDK came from a general frustration around the limitations of mobile observability, the internal architecture details can be traced back to the work many of the initial bitdrift team members did on both Envoy and Envoy Mobile during their Lyft tenure.
We are excited to announce the release of bitdrift's first product, Capture, as well as our $15M series A financing from an amazing group of investors led by Amplify Partners! Focused on mobile observability, we believe that Capture will revolutionize how mobile engineers debug their applications.
And some would argue that billion dollar companies like OpenAI, Meta etc should figure out a way to compensate the people who created the content they depend on.
Making the uncensored, unbiased, un-"aligned" results available to all for a fair price is compensation enough, I think. That's what we should be pushing for.
Whether demon or genie, any notion of putting this tech back in the bottle is a non-starter. As is turning it into a giant money grab for the copyright industry.
Given that the README literally has Android support and build instructions, it would be helpful if you qualified your comment with more than a one-liner like that.
Can you detail, say, why curl as a backend isn't necessarily sufficient here?
