jgarberGWG: Cool! Let's pick this conversation up again (particularly regarding a DC IWC). Hope you (and everyone else here) have a pleasant evening (or afternoon or morning depending on where you are)!
KartikPrabhu, chrissaad, davemenninger, mdik and gRegor` joined the channel
mkoben_thatmustbeme: I've been working on an indie-auth'd accessible "Dashboard" view as my default browser homepage, but I've been having problems with IndieAuth losing the authentication. >.<
mkoOh, I'm not blaming IndieAuth at all. I actually meant to say "with losing the IndieAuth authentication" but apparently transcribed it when I was typing. I'm a bit scattered this morning.
tantekaaronpk - I proposed precisely that two days ago in the W3C Social Web WG - that "x is following y" should be a post, just as "x favorited/liked y" is a post. :)
LoqiTo follow is the concept of establishing a digital relationship to another person or entity so that you can receive updates from them over a given social media channel http://indiewebcamp.com/follow
tantekben_thatmust: I have /YYYY/DDD/TN where YYYY-DDD is ISO ordinal date, T is single character post type, and N is the incremental number of that post type for that date.
ben_thatmustbemeheh, tantek, I love MVC for that, model doesn't necessarily mean i have to store in a DB, just a translation from somewhere to my code... i'm thinking I just make my models pull/write to on disk files, but then cache in DB
tantekI made the choice of date-primary over type-primary because dates are a known thing with a known range, whereas types are still being figured out. Thought that was a no brainer in terms of designing which should be more primary in URL / storage design (that's supposted to be longterm, thus more stable).
aaronpkoh another consideration of my URLs is that I often create metrics posts out of order (some data is imported hours after it's created, when I may have created several other posts in the mean time)
aaronpkso I think I'd want to support that format still too. I would end up with two URL formats: YYYY/MM/DD/N and YYYY/MM/DD/HHMMSS (and also YYYY/MM/DD/N-slug)
aaronpkonly potential danger there is if I somehow had over a million regular posts in a single day. but that seems unlikely. 999,999 ought to be good enough for anybody.
aaronpkhttp://indiewebcamp.com/permalinks has a link to my tweet from 2009 about URL shorteners. I wanted to find the version of that post on my site, but in 2009 I didn't have a citation on my tweets
Mark87You have multiple applications that weren't designed to interoperate and store their data in different ways and formats, and you wrap them in adapters and make them talk to each other, or present a higher level adapter that aggregates their functionality to make "one" application
Mark87_I ask because the realm of indie websites could be thought of in some ways as similar, and I just wonder if theres anything to be learned from that connection
LoqiCORS is an acronym for "cross-origin resource sharing," a mechanism for allowing browsers to make JavaScript requests to fetch resources from other domains http://indiewebcamp.com/CORS
tilgovigood for the blogger who doesn't want to write anything but add annotations to their site. and good for the individual who wants the bookmarklet/extension in their browser for annotating other sites.
tilgovicweiske: if we had the server API well documented and made it easy for you to build the front end without any Python knowledge, would that help? Then you could just implement the REST endpoints for storage.
tilgovicweiske: yeah. right now that use case is covered somewhat well, but only if you want to take it as a "black box" and let us run the service or if you want to run the whole stack yourself.
tilgoviAlso I'm so sorry for any nonsense I'm leaving on anyone's notes as I test broken things. I looked around but didn't find whether anyone's built a validator I can use to test.
KartikPrabhutilgovi: interesting. I seem to have picked up some microformats from that page already but didn't seem to pick up a "in-reply-to" URL even though it exists... I'll debug this evening
tilgoviI'm tempted to have one that's just the URL for the header/metadata part of my posts and one that's on the quote itself that has the fragmention
tantekaaronpk, re: another great example of why you should have date-based permalinks with full path navagability, see also the write-up of archive-based dated-link repairing from last Thursday! http://indiewebcamp.com/irc/2014-10-23#t1414105046134
aaronpkben_thatmustbeme: I'm talking about two separate schemes. the first, for articles/notes/photos/checkins/etc is just an incrementing index starting at 1. I'm limited to 99,999 that way. The other, for metrics, is always HHMMSS and I can have up to 86400 of those.
joskartantek: Wouldn't the "fetching-permalink-from-archive" thing work for most use-cases even though the date is not embedded in the permalink? (since I guess you already have timestamps for when you linked to it in your posts / embedded replies / whatnot)
tantekjoskar - "you already have timestamps for when you linked to it in your posts" - that assumes information *outside* the URL itself. That's my point. purely by the *URL* without any side-information you can attempt recovery etc.
joskarI can see why it is more fragile to trust your own timestamp than the permalink itself. I personally wouldn't worry about "less work" since domain takeovers very seldom happens thought
Loqijoskar meant to say: I can see why it is more fragile to trust your own timestamp than the permalink itself. I personally wouldn't worry about "less work" since domain takeovers very seldom happens though
danlykejoskar, I haven't been following this thread as carefully as I perhaps should have, but when you say "domain takeovers very seldom happen" do you mean "we rarely lose our own domains" (probably true), or are you talking about the domains we link to (got many examples of that).
joskardanlyke: I meant "very rarely" more as "not frequent enough to care about speed of execution". I acknowledge that domain deaths happens all the time, but probably won't affect you more than a couple of times per year.
joskartantek: I guess my point of view is "It is easier to change your own habits than to change others." I don't think that forcing a permalink-format onto people is going to work. (although you can encourage the use of one)
tantekjoskar: you're right about changing your own habits being easier. hence what I was suggesting was a practice for indieweb site owners to do themselves with their own URLs first, and second, local-link-wrap any URLs they link to that don't follow the year/date pattern.