Projects

xav.cc

xav.cc is an open-source URL shortening service, built on the PHP framework Symfony. The url shortener itself is available as the "sfDoctrineShortUrlPlugin" plugin for Symfony, and xav.cc adds some functionnalities : an api, an administration backend, etc.

Cas.im/ir

Casimir is a simple to install and use URL shortener, that let the user set the short URL he wants. It only needs PHP and MySQL to run.

sluggable-mixin

This project allows a Google AppEngine developer to quickly and easily add URL-ready slugs to entities in the DataStore.

Ascii Hex URL Decoder

This tool decodes Ascii Hex encoded data found in URLs used in recent SQL Injection attacks.

Strongly Typed Url Generator

The UrlGenerator tool is used to generate strongly typed Urls according to the website directory. So you could navigate to a URL or receive the request parameters safely. The project is developed based on C# and ASP.NET 2.0.

django-ittybitty

This application offers those with Django-powered sites to have their very own URL-shortening capabilities with great ease. For an idea of what "URL-shortening" means, have a gander at http://mashable.com/2008/01/08/url-shortening-services/ or just Google "url shortening". ... [More] It's kind of a big deal all of the sudden. Why should you use this when all of those services already exist online? Maybe it's just me, but I don't like relying on 3rd party servers in order for my site to function, and that includes relying on other servers for people to follow a link to my site. With this application installed, you no longer need to worry about downtime on those other servers affecting your traffic at all. If people can't get to your site using the shortened URLs generated by this application, you probably have bigger problems (ie your site itself is down). By the way, here's the article from scripting.com that inspired me to create this project: http://www.scripting.com/stories/2009/03/07/solvingTheTinyurlCentraliz.html FeaturesHas potential to shorten up to 18,446,744,073,709,551,615 URLs in 64 characters or less (plus the length of "http://www.yourdomain.com/"). if you have that many URLs to shorten, you are likely to need more hardware before you need more URLs... Uses a simple template tag to give your templates access to the shortened URL for any given page on your site Will not try shorten a URL if the URL itself is shorter than its generated shortcut URL would be Keeps track of how many times a particular Itty Bitty URL is used to access the real URL on your site Requirementsdjango-ittybitty requires a relatively modern version of the Django framework. By modern I simply mean a version with the newforms-admin functionality. If you're running on Django 1.0 or later, you're good. django-ittybitty also relies upon the django.contrib.sites framework in order to create the full URL for redirecting users. InstallationDownload django-ittybitty using one of the following methods: easy_installYou can download the package from the CheeseShop or use easy_install django-ittybittyto download and install django-ittybitty. Package DownloadDownload the latest .tar.gz file from the downloads section and extract it somewhere you'll remember. Use python setup.py install to install it. Checkout from SubversionExecute the following command (or use the equivalent function in a GUI such as TortoiseSVN), and make sure you're checking ittybitty out somewhere on the PYTHONPATH. svn co http://django-ittybitty.googlecode.com/svn/trunk/ittybitty ittybittyVerifying InstallationThe easiest way to ensure that you have successfully installed ittybitty is to execute a command such as: python -c "import ittybitty; print ittybitty.get_version()"If that displays the version of ittybitty that you tried to install, you're good to roll. If you see something other than that, you probably need to check your PYTHONPATH environment variable. ConfigurationFirst of all, you must add this project to your list of INSTALLED_APPS in settings.py: INSTALLED_APPS = ( 'django.contrib.admin', 'django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', ... 'ittybitty', ... )Run manage.py syncdb. This creates the table in your database that is necessary for operation. Next, you should add an the Itty Bitty middleware to the MIDDLEWARE_CLASSES in your settings.py file. For example: MIDDLEWARE_CLASSES = ( 'django.middleware.cache.UpdateCacheMiddleware', 'django.middleware.common.CommonMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.contrib.auth.middleware.AuthenticationMiddleware', 'django.middleware.doc.XViewMiddleware', 'ittybitty.middleware.IttyBittyURLMiddleware', 'django.contrib.flatpages.middleware.FlatpageFallbackMiddleware', 'django.middleware.cache.FetchFromCacheMiddleware', )Note: if you have django.contrib.flatpages installed, you will probably want to place the ittybitty.middleware.IttyBittyURLMiddleware class above the django.contrib.flatpages.middleware.FlatpageFallbackMiddleware in your MIDDLEWARE_CLASSES. This is so that the flat pages middleware will check for a flatpage before the Itty Bitty middleware tries to kick in. UsageOnce all of your configuration is taken care of, using django-ittybitty is very simple. In any Django template, just {% load ittybitty_tags %} and have fun with the {% ittybitty_url %} template tag! For example: {% extends 'base.html' %} {% load ittybitty_tags %} {% block content %} Link to this page! {% endblock %}or: {% extends 'base.html' %} {% load ittybitty_tags %} {% block content %} {% ittybitty_url as ittybitty %} Link to this page! {% endblock %}or: {% extends 'base.html' %} {% load ittybitty_tags %} {% block content %} {% ittybitty_url as ittybitty %} {% with ittybitty.get_shortcut as short_url %} Link to this page! Link to this page again! Link to this page one more time! {% endwith %} {% endblock %}If you want each and every page on your site to have a link for "link to this page", you could throw the {% ittybitty_url %} tag into your base.html (or whatever template everything else inherits from) and call it a day. [Less]

