julianfIn Quill -- that's you aaronpk, isn't it? -- I'm a bit in the dark about what format the 'content' field accepts. Plain text? HTML? Markdown? Whatever the micropub endpoint accepts?
Loqi[Tantek Çelik] h-entry is a simple, open format for episodic or datestamped content on the web. h-entry is often used with content intended to be syndicated, e.g. blog posts. h-entry is one of several open microformat standards suitable for embedding data in HTML/H...
aaronpkjulianf: hm sorry it's not clear. the "content" field is from h-entry. in microformats, it can be either text or HTML, buf if it's html then the value of content will be {"html":"<b>foo</b>","value":"foo"} whereas when it's plain text it's just a string
aaronpksome peoples' servers accept things like markdown or other variations of plaintext, and of course if you type markdown in quill's plaintext box and your server is expecting it, then it works fine.
julianfHuh? Not sure what "client" you refer to. In my case the writing client software was Quill, and the reading client is WordPress's HTML rendition of the post on my blog.
julianfquill.p3k.io/new is a micropub UI for composing plain text content, and quill.p3k.io/editor is a micropub UI for composing rich text content, and other UIs can do plain or rich content as they choose, right?
julianfA 3-yr research project with money and big sponsors, and an intention to build an "open-source personal networked device ... that collates, curates, and mediates access to an individual’s personal data ...".
bearmorning everyone, this is your friendly security ursine with a request that everyone on iOS update the the latest 10.1 version that dropped yesterday -- some important security fixes are in it
tanteksnarfed, yup, definitely a YMMV thing. In my experience, best not to to upgrade major (integer) versions unless there is a very specific strong positive reason you need to. Because they always break things you were depending on.
snarfedyup, it's a tradeoff of feature changes vs risk of getting hacked, losing accounts (/money), unknowingly letting your phone be part of a botnet like the one that took down Dyn the other day...
tantekalso re: the one that took down Dyn, that was cited as being IoT devices like security cameras, I didn't see any reference to phones in any of the articles I read
snarfedoh agreed. the problem is that afaik there's no 9.x that includes these fixes for 9, since apple doesn't do long term support for older ios versions
tanteksnarfed, there's no evidence these bugs were in 9. major security bugs often get introduce in integer version upgrades (another reason to avoid x.0 versions)
snarfedtantek: there's no evidence that it wasn't in 9 either :P since apple doesn't say. other ios exploits have been reverse engineered and found in old major versions, though, so there's definitely precedent.
snarfedyour stance is definitely important for security ppl to understand though. lots of people (maybe most) prioritize functionality over security. we have to figure out how to work with that and still keep software secure. we mostly don't know how to do that yet.
tantekI think a conservative security person stance here would be to insist on decimal security updates to software for the hardware lifetime of those devices.
bearit's made harder when you have some items that can be updated on their own schedule and others that are part of a bundle (like all core iOS apps/features)
tantek2. a proposal for how to minimally markup a checkin post such that the "check in" user intent is captured, with sufficient information, re-using existing formats / properties and only adding one property to h-entry, p-checkin: https://chat.indieweb.org/2016-10-24#t1477349895913000
tantekso unless someone finds any gross flaws in the reasoning of those two brainstorms, I'm going to write them on the wiki as a next step. then once they're there, will attempt some prototyping of sorts.
KartikPrabhutantek: one question, would it be better to use a more "Generic" name than "*-checkin", so that it might be reused in other things. For example "p-name" is generic enough to be used in "h-card" and also in "h-entry". Avoids proliferation of specialised properties
tantek(checkins do require something more since they have multiple pieces of information that need to be conveyed in a way that is otherwise ambiguous, e.g. photos/notes with location info)
tantekone possible interesting case of the "checking into media" thing is the checking into a live broadcast case, where it is an actual "event" as it were, with a specific time (even start / end times) and a virtual "location" (whatever channel / frequency / URL the broadcast is occuring on)
aaronpkthe venue manager can create events and when people check in at specific times, the app prompts the user to choose the event to check in to also
tantekso... to answer your question aaronpk, if we wanted to capture ALL the information, e.g. what time you checked into the movie as distinct from when the movie *started*, your p-checkin h-event would have your actual checkin time and movie theater venue, then also have a u-* (TBD) property that would link to the actual Event (movie instance) you were checking into
tanteknormally we try to re-use terms from iCalendar, however "related-to" is pretty useless, especially since the actual meaning is captured in the "reltype" param of the "related-to" property
tantekexcept that we now (and have for a while) frown upon mixing use of 'rel' and 'class' in a microformat (because it introduces sufficient confusion of when to use which attribute as to result in much more authoring confusing and bad data)
tantekso then the question is, is that too loose a use of p-location / u-location, or does it completely make sense that a "location" could be a spacetime location, and thus an h-event?