Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Tbh i agree with yy team.
If you're including someone new in an email thread, don't make them read through poorly formatted email threads for bug reports. It's a pain.
Instead, include postman requests as attachments.
Alternatively take the two extra seconds to copy and paste the relevant parts into the mail you're sending to team yy. -
@polaroidkidd these parts have been sent as a screenshot with highlighted lines answering their query :)
Also, it's not even out service that's failing... Suppose you're an average Joe and you're trying to log in to your dropbox account using google's SSO (let's assume allright). It fails. Once reached out Dropbox claims that one of Google's APIs is not responding nad advices you [their customer] to reach out to google {???}. And Google asks you to provide exact info, which APIs are failing, what request is being send and what responce you're getting :) An average Joe, NOT an employee of Dropbox :) -
@netikras but, you're not an average Joe. You're a software engineer. You're held to higher standards than the average Joe when it comes to tech.
If it's an average Joe I doubt they'd even know what an API request is our looks like. -
@polaroidkidd Okay, scratch that. You're a software engineer at a local company and you're trying to log in to Dropbox w/ Google's SSO :)
Does that mean it's your responsibility now to make sure Dropbox has a good connection w/ Google in Dropbox'es backend? Just because you're a sw engineer? Does that mean you should know all Dropbox'es secret keys/auth details used in integrations w/ google? All Dropbox'es responses and custom-made Google's APIs, dedicated to Dropbox only? -
@netikras no. It means you're supposed to know how to write an email containing a bug report and not bitch about someone refusing to read through a email thread or have to manually write out requests attached in a god damn image instead of a postman. Honestly, I would have just straight out ignored your request for support simply because you attach images of requests and responses instead of files I can actually work with.
I'm out. -
@polaroidkidd :) Too bad then. I wish I'd never have to deal with you ever, considering support requests.
If it's a screenshot bugging you -- ask your clients to provide a plain-text version instead of blindly claiming you DO NOT SEE this info
If your inner clockwork is not working at your back office, do not ask your customers to do your fucking job and fix YOUR tools. It is YOUR responsibility
I've spent way too much time in service support to be as arrogant and ignorant as you're suggesting (or xx/yy parties in my rant)
> Hi xx team, we are getting 500 errors from your api. Here's http request and resp.
< hi, we are calling yy team's api http://yy.Com?/api/yyy and it does not respond in 3 minutes, so we treat this as an esockettimeout. Please reach out to yy team
> hi yy team, can you assist us?
< hi, please provide request, url and response you're getting from us
> yy, all this info is in this very mailtrail
< hi, I cannot see request nor response anywhere
> [screenshot w/ highlighted "http://yy.Com?/api/yyy" and "and it does not respond in 3 minutes". Please read through this email thread, it has all the info
< hi, I need request and response to investigate this issue. Esockettimeout is not our error
<wtf are you smoking???>
rant