Hi, 1) We could change this part of the URLs to something like: <domain><delimiter><listname>. This way we can compose the full fqdn_listname from the URL but it's not as obvious as the list's email address (it's also still readable).
2) Adding to Richard's slug idea: We could provide a "slug"-field in the list settings (and create list) form. The default slug is the format described in 1) - but an admin can change it to any custom (and shorter) slug they like (as long as it's unique). I suggest that we save the slug/fqdn_listname mapping in a local db table (it's only a ui specific setting, so the core doesn't need to know about it). Cheers Florian Am 12.06.12 05:06, schrieb Stephen J. Turnbull: > Barry Warsaw writes: > > > hashing the mlist fqdn and taking a substring would probably be good > enough. > > Ewwwwwwwwww! > > -1 > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers@python.org > http://mail.python.org/mailman/listinfo/mailman-developers > Mailman FAQ: http://wiki.list.org/x/AgA3 > Searchable Archives: > http://www.mail-archive.com/mailman-developers%40python.org/ > Unsubscribe: > http://mail.python.org/mailman/options/mailman-developers/f%40state-of-mind.de > > Security Policy: http://wiki.list.org/x/QIA9 _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org http://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
