Mark87_So I'm going to define my own "h-* format that contains properties useful in describing the makeup of any generic h-* object, hard code that one property into my parser, then if you feed it the URL of any page with that markup on it, it can learn to parse any microformat
Mark87_Tantek part of my experiment is slightly restricting the available microformat expression. So its more pseudo-mf2 and probably will be for a while
Mark87_I would love feedback on my feed reader though. I'm tracking a few IRC users in it, and I am intending to implement more indie features like replies and indieauth!
GWGOkay, so my Syndication Links plugin, which adds boxes/icons for things you've POSSEd now has Twitter, Facebook, Google Plus, Instagram, Flickr, Youtube, LinkedIn, Tumblr, and other WordPress...
GWGWhich is why I think I need to figure out some new parameters, then how to populate them. Which is not an aesthetic design problem. It's a structural one
GWGAlso, the problem of how a major change would affect my biggest user not me...but I haven't figured out what I'm doing yet anyway, so it isn't an issue yet
fiatjafwith two days following the chats here I've seen how much these people take the things seriously, use the chat for saying important things and then referencing/complementing the indiewebcamp wiki with this info
Mark87_Although lets say I wanted to post a link, title, and some text similar to reddit. What microformat should I use to signal that its a different kind of post than a post that must happens to contains that link. IE, th post is about that link. Or is that even a meaningful distinction.
LoqiMark87_ meant to say: Although lets say I wanted to post a link, title, and some text similar to reddit. What microformat should I use to signal that its a different kind of post than a post that just happens to contains that link. IE, th post is about that link. Or is that even a meaningful distinction.
pdurbinaaronpk: that reminds me, when one links to a particular line in the logs, you see a few lines of context, but what if this were configurable with URL parameters? Like grep -C10 or grep -B3 -A12.
Mark87_Aaronpk++ very cool. Do you save all your bookmarks into a list along the links of delicious or instapaper or pocket for later reading? Or is there some differentiation, where some types of bookmarks are saved into a list and others are just treated as posts in their own right?
kylewmsqueakytoy2: your prototype looks cool. just a heads up: being based on client-side templates, you would have some difficulty interoperating with indieweb protocols like indieauth and webmention
snarfedpersonally, i'd love to see a "related work" section (including e.g. asheville, ostatus, pants, maybe transmat.io), with descriptions of how they're similar and different, why squiso is needed, and maybe how they might interoperate
hmansBasically, what I'll be doing is verifying the email the user entered, then giving them their "own" subdomain named after a (unique) hash generated from the email. Comments posted will just be indieweb posts, so it's really not much different from an indieweb blog hosting thing, except there's a comment form that can be embededded remotely.
hmansIn #pants, I will eventually be applying the usual spam detection heuristics to all incoming webmentions. But I really only want to solve that problem once it actually becomes one.
hmans#pants has social networking bits (you can follow people etc.), so it already makes some decisions based on that (eg. accepting all webmentions coming from domains you're following.) But it's also meant to support webmentions from other sources (minus spam, obviously.)
tantekand in the OAuth dialog "This application will be able to: … See who you follow, and follow new people. ; Update your profile. ; Post Tweets for you."
tantekespecially if you generalize it to "other people's stuff that I show on my post(s)", and then try to design for at least current (personal) scale, with maybe an order of magnitude of over-engineering
tantekKevinMarks: OAuth itself was agnostic on options/perms I thought - whereas Twitter made specific decisions in their implementation - is that what you speak of?
tantekaaronpk, I tend to prefer positive framing too, and only document the negative behaviors when there's bad behavior that's spreading (hence "antipattern" - a pattern that is spreading, even documented, that is bad)
KevinMarks__Now there is a Facebook/twitter auth fear - my sons wouldn't click the "connect to facebook" button in known for fear of what it might post
KevinMarks__Auth at the point of use is the instagram pattern - it asks you to connect with write permission when you have something to share, not in advance
neuro`tantek: no, old articles make people leave your page (say marketers and trafic managers) and everythng older than a few days is considered as old.
tantekneuro`: also, their logic is flawed. by writing *date-stamped* articles, you can then determine (by level of interest) which ones to write *updates* for. And once you are writing (perhaps yearly) updates on a topic, you become better known as a long term *expert* in that subject.
tantek!tell adactio inspired by your blog post "Twitter Permissions" and recent discovery of yet another service (seen.co) that requested write perms up front, I wrote up this new page on the wiki: http://indiewebcamp.com/incremental_authorization please review and edit/add to as you see fit!
tantek.comedited /MediaWiki:Sidebar (+44) "add building blocks, just after projects, for those looking to see what pieces you can use/build to make an indieweb site" (view diff)
kylewmis there any interest in doing something like indie-config over micropub? thinking something like how you discover syndication targets, you could also discover web-action handlers via a GET request
tantekkylewm: I know we discussed the length of the Sidebar before, but I was a bit surprised to not be able to find building blocks there - so I added them
tantekit feels like we're seeing more new people show up that already have their own website, they don't need to be convinced "why", they don't need a "project" to install, they just want to know how to interoperate with IndieWeb sites
Loqiadactio: tantek left you a message 18 minutes ago: inspired by your blog post "Twitter Permissions" and recent discovery of yet another service (seen.co) that requested write perms up front, I wrote up this new page on the wiki: http://indiewebcamp.com/incremental_authorization please review and edit/add to as you see fit!
tantekif you get a chance, honestly interested in your opinions/feelings on how much of an itch is it for you to be able to tag the people in the photos per http://indiewebcamp.com/person-tag and even auto-POSSE those person-tags along with your photo to Flickr etc.
hmansKartikPrabhu__, I know. I'm thinking of a site that allows non-indieweb enlightened users to comment on indieweb stories without going all in, giving them a familiar looking (eg. wordpress-like) form (name, email, comment).
hmanstantek, are we talking about the Twitter that has a 140 character limit, doesn't send webmentions, uses no microformats, requiring everyone to use intermediates like bridgy?
tantekright - that seems reasonable if your goal is to allow people to comment with minimal work - and many are already signed up on Twitter, making it even easier
tantekperhaps explain the value of more than Twitter and less than an indieweb site that you're thinking of? and why a user would prefer that to "just" using Twitter, or "just" easily creating hosted site on withknown.com?
tantekhmm - I find the quality of comments made through such forms to be so low in general as not be worth providing such a UI. But perhaps you have experienced something different.
hmansTwitter simply doesn't work for any type of meaningful discussion and feedback, and I'm pretty sure asking everyone to go to Known and sign up for a site there will lose most of them.
KartikPrabhu__!tell aaronpk maybe the lower footer on the beta version of chat logs could be stuck to browser window? easier to find context and reply directly without scrolling down
hmansYeah, I'm aware of the discussion and the problems. I think commenting on a specialized blog is something entirely different from commenting on a Youtube video.
JohnDuhI think it’s a matter of size. Blog comments don’t scale well. Blog comments implemented in a way like reddit or hubski could work for larger blogs/sites/communities.
hmansI love the (indieweb) idea of making people just publish their comments on their own (indieweb) domain and send a webmention, but that is an extremely high barrier for most people.
tantek!tell aaronpk it seems some browsers (ahem) redirect twtr.io URLs to www.twtr.io when offline, and then when resuming online, they retry the www.twtr.io URLs which then 404. Could you redirect permanent from www.twtr.io to twtr.io?
tantek!tell aaronpk on second thought, keep returning 404 from www.twtr.io. I'm going to file a Firefox bug on this. This is dumb behavior in the browser and I'll use twtr.io as an example of why the browser shouldn't be "sticky" to the www.* version of a URL.