7 ms·

http://forum.dlang.org/thread/l37h5s$2gd8$1@digitalmars.com http://forum.dlang.org/thread/l37h5s$2gd8$1@digitalmars.com Back to the 90s URLs.

• sliverstorm 13y ago
  It's not like modern forum URLs are all that much better. I mean, yes, superficially this is less obtuse: http://advrider.com/forums/showthread.php?t=801516 http://advrider.com/forums/showthread.php?t=801516 But the number holds no meaning to a human either way.
  • e12e 13y ago
    No meaning is a little strong, eg: http://advrider.com/forums/showthread.php?t=801515 http://advrider.com/forums/showthread.php?t=801515 exist (while http://advrider.com/forums/showthread.php?t=801517 http://advrider.com/forums/showthread.php?t=801517 doesn't at this time). "Normally" such an app (avrider) would be set up with routing such that the url became /forum/thread/<id> -- and with a simple 6-digit id, that's much more managable to type/communicate manually than an uuid or something. All that said, I basically agree -- exposing some "magic" constant/serial number to the user usually doesn't do much to help with the ux. It's actually an interesting problem: what would be the better, more "true" web/REST-like url-scheme for a forum? Perhaps forum/topic/sub-topic/thread-topic ? How limiting would that be wrt. reorganizing the forum threads (and not breaking links) -- this is especially an issue if there's a chance of re-using uri's -- it's annoying to have a link to one discussion morph into a link to another one. I don't think there are any solutions that are significantly better than a (symbolic/numerical) thread/topic id... edit: Actually I see the sense in the email-id-like urls of the d-mars forum (or usenet-like).
    • sliverstorm 13y ago
      Thing is nobody really ever types a url anymore, beyond perhaps: http://advrider.com/forums http://advrider.com/forums