#tantekianloic - it was designed to be a type-dispatching system
#tantekthat is, each type prefix potentially has a different algorithm for how the rest of the URL is interpreted/decoded
#tantekI did it that way so I could partition different kinds of posts into discrete problems that I could solve as I got to them, rather than assuming a universal decoding for all post types
#tantekhaving learned that how you archive/backup a bunch of text can (could) vary greatly from more space intensive needs like images, audio, or video
#tantekso it's useful in that it allows me to focus on one problem at a time, and postpone solving other problems
#tanteka useful characteristic of any kind of deconstruction approach to larger problems
#ianloictantek, hmm interesting. So your shortener has / can have a lot of knowledge about the implementation of your specific blog / audio / video stores?
#tommorristantek: yeah, well each one may have some more detail, plus a big "checkin" button. it's just divs with paras inside, but might end up being a table, or an ordered list of definition lists.
#tantekthe initial destinations at least (what the shorturls expand to)
#tantekthey may of course 301 to longer links - which is how I implement slugs for example
#tantekand thus can *change* the slugs of my posts without having any links break
#tantek(unlike pretty much every other CMS out there - wordpress etc. - where if you change the slug of a post, you break all links to that post)
morrocco_mole joined the channel
#@carlbert_RT @aral: Worrying trend using Facebook, Google+, and other walled gardens as blogs. Especially geeks should know better. #indieweb
aaronpk and morrocco_mole joined the channel
#@LorryWoodmanRT @aral: Worrying trend using Facebook, Google+, and other walled gardens as blogs. Especially geeks should know better. #indieweb
friedcell1, tantek, andreypopp, eschnou, eschenal, friedcell, catsup, danbri, donpdonp and mxuribe joined the channel
#aaronpk!tell tantek catching up on the URL discussion earlier... I totally understand the arguments for more information in URLs, but I don't see how having the date+sequence in the URL for a venue is any less opaque than an incrementing integer, or a uuid
#tommorrishopefully London next year. a bit easier to get to.
#barnabywaltersyou’re in London, right? so a lot easier to get to!
#tommorrisI'm about half way between London and Brighton, so yes.
#barnabywaltersnow I’ve figured out I can get cheap bus travel to London if I get up really early, I should be able to go to a whole load more stuff
#barnabywaltersjust reading through the logs I missed from last night — to clarify, "opaque" in this context refers to something without specific meaning, right?
#Loqitantek: aaronpk left you a message 1 hour, 17 minutes ago: catching up on the URL discussion earlier... I totally understand the arguments for more information in URLs, but I don't see how having the date+sequence in the URL for a venue is any less opaque than an incrementing integer, or a uuid
#barnabywaltersaaronpk: only w3c stuff I can find about opaque is it being used a lot, and then css/svg properties :)
#tantekaaronpk - dates can be used to correlate information, universally, long after the fact. incrementing integers or other apparently random uuids cannot.
#barnabywaltersso it seems that there is in fact no easily accessible definition of "opaque" as used in this context
#tantekbarnabywalters - opaque can be used to mean in this context as, provides no other information.
#tantekwhich is a reasonable equivalent to the common definition, you can't see anything through it.
#tantekincrementing integers is not totally opaque, since it does still give you a tiny bit of information (relative sequence)
#tantekbut the garbage UUIDs you see are typically opaque
#aaronpkif I use strings like XXXX.0000.YYYY in my URLs to identify things, you have no idea what that means at first, so it's opaque. If I then told you that I'm encoding information in the characters and told you the encoding scheme, it's no longer opaque
#aaronpkso strings are opaque unless they have a known structure and can be decoded
#tantekif they're not opaque to the creator, they're not opaque. that's just delayed discoverability.
#aaronpktantek's short urls are opaque unless he publishes the encoding scheme (type+date+sequence)
#barnabywaltersso the opacity of any given string depends on the context and available information
#tantekaaronpk - and even that's not necessarily true, as people good a (de)crypto can reverse engineer things from patterns
#tantekand feel free to cite the definition given above
#tantekaaronpk, in fact, I'd say that reverse-engineerability is a feature of a good id hash - the easier that people can decode what's going on from the fewest number of instances of the hash, the better.
#barnabywalterswrt self-hosted indieweb venue URIs: I’m wondering if there’s some straightforward way of scavenging/syncing venue information between multiple sites
#Loqibarnabywalters meant to say: …I define a delegate URI and build the backend for it, and it’s done
#barnabywaltersi suspect YAGNI syncing/updating venue information, but it could be done by linking to "this venue on my friend’s sites", and periodically polling (or using pingback, or something) for changes
#tommorrisbarnabywalters: publishing your own URIs for venues is quite useful. your friends could feasibly look at your list and use that as part of their checkin process.
#tommorrisso, for instance, if I checked in at place X, and then two minutes later, you went to your site to checkin and your phone told your site that you are very close to me, and we've added each other as contacts, there's some likelihood we are at the same place.
#tommorrisso the UI could (like 4sq) show that you have friends there
#barnabywalterswe don’t have a self hosted venues wiki page yet, do we?
#tommorristhat's obviously a way off, but declaring same-as relationships between venues is useful.
#tommorrisbarnabywalters: not yet. but I'm making progress on checkin
#aaronpkshort version: a checkin is stating that you are at that venue. it may contain text or photos as well. a note with a venue is where the venue adds context but your intent was not to say "I'm here"
#barnabywalterstantek: not much, but self-hosted doesn’t specifically mean "under your own domain", wheres I interpret indieweb to mean that
#Loqibarnabywalters meant to say: tantek: not much, but self-hosted doesn’t specifically mean "under your own domain", whereas I interpret indieweb to mean that
#tantekso indieweb is self-hosted on your own domain?
#tantekso it sounds like you meant indieweb venues from those definitions that you gave ;)
#barnabywaltersindeed I did :) Thanks for prompting a rethink
#tantek.comedited /venues (+2619) "definition, merge indieweb venues subsection from checkins page into this page" (view diff)
#tantek.comedited /checkin () "(-1349) /* indieweb venues */ move most content to the new venues page." (view diff)
#tantekbarnabywalters - take a look at the merging of content on the venues page and see if it makes sense to you - tried to preserve some sense of logical flow
#tantek(and thanks for starting the page, that was very much necessary)
#barnabywaltersthe amount of effort it would take to manually input opening hours+variations on them makes cross-site duplication or updating necessary IMO