45
browny99
129d

FUCKING TELEGRAM FUCK YOU STAY IN YOUR FUCKING API DOCUMENTATION AND STOP FUCKING TESTING YOUR SHIT ON A PRODUCTION SYSTEM WHY WOULD YOU DO THAT FUCK OFF WHY AM I EVEN DEVELOPING SHIT FOR YOUR PLATFORM ANYMORE WHEN FOLLOWING YOUR DOCUMENTATION LEADS TO FUCKING ERRORS AND WE HAVE TO DECOMPILE AND REVERSE ENGINEER YOUR FUCKING "OPEN SOURCE" APPS BECAUSE YOU DONT EVEN BOTHER TO FUCKING UPDATE THE SOURCE CODE ONCE A YEAR WHAT THE FUCK

Thank you for your attention

Comments
  • 4
    8 points
  • 9
    Fuck you and telegram in the same sentence: 👌
  • 2
    Agreed
  • 3
    👏
  • 5
    Didnt read
    ++ for all caps
  • 1
    What API are you talking about? The bot API isn't at all complicated. The messaging protocol is though, but there's enough of documentation for that.
  • 1
    @monkehparade Both. Their normal API docs are shit, but MadelineProto makes stuff way easier. But the Bot API does some very weird stuff. Errors usually don't have an error code, they just have a description, which may change, or may not, who knows, and they change encodings, return types etc on the fly with no documentation bricking a lot of bots in the process.
Your Job Suck?
Get a Better Job
Add Comment