61–70 of 87 posts
Earlier quoted context omitted.
If my browser is downloading some data, then what’s the difference if my AI agent is doing the same? I’ll even tell you it’s my browser. Who are you to say what qualifies as a browser?
The law will say what qualifies as a browser. Computer programmers are not legal experts lol. The law is not a program. The difference between you accessing it and a computer accessing it makes these things different.
In my experience reverse engineering is often the easy bit, or at least easy compared to what follows: maintenance. Knowing both when and how it fails when it fails (eg in cases like when the API stops returning any results but is still otherwise valid). Knowing when the response has changed in a way that is subtle to detect, like they changed the format of a single field, which may still parse correctly but is now i…
We feel your pain with maintenance. We have plans to handle this by using LLMs to detect response anomalies. From our experience, reverse engineering is still less prone to breakage compared to traditional browser automation. But we definitely want to make integrations even more reliable with maintenance features.
Every X hours test the endpoints and validate the types and field names are consistent... If they change then trigger some kind of alerting mechanism to the user.
Earlier quoted context omitted.
We feel your pain with maintenance. We have plans to handle this by using LLMs to detect response anomalies. From our experience, reverse engineering is still less prone to breakage compared to traditional browser automation. But we definitely want to make integrations even more reliable with maintenance features.
Wouldn't something like snapshot testing from a scheduled probe be more effective and reliable than using an LLM? Every X hours test the endpoints and validate the types and field names are consistent... If they change then trigger some kind of alerting mechanism to the user.
It's time for there to be a legal protection framework for OSS maintainers to stop being bullied with legal threats from Megacorps.
What's the stance on security for handling private tokens/cookies/sessions/etc?
Nice work, congrats! How do you deal with security related stuff like recaptcha, signed requests and so on? Do you also support internal APIs of mobile applications? If so, how do you deal with AppCheck / PlayIntegrity / Android Key Attestation / Apple App Attest?
Thank you! Integuru itself doesn't handle recaptchas and signed requests, but we have a hosted solution where we use third-party services to handle recaptchas and manually create integrations for handling signed requests. We do not directly support APIs for mobile applications; however, if you use MITM software and get all the network requests into a .har file, Integuru should work as expected. We do not handle AppCh…
It actually worked decently well but of course there where edge cases and i was thinking of giving it a shot more recently to fill the gaps with LLMs.
Pretty cool to see someone take this idea much further and make it a service and I feel like theres even more potential here, and not just for integrations.
At one time I experimented with reverse engineering API from HAR files to automatically generate open API spec then client. It actually worked decently well but of course there where edge cases and i was thinking of giving it a shot more recently to fill the gaps with LLMs. Pretty cool to see someone take this idea much further and make it a service and I feel like theres even more potential here, and not just for in…
Earlier quoted context omitted.
New pipe breaks regularly. It's almost like YouTube changes the API on purpose to hurt 3rd party clients that don't show ads.
Either that, or they just straight up don't care. I think it's pretty likely that they just don't look at or test Newpipe when they change their APIs. If the change doesn't break any official clients, it goes through. With how large Youtube is, I iimagine API changes are not infrequent.