4 ms·
I agree. It was meant to be a bit... cheeky. Honest question though, is your issue with the fact that LinkedIn isn't plain-text, or the nature of the informatio
by JosephRedfern 9y ago
I agree. It was meant to be a bit... cheeky. Honest question though, is your issue with the fact that LinkedIn isn't plain-text, or the nature of the information that LinkedIn provides?
- jwfxpr 9y agoNeither. If any of us curl/wget/whatever that file, we gain no usable, plain text, human information. We then have to, manually, notice the redirect, take a manual action to follow up, and then those two further objections would apply. Why implement a text file spec that doesn't serve a text file? Even if all your text file contained was "Please see http://linkedin.com/example” http://linkedin.com/example” it would be a correct implementation.