David Shanske to use the type indicator to display mentions as a facepile. The plugin works, but redevelopment is ongoing.
This is an automatically-generated summary of the IndieWebCamp wiki edits from October 31 through November 7, 2014
Created by David.shanske.com on November 7
Semantic Linkbacks is a WordPress plugin that upgrades the presentation of linkback notifications (like Trackback, Pingback, or Webmention*) from the ugly default pingback presentation of "[…] random text excerpt […]" to a much more meaningful and user-friendly display as comments, reposts, likes, and favorites, detected using microformats2 markup from the source of the linkback.
For explicit in-reply-to interactions, the plugin also changes the WordPress comment type to from "webmention" to "comment". Otherwise, it creates human readable whole sentences like "Alice liked this article on alice.example.com." with hyperlinks to the source author and permalink.
For in-reply-to interactions, the plugin adds a "type" indicator in the comment metadata for the specific type of interaction:
This "type" indicator enables further interaction-specific presentation customization, such showing likes/favorites and/or reposts as a facepile.
*WordPress supports Pingback and Trackback by default; for Webmention support, you must install the separate Webmention Plugin which is very nicely complementary to the Semantic Linkbacks plugin.
David Shanske to use the type indicator to display mentions as a facepile. The plugin works, but redevelopment is ongoing.
Created by Tantek.com on November 7
This article is a stub. You can help the IndieWebCamp wiki by expanding it.
User interface, often abbreviated as UI, formerly called human interface (HI), refers to presentational and interactive design elements of potentially any tool, but usually electronic tools, specifically their hardware and/or software.
A user interface is also often referred to in context simply as an interface, or implied when used as a compound noun with some user-level concept or object, e.g.:
Created by David.shanske.com on November 7
The WordPress Outreach Committee is a group of active Indiewebcamp participants who reach out to individuals already running WordPress to add Indieweb functionality to their existing sites. This would include people who have actively requested assistance in converting as well as people who might be amenable to the suggestion.
Looking for help? Try one of the people below.
David Shanske, ...
Created by Tantek.com on November 7
This article is a stub. You can help the IndieWebCamp wiki by expanding it.
Jux was a content hosting silo that specialized in allowing users to publish slideshows and other multimedia that mixed text with photos and videos.
Jux was hosted at jux.com.
[1] 2014-11-30: expected shutdown of Jux.com per 2014-11-05 GigaOM: Personal media publishing platform Jux.com is shutting down by the end of the month
Created by David.shanske.com on November 3
| If you have a personal site | If you want a personal site |
|---|---|
| Are you a Creator (create & share design, UI/UX, and/or code)? Either: add yourself to the guest list by Logging in with your own domain, or Publish a post saying that you're coming with a link to this RSVP page and send a pingback to it. | If you're in the process of setting up your personal site, or don’t have a personal site but want one, or want to create and contribute to the IndieWeb but don't know where to start, you’re still very welcome! Find a creator (either listed below, or ask on IRC) to team up with and ask them to add you as their apprentice. Then get your site setup with IndieAuth and edit your entry! |
Curious about attending? See what happened at the main IndieWebCamp 2014 in June!
Alphabetically sorted by full display name.
Name: Ben Roberts
IndieWeb Projects: https://github.com/dissolve/openblog
Personal URL: http://ben.thatmustbe.me
Elsewhere: @dissolve333
Name: David Shanske
IndieWeb Projects:
Personal URL: https://david.shanske.com
Elsewhere: @dshanske
Name: Your Name
IndieWeb Projects:
Personal URL: your domain
Elsewhere: @yourname
Apprentices, add yourselves with your name, personal URL (if any), Creator, more info. Alphabetically sorted by given name.
Folks that can't make it
No one is listed yet. Add yourself to the list using the attendee template!
Sorry to miss you folks - hopefully you can make it next year!
No one is listed yet. Add to the list using the attendee template
Created by Tantek.com on November 7
This article is a stub. You can help the IndieWebCamp wiki by expanding it.
User experience, often abbreviated as UX, refers to the total experience a user has with a tool, or even an entire company, across all methods of communication and interaction with that tool, including both direct interactions using a tool UI and indirect interactions via other tools such as email, SMS, phone calls, in-person human representatives of the tool or company, etc.
Created by Tantek.com on November 1
You're here because you recently accessed a wifi network with a captive portal and it used a relative redirect to send you to this page, which your browser remembered and then reloaded after you switched to another wifi network.
Go back in your browser history and reclick the link you clicked before.
If you got here from using a bookmark, select the bookmark again and it should now work.
Created by Tantek.com on November 7
This article is a stub. You can help the IndieWebCamp wiki by expanding it.
Interface most often refers to user-interface in the context of the IndieWeb, since we're a user-centric / design-centric / UX before protocols&formats principles crowd.
Less often, use of "interface" may sometimes refer to "application programming interface" AKA API.
Created by Aaronparecki.com on November 7
Contents |
Q: should a markdown-based client send the "content" field as markdown or rendered html? If the latter, should it send an auxiliary field with the raw markdown?
Aaron Parecki points out that this will not be very useful without the ability to fetch raw content, and resubmit an edited version (which will mean expanding the spec significantly)
Goal: if Aaron is reading Barnaby's website, create an inline comment form on Barnaby's site that can post a comment directly to Aaron's website.
If Aaron's site supports Micropub, Aaron's browser (or Barnaby's server) could make a Micropub request with the contents of the comment form directly to Aaron's website. However, Aaron cannot trust either Barnaby's comment form (it could have malicious hidden properties or change the request before submitting) or Barnaby's server.
Rather than Aaron's server issuing an access token to Barnaby's server (which essentially would allow Barnaby's server to post content on Aaron's site as Aaron), "trust-less Micropub" describes a way to support posting content via Micropub without granting full access to the third party client.
1. Aaron is reading a post on Barnaby's website and wants to comment. He fills out the comment form and clicks the "sign in to post" button.
TODO: screenshot mockup
2. Barnaby's site begins the IndieAuth "authentication" flow to discover Aaron's website and his micropub endpoint. The request only includes the "comment" (or maybe "preview"?) scope value, and not the "post" scope, since Barnaby's site is merely trying to identify Aaron, not obtain authorization to act as him.
TODO: screenshot mockup
3. After successfully signing in, Barnaby's server now has an access token for Aaron's site and knows his Micropub endpoint.
4. When Aaron submits the comment form, Barnaby's server (or Aaron's browser, it's equivalent) makes a POST request to Aaron's Micropub endpoint containing the following:
5. Rather than immediately posting the comment, Aaron's browser is directed to Aaron's own website with a token in the URL corresponding to the comment request. Aaron's website authenticates Aaron however it wants, and displays the request of the action Barnaby's website is trying to take. This may look something like the following:
TODO: screenshot mockup
6. After Aaron approves the request, his server posts the comment and then redirects his browser to the redirect URI specified in the original request, taking him back to Barnaby's post.
See the original IRC discussion.
An alternative to indie-config for discovering the user's action handler URLs. This method does not require a JavaScript or a custom schema handler to be registered in the browser, but it does require the user to support micropub and be signed in on the site they are browsing.
It would be nice to have multiple in-reply-to links posted in micropub. With tags and syndicate-to, the values are given as a comma separated list. However, "," is a valid URL character and even given as examples in [1]. This could potentially be a problem for syndicate-to as well. POST methods already have a standard for passing arrays of values. Perhaps we should be using those.
PHP requires "[]" characters in the parameter name to be parsed as an array. Other languages (at least Python) do not, but it would probably make sense to make the [] part of the spec so that PHP implementations don't have to do their own special parsing. Kylewm.com
Currently there is no field to specify delete. Updates are implied by existance of a url= field. Updates to content and adding a syndicate-to link simultaneously are not possible as it would be interpreted as syndication text. I suggest we add a field to specify the CRUD operation. Postly uses operation='create', operation='edit', operation='delete', and operation='undelete' (since deleting just removes from public view).
Because handling arrays in form encoded POST requests is somewhat under defined, it may be nice to consider allowing a system similar to http://www.w3.org/TR/html-json-forms/ before json forms are adopted for browsers.
Right now a number of clients/endpoints support arrays in micropub post requests through the use of a csv fields. This requires parsing of the form-encoded body, then further parsing the field values as CSV -> Array. Most parsers support the notion of a form based array by appending [] to the end of keys that make up the array. Supporting this would eliminate the extra step of parsing csv fields assuming everyone has access to a form-encoding parser that can support this.
Created by Tantek.com on November 7
This article is a stub. You can help the IndieWebCamp wiki by expanding it.
A posting interface is a user interface for creating posts, typically on your own website.
See create for IndieWeb Examples of posting interfaces.
