41–50 of 97 posts
Wireshark + some post processing?
Congrats. You may want to consider dropping the "reverse engineer" language though, since most every application's ToS is clear on that being prohibited. Perhaps just "replay any application" or similar.
Yeah agreed this messaging is a bit confusing. Our focus is on helping people build automations, not do any mass-scale scraping.
so if API is published, there is nothing to reverse engineer. and if API is not published, and you MITM with self-compromised CAs, and then use it (commercially?) you ~100% breaking ToS. this is just un-ethical. or YC does not have regard anymore for such things?
Ehh…
smeels like severe breach of ToS. virtually every single website and app mandates not to reverse engineer and not to temper with inner workings (including client-server networking). side note, YC25/YC26 batches have multiple startups that blantly violate ToS and sitting on a timebomb just pending a lawsuite and Cease and Desist Letters.
I do have to push back on the ToS comments though. Automation is used daily by nearly all companies. RPA is a billion dollar industry. Browserbase raised at 300M valuation. Is using puppeteer to automate a form submission a violation of ToS? If so then why is using a screen reader not? Is it the intention? Why is hitting network requests directly different? I personally don't think that automation is unethical (as long as it is not affecting server capacity). I don't think the answer to the ethical problems in scraping is just not to automate at all. Open to disagreement here though.
This makes me want to never create a public service again.
Definitely get that. Being hammered by scrapers is a massive PITA (especially with latest aggressive AI crawlers). We focus primarily on allowing people to automate their existing workflows. For all hosted workflows we have rate limits to prevent mass scraping/affecting server workload in any real capacity. In fact, because we don't load js/html and hit endpoints directly I would guess that we consume less server res…
If I’d make a mobile app and users simply use your automation service instead of my mobile app, I’d lose traffic/money/motivation to improve it.
If they run into issues from your service now it could make my app look bad while the error isn’t with the app.
See tailwind for an example tale.
so if API is published, there is nothing to reverse engineer. and if API is not published, and you MITM with self-compromised CAs, and then use it (commercially?) you ~100% breaking ToS. this is just un-ethical. or YC does not have regard anymore for such things?
so if API is published, there is nothing to reverse engineer. and if API is not published, and you MITM with self-compromised CAs, and then use it (commercially?) you ~100% breaking ToS. this is just un-ethical. or YC does not have regard anymore for such things?
There is nothing unethical about this. You can technically do this with a browser and its dev tools.
You being here is far more unethical than this app.
smeels like severe breach of ToS. virtually every single website and app mandates not to reverse engineer and not to temper with inner workings (including client-server networking). side note, YC25/YC26 batches have multiple startups that blantly violate ToS and sitting on a timebomb just pending a lawsuite and Cease and Desist Letters.
Earlier quoted context omitted.
Yep we handle gRPC and websocket. gRPC is a bit sketch/hard to do because of the way the protocol is designed. FWIW not many sites implement gRPC (some google sites and spotify being the only two I can think of), and if they do they usually have decent APIs. Feel free to try and lmk if you have any issues!
so how do you parse gRPC binary? unless you have proto definitions, it is blackbox and is totally unsuable, isn't it?
how does this work? for eg, how is it possible to even deduce bitcoin structure from rpc list?