One of our links might be the top story on Reddit, for example. The shortlink follower should be resilient to load spikes. The whole point of a link shortener is to make short links! Having shorter links than our competition could be a business advantage. Our shortlinks should be as short as possible. We should be able to store a lot of links, since we're not automatically expiring them. If we're designing something, we should know what we're optimizing for! What are we optimizing for? Let's proceed with these requirements so we're working on the same problem. It's okay if your list of features was different from ours. Let's definitely support that.ĭo we need analytics, so people can see how many people are clicking on a link, etc? Should we let people choose their shortlink, or just always auto-generate it?įor example, say they want ca.ke/parkers-resume. Worse, what if a book already had the shortlink printed in a million copies? So let's let links exist forever. an internal "resources" page on a private university intranet)? Or.what if someone printed a bunch of pamphlets that had the URL on it, didn't give out any pamphlets for a few months, then started giving them out again? That seems like a pretty reasonable thing that might happen (putting a URL on a printed piece of paper is a great reason to use a link shortener!) and having the link suddenly stop working would be quite frustrating for the user. But what if it's on the private web (e.g. Are there cases where (2) could still frustrate users? If a link is on the public web, it's likely to get hit somewhat regularly, at least by spiders. We could remove links that haven't been visited in some length of time.like 6 months. We could remove links that were created some length of time ago.like 6 months. If people can't delete links.do they persist forever? Or do we automatically remove old ones?įirst, it's worth considering what policies we could use for removing old ones: Since it's an API, do we need authentication or user accounts or developer keys? Is this a full web app, with a web interface?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |