@riley @foone they already do with unacceptable "#ToS" and laws that criminalize said #API0...

• And I'm millimeters away from snapping!

@troed @dalai @foone The problem will be that one will have to reimplement the "#API" as #api0 from scratch by running inspectors in browsers all the time...

• Remember: The platforms that run these are hostile to the very idea of said phat client.

It'll necessitate all api 0 calls to come from the same #IPv4 and/or #IPv6 as the end-user and hide itself with a fake #UserAgent to prevent countermeasures like #RateLimiting and #blocking.

@troed @dalai yes, you did misunderstood it as it's still some shitty bridging which runs a way higher risk of getting blocked by #API changes instead of a *"cleanroom" implementation that parses the webinterface and web API with a regular #UserAgent like a #Browser.

Or as @foone said: "#api0"

• It should be broken down to something that is not dependent on centralized infrastructure to work!

I mean, these ain't like in the old days where a few Megabytes got you #Pidgin and other Multi-Protocol Clients of the old days where everyone had to implement bespoke, custom and incompatible and often completely undocumented, proprietary protocols like #ICQ, #AIM, #SIPE, etc.

• Nowadays all these do have some kind of #WebApp or Web Interface one can just login (because none of them do proper #E2EE with #SelfCustody of all the keys!) so this should be way easier these days:
• All they do is do HTTP(S) GET/POST so the most critical part is to attain credentials like a #Login #cookie and to basically run a console on i.e. #Firefox to reverse-engineer the "#API0"...

@benetherington @foone #API0 is kinda like #web0 I guess... ^