#aaronpkdid Atom ever get its own logo or does it just use the RSS one?
bengo, KevinMarks__, KevinMarks_, electronicmaji and snarfed joined the channel
#tantekaaronpk - that's not an RSS logo - the standard "feed" logo was actually done / designed by Mozilla, and openly licensed for anyone to use as a "feed"
#pdurbinGWG: ok, based on http://indiewebcamp.com/2015/Cambridge I just put dinner at 18:00 after day 1 in my calendar. Will see if I my wife can pick up the kids from school that night. Thanks. :)
#tantekpdurbin: would be great to see you even if just at dinner
#Mark87my mind is exploding. Is it url format? username=null, domain = kodomulo, port=tyler.cat? Or is it username = @kodomulo, password=tyler.cat? I'm so confused
#tjgilliesmatrix has federated channels too. my relay is on #irc/indieweb:tyler.cat
#aaronpkyay finally renewed the cert for ownyourgram.com
#matrixrelay<@kodomulo:tyler.cat> oh its a rails project
#matrixrelay<@kodomulo:tyler.cat> marvelous, I was gonna write one from scratch but this is much better
#matrixrelay<@kodomulo:tyler.cat> needs to learn rails again
#hmansaaronpk, it's both a blog engine and an aggregator; you can follow "any" indieweb user, and it'll go through various things (ATOM/RSS, h-entry, h-feed etc.) to try and pull their posts. I've also implemented u-like-of et al.
#matrixrelay<@kodomulo:tyler.cat> but why... pants?
#aaronpkwow! would it be considered a reader then?
#hmansBut it's not really in a good place to use right now. The old code base is "not enough indieweb", the new (indiepants) is about 70% done, but we're in the middle of moving house right now, so it needs to wait for a couple of weeks.
#matrixrelay<@kodomulo:tyler.cat> seems a bit peculiar
#hmansI was thinking about other names at some point, but always came back to Pants, it just stuck.
#hmansaaronpk, pretty much -- but it is shoehorning remote posts into a "social feed" structure (instead of giving you a feed-reader like interface. If that makes sense?)
#hmansThe overall goal (regarding UX) is to emulate a Facebook-ish social network without the centralized, silo bits.
#brettjgillies: I have set up something similar to what edrex was talking about. It needs some work though, but conceptually automating a git workflow is all you need to add new stuff
#bretI'm in the process of breaking it into small modules
#hmansPants has a (very simple) API for (mobile) clients, a friend is working on some basic clients for Android and iOS. Idea here is that it works "just" like any other social network, except you log in to your own site (and not the network provider's.)
#shanersAnd I vaguely remember talk of a kind of sorting hat algorithm for determining which kind of post an incoming `h-entry` is based on its attributes.
#shanersLike, if it has a `content` and no `name`, it's *probably* a Note.
#aaronpkyes, or possibly also post type is not important, you can just store the attributes that are found and display it accordingly
#shaners@aaronpk @tantek Do you remember anything like that being discussed?
#aaronpkpost type is mostly an implementation detail within a site
#shanersAgreed. It's an implementation detail that I happen to care about. ;)
#aaronpkbecause an h-entry may have any number of attributes such as content, name, photo, icon, location, etc.
#aaronpkbut the code that deals with the photo for them is the same as for my regular photo posts
#Mark87this sounds like a project I built once before.... You can infer that an h-entry iwht a u-photo is a photo post, but what happens when I post an album as a blog post? There will be multiple u-photos. Just look at facebook
#aaronpkit's just like "hey is there a photo property? if so, spit out this template"
#shanersOk. Me and @tantek both have `h-entry h-as-note` on our notes. But we've (a while ago) agreed that it should prolly just be `h-entry h-as-note` since it's only being used for styling by each of us.
#voxpelliwhere's more docs on the h-as? I know I experimented with it about four years ago, but haven't kept up to date on it
#shanersWhat if we added an optional `as=` attribute on a micropub payload for more specificity?
#shaners@voxpelli: there aren't docs on it. It was an experiment.
#aaronpkben_thatmustbeme: any thoughts on that, since you've implemented a much more thorough micropub posting interface?
#voxpellishaners: oh, but no notes on it or anything? I only experimented with it pre-mf2 and only used it for verbs, not for object types
#aaronpkshaners: interestingly I read that as the english "as" rather than an acronym of activity streams, so I would read "h=entry&as=photo" as "a post as a photo"
#shaners@aaronpk: Exactly. That's the thing I like too.
#shaners@voxpelli: I only use AS for their vocabulary research. Not any of their Atom/JSON implementation. ¯\_(ツ)_/¯
#voxpellishaners: I've done both – but the vocabulary research they did for both verbs and objects – would be nice to use the verbs and objects in mf2 as yeah – it's solid work on the research
#tantekI suppose it's my fault for planting the h-as-* idea, I think it was as a result of FSWS2012 discussions.
#aaronpkvoxpelli: I believe AS2.0 is moving away from using verbs
#tantekover 2 years later, I don't think it was a useful experiment and am considering dropping all the h-as-* class names
#tantekI'm more than ever convinced that explicit post typing in a format is not justified by current use-cases
#shaners@tantek: I'm going to drop the h- part but keep the as-note (mainly for CSSery)
#aaronpktantek: we should document the occurrences of when explicit post typing starts to look like a good idea
#tantekand that the AS design biases in that direction are mis-informed or based on flawed assumptions
#aaronpklike the example shaners ran into with the featured image for a blog post
#tantekaaronpk - the *only* scenario I can think of offhand is when a user actually chooses in a UI the post type
#tantekthat they want regardless of whatever else they add to the post
#aaronpkyes but even most posting interfaces are moving away from that model
#aaronpkit seems that an h-entry with content and location could be either a note with location or a checkin with a comment, so we need to figure that one out
#shanerstantek: I still think there is room for different kinds of posting interfaces. I like the explicit separate post types / UIs.
#tantekaaronpk - indeed - we need to figure that one out by looking at how are users creating those posts and what are their apparent intentions - can we find any patterns among the existing UIs / implementations?
dariusdunlap joined the channel
#aaronpki haven't sat down to figure it out yet, which is one of the reasons i still haven't added checkins to my site
#shaners@aaronpk: How do you differentiate between a Note and a Weigh-in or "Drank a coffee"? Are those all just notes?
#voxpelliwhat is important is probably presentation hints rather than explicit types
#Mark87the alternative to keying off explicit post types is keying off an arbitrary number of property combinations. Which is easier?
#aaronpkMark87: no, the alternative is to not care about explicit post types
#tantekI know benwerd has expressed similarly about Known's post creation UI - that he's seen people continually stumble at the "pick a post kind" step.
#shaners@aaronpk: In HS, we have a core Post (with common attrs) that all other post type build on top of.
#aaronpkbut then I quickly ran into the case of "I want a photo to be presented identically on many post types other than a photo post"
#Loqigives aaronpk a photo to be presented identically on many post types other than a photo post"
#voxpellithe importance of "types" is mostly in giving presentation hints to indiereaders and webmentions presentations though?
#shaners@voxpelli: And presentation on your own site.
#voxpellishaners: yeah, unless you want to add extra personal data for pure presentation on your own site
#shanersAnd for me (and work on Homesteading), some post types will be embeddable into other posts.
#Mark87@aaronpk You will still care about combinations. I.e., if e-content present, show this interface, unless a u-photo is present, then show this interface. "Well just show or a hide a standard photo presentation and its easy". What if you have several u-photos because the post is an entire album?
#aaronpkMark87: i plan to deal with that as it happens, not try to overthink it before making any progress
#shaners@voxpelli: For example, I'm writing an article (or note or checkin), and want to plop a photo/video/audio from my own past posts (a la media library) into this new post.
#Mark87@aaronpk, sure that's fine. That's in line with the whole ethos of indieweb. I'm just saying that at some point, you have to choose what you support, and its easier to say "I support h-entrys" rather than "I support bundles of properties in these combinations"
#tanteksaying what user features you support > saying what plumbing you support
#voxpellishaners: and you don't want the photo to change the "type" thus you want to explicitly tell that the post isn't a photo "type" post?
#tantekvoxpelli: I think that's the key distinction. This isn't about what the post type "is", but rather, did the user take an explicit action to create a *specific* post type.
#tantekwhich also affords the possibility of having a UI for users to *change* the type of post (why not?)
#tanteke.g. I write a note, and later with an update I expand it to a blog post.
#tanteki.e. article with explicit title, more paragraphs etc.
#tantekcould similarly happen with posting a photo with caption, and turning it into a blog post
#tantekreal world example: I kind of did that yesterday, by posting a photo on IG with a note (more than a short caption), and then later turning all that content into a blog post on my own site
#tantekThat felt more like "updating" my previous post, expanding it, rather than "embedding" my previous post in a new post.
#tantekthe copy and paste of the prose in particular from photo "caption" to blog post prose really made the difference for me, in terms of update vs. embed
#voxpelliAnother direction would be to mark up some of the content as the primary/central ones (u-featured?) as opposed to more peripheral data?
#tantekvoxpelli: that's just renaming the problem from "type" to "primary" ;)
#tantek.comedited /Federated_Social_Web_Summit (-19) "/* San Francisco 2012 */ use of h-as-* may have started here, I don't remember offhand if I implemented it myself before the summit" (view diff)
#voxpellitantek: I'm thinking more like a flag rather than added content – if you have a photo, a geo and a blog post content marked up – then adding a flag to one or more of them telling that your primary intent and focus of the post is to those one or more particular parts and the other is just additional data that's not your prime focus or intent of the post
#voxpelli– thus providing a presentation hint on what content a indiereader should put in center if in doubt
#shanersSo. Kind of related to my request to add `as=note` to a micropub payload...
#shaners...HS has title and subtitle on most all posts (except notes)
#voxpellitantek: are there are flag/bool kind of mf2-properties?
#voxpelliOne usecase for the ".x-primary" would be to know if a "u-like-of" or the "e-content" is the primary focus of the post and thus whether to render it in a facepile or as a standalone comment
#shaners@aaronpk: Any reason you see that I can't send `title=foo&subtitle=bar&name=foo+%20+-%20+bar?
dariusdunlap joined the channel
#voxpelliRight now my WebMention endpoint treats all h-entries with a "u-like-of" as being a "like-type" post – which limits the ways people can experiment with different kinds of likes
#aaronpkvoxpelli: there is no content for like-of normally, so if it has content it would be more than a like
#tantekvoxpelli: it represents how people implement likes
#tantekif you want to experiment, you can do so with content / presentation - no need for plumbing
#tantekthat is, don't let plumbing limitations stop your *visual* *human readable* experiments
#aaronpkshaners: it's "name" instead of "title", and I don't see any reason you couldn't send "subtitle" too. that's not the same as summary, right?
#tantekbecause such visual human readable experiments are how we discuss whether any new plumbing is necessary or useful or not
#voxpellithe only way I can experiment with rendering them inside/outside facepile is by guessing what the intent is by sniffing different parameters of the post and trying to find an intent/focus in there :P
#tantek.comedited /ActivityStreams (+523) "/* Use with microformats2 */ note 2011 post about as-* classnames, cite post about using h-as-*, considering removing h-as-* class names" (view diff)
eschnou joined the channel
#aaronpkshaners: i'm confused about that, it seems like a weird hack
#tantekHTML WG concluded the opposite re: <hgroup> element for example, for grouping a title and subtitle.
#aaronpkpretty much every Medium post has a subtitle afaik
#voxpellitantek: just thinking whether it would at all be possible to have something like a ".x-primary" in mf2 – a modifier of an existing mf2-property
#tanteklike any other such feature, anyone interested in it can start by documenting URLs to real world visual examples
#tantekvoxpelli: modifiers of existing properties sounds like it could add complexity
#tantekprobably better to start with what is the use-case / user-flow that results in capturing some sort of notion of "primary"
#shanersTo be clear, I'm not asking to add any properties to h-entry.
#shanersI'm only asking if it is against the micropub spec at all to send attrs that are not a part of the corresponding microformat's spec.
#voxpellishaners: I think the discussion branched into two separate branches ;)
#aaronpkso far the only properties in micropub posts that are not part of the microformat post it's creating are things that cause actions to happen on the server, like syndicate-to
#shanersAre micropub servers expected to quietly ignore properties that it doesn't know about?
#voxpellitantek: yeah, I guess getting more of a discussion going on how to present different kinds of data could help that – will make a note to blog about the decisions I make in my endpoint and how to avoid "typifying" the presentation
#shanersie, if i send `name=foo : bar` and also `title=foo&subtitle=bar`, will your micropub server just ignore `title` and `subtitle`?
#aaronpkthat is what would happen if you don't do anything explicitly one way or the other, so yes
#tantekvoxpelli: that makes sense. yes a blog post exploring that would be great.
#shanersOk. So, I will experimentally send `as, title, subtitle` in HS's micropub payload for our own uses. And any other server that don't want to use those properties can just ignore them
#aaronpkit will certainly work. you should probably also add support for accepting the "name" parameter that other micropub clients will be sending
#aaronpkand those posts would just have a blank subtitle
#tantekaaronpk, how does a micropub server distinguish between such "control" properties like syndicate-to and all other properties which presumably apply to the object being created?
Mark87 joined the channel
#shanersTotes. We prefer title/subtitle, but will fall back to name if title/sub are not present.
#aaronpkcurrently the list of "control" properties is documented on the wiki, and i believe all server implementations only accept properties they know about
#tantekaaronpk - is there any naming convention for control properties vs. others?
#aaronpkno, although i believe the only one right now is "syndicate-to"
#tantekI'm wondering if we should pick a prefix for control properties
#shanersIs currently the only thing is discoverable by a client via `?q=` ?
#shanersHas there been discussion about `?q=post-types` (or some other name) to discover what post types that server knows how to deal with?
#aaronpkone of the other nice things about non-explicit post typing, is that if someone uses a micropub app to post a bookmark, but their server doesn't know what to do with the "bookmark" property, it would still create a plain note with the "content" property which the client could set to "bookmarked _url_"
#voxpelli+1, would be nice if the server could inform the client that it it received unknown properties so the client can decide on alternative paths, can it?
#shaners@aaronpk: I agree about graceful fallbacks.
#shanersStill think it'd be useful to discover the "known" post types that a server create.
Mark87 and danlyke_ joined the channel
#aaronpkjust finished the "follow/unfollow? interface for Monocle
#shanersPS. aaronpk thank you so much for making Quill as both a step by step building guide and a reference implementation. Next time we're in person, a burrito on me. ðŸ‘
#KartikPrabhushaners: unfortunately the @ before a nick does not ping them on IRC. Also links to twitter profile (which might be someone else) in IRC logs. just fyi :)
#KartikPrabhutjgillies: code first ideas will follow