elf-pavlikcapability url is Capability URLs grant access to a resource to anyone who has the URL. There are particular application design patterns for which this is useful as they remove the necessity for users to log in to a site and are easily delegated to others. But their use can open up some security issues. URLs are not generally required to be kept secret, and there are various routes through which capability URLs can leak into unintended hands. This
Loqiconneg is short for HTTP Content Negotiation, a method by which a browser or other web client can request content of various types from a web server, and depending on what is requested, and what the server supports, it tries to provide the best it can https://indiewebcamp.com/conneg
ben_thatmustbeme!tell tantek makes it so that I often do not bother, but will usually do just a quick skim. The recent conversations were largely interrupted and I had a free block of time, so I did read back
ben_thatmustbemestill reading through... but interesting thoughts about pubsubhubbub. I really don't like it for the fact of huge spec with lots of extra but then doesn't work for things like this.. PuSH only works for subscribing to feeds.. I feel like we need to be able to subscribe to posts as well... similar to FB & G+ once you comment on a post (g+) or are tagged in a post (FB) you are subscribed to it and get future updates on
ben_thatmustbeme!tell elf-pavlik catching up on your questions of content type header for html+microformats. I don't think it makes sense. You would need headers for html+rdfa+mf2, html+mf2, html+rdfa, html+... and every other format that ever gets made. Its not at all sustainable or desirable
Loqielf-pavlik: ben_thatmustbeme left you a message 57 seconds ago: catching up on your questions of content type header for html+microformats. I don't think it makes sense. You would need headers for html+rdfa+mf2, html+mf2, html+rdfa, html+... and every other format that ever gets made. Its not at all sustainable or desirable http://indiewebcamp.com/irc/2015-05-03/line/1430660777073
aaronpk!tell benwerd you should consider a fixed-reference paging mechanism for Known, I was searching google for a photo and of course now that you added photos, offset=489 has a totally different set of photos now
aaronpkbut if all my website does is render microformats feeds, accept webmentions, and expose a micropub endpoint, I don't see why using someone else's reader to read and write to my site is a problem
AcidNerdstill wondering how this reader part will be "live" under Known or WP, but i love the idea, if only i could embed my own website with my current inoreader usage and push new articles i want to share directly to my site
aaronpkthe real qustionin this SWAT0 thing is the last step... does barnaby's website send webmentions to both aaron and ben? or does barnaby's website mention ben, which then sends a webmention to aaron for the update?
GWGI'm having trouble figuring out how to frame the conversation with a group of people working on a project that has just inserted hentry and hfeed around everything about why they should change that. Or how they can without breaking half of the sites that expect it.
kylewmso Known wants the ability to query Bridgy to see if a particular user is connected ... would it make sense to add microformats with a bunch of experimental properties on user pages https://www.brid.gy/facebook/12802152
GWGsnarfed: There is an option for public override. I'm defaulting to private till I work out the bugs. Like is sort of working. Categories I can do. As I said, it goes back to the question of the markup. Right now, on my site, the markup is done by the post kinds plugin. Whereas on yours, web actions would mark it up itself. That makes me think I should split display from taxonomy again, but I'm not 100% sure how to make that work
Loqitravel is a post type about plans to change locations in the future, similar to an event post about a future event, and related to exercise posts that involve changing location https://indiewebcamp.com/travel
tantekrel-muse was used initially for a few years since introduction (like mid 2000s), but in general a lot of the XFN rel values didn't get much use because they were tied to blogroll useage which itself waned over time
aaronpknow that I think about it, people started doing the rel=met thing again on twitter, but without any structure of course. around 2009-2010 I'd see a looot of tweets like "just had a great chat with @___ over coffee!"
KartikPrabhualso, I want the UI to work even if marginalia are moved and rendered server-side. WHich is why I want to separate the JS which moves marginalia to the correct place and only use CSS for the UI
tantekI fixed/improved *a ton* of storage handling when I implemented "like" posts in Falcon and am really glad I did it then as I had a fresh use-case in my head the whole time driving the cleanup of tech debt.
tantek(one of the reasons "like" posts took me so long. the other reason was all the explicit delibreately methodological up front "open design" I did on them and captured in Brainstorming on the /like page)
ben_thatmustbemeKartikPrabhu: can you possibly just use only spans and classes to make the same appearance as an ol? I would certainly recommend against changing existing markup as that can break styling.
KartikPrabhuI mean. I currently use <ol> for a list of responses. But if I make marginalia.js use that specific markup to hack around the display issues, the whole thing breaks if I decide tomorrow that my list of responses should be a div or something