Aaron Parecki

@rhiaro that is a long list! I vote for: "Make various feeds discoverable" and IndieAuth

@chels_bar hai! Send me your email address to aaron at parecki .com! btw will you be able to make it to IndieWebCamp MIT this weekend?

The definition of properties such as content allow for HTML markup to be included. However, the spec does not require that the media type be specified. This leads to inconsistent results when the consumer doesn't know what to expect.

For example, if the "content" property *can* contain HTML, a consumer will be either stripping the HTML, sanitizing it, or displaying it directly. However, if a user enters something like "I had a great time at the View Source conference <o>", (<o> being an ascii representation of the conference logo), the consumer would need to HTML escape that before rendering it otherwise it would disappear from display. However there is no way to know whether the value is meant to be the literal text or interpreted as HTML.

Additionally, the current spec does not allow for different media types for summary and content, since the mediaType property lives next to those properties. The following example demonstrates the problem:

```
{
"@context": "http://www.w3.org/ns/activitystreams";,
"type": "Note",
"mediaType": "text/html",
"summary": "Hello <o>!",
"content": "<b>Hello &lt;o&gt;!</b>"
}
```

My suggestion is to require that string values can *only* be plaintext, and if you want to have HTML for a value, then you enclose it in an object where you can specify mediaType. This would look something like the following, I'm open to suggestions on names:

```
{
"@context": "http://www.w3.org/ns/activitystreams";,
"type": "Note",
"summary": "Plaintext summary, always HTML escaped <o> before displaying",
"content": {
"type": "Object",
"mediaType": "text/html",
"value": "<p>HTML content goes <b>here</b></p>"
}
}
```

@obensource #viewsource It's so close to my old Nerdhaus logo! <n> http://wiki.projectnerdhaus.com

@kylewm.com I'm getting really interested in private/friends-only posts as well, ever since I started posting things in the XOXO Slack more often. I'm finding these community-oriented networks allow me to say things there that I wouldn't want to post publicly. Not even so much as a privacy thing, but also just because the audiences are drastically different, people know what to expect when I say something in the #cocktails xoxo channel, and that's very different from what you'd see in the #pets channel. Great example is I don't really want to post a ton of cat pictures publicly on my site, but I do share pictures in the #pets channel!

@wctek Awesome, thanks! This is working out great so far! https://instagram.com/p/9cokcWjcnM/

@mager @wadey @schuyler @mjmalone I was able to do it in ArcGIS Online: http://arcg.is/1P04QqI Shows the % area in each zipcode for my input

@wadey @mager @schuyler @mjmalone Probably too late for that now, huh. There are some utilities at http://terraformer.io that might help

@zebel They do say it's based on "magic". I think it's triggered by any change, such as someone favoriting a photo. @FlickrAPI

...er, I mean next next weekend.

@mattgrommes Thanks again for all your help!

@turoczy @SlackHQ ...oh.... Yeah... Scrolling sidebar would be nice. Next team I add will put me over the height of my screen.

@turoczy @SlackHQ wait what? I reorder those all the time. They only save the position if you properly close the app tho.

@benwerd Wunderlist, GitHub and text files. #todo

@erikbates @kevinmarks Absolutely! They even already made a Wordpress plugin for cross-posting to @Medium! https://github.com/Medium/medium-wordpress-plugin #indieweb

@cramforce oh? Interesting! I saw that schema.org is required and assumed that Google is getting the content from there.

@kylewmahan I usually click through a couple levels up looking to see if any of the URLs up the chain show comments #indieweb

@doingweb Great meeting you too! Maybe we'll run in to each other at food cart lunch downtown soon! ;-) #PodcastDay