The play I had in mind is this:
Not our only trick, but certainly one of our tricks, and one of our most important tricks, in delivering a campus portal, is presenting hyperlinks to stuff.
Abstracting those URLs via a URL shortener, therein modeling who it is who ought to be able to manage which URLs, and providing UIs for that management, takes some pressure off of the portal itself. Yes, it'd be nice to have more and more powerful delegated administration, content management, but maybe we need that less if we at least had delegated administration over named, shortened links.
So I look at Kutt, and wonder if I could abuse it a bit by putting user group identifiers in the password field and make it require you to have the specified group to administer a given link. Then whenever adding content in the portal, put all the hyperlinks into a Kutt instance, and then use Kutt to manage the evolution of those links over time (and enjoy analytics on them.)
On Friday, March 13, 2020 at 12:15:19 PM UTC-5, Christian Murphy wrote: