Ask HN: What is the most annoying integration you've had to build?
7 comments
Authorize.net payment gateway using SOAP and XML. Don't want to go there again.
I did some work with payment gateways in the 90s; never again!
Also, I did some work with the GSMA (mobile carrier association) specitied SOAP based SMS api. That was exciting... Turns out different implementations of the server need different xml posted to them, even though they theoretically use the same spec. And then there's SMPP which is an open specification, except the standards org disbanded and shut their website, so you've got to find random PDFs out on the web somewhere.
Also, I did some work with the GSMA (mobile carrier association) specitied SOAP based SMS api. That was exciting... Turns out different implementations of the server need different xml posted to them, even though they theoretically use the same spec. And then there's SMPP which is an open specification, except the standards org disbanded and shut their website, so you've got to find random PDFs out on the web somewhere.
On top of gstreamer - it's an absolute mess with no coherent threading model
SOAP server (in PHP 4) to send fax messages using Hylafax.
Building an integration with Microsoft Teams has been infuriating, especially after working with the Slack and Discord APIs (which were so much easier to manage)... I'm curious what other potential high-value integrations have been difficult for others.
We'd contracted to mail stuff to another company's customers, as we had bulk mail equipment etc; I'm the tech sent to their office to procure an actual list of addresses to mail things to. Ask them about their database and no one knows what the words mean. To them the customer list is on the magic computer that got sent from out of state and they only touch with great trepidation and potent fear.
No unauthorized users could touch the "customer list" machine, so there was no hacking it out of the software in a sensible sane way. None of the rituals in their little book come close to "dump database in CSV" and the thing is equipped with only a modem, a floppy drive, and a big ass tractor feed line printer they run the bills on.
But the "run the bills* ritual is one they have, and the printer connects to a parallel port, and I can with a little bit of bodge connect my little laptop to the other side of that parallel port... capture the "bill run", parse out the addresses, and finally emit their DB in a useful form.
Building that was actually fun, but then no one else could assemble the laptop stack to actually perform the procedure so I owned the entire operation for the short time it ran.
No unauthorized users could touch the "customer list" machine, so there was no hacking it out of the software in a sensible sane way. None of the rituals in their little book come close to "dump database in CSV" and the thing is equipped with only a modem, a floppy drive, and a big ass tractor feed line printer they run the bills on.
But the "run the bills* ritual is one they have, and the printer connects to a parallel port, and I can with a little bit of bodge connect my little laptop to the other side of that parallel port... capture the "bill run", parse out the addresses, and finally emit their DB in a useful form.
Building that was actually fun, but then no one else could assemble the laptop stack to actually perform the procedure so I owned the entire operation for the short time it ran.
The ones the decide they didn't need and end up never using. All the wasted effort...