2 ms·
All of the involved parties should fix the problem on their own. Any single one of them fixing the issue won't prevent it from popping up again, since you can s
by Androider 6y ago
All of the involved parties should fix the problem on their own. Any single one of them fixing the issue won't prevent it from popping up again, since you can substitute or circumvent the fixed layer.
Signal should handle this case explicitly in the app, since it's a common frustration for their own users when typing dots, commas and parenthesis.
Android should maybe fix the library, but at the very least fix the documentation to mention that it is not intended to be used in context of prose. Android fixing their library is the least useful of all possible fixes, since it won't propagate to users of Android in any meaningful way for a decade.
The Virgin web team should see that there's elevated 404's, and configure their system to ignore trailing full-stops.
A company the size of Virgin probably already has a process to review marketing messages, but it's likely to be someone eyeballing it, and they should fix it to catch this automatically. They probably already use a marketing automation and scheduling system, that could fix it by verifying the links before pushing.
- bluedino 6y agoIf I was the web team I wouldn’t fix it. You have the chance of breaking some other thing that’s intended to work that way, and you’re guessing what the visitor wants to do, and shouldn’t assume
- Xylakant 6y agoAs the web team, you could specially redirect that one single URL. That wouldn’t make any assumptions on what the user wants - it’s clear they want to go to that specific URL.
- deleted 6y ago[deleted]
- bastawhiz 6y ago> Signal should handle this case explicitly in the app I'm not sure I agree with this. Eliminating the use of a system library because of single bug likely makes everything _worse_ in the end. You might work around this one bug, but how many other bugs might you be introducing? Or how many bug fixes will you miss out on because Android fixed something upstream? If every app has to implement its own URI parsing because the one provided by the system isn't perfect by default, you end up with an objectively worse situation than you started with. How many bugs around punycode or obscure query param parsing rules or unicode or URIs with credentials or new top-level domains will pop up because every app uses a different library with different behavior and different test suites, or a different version of each library? Android fixing their software _does_ actually make a difference, especially with recent versions of Android which update much more seamlessly than older versions have.