Loqiownyourresponses is a project to enable PESOS as a service for likes, replies, reposts, and event RSVPs from silos to your own indieweb site https://indiewebcamp.com/ownyourresponses
tantekKartikPrabhu: alternatively, if you have a solution, it can be helpful to suggest it along with reasons why it may be better than existing approaches.
aaronpk!tell tantek I would be curious to see your thoughts on implied post types written up as a spec, for the purpose of deciding which posts to show in my different "collections/feeds"
Loqitantek: aaronpk left you a message 2 hours, 56 minutes ago: I would be curious to see your thoughts on implied post types written up as a spec, for the purpose of deciding which posts to show in my different "collections/feeds" http://indiewebcamp.com/irc/2015-09-28/line/1443497824862
M-keganBut implied types trigger my knee jerk DONOTWANT spider sense. It becomes hard to do anything more exotic than what was considered when doing the implied algorithm
M-keganAnd that's ignoring the combinatorial explosion of "location clobbers pic unless there is foo in which case bar" which then becomes really hard to grok. Explicit types make it easier to reason about in general which I much prefer. Hence wanting to know a good reason for considering it
tantekin fact, so much so that "easier to reason about in general" is a very poor way to design anything where a user in is involved. since "reason about" implies data-centric = plumbing-centric thinking which is an anti-pattern.
tantekas to why explicit post types are "being abandoned by post creation UIs", you'll have to ask the common popular silos, however one aspect is, lower cognitive load for creating content.
M-keganI reject the notion that "data-centric = plumbing-centric" - if you want to encode display information in the request along with representing the post in a way which is usable beyond display (searching, subscribing to post type subsets) - the most flexible display is arguably HTML which is a pita to parse, the most pure data form being explicit types with properties relevant to the type. To me, it sounds like the
M-keganimplied types is a way of trying to "compromise" one or the other, rather than keeping them completely out of each other's hair (e.g. with an html key and allowing template style {{vars}})
M-keganI also don't buy "does not occur in practice" as a general rule - of *course* you don't think it will occur in practice, the whole point is to design a solution which solves all the things you think *do* occur in practice. My argument is that you don't know what the end-user will do and making assumptions about how types are composed sounds like Trouble as end-users develop bodges to work around assumptions baked into
M-kegane.g. it's feasible that I *want* to tie a p-location to a u-photo (because the location is NOT a check-in but is a "this photo was taken at this location") rather than the assumption that it is tied to the entire h-entry
pfefferle, ttepasse, ttepasse_ and elf-pavlik joined the channel
tantek!tell M-kegan the counterpart of "does not occur in practice" is designing what *does* occur in practice, and deprioritizing (not worrying about) what there is no evidence for, or what "will occur". Also "all the things" is not the point, but rather, solving for the 80/20 *today*, and continuing to gather data, and iterating.
tantek!tell M-kegan current thoughts on checkins are here: https://indiewebcamp.com/checkin - there are some recommended practices however no convergence in practice as of yet - would be great to see how you publish checkins on your personal site!
kylewmhmm, it is unfortunate that the micropub spec is using a mix of - and _ in properties... e.g. "in-reply-to", "syndicate-to[]" vs. "place_name" and "access_token"
tantekkylewm: it's similar except that in practice (in /create UIs) as soon as a user uploads a photo, there is consensus that it's a "photo" post, regardless of whether they'd started writing a note or not.
ZegnatDidn’t Instagram change their location policy not too long ago to make it harder for your location to pop-up on maps? I wonder if that will negatively effect the number of checkins you are seeing.
aaronpkand tantek is correct that access_token is plumbing stuff, not really part of the micropub request, since it's from OAuth 2 and is only used if a header is not sent
aaronpkthe problem is when I want to include a photo with the reply, (which I didn't think of at first), I'd have to update my reply template to be able to display photos
aaronpki'm switching now to this "implied post type" idea, where everything starts as a post, and posts can have various properties like a photo, an "in-reply-to", etc, and the code knows how to display the posts depending on what's in it
tantekrosetree1: re: your question, I have both /article and /note replies on my site, and what makes them replies is the presence of an in-reply-to link. I have also seen /photo replies e.g. in comment threads (even on github) where literally the only thing in the /reply is a photo (like a meme image).
rosetree1I’m currently thinking about differentiating between articles and notes. Just to make sure visitors can subscribe to multiple feeds (long posts, short posts, everything).
tantekthat is, you can provide a UI / archives of "multiple feeds (long posts, short posts, everything)" *regardless* of how you differentiate internally
aaronpklast night I started writing some rules that automatically add posts to different feeds based on their implied post type, but I can always override that if I want
tanteke.g. right now I have explicit distinction between articles and notes in my URL structure, but I'm leaning more towards getting rid of that (making everything "notes")
aaronpkwell, at least identical for the post types that are in common. I have a few more feeds I'm planning on publishing than what's on the wiki page now
rosetree1I think I’m going to drop my idea of a specific post URL. I don’t completly understand why and couldn’t explain it, but it seems to be better :)
rhiaroI'm going to expand my different types of feeds soonish, and work out rules for automatically adding to a feed, plus ui for manually indicating feeds at post-time
rhiaroSo if you want to subscribe to be you get options of different sets of stuff to follow.. Be good if a reader could offer this, rather than relying on someone knowing what they want to subscribe to
aaronpkalso I think it's funny that I'm ending up back here after having designed+built exactly that feature into a twitter clone the year after twitter launched
M-kegan!tell tantek I agree that UX driven development is good. I also agree that solving the problem for the majority of use cases is pragmatic and iterating for "the 20%" is a good strategy.
LoqiM-kegan: tantek left you a message 2 hours, 32 minutes ago: the counterpart of "does not occur in practice" is designing what *does* occur in practice, and deprioritizing (not worrying about) what there is no evidence for, or what "will occur". Also "all the things" is not the point, but rather, solving for the 80/20 *today*, and continuing to gather data, and iterating. http://indiewebcamp.com/irc/2015-09-29/line/1443537703049
M-kegan!tell tantek I see the problem as two distinct issues : "how do I represent a complex type post in such a way that I can subscribe sensibly to all checkins say" and "how do I represent this complex type post on the UI".
tantek.comedited /post-type-discovery (+396) "/* Next steps */ explicitly note plan to to use W3C wiki, github, irc if spec is accepted as an editor's draft in the Social Web WG" (view diff)
Loqitantek: M-kegan left you a message 56 minutes ago: I agree that UX driven development is good. I also agree that solving the problem for the majority of use cases is pragmatic and iterating for "the 20%" is a good strategy. http://indiewebcamp.com/irc/2015-09-29/line/1443546843092
Loqitantek: M-kegan left you a message 56 minutes ago: I see the problem as two distinct issues : "how do I represent a complex type post in such a way that I can subscribe sensibly to all checkins say" and "how do I represent this complex type post on the UI". http://indiewebcamp.com/irc/2015-09-29/line/1443546854304
tantek!tell M-kegan I agree /checkin is challenging in many ways (UI, representation etc.) hence have not included it in the current (first) explicit version of Post Type Discovery. Feedback welcome! https://indiewebcamp.com/post-type-discovery
tantekand I'd say in practice that's what you want. e.g. you reply to a github issue with some random meme image - did you really want that in your "photo stream" ?
tantekthe converse is, I totally want the freedom to reply to people with WHATEVER, and NOT have it pollute the streams of "my stuff" that people subscribe to
snarfeddo we have guidelines or an algorithm for how to present webmention sources with multiple "types?" e.g. if the target link has both in-reply-to and like-of?
aaronpki suppose it's not unreasonable to treat that as two actions and display it accordingly. I would display both the profile pic in the "likes" facepile, and also show the comment
aaronpkwhat's the point of saying "this post is a _____" when what you'd actually be doing is looking at the properties on the post and deciding one or more things to do with it
KevinMarks"2. Blogging on Medium feels like a new media format native to the web and that could only come post social. The best Medium posts are a combination of collaging and blogging. You include tweets, gifs, pull quotes, graphics, and videos along with your text. The social era fragmented the networks by media type. Medium gives you a way to pull it back together."
kylewmtantek: I actually do step 11 the opposite way. if content ⊆ name, (and just contained in, not necessarily the prefix) with the idea that name will either the be == the plaintext equivalent of content, or it was auto-generated and will be the content + all the other stuff around it
JeenaIf you don't have a good and flexible application structure from the start, you gonna have a hard time to fix that later. But if you wait until you have a good structure before you start, you never gonna write anything anyway, so refactor all the things!!!
nitot_, gRegorLove, KartikPrabhu and snarfed joined the channel
JeenaIf I have a note A and I reply myself to that with a comment B then with salmentions I would need to resent webmentions to all the comments associated with note A, does it mean I should send a webmention to comment B too because it is now associated with note A? Those salmentions are a complicated beast.
gRegorLoveJeena: I thought Note A would only need to send an updated webmention to whatever it was in-reply-to (if anything), not all the comments on it.
LoqiSalmentions are a way to propagate comments upstream by sending a webmention from a reply post to the original post when the reply recieves a comment https://indiewebcamp.com/salmention
Jeenaif you take a picture of me and tag it, then I write a comment and later tantek writes a comment too then I want to know that he wrote that comment
Jeenaok forget the person-tag, you write a note, I comment on that note, later tantek comments on this note too, I still want to be informed that he did that
Jeenahm, ok, I tried to read the definition really slowly on http://indiewebcamp.com/salmentions and I guess gRegorLove is right, it seems only to cover the in-reply-to chain of events
ZegnatIt all sounds like it will be a secondary product/service though … maybe a new try for them to become profitable? Want to post news on Twitter, need more than 140 characters, pay up.
ZegnatMost IndieWeb is just linking to your own site, though. While those other services are specifically made for everyone to use them to post tweets over 140 characters. And if Twitter wants to run a service like that, well, I do remember what they did to Twitter clients
aaronpklike... as much as i appreciate tantek's really long notes that link to my posts, i don't want the full text of those showing up as a comment :)
kylewmI'd be kind of interested to see that Civil Comments model applied to all of twitter. before you can write something, it shows you three random status updates (+ your own) and you have to rate them as constructive before they are published