I failed to make LinkedIn fix their broken international domain URL parser • Hacker News Board

Re: I failed to make LinkedIn fix their broken international domain URL parser

#91

Post by strbean » Wed, Nov 18, 2020, 12:02 AM UTC

Klinky wrote: post #81

ballenf wrote: post #65

Earlier quoted context omitted.

They didn't claim it wouldn't impact revenue. Just that there are probably bigger issues that impact more revenue that should be worked on first from a purely ROI point of view. If and when this issue has a higher ROI than anything else, it should be worked on. The flow of new issues with higher ROI may prevent that from ever happening. I think every developer can easily name 5+ minor bugs in a product they're workin…

Hopefully there is some good logic and systems in place to actually calculate ROI, and it's not just a PM chasing trends and pushing out new features based on their gut. I wouldn't say a user-facing bug that prevents collection of revenue is minor. It's also a little alarming this isn't caught via QA or automated tests. Did this ever work? What other stuff is slipping through? Are we sure the report even escaped supp…

Financial systems are an absolute nightmare, so it doesn't surprise me that some oddball detail in a small country eludes tests. Pretty much every processor, network, and country has a million of those oddball details, and they change regularly.

At work, the platform I have to deal with has dozens of fields on every request and response that are specific to Brazil!

Re: I failed to make LinkedIn fix their broken international domain URL parser

#92

Post by nottorp » Wed, Nov 18, 2020, 1:45 PM UTC

matttb wrote: post #78

mhh__ wrote: post #39

Earlier quoted context omitted.

When this happens is it literally just companies trying to save money so they only need to hire JS developers? Or are static sites not webscale anymore? The web framework I use for my personal stuff just takes templates in and fills it with whatever a request requires, and it's definitely easier than dealing with JS wat-isms.

Pretty sure it's just to combat scraping

... or combat people, you know, actually checking their linkedin accounts once in a while?

I'm not actively looking for a job. I used to check linkedin randomly like twice per week to see what happens. After their new slow motion interface, that changed to once every 3 months. Sorry, recruiters with incredible opportunities.

Re: I failed to make LinkedIn fix their broken international domain URL parser

#93

Post by fsociety » Wed, Nov 18, 2020, 6:25 PM UTC

smt88 wrote: post #18

jansommer wrote: post #3

I'm not surprised the author can't convince LinkedIn to change anything. Had a similar experience with Tinder where Paying in their web application using a danish credit card failed because their cc service returned "visadankort", which had to be changed to "visa" through the developer console for the payment to go through. Got tired of that and filed a bug. Oh the battle it took to actually convince them that an ent…

I'd have to assume "supporting Danish credit cards" is lower on their list of revenue-impacting issues than you expect. If Denmark were a US state, it wouldn't even be in the top 20 in terms of population. If you assume that Denmark has lower usage of Tinder than US, CA, or UK, and then you assume that not all Danish people are paying with Danish credit cards (many of them would be using Play Store subscriptions, whi…

I dunno it’s more about the principle of not fixing the product. I think software teams would benefit greatly by setting principles that they follow instead of justifying everything by revenue.

Not saying you support the revenue-only model btw :)

Re: I failed to make LinkedIn fix their broken international domain URL parser

#94

Post by lopmotr » Fri, Nov 20, 2020, 6:58 AM UTC

jobigoud wrote: post #82

lopmotr wrote: post #76

Earlier quoted context omitted.

Everyone uses Latin script because too much depends on it. Even "https" and ".dk". Localized scripts are exclusionary to everyone else who has no hope of typing them or even identifying them in a unicode table to copy and paste. A funny situation happens in China where even the most computer illiterate old person can type latin letters on a PC with enough patience just by matching appearance to their keyboard, but ma…

> Localized scripts are exclusionary to everyone else It's the other way around, not supporting other letters is excluding everyone else because essentially only English doesn't have diacritics. "Año" and "ano" are not the same word, degrading to ascii only is not an acceptable solution. Imagine for example that the letters 'd', 'q' and 'w', weren't availabe in domain names for some reason and you had to use alternat…

By exclusionary, I mean it excludes people, not words.

But if ñ is so important, then so are capital letters because "Olive" is a person and "olive" is a fruit. Imagine typing English without capital letters.