31–40 of 94 posts
This is the problem I had in mind when building https://chota.link . I have seen too many broken previews. This little app lets you create short link and specify metatags. Try this short link on LinkedIn: https://chota.link/jVZ2Hd . I tested it and seems to be working.
"punycode" does seem to break a few things in userland, but obviously should exist for the web to be more useable in more languages. I've delved into the subject a bit and as someone else has mentioned, "homograph attacks" are a thing. Looking deeper, it seems each TLD has a set of dictionaries and rules for what is an acceptable combination of characters, and what isn't (to avoid homograph attacks)- and as I underst…
Am I misunderstanding or are you looking for Unicode normalization? http://site.icu-project.org/design/normalization/custom
Earlier quoted context omitted.
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…
The question is what the cost of that fix would be. Once the ticket reaches the developer it's probably quickly done and pays for itself with a handful registrations. However getting from support to a developer is the complex part. (Support has to understand the issue and then it has to be routed to the correct team ...)
That's not how they would likely see it. If their devs are 100% utilized (which I'm sure they are), then fixing any issue -- even a 30-min one -- is going to mean that a different issue is delayed.
The question becomes this: at what point is fixing this issue more valuable to the company than any other issue the same dev could work on?
And the answer is possibly "never", depending on what high-impact bugs, features, or technical debt they have on their priority list.
This is the problem I had in mind when building https://chota.link . I have seen too many broken previews. This little app lets you create short link and specify metatags. Try this short link on LinkedIn: https://chota.link/jVZ2Hd . I tested it and seems to be working.
Any reason on the name? Chota is a despective way to say "Penis" in South America.
Working with internationalized URLs (IRIs) is a Cursed Problem. Here is the IRI for the Wikipedia page on semiconductors. When you click on it, it should show you a page with a picture of a silicon wafer on the left. https://ar.wikipedia.org/wiki/شبه_موصل Now try copy/pasting that link text into different web apps and see how they respond. HN seems to handle it correctly. Twitter doesn’t, it considers شبه_موصل to be…
Earlier quoted context omitted.
That's not my experience. Going to https://xn--coronaprver-ngb.dk/ in Firefox presents the invalid certificate, but going to http://xn--coronaprver-ngb.dk/ redirects me to https://www.coronaprover.dk/ . It seems Brave always tries with https, and thus it fails. Not that it is confused by IDN.
The link provided was https:// so it would be a serious security issue if it downgraded to http. It is the website that is broken (or at least does not support that link).
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…
Earlier quoted context omitted.
The question is what the cost of that fix would be. Once the ticket reaches the developer it's probably quickly done and pays for itself with a handful registrations. However getting from support to a developer is the complex part. (Support has to understand the issue and then it has to be routed to the correct team ...)
I completely understand why you see this as a 30-min fix, and therefore they should just knock it out. That's not how they would likely see it. If their devs are 100% utilized (which I'm sure they are), then fixing any issue -- even a 30-min one -- is going to mean that a different issue is delayed. The question becomes this: at what point is fixing this issue more valuable to the company than any other issue the sam…
It's not like they are doing Moon landing there 24/7. It's a simple bug with direct impact on the revenue. They should take a half hour break and fix it.
At some point Linkedin changed their site from something that at least worked to some javascript that i can actually watch loading and assembling the page because it's so slow. And you expect ... support for internationalized domain names?
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.
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…
Some companies do what's right. Some only prioritize based on revenue maximization.
Locking out an entire country is clearly wrong. Only prioritizing for revenue maximization is only ambiguously right.
It's not like fixing a bug is going to bankrupt Tinder.