irssi-mysql-url-logger

Log urls with irssi to a mysql database.

wp-custom-urls

Custom URLs Plugin for WordPress

moohistory

MooHistory is a URL hash wrapper for MooTools which is designed to emulate the onhashchange event for all A grade browsers. MooHistory also uses its own style of formatting the anchor hash (#/hash/). MooHistory is different from other JavaScript history manages because it doesn’t over complicate ... [More] the simple process of URL history tracking. http://www.yearofmoo.com/moohistory/ [Less]

jaxlex

jaxlex is a cross-platform rich links manager with the goal of overcoming the inherent limitations and inflexibilities of the XBEL format (http://pyxml.sourceforge.net/topics/xbel/) and the Bookmarksync (http://sourceforge.net/projects/bookmarksync) project. FeaturesMost of these features are ... [More] lifted directly from the mozilla feature-request wiki. Smart Folders and TaggingI would like to be able to sort my bookmarks into 'Smart Folders,' and have those folders contain bookmarks based on various criteria, including by way of a user-definable 'tagging' system. For example, let's say I have a few dozen bookmarks. Some tagged with 'News,' some with 'Games' and others with 'Ottawa.' Some of these bookmarks are Live Bookmarks, and others are just regular old bookmarks. I would like to have one Smart Folder that contains all of the 'News' + 'Ottawa' bookmarks, another with 'News' + 'Games,' another with just 'Games,' a fourth with just 'News,' and a final with all the Live Bookmarks, regardless of tagging or other criteria. Keyword Option for Bookmark FoldersWhat about adding keywords to bookmark folders like we have for bookmarks? That would be smooth. Then you can open a folder from the search bar. This would be very useful for opening a group of bookmarks in a subfolder, instead of accessing from the bookmarks toolbar. The keyword should trigger the “open in tabs” command. Visual BookmarksVisual bookmarks are a screen shot of a bookmarked webpage created the last time it was visited or when the bookmark is created. The idea is that visually oriented people — aka designers — would likely remember a website more by it's design and appearance than the name or current title of the website that they saw for the split second while they click OK on the Add Bookmark Window. Another reason for visual bookmarks is when people are use to a website for it's design and have stopped visiting it regularly for a while, and when they are fumbling through their bookmarks looking for it again it may have changed it's design. With Visual Bookmarks, a screen capture could be made of the old design to help them realize that what they are looking for well, isn't anymore. To implement it there should be an array of options like file format, screenshot dimensions, history, and update interval. File format/saving options are self explanitory and really a high quality JPEG or PNG would be best. The dimensions of the screenshot would be equivilent to setting the inner part of the window to exactly 900x900 or 3600x800 and taking the inner screenshot from there; assuming they entered 900x900 or 3600x800, it could be anything. It is important that they are NOT setting the window size as menu bars etc would be variable between clients and frivilous. A screenshot history option are how many out of date screenshots to keep, perhaps a redesign locator which could compare screen shot similarities to detect a design change, but that is probably FAR to ambitious. The update interval would be the frequency screenshots are to be updated, set globally and per screenshot. The output of these screenshots would appear perhaps when a bookmark is hovered over or in the Manage Bookmarks window. Automatic Grouping of BookmarksI would love to see a system that would allow automatic grouping of similar bookmarks, being too lazy to keep my ever growing bookmarks properly categorized. In another section someone has suggested tagging for categorization. I have situations where a site I visit is both a source of news and a source of reviews for instance. How cool would it be if you typed a bookmark tag into the address bar and it opened, in tabs, all the bookmarks that had that tag? Bookmark MaintenanceOver the long term, the bookmarks list becomes less useful as it becomes weighed down with the cruft of bookmarks that have lost usefulness for various reasons including: The page is gone (404) The page has moved somewhere else (301/302) The information has fallen out of date The user has forgotten why the page was worth bookmarking The user lost track of the original bookmark, making redundant bookmarks (no doubt this list can be expanded) Eventually it becomes easier to Google for the links anew rather than hunt through the unweildy bookmark list. Faciliating management of these issues would be very helpful for maintaining a streamlined, functional list. Some possibilities: Live Collections Using Advanced MetadataSimilar to the Live Folders concept mentioned above, but allow bookmarks to be automatically collected based on metadata other than just tags (such as server-provided data). For instance, periodically do HTTP HEAD requests to bookmarked addresses, and flag those that return statuses other than 200 OK. Collected into live folders based on their status codes, the user would be able to easily cull dead links and decide whether to update the moved ones. Likewise, allow bookmarks to be grouped based on criteria such as last access date (to cull, or rediscover, links you never use anymore), the page's Last-Modified date (to identify resources that have grown irrelevant), and duplicate/similar addresses (including those that have obviously different URLs but would become redundant based on a 301/302 status update). If the client-side metadata (such as last access) could be shared across workstations (i.e. between work and home computers), that would also be cool. Visual Cues in Bookmarks MenuFavicons and screenshot previews are helpful visual cues about a bookmark. Extend this concept to other metadata. For instance, maybe the user would want 404s to be grayed out, and recently-visited links to be bolded. Or certain tags might be asssociated with small graphics similar to favicons, so the user can quickly skim down a long list, identify the few bookmarks that meet his/her criteria (ex. IE + hacks + 4stars) — even through he doesn't recall their titles. This could also be done through the use of super-imposed mini-icons over the favicon. It would be similar to the shortcut arrow that windows and mac users are familiar with. Perhaps a tiny (X) in the bottom right side of the favicon for a bookmark that was a 404, or a colored star system for the rating, etc. Bookmarks Menu SortingAllow user-defined sorting of the Bookmarks menu. Chronological order quickly becomes non-meaningful in a long list. Allow sorting by title, domain, or date, etc. A pair of persistent no-sort options too, please, on a folder by folder basis. No sort folder contents only, no sort entire folder substructure. I often do not want particular folders sorted, particularly when exporting bookmarks to edit them into a web page. If you also increased the size of the manager's description form, I could go back to using the bookmarks tools as a handy outliner like I did in Mozilla. A related enhancement: enable separate exporting of bookmarks folder substructures with a templating capability so users and developers can more easily define export formats, and add export to clipboard (rather than a file) as an option. Fore some ideas on implementation, see the Mozilla CopyURL-Plus extension, the handiest browser extension on my desktop. It would also be useful to be able to sort the folders/subfolders separately from the individual pages. Temporary/Time Based BookmarksI think many of us frequently need to save websites we wish to return but don't want to keep them bookmarked forever. For instance when I comment on blogs I often like to return to reply to the discussion later but if I kept every article I'd commented on in my bookmarks it would rapidly grow unwieldy. An earlier contributor uses bookmarks for keeping a 'to visit' list and would like to be reminded about the contents of the list when non-empty. Similar use cases would be remembering items you are comparing to purchase, funny pages you want to show friends, long articles you are reading, remembering conferences or other events that will lose relevance shortly, and remembering stories to write a blog entry about. In firefox 2 this sort of use is very cumbersome. With 'add bookmark here' bookmarks can be added efficently enough but every time one wants to remove bookmarks you need to go to the manage bookmark's screen. Some more efficent means of removing temporary bookmarks is needed, perhaps several. The following features all seem good: Expiration times for bookmarks, when created you can specify a date on which the bookmark will be deleted/become invisible. Folder based expiration times, particular folders could time out bookmarks when they age past a certain date. Most recently used display with bookmarks disappearing after they fall below some threshold. The above but at the user's request. Easy option to delete without entering the organize bookmarks page. Of course all of these really need appropriate sort option. POST bookmarksSome website searches dumbly use POST instead of GET so you can't just associate a simple keyword and smart bookmark. Making it possible to store POST requests would prevent me from writing boring javascript bookmarklets. Exporting BookmarksWhen we export bookmarks, it would be nice to have a property on each category and bookmark that could make them private and so, not exportable. This is important because if we want to share our bookmarks there are always bookmarks that should not be shared. If there was some automatism that would export public bookmarks to a server that also would be very interesting. [Less]