2014-11-17 UTC
julian`` joined the channel
# 00:11 GWG tantek: That you would be showing contacts based on logged in status. It was based on your work. But, being as login is often automatic, how do you know what a person wants you to not share?
# 00:11 tantek GWG - where/how were those UI thoughts captured on the page?
# 00:24 GWG What's the link for HWC this week? I want to try my first RSVP
fmarier joined the channel
# 00:26 kylewm hey this week is the one-year anniversary of HWC
# 00:33 GWG kylewm: Didn't work. Can I get some assistance?
# 00:34 kylewm GWG: RSVPs are reply posts just like a normal reply, so you should have u-in-reply-to instead of u-rsvp
# 00:36 GWG Just found a code problem. One second
# 00:37 kylewm rascul++ just noticed you added navigable urls
# 00:38 rascul i was (slowly) working on redoing a bunch of code since iwc cambridge, and now it's about done and other things are easier to do :)
# 00:38 rascul gonna read up more on webmentions and see what to do for it
# 00:43 kylewm is reading about Gogs, a "self-hosted Git service written in Go", whose code is hosted on github
# 00:43 GWG kylewm: Thank you. That requires a bigger rewrite. I added in RSVP, but the plugin was originally designed for responses. I hard-coded the h-cite.
mlncn joined the channel
# 00:44 kylewm GWG: you could just stick <span class="p-rsvp">yes</span> in the post body... that's all I do
# 00:48 GWG Where's the webmention form on a Known site?
# 01:01 GWG The Status format of my site, the one with the picture of me when I post, links to the author url. But that page does not have an h-card.
# 01:02 GWG It should link to the site or not link at all.
# 01:26 kylewm.com created /session_facilitating (+1859) "Created page with "<dfn>Session facilitating</dfn> refers to facilitating a brainstorming session at an IndieWebCamp event. Session facilitators are responsible for setting the discussion topic/goa..."" (
view diff )
# 01:32 kylewm GWG: I don't quite understand what the issue "Web user" issue is... Indiewebify.me likes your markup just fine
# 01:33 GWG kylewm: I think it was because it picked up the link to /author which is the WordPress default. I fixed it
KartikPrabhu and jonathanfrei joined the channel
# 01:56 aaronpk I haven't been able to figure out how to join from the G+ page
# 02:02 GWG All attendees should be in the Hangout
# 02:03 GWG That will give you the video feed once it is up, I believe
# 02:05 aaronpk sadly has nothing to demo, just writing up notes on micropub today
# 02:09 GWG thedod is demonstrating templating in Mustache to format webmentions from the IndieWebCamp wiki page.
# 02:13 GWG ben_thatmustbeme is demonstrating some improvements in his MicroPub implementation.
# 02:16 GWG rascul is now presenting his sites...chainging his permalinks
# 02:18 rascul i did more, but talking to a computer is weird and i forgot the other things :(
# 02:19 GWG aaronpk typed up his notes from the MicroPub Session.
# 02:35 GWG This now concludes IWC Online 2014.
# 02:36 GWG Not sure what the next event will be, but I think this was a format worth exploring
# 02:36 GWG We learned that Hangouts on Air is great for demos.
# 02:37 GWG And now its onward to...DC? Providence? NYC?
mdik joined the channel
KartikPrabhu and snarfed joined the channel
chrissaad joined the channel
# 02:58 GWG I would attend DC if I could. But there is no...interested but not organizing section
chrissaad, reedstrm, KartikPrabhu and lukebrooker joined the channel
jonathanfrei, lukebrooker_, reedstrm, hodlr, snarfed, gr0k and thedod joined the channel
# 04:35 thedod Sorry. Internet went down towards the end of the event
# 04:36 thedod anyway, respect to GWG and all of you. I really enjoyed it
KartikPrabhu joined the channel
# 04:51 GWG pdurbin: You were welcome to show.
KartikPrabhu joined the channel
# 05:00 GWG pdurbin: You can watch the video.
wolftune and tantek joined the channel
# 05:38 kylewm whoa, I think you can't log in to the Instagram website without allowing Facebook Connect
jonathanfrei, loic_m, friedcell, wolftune, tantek and Jihaisse joined the channel
pfefferle, KartikPrabhu, eschnou, mlncn, Pierre-O, Sebastien-L, alexhartley, pfefferle_, jonathanfrei, friedcell, modem, modem_ and alanpearce joined the channel
loic_m joined the channel
scor and pfefferle joined the channel
Pierre-O joined the channel
# 13:35 tommorris I'm interested too. I may download WordPress and test out the plugin at some point.
bnvk joined the channel
Sebastien-L, friedcell, pfefferle, danlyke_, brianloveswords, Pierre-O, alexhartley and loic_m joined the channel
friedcell, shiflett, brianloveswords, reedstrm, modem, snarfed and bnvk joined the channel
# 15:53 bnvk hello all you ppls I haven't chatted with in awhile
tantek joined the channel
chalettu, mlncn, brianloveswords and alanpearce_ joined the channel
brianloveswords, alanpear_, eschnou and danlyke joined the channel
alanpearce and mko joined the channel
# 16:25 GWG pfefferle: Thank you for the pull requests yesterday. I still have that question for you though.
# 16:26 GWG pfefferle: I was hacking on it at the time
# 16:27 GWG pfefferle: Is it worth filtering comment_class in semantic linkbacks in order to add mf2 markup or should that be left to the theme, do you think?
# 16:28 pfefferle GWG I tried it completely via wordpress filters/actions, but there are not enough of them
# 16:29 pfefferle GWG but we can add some more through the semantic-linkbacks plugin
# 16:29 GWG pfefferle: And I just updated Semantic Comments, my comment replacement, to replace the comment walker entirely.
# 16:29 GWG pfefferle: My issue is always trying to figure out the right level in the chain for an event to occur.
# 16:30 GWG So, should something be generalized and put in semantic linkbacks or specialized elsewhere?
# 16:31 GWG pfefferle: My proposal is that comment_class should be filtered to add the linkback type as a class to the comment.
# 16:32 GWG pfefferle: Yes. I thought about doing it elsewhere, but I thought it made sense to do it in the plugin.
# 16:32 pfefferle I think this should be part of the plugin, because the plugin sets all these types…
wolftune joined the channel
# 16:33 GWG pfefferle: That was what I was thinking. Wanted to get your opinion before I wrote it up and sent over the pull request
# 16:35 pfefferle I don’t think p- or u- is a good idea, because it is no property or url
# 16:35 GWG Okay. Will write the code when I get a chance.
# 16:38 pfefferle is there a list of the activitystreams object types that will come with spec 2.0?
brianloveswords joined the channel
# 16:48 mko Interesting. You include the caption as part of u-photo?
# 16:48 tantek rascul: you have <span class="u-photo"><img src=""> but that's not doing what you think
# 16:48 mko rascul: I'm pretty sure u-photo should be on the img, not the container around it.
# 16:48 tantek "u-photo" is implying you mean for the property to be parsed for a URL first, then text second
# 16:50 GWG pfefferle: I can't figure out the one for a generic mention
# 16:55 tantek in general, AS is a good source for previous research, but should not be used as any kind of canonical list of types - because they're based in "wants" - not cited research of existing examples and implementations implementing publicly.
# 16:55 kylewm rascul: I really like how minimalist your html is. almost no classes that aren't for mf2
# 16:55 GWG is still not sure what classes to use
# 16:56 rascul kylewm the site generator uses mf2 internally also
# 16:56 GWG tantek: Semantic Linkbacks generates the code for the different types of responses, but doesn't mark them up. That is what I want to add, but need a simple clean markup
# 17:00 tantek wow - nothing is showingup - are you blocking pin13? or doing UA-based sniffing/blocking?
npdoty joined the channel
Pea1 joined the channel
scor and brianloveswords joined the channel
chrissaad joined the channel
# 17:52 tantek tommorris: would appreciate your review of /wikifying in the context of the indiewebcamp community
herbsmn joined the channel
# 17:54 tommorris also, my Eye-Fi arrived today. I'm going to play around a bit this evening to see if there is an easy way to have my pictures go from my camera straight to somewhere I control on the web.
# 17:54 tantek tommorris: that WP page is good general wiki editing advice, which I tried to avoid with /wikifying
# 17:54 tantek and rather focus on aspects of /wikifying that are more in the spirit of what indiewebcamp is about
# 17:55 tommorris tantek: yeah, just pointing out the potential namespace conflict, to ensure we are clear that if they aren't the same, we should document that.
# 17:55 tommorris a lot of people apply Wikipedia assumptions to anything Wiki-ish. :)
# 17:55 tantek right, ours already has the namespace of indiewebcamp.com :)
# 17:55 aaronpk tommorris: I believe the eye-fi relies on their cloud service, but can upload to an FTP server
# 17:56 aaronpk probably supports sftp, I kind of assume that when I say ftp now
# 17:56 aaronpk point is it's not like it goes directly from the card to your server
# 17:56 tommorris aaronpk: got the Pro one. was more thinking of having some scripts on my desktop, or some processes on my phone, to do the auto-upload.
# 17:56 aaronpk ah yeah, if you are in range of a computer and your computer is connected to the card's wifi then it goes direct to your computer
# 17:56 tommorris I mostly bought it so I can quick-post stuff from my phone while out-and-about. seems silly to be taking both a good photo and a phone snap. :)
# 17:57 aaronpk but that ties up the wifi connection of your computer so you wouldn't get an internet connection that way
# 17:57 tantek thanks tommorris - added the ref to WP wikify
# 17:58 tommorris EyeFi + iPhone + posting to my own site in Safari is a good first start.
# 17:58 aaronpk eyefi + mifi would mean the camera can upload via the cell connection any time which is cool, but still relies on eyefi.com
# 17:58 aaronpk just depends on how much you don't want to use their servers
# 17:58 aaronpk I really don't mind because it's not like they store the photos or anything
# 18:00 tommorris my use case is this - back on 2014-03-29, I posted this https://tommorris.org/posts/8872 - I would have liked to have taken it with my decent camera (X-Pro1), then posted it to my own site from my phone, with the photo hosted on my own (sub)domain.
snarfed joined the channel
Sebastien-L, alanpearce, alanpearce_ and pauloppenheim joined the channel
# 18:23 aaronpk flickr supposedly does auto upload but it's not very good
# 18:24 aaronpk they actually use the background location things to wake up and upload photos when you move around
# 18:25 tommorris I'll test it out. My plan is dump everything into an S3 inbox. then have some code that handles the file from S3 (makes sized images, notifies web server). ideally, I'd take a photo, then go to my site and it'd already be there ready to post into my stream.
# 18:27 aaronpk hey it supports webdav! you could write a webdav handler on your web server to do all the processing immediately!
# 18:28 aaronpk hm I was *this close* to resurrecting my dropbox->flickr sync script but I might just try this instead
# 18:30 tantek Wednesday's HWC will be 1 year of HWC meetups!
# 18:32 tantek can you find anyone else to help run Portland HWC? co-host?
# 18:33 sparverius i feel like photo auto upload should be solved in terms of battery usage
brianloveswords joined the channel
# 18:34 aaronpk meh I chew through so much battery that I don't even care if it adds to the usage
# 18:34 sparverius if wifi then upload. if mobile and not low battery then batch and upload lower res version.
# 18:35 tantek sparverius - what what if wifi AND mobile (i.e. mifi) ?
# 18:35 sparverius well you cant reasonably know if you're on a mifi or not so fuck that use case
brianlov_ joined the channel
# 18:35 tantek same way that freenode requires SASL from mifis
# 18:36 tantek so it must be somehow doable - just need to care
# 18:36 sparverius i mean if you hook your phone to a mifi, the expected behavior is that the phone's going to act like it's on wifi
# 18:36 sparverius and id rather have a slightly worse but consistent behavior than really smart but occasionally messes up
# 18:36 tantek expected behavior - whatever is best for the user :)
# 18:36 reedstrm there's also diff. use cases: live post just for personal archive/control, and live post to avoid loss-of-picture if loss-of-camera occurs (equipment failure or 3rd party action)
# 18:37 sparverius for the former, as long as it happens eventually (within a day), i think it's fine
# 18:37 reedstrm An option to ship a low res as 'better than nothing' seems like a good thing.
# 18:37 sparverius for the latter, the compressed version is part of the reason for that
# 18:38 sparverius i think as devices become more location aware, you'll be able to fold things like "if !connectedToFitbit then ohShitIveBeenLost()"
# 18:39 sparverius but anyways tldr the reason ive been thinking about it is that i set up a new phone, and google plus photo always gets my compressed images, but i dont really think of those as "backed up"
# 18:39 reedstrm hehe: I want to see the code for that later method :-)
# 18:39 sparverius and im using that doubletwist photo sync which seems to work well, but i'd love for it to be over the internet vs requiring that i'm at home
# 18:40 sparverius incidentally, my phone has a 20MP camera and can shoot 4k video, so bandwidth and cpu/battery usage for compression are becoming real issues :/
# 18:41 reedstrm sadly, the pixel count wars have subsided in real cameras, but continue in phone-attached-cameras.
# 18:41 Loqi reedstrm meant to say: sadly, the pixel count wars have subsided in single purpose cameras, but continue in phone-attached-cameras.
# 18:42 sparverius reedstrm: it's a really good sensor, pixel count aside. they're using it to compensate for lack of physical zoom... for better or for worse :/
# 18:43 sparverius but im seriously running into issues with self hosting regarding bandwidth usage
# 18:44 reedstrm right - it's all about the glass (lens systems) theses days. That's an interesting trade, though. Esp. if they squeeze in OIS
# 18:44 sparverius sony seems to think super highly of their camera software, so much so that if you unlock the bootloader, you lose the drm keys for it
# 18:46 reedstrm Sony thinks super highly of anything they license to you: and even your own stuff. cf: sony root kit
# 18:47 sparverius actually in the case of their phones, they've been extremely open, even sending code back to AOSP before releasing the new OS
# 18:47 sparverius im okay not having proprietary stabilization if it means i can have cyanogenmod and appops
# 18:48 reedstrm Huh, that's good to hear. Typical big-corp with many personalities, I guess.
tilgovi joined the channel
# 18:51 sparverius yeah it's why i bought a sony. it was basically that or OPO or nexus or motorola, and none of them made phones that i could use with one hand
Sebastien-L and fiatjaf joined the channel
snarfed, verdi_ and gr0k joined the channel
snarfed joined the channel
KartikPrabhu joined the channel
herbsmn joined the channel
# 19:41 GWG KartikPrabhu, I was inspired by your site.
# 19:42 aaronpk man flickr has been getting really unreliable for me lately
# 19:42 aaronpk and now that I think about it, some of the main reasons for using it in the first place no longer apply
# 19:42 aaronpk mainly the integration with mac apps like Skitch, and a host of good upload tools
# 19:43 GWG KartikPrabhu, I do spend a lot of time looking at design elements.
# 19:44 GWG KartikPrabhu, I rewrote my Facepile code to separate by mention type.
# 19:44 GWG I was looking to update the design.
# 19:45 GWG Also I put in a toggle for a comment form. In case I want to bring it back.
# 19:48 GWG KartikPrabhu, I obsess sometimes about details.
alanpearce, benjamin-agaric, SRCR_, j12t, snarfed, hodlr, gr0k and eschnou joined the channel
alanpearce, gr0k, friedcell, KartikPrabhu, fmarier and tantek joined the channel
alanpearce_ and brianloveswords joined the channel
# 21:08 snarfed congrats on running IWC online, GWG! (and ben_thatmust!)
KartikPrabhu joined the channel
# 21:08 bret yeah thanks GWG and ben_thatmustbeme !
# 21:09 bret i wasn't able to make it due to school :(
friedcell joined the channel
# 21:10 GWG ben_thatmustbeme: I don't they are giving you enough.
# 21:24 bret tantek: were you planning to use that for posting code diffs?
# 21:24 bret 13:24 <tantek> bret - yes, *all* kinds of diffs
# 21:25 tantek a diff post is a special kind of reply, that indicates a set of suggested changes to the post it is replying to.
# 21:28 bret basically the idea that popped into my head was posting of a git patch to a permalink
KartikPrabhu joined the channel
# 21:28 bret marking it up, so that the diff is identifiable and adding action buttons
# 21:29 bret would be a lightweight form of a pull request, and totally comparable with indieweb flow
# 21:30 mko bret: I've actually got a "pull-request" template type already made, but not implemented because I've not had a reason to do it yet.
# 21:32 bret mko: sweet! i'm not sure the target of the WM yet... maybe if I have a permalink page for a repo/branches on my site (with syndication links to GH)
# 21:33 tantek I vaguely recall some brainstorming about how to do edit posts
# 21:33 mko Maybe. I don't know how you'd syndicate a PR to GitHub really.
# 21:33 tantek and I didn't see anything captured on the wiki
# 21:33 tantek or perhaps we thought we could re-brainstorm whatever we came up with
# 21:34 bret mko: you wouldn't have to. but then again this is all getting super complicated.... just making a post with a single diff of a specific repo would be enough.
# 21:34 bret tantek: there is some documentation about how to mark up post update edits.. you and barnaby have that iirc
# 21:34 reedstrm bret: simple is important, but scaling to a more complex workflow is good, too.
# 21:35 bret i wast just looking at it the other day
# 21:35 reedstrm a text diff and a code diff may be very diff. animals. ...
brianloveswords joined the channel
# 21:35 bret reedstrm: git diffs/patches are just a block of text iirc
lukebrooker joined the channel
# 21:40 tantek that's different - ins/del are for inline edits
# 21:41 tantek an actual edit/diff *post* itself would (should need) not contain the entirety of the original - though I suppose that's an easy but dumb way to do updates/edits.
# 21:41 tantek just a complete replacement e-content for whatever it is in-reply-to
# 21:43 tantek perhaps if the in-reply-to URL had a fragment referring to a specific paragraph id, then the edit post could contain "only" the replacement for that entire paragraph
j12t joined the channel
# 21:43 tantek perhaps if the in-reply-to URL had a fragmention referring to a specific phrase, then the edit post could contain *only* the replacement for that entire specific phrase
# 21:44 bret :) i like it..... crosses fingers the ##fragmention is specific enough
# 21:49 tantek perhaps if the in-reply-to URL included *two* fragmentions referring to a specific start and end phrase, then the edit post could contain only the replacement for that entire range of content from start to end phrase
# 21:49 reedstrm tantek: have been thinking about adding that very bit to an editor API we're using - eventually to support sync with simultaneous/collaborative editing
j12t joined the channel
# 21:50 reedstrm gotta be careful about the underlying structure, of you do two pointers ...
j12t joined the channel
scor joined the channel
# 21:56 bret what the target should be.... i'm not sure. the easiest would just be a page representing the repo.
sh4l joined the channel
# 22:01 aaronpk sending a post with the diff would not be a webmention
# 22:01 aaronpk a webmention would be hosting the diff on your site, the nsending a webmention with the two URLs
# 22:02 aaronpk the source would need a basic mf2 structure that contained the target URL as well as the patch file
# 22:02 bret Right. Was trying to say that basically ;)
# 22:02 aaronpk like <div class="h-entry"><a href="example" class="u-target"></a> <pre><code class="u-diff"></code></pre></div>
# 22:03 Loqi aaronpk meant to say: like <div class="h-entry"><a href="example" class="u-target"></a> <pre><code class="e-diff"></code></pre></div>
# 22:06 tantek except I question putting the patch in a separate file and not just inline in the post
# 22:06 tantek not sure why so many classes are needed either
# 22:07 aaronpk well you need something to indicate that this is a patch, not just a post of regular text
# 22:07 tantek pretty sure it is workable with just *one* new classname, similar to like/repost
# 22:07 reedstrm tantek: isn't the patch inline in the <pre><code> section in aaronpk's example?
# 22:07 tantek which implies that the e-content of the edit post should replace the e-content of the in-reply-to URL
# 22:08 tantek or lacking an e-content at the in-reply-to URL, the entirety of what is at that URL
# 22:08 tantek no need for u-target - there's already u-in-reply-to
# 22:09 tantek also - why prematurely optimize the markup for just code? I'd think little prose wiki edits would be more common
# 22:10 tantek note that by "simply" (re-)using u-in-reply-to, you can reply to /edit posts as well with another /edit post - to patch a patch as it were
# 22:10 tantek and for any client that doesn't understand edit/update semantics, they'll still show it sensibly as a thread
brianloveswords joined the channel
# 22:13 reedstrm tantek: I'm not seeing this as the serialization format for an edit-mechanism. Coders can talk in patches, much like maths type talk in mathematical statements and proofs. A patch can be a statement of it's own.
brianloveswords joined the channel
# 22:14 reedstrm Or am I a rep. of a fading dinosaur class, for reading patches? :-)
lukebrooker joined the channel
scor joined the channel
# 22:18 reedstrm right -perfectly readable for me, even though I don't know the codebase. I'd +1 that or sign off, or extend the discussion w/ a short form post rebmentioning back to it, etc. W/o having to apply it to a repo.
# 22:19 tantek aaronpk, I'm not sure replicating a specific software's one-off textual diff format is a good longterm strategy
# 22:20 reedstrm tantek the format isn't github's it's git's - it's a standard patch w/ amil headers for some extra metadata
# 22:20 tantek URL to the standard for this patch file format?
# 22:21 Loqi reedstrm meant to say: tantek the format isn't github's it's git's - it's a standard patch w/ email headers for some extra metadata
# 22:21 tantek hey if you're going to call it "standard", you're going to have to provide a URL to said "standard".
# 22:22 reedstrm I'm sure it's part of the SUS , no need for scare quotes
# 22:23 tantek Jeena - thanks, that's at least a man page for implementation "patch" of said "difference listing"
# 22:23 aaronpk i would hate to have to parse that mediawiki html to apply the diff
# 22:23 tantek and reedstrm - again, that's software documentation, not a format spec
# 22:23 aaronpk but yeah i'm all for prettying up the presentation of the diff file like github does
# 22:23 reedstrm I find the context diff more directly readable, as well.
# 22:23 tantek aaronpk - I'm not advocating the format of the mediawiki HTML!
# 22:24 tantek I'm pointing out the *presentation* is better
# 22:24 aaronpk but you need something machine-readable underneath
# 22:24 tantek sure, that's what we're good at figuring out here
# 22:24 tantek however you must start with something human readable on top
# 22:24 tantek saying, here's a diff text thing, good enough, is as bad as the pingback folks with there "… nonsense …" text
# 22:25 aaronpk i dunno, i read the diff format all the time when i'm coding, it's not that bad. certainly github's red/green coloring is better but...
# 22:25 tantek exactly, and some people read MIME headers, or .vcf, or .ics or CSV, or some other one-off text format
# 22:26 Jeena tantek but doesn't github offter this nice frontend for diffs you're talking about when you say nice representation?
# 22:26 aaronpk also I suspect there are plenty of open source libraries for generating pretty html versions of diff listings
# 22:26 tantek we instead pick something where the UX is fairly *good* (competitive with the best in silos / software out there), and then make sure there's markup underneath to make it machine readable. not vice versa
# 22:26 tantek Jeena - then cite the new frontend views of diffs from github that you speak of
# 22:26 aaronpk that's basically waht i'm getting at with this whole exercise... started with github's diff view (link I gave previously)
# 22:27 aaronpk exactly. i was proposing markup that could be added to github's diff URL to make it mf2 parsable
# 22:28 aaronpk also note that github's version is actually the diff format but just styled with css. it even has the + - markers
# 22:28 tantek ok - that probably should get captured on the wiki as an example then
# 22:28 Jeena it says: commit 78aea731f5bb2564cffe155c9ac9591ccc43cef4 ;)
# 22:29 tantek aaronpk, the commit you pointed to - looks different than an *edit*. It looks like a *collection* of edits.
# 22:30 aaronpk a pull request URL is a collection of multiple edits
# 22:30 reedstrm tantek: you didn't read down: yes that's a man page format, but it's also IEEE Std 1003.1 2013, and give complete implementable details in the STDOUT section, complete w/ IEEE 'shall' language.
# 22:30 tantek is that also a "changeset"? or is that something different?
# 22:30 Jeena hm but it is not easy to find a description of the diff patch format
# 22:31 tantek reedstrm - right, it was tl;dr, too many pages to scroll down to see anything relevant so it looked just like more software docs
# 22:31 reedstrm Jeena - I feel your pain. I think the links we both found are in fact it.
# 22:31 tantek it shouldn't need to be embedded in some specific software documentation!
# 22:32 tantek is it implementation dependent? or is there a test suite for it and other implementations?
# 22:33 aaronpk "I couldn't find a thorough spec for the format called "unified diff" so I decided to research it. Here are my findings."
# 22:35 tantek oh hey look at that - commondiff.org is available - who wants to write and post / host the spec? ;)
chrissaad joined the channel
# 22:35 reedstrm That's 2006 - the Open Group I think they had another name w/ Unic in it then) was making you pay for docs back then.
# 22:39 bret i was just presuming the diff contents would be diff format agnostic.
# 22:39 bret with the primary idea of just doing git patch style diffs (for code)
# 22:39 tantek bret - hence I proposed a simple *non* diff format
chrissaad joined the channel
# 22:42 bret the the type of diff is really decided by the target... which knows what it represents to some degree... i.e. received a wm with a diff in it... I am a git repo.. therefore this can only be a git patch diff... or this is a diff.. I'm a note, so this can only be some kind of prose diff... apply if approved and valid format
# 22:45 tantek bret - that's as silly as saying the type of the note is decided by the target
# 22:45 tantek so if it needs something specific, like a proprietary API call, then you do that as part of POSSEing to it
# 22:45 tantek you don't contort your own site into whatever *a* POSSE destination needs
# 22:48 aaronpk it's a relative redirect that is missing the host :(
# 22:49 aaronpk oh it's hosted on github pages. they do weird stuff.
# 22:50 tantek bret - I just think it's a bad idea to start posting stuff that's more machine than human readable
# 22:50 tantek bret - just look at all the design work that aaronpk has done to post nice human undertstandable aaronparecki.com/metrics - instead of just raw lists of lat/longs, or other CSV data dumps
# 22:51 tantek same reason you shouldn't be posting raw plain text diff files
# 22:55 bret right it wouldn't be raw.... it would be styled after the PR thread opening post
# 22:56 aaronpk yeah basically i'd add some tags and css to make it look like github. I think the mf2 parser would even result in the plaintext diff-compatible format as the "text" of the e-content
# 22:56 Jeena hm my comment doesn't show up on aaron-gustafsons website, I wonder if this is my or his fault
chrissaad and myfreeweb joined the channel
# 22:57 Jeena uhm why your? I assume you are not Aaron Gustafson?
# 22:58 aaronpk oh i think he might need to regenerate the jekyll site
scor joined the channel
# 22:59 bret diff code could start collapsed as well
# 23:03 bret i want to post a gif of a screen cap going to File -> Print as an answer to permanence
# 23:11 tantek bret - how about print to laser etched titanium sheets? you know, just in case of fire
# 23:16 tantek now if only the Long Now folks would actually host their media somewhere more permanent instead of on silos
danlyke and reedstrm joined the channel
benjamin-agaric and gr0k joined the channel
# 23:44 tantek snarfed, given the audio/video storage at archive.org - seems like an obvious thing