Chris Angelico wrote: > In some cases, the correct solution would be a short URL at a domain > that the provider controls. But that's no different from running your > own shortener service - it still has the extra indirection and > consequent risks. So for a lot of people, a public shortener is just > as good.
A domain that the provider controls is different: It reduces the risk of the shorter URL breaking because there is only one stakeholder. BTW and JFTR, this thread has gone *way* off topic. -- PointedEars Twitter: @PointedEars2 Please do not cc me. / Bitte keine Kopien per E-Mail. -- https://mail.python.org/mailman/listinfo/python-list
