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
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.
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
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
tantekaaronpk - dates can be used to correlate information, universally, long after the fact. incrementing integers or other apparently random uuids cannot.
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
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
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.
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"
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
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
barnabywaltersthe amount of effort it would take to manually input opening hours+variations on them makes cross-site duplication or updating necessary IMO