IndieWebCamp January 9-16, 2015

This is an automatically-generated summary of the IndieWebCamp wiki edits from January 9-16, 2015

Table of Contents

New Pages

Changed Pages

New Pages

followers you know

Created by on January 13

Followers you know (sometimes ambiguously called followed by) is a Twitter feature shown on user profile pages when logged in that displays both a number and a sampling of users you follow who follow the profile you are viewing.


Silo Examples


Examples of "Followers you know" in the Twitter UI.

Twitter pop-up profile


Pop-up profile preview, note highlighted "Followed by ", then names of (up to) 3 of those followers, then "and 89 others", all of the text preceded by (up to) 4 of those followers (in icon form).

Twitter full profile


Full profile view, note "92 Followers you know" with (up to) 10 of those followers (in icon form).

See Also

Created by on January 14

Come to the land of Buddha.


Created by on January 13

  • Tue, January 13 stub with dfn, statement of intent with an example, see also
  • Tue, January 13 /* Kyle Mahan */ links for twitter-atom and instagram-atom
  • Tue, January 13 /* Kyle Mahan */ add titles for *-atom links

app quits are public statements by individuals announcing they have publicly quit using (and uninstalled/deleted) specific (often "native mobile") apps (typically silo owned or created) either with intended permanence, or temporarily.

Statements of intent

Kyle Mahan

Kyle Mahan “that much closer to taking instagram and twitter apps off my phone \o/”[1]

See Also


Created by on January 12

  • Mon, January 12 Created page with "<dfn>[ Pushover]</dfn> makes it easy to get real-time notifications on Android, iOS, and desktop systems. Pushover offers a simple ["
  • Tue, January 13 add IndieWeb examples section
  • Wed, January 14 /* IndieWeb Examples */ adding barryf

Pushover makes it easy to get real-time notifications on Android, iOS, and desktop systems.

Pushover offers a simple API.

IndieWeb Examples

  • David Shanske uses Pushover to receive webmention and IRC notifications
  • Barry Frost uses Pushover to notify him of webmentions (including unsuccessful webmention attempts)
  • Kyle Mahan added support for sending Pushover notifcations when webmentions are received in Red Wind.


Pushover offers a free five-day trial. After that, it costs a one-time license fee, currently $4.99 to purchase the app for your platform. Once the app is purchased for the platform, it can be used on unlimited devices.

Each application registered to Pushover can send 7500 messages per month for free, which is sufficient for most personal uses.

For high-volume applications that need to send more than 7,500 messages per month, additional capacity can be purchased (currently 10,000 for $50.00 USD, 25,000 for $115.00 USD, 50,000 for $225.00 USD). Once an application uses its free allowance, subsequent messages will start deducting from its purchased reserve until the first of the next month.


Created by on January 16

Itches, in the context of the indieweb, are individuals's personal sources of annoyances using the web or in particular their own website, that they use to itemize and prioritize what to create, design, build, and improve on their own website, often by first listing such "itches" on a section in their User: page.



The focus on scratching your own itches was one of the motivations for founding IndieWebCamp.

Listing itches on your User: page is a key step in wikifying and keeping yourself focused on what you care about, rather than being distracted by the latest Twitter drama.


Collect Itches on your User: page in an == Itches == section.

When you start collecting lots of itches, you may want to start prioritizing them, especially by what you're currently working on. Start a "Working on" section for that:

== Working On ==
* the next thing I'm working on
* the next next thing I'm working on
* ... etc.

IndieWeb Examples

Examples of IndieWeb community members's itches documentation (feel free to add your own)

See Also


Created by on January 12


Homebrew Website Club Meetup




- – Homebrew Website Club broadcast & peer-to-peer meetup & beforehand:

• optional 17:30-18:30 – quiet writing hour for the venues that explicitly have it.

All times are Pacific Time unless otherwise noted in venues.


San Francisco




The Living Room, 2423 W North Ave., Chicago, IL
Note the Chicago meeting is at 19:00 CDT


new! 17:30-18:30 Quiet writing hour before the meetup. Come on by to blog or do other writing quietly.

Homebrew Website Club Meetup: Are you building your own website? Indie reader? Personal publishing web app? Or some other digital magic-cloud proxy? If so, come on by and join a gathering of people with likeminded interests. Bring your friends that want to start a personal web site. Exchange information, swap ideas, talk shop, help work on a project...

See the Homebrew Website Club Newsletter Volume 1 Issue 1 for a description of the first meeting.


San Francisco:

  • add indieevent...
  • ... and POSSE copy


  • add indieevent...
  • ... and POSSE copy


  • add indieevent...
  • ... and POSSE copy


Optional RSVP - just show up! You're encouraged to RSVP by any or all of:

  • adding your name below (and indicate parenthetically if you're in for writing hour)
  • sending an indie RSVP to the respective indie event listed above for your location,
  • RSVPing on its POSSE copy on Facebook (also linked above)

Or just show up and say hi! We're a friendly bunch. You may also RSVP after attending.

San Francisco:

  • ... add yourself!


  • ... add yourself!


  • ... add yourself!


San Francisco

  • ...


  • ...


  • ...

Blog posts

Blog posts before the meeting:

  • ...


  • ...
Homebrew Website Club
2015 02-1101-2801-14
2014 12-1712-0311-1911-0510-2210-0809-2409-1008-2708-1307-3007-1607-0206-1806-0405-2105-0704-2304-0903-2603-1903-1202-2602-1201-2901-15
2013 12-1812-0411-20


Created by on January 12

  • Mon, January 12 Created page with "<span class="h-card" style="white-space:nowrap">{{sparkline|}} [[|Matthew Levine]]</span>"

Matthew Levine


Created by on January 13

Barry Frost


Created by on January 13

Websocket is a full-duplex single socket connection over which messages can be sent between client and server. Websocket is designed to be used instead of Comet, Ajax or other long-polling techniques.

See Also


Created by on January 12

  • Mon, January 12 Created page with "<dfn>[ Pushbullet]</dfn> is a free service that sends rich notifications to your Android or iOS device, as well as various web browsers. The service is..."

Pushbullet is a free service that sends rich notifications to your Android or iOS device, as well as various web browsers.

The service is currently free for all users and developers and offers an API for development. Premium services are planned for the future.


Created by user:danlyke on January 15

  • Thu, January 15 user:danlyke Adding template for Dan Lyke

Dan Lyke


Created by on January 15

This is the planning page for IndieWebCamp Edinburgh 2015, one of several 2015 IndieWebCamps.

Tentative dates:

  • Weekend: ...
  • Weekdays: Week commencing 20th July.





If you're interested, especially if you can make the dates above, please add yourself!

Once we've confirmed the dates and venue, we we'll move this section to an official 2015/Edinburgh/Guest_List.


Session ideas

(Just ideas, no committments here; +1 if you're interested!)

Co-located events

See Also


Created by on January 15

Emma Kuo


Created by on January 15

Barnaby Walters


Created by on January 16

POSSE독립 사이트를 만들어 한번에 전파하자-Publish (on your) Own Site, Syndicate Elsewhere라는 뜻의 약어입니다. 이는 여러분이 소유한 자체 도메인에 먼저 콘텐츠를 올리고, 이를 다른 외부 서비스로 전파하여 원래 콘텐츠 사이트로 돌아오게 하는 전파 모델에 기반합니다.

POSSE 모델에 의하면 여러분의 친구가 다른 소셜 네트워크를 사용하더라도 (Facebook, Twitter, 등) 여러분의 글을 쉽게 받을 수 있습니다.

이는 "IndieWeb" 운동이 "모든 사람이 자신의 사이트에 블로그를 하자" 혹은 "모든 사람이 StatusNet/Diaspora와 같은 소셜 네트워크를 구축하자"와 확연히 다른 접근입니다.

POSSE는 실제로 웹 사이트 연합 보다 좀 더 중요합니다. POSSE는 앞으로 미래에 연락 하게될 사람과 커뮤니케이션하는 것 보다는 현재 활동중인 친구와 지금 연결하는 게 더 중요합니다. 물론 소셜 네트워크 연합 방식이 POSSE보다 더 빠르게 적용이 되더라도 더 많은 사람들이 연결 될 수 있는 장점이 있습니다.


IndieWeb 예제

아래 IndieWebCamp 참여자들은 POSSE 구조를 지원하는 웹 사이트를 가지고 있습니다. 직접 구현이 완료되었다면 스크린샷을 만들어서 올리시거나 해주시기 바랍니다.

Tantek as of 2010-01-01[1] (2010-01-26 Twitter syndication started[2] and caught up[3][4]). Tantek Çelik implemented POSSE in Falcon on

  • all self-hosted posts (notes, articles, etc.) are openly PuSH+Atom real-time syndicated with a PubsubHubbub hub to Google Buzz, StatusNet, etc.
  • notes (and article titles) are snowflake copied by the personal site server to Twitter with permashortlink citation links/references (see Whistle for details) back to the original. Copies of notes to Twitter are also automatically recopied from there to Facebook.

Barnaby Walters as of 2012-03-12. Barnaby Walters implemented POSSE over at

  • as of 2012-09-25 all collections (notes, articles, activity) are PuSH-subscribable feeds.
  • Using the Client to Server to 3rd Parties flow 06:08, 25 September 2012 (PDT)
  • Syndicating to Twitter + Facebook
  • As of 2014-06-19 Taproot can now optionally post additional POSSE tweets when updating a note or article — example of updated note and POSSE tweet for the update. Note that Bridgy successfully backfeeds silo interactions from the update tweet as well as the original POSSE tweet

Brennan Novak as of 2012-07-01[5][6]. Brennan Novak implemented POSSE on his site with copies posted to Twitter and Facebook

Aaron Parecki as of 2012-08-19[7][8]. Aaron Parecki implemented POSSE on his site with copies posted to Twitter containing permashortlinks back to originals on his own site.

Sandeep Shetty First post POSSE'd on 2012-11-05. I primarily syndicate to Twitter using a very lo-fi solution of adding silo (Facebook, Twiiter, Google+) provided share links to each post that I can manually click to prefill content, edit and post. I've avoided API integration because of the extensive experience I've had using Facebook API and dealing with it's random changes. "Integration" has high costs sometimes so I keep it as simple as possible.

Ben Werdmuller as of 2013-05-31 [9]. Ben Werdmuller implemented POSSE in his idno platform via plugins. New content has an associated Activity Streams object type; POSSE plugins listen for post events associated with those object types and syndicate appropriately.

  • Notes and articles are syndicated to Twitter and Facebook
  • Images are syndicated to Facebook, Flickr and Twitter
  • Places are syndicated to Foursquare
  • More plugins are very easily possible; the Foursquare plugin took about an hour to build

Shane Becker - need to copy example from rel-syndication page

Glenn Jones as of 2014-01-14 Glenn Jones The blog implemented POSSE using a new version of system. New content added to transmat is associated with objects types. A POSSE twitter plugins listens for post events syndicating content. At moment only notes are syndicated.

Jeremy Keith as of 2014-05-27 Jeremy Keith has implemented POSSE using his own custom CMS.

Shane Hudson as of 2014-09-19 Shane Hudson has implemented POSSE to Twitter for Craft CMS.

  • Previously working on Wordpress but he was not keen on the UX.
  • Has reply contexts working but has to manually copy the ID.
  • Not yet POSSEing photos but plans to.
  • Currently he has to manually copy the tweet from the main text box to a 140 character limit tweet text box. He plans to make that automatic.

기타 한국어 사이트

여러분이 만든 POSSE 지원 사이트를 모아서 아래에 올려 주시기 바랍니다.

부분적인 POSSE 사이트

아래 사이트는 POSSE 기능 일부를 지원하고 있습니다.

  • implements a partial POSSE with the following setups:
    • SNSAPI is a lightweight middleware to unify the data structure and interfaces of different social networking services. It gives the scripting flexibility for developer users to manipulate social silos.
    • SNSRouter is a web UI built upon SNSAPI where one can read an aggregated timeline from different sites, mass forward messages, and update statuses on all channels.
    • Part of my daily usage is to go to my running SNSRouter, read messages and update statuses on it. The new status is written to the RSS feeds, , and other silos. ( This feed is indeed a mix of POSSE PESOS )
    • As is said in one of the description paragraph above, this model is not truly POSSE. One can not (hardly) distinguish original/ syndicated status. I'm planning to put a page with permlink on my site upon each status update and then use SNSAPI to syndicate to other silos.

다른 접근 방식


A similar but opposite approach is PESOS where content is posted first to 3rd party services and then copied/syndicated into a personal site.

If exact copies of content are posted on both a personal site and 3rd party services, there's no way to tell (short of comparing possibly non-existent sub-second accurate published dates) whether a site is using POSSE or PESOS. Sites can provably support POSSE by including perma(short)links in syndicated copies that link/reference back to published originals.


PESETAS is like PESOS but copying/syndicating everything to a particular silo (without any involvement of a personal site).

For example, most silos support cross-posting to Twitter, thus you could connect everything to your Twitter account and always (auto-)cross-post there to keep a copy.

E.g. Tumblr has a UI for cross-posting to Twitter. See Webapps StackExchange post for documentation and screenshots of UI.

Tumblr is a better PESETAS destination however, since it is well established, allows for a wider variety of content, and allows more text, and links to URLs directly instead of linkwrapping them like Twitter does.


POSSE is considered a robust and preferable syndication model for the following reasons:

  • Ownership. By posting first on your own site, you create a direct ownership chain that can be traced back to you without any intervening 3rd party services (silos) TOS's getting in the way (which is a vulnerability of PESOS).
  • Reduce 3rd party dependence. By posting directly to your own site, you're not dependent on 3rd Party services to do so -- if you can access your site, you can publish your content
  • Own canonical URLs to your content. Canonical URLs to your content are on your domain.
  • Copies can cite the original. By posting content first to your own site (and thus creating a permalink for it), copies that you post on 3rd Party services can link or cite the original on your site (see syndication_formats and POSSE Notes to Twitter)
  • Discovery of your original content. discovery of your original content from the copies on 3rd party services is enabled by the permashortlinks to your originals posted on said services
  • Better search. Searching public content on your own domain (with any web search engine of your choice) works better than depending on Twitter exclusively to search your tweets.[10]. And when the copies link to your original posts, search engines figure that out by following those links back to the original and ranking it higher.
  • backfeed can be used to pull in (reverse syndicate) responses from other services
  • allows taking advantage of other services' social layers and aggregation features while storing the canonical copy of your content on your own site
  • ...

How To Implement

There is no one POSSE implementation technique, you have to implement it per silo destination.

In general, when your content posting software posts something, it should also post a copy to the silo destinations of your choice, with a permashortlink (or permashortcitation) back to your original.

The details of how to do so vary per destination. See the sections below.

POSSE Destinations


Twitter is perhaps the most popular POSSE destination and a good place to start.

If you can start posting notes (tweets) to your own site and POSSEing to Twitter, instead of posting directly to Twitter, you have taken a big step towards owning your data.


  • API Access - posting new tweets works nicely due to permanent API tokens, and the return value contains a URL to the posted
  • Supports very complete web action endpoints, so semi-manual posting is easy to implement

See POSSE to Twitter for details on how to POSSE both notes and articles (blog posts) to Twitter.


Main article: POSSE to Facebook
  • API Access - New posts can be created through the API using the Publishing API
  • A web action endpoint ( is supplied by the Feed social plugin for semi-manual posting. Requires a facebook app id, but no authentication. It accepts a callback URL, to which it redirects with ?post_id GET param set, from which a URL can be constructed.

Google Plus

Main article: Google+#POSSE


Main article: Medium
  • how does do it? (all his articles are POSSEd to Medium)


Main article: WordPress
  • how does do it? (all his articles are POSSEd to WordPress)

Plain Text Notes

Some destinations (e.g. SMS or push notifications) may require a pure plain text representation.

Software Libraries

  • PHP
    • The POSSE namespace in php-helpers (might be moved to a separate package) contains various truncation, preparation and syndication functions including HTML => plaintext µblog syntax converter

Publishing Flows

There's at least two ways to implement a POSSE content posting flow:

Client to Own Domain to 3rd Party Services

  • The user writes a piece of content using a publishing client
    • Optional: client provides UI for selecting which 3rd party services to push to if it knows about them, with optional customizations for per service
  • Having finished the content, the user publishes content to their server (optionally: with metadata of which 3rd party services and any customizations thereof)
    • Optional: client can generate a permalink knowing the state of the server, and publish to that permalink
  • The server publishes the content, generates a permalink and summary (and/or customized content suited to 3rd party services) if necessary
  • The server posts copies with permalinks to 3rd party services


  • User only has to interact with one site over the internet, their own
  • Syndication can be done fully automatically by the server


  • any?

Client to Own Domain and 3rd Party Services

  • The user writes a piece of content using a publishing client
  • Having finished the content, the user publishes it to their server
  • The client queries the server for the URL of the content it just pushed
  • The publishing client presents the user with an interface for selecting:
    • Which 3rd party services to publish to
    • The exact content published to the services, pre-filled with a summary based on the produced content
  • The user selects the services and submits the form
  • The publishing client posts the content summaries out to the 3rd party services


  • More user control over timing and editing of copies of content to 3rd party services


  • Syndication requires a manual step each time
  • Dependent on client connectivity directly to 3rd party services (problematic in flakey mobile situations, or when client is publishing using domain-censored internet access).


All of the above, and to date (2013-222), POSSE has solely described syndicating the Creation of content on your site (publishing) to other sites. This model has been quite successful and perhaps may be sufficient.

However, it is worth exploring the potential utility of a full CRUD protocol for POSSE.


Create is the POSSE default. You create content on your site, you POSSE your creates to other sites. All of this is described above, and in silo-specific details on silo pages.


Read as a verb is interesting when applied to POSSE.

At a minimum, it's useful to implement storing links to syndicated copies of your content to provide for the future possibility of reading from downstream POSSE copies.


Actual direct uses of Reading from downstream POSSE copies:

In addition, keeping a rel-syndication link to the POSSE copy enables deleting it to perform an Update or a Delete action, as described in the following sections.


If a downstream service allows updates/edits, then when you edit your post, you could propagate that update to the downstream POSSE copy as well. (Any existing POSSE destinations that allow this?)

It would be possible to POSSE updates to Twitter (or any other silo that disallows edits to posts) by deleting the POSSE tweet and reposting.

Consider only POSSEing updates to Twitter:

  • if no one has replied to it yet (otherwise you'd break a threaded conversation on Twitter)
  • if your changes would be shown in the truncated copy on Twitter (i.e. if your changes are past the 140 (more like 120) character horizon, no point in churning the Twitter copy).
  • within a very short time window, maybe like 2-5 minutes, because otherwise the update will be seen as a duplicate to people who are reading you on Twitter.

All of these concerns are regarding the experience that you provide to your friends reading your tweets on Twitter, which of course should be the whole (design) reason you're bothering to POSSE to Twitter in the first place.


Deletes seem fairly straightforward to POSSE, especially to services which themselves propagate deletes to clients.

E.g. one can delete a note on Twitter at any point.

Similar to updates, consider:

  • if there are already replies to a POSSE copy (or activity like favorites/retweets), consider keeping it to keep conversation threading (and others' favorites/retweets).

However, if you really feel like deleting the content from your site and POSSE copies (e.g. on Twitter), go ahead and do so.

Perhaps this is an opportunity for the UI for the deletion of a post to check to see if there's been any activity (replies, favorites, retweets) on the POSSE copy before performing the delete. One possible implementation could involve the UI informing the user of this activity (or lack of it) and reconfirming the delete request on a per-service basis.


Worry about search engines and duplicates

Q: Do we need to worry about search engines penalizing apparently duplicate posts?

A: That's why the POSSE copies SHOULD always link back to the originals. So that search engines can infer that the copies are just copies. Ideally POSSE copies on silos should use rel-canonical to link back to the originals, but even without explicit rel-canonical, the explicit link back to the original is a strong hint that it is an original.

This is also an advantage of POSSE over PESOS. With PESOS - there's no way to tell what's the original and what's the copy - so they do look like duplicates.

POSSE-post-discovery and backlinks

Q: can use posse-post-discovery to find the relationship between a syndicated post and the original when there is not explicit link. Does this mean I should stop adding backlinks to syndicated copies?

A: POSSEing without a backlink is considered a last resort, and has some costs associated with it. See posse-post-discovery#Tradeoffs for more details.


Related conceptually:

  • sometime before 2014-06-21[11]: POSE (Publish Once Syndicate Everywhere) term defined at some point prior to POSSE. Conceptually it was looser than POSSE, as "once" could be interpreted as on a silo rather than your "own site", which POSSE (and the conceptual predecessors) made explicit.


Articles and blog posts about POSSE, especially implementing it:

See Also



Created by on January 15

Ben Roberts

sticky content

Created by on January 15

  • Thu, January 15 stub with dfn, see also, different from sticky post

Sticky content refers to the practice of deliberate website content creation (and design) to motivate readers of a website (often commercial and/or ad-driven, such as many silos) to hold readers's attention (hence sticky), for increasing amounts of time, and to return (frequently).

Similarly named, but different in meaning, a "sticky post" is another way of saying pinned post.

See Also


Created by on January 13

A Task Queue is a method used to distribute work across machines or threads by defining a FIFO queue of work to be done.

See Also

Changed Pages


9 edits by,,
  • Mon, January 12 /* IndieWeb Examples */
  • Mon, January 12 /* More building blocks */
  • Mon, January 12 /* Getting started with Wordpress */
  • Mon, January 12 /* Adding Indieweb Support/Elements to a Wordpress Site */
  • Mon, January 12 /* Adding Indieweb Support/Elements to a Wordpress Site */
  • Mon, January 12 /* Spam/Comment Protection */
  • Tue, January 13 /* POSSE to WordPress */ expand with explicit POSSE reply to WordPress
  • Tue, January 13 /* POSSE reply to WordPress */ add my example
  • Wed, January 14 /* hosting service */ main, note content needs to be incorporated into the [[]] stub


8 edits by,, user:danlyke,,
  • Thu, January 15 move why to top, clean up a bit, add levels, add new client side search section with possible how to
  • Thu, January 15 /* IndieWeb Examples */ add myself
  • Thu, January 15 user:danlyke Added search implementations by danlyke
  • Thu, January 15 /* IndieWeb Examples */ add myself
  • Thu, January 15 /* search box - level 2 */ clarify time ordering is part of level 2
  • Thu, January 15 user:danlyke /* IndieWeb Examples */ danlyke bragging about how long his site has had locally hosted search
  • Thu, January 15 /* Ben Roberts */ add date
  • Fri, January 16 /* Kyle Mahan */

7 edits by,,
  • Tue, January 13 expanding with explanation that != indieweb
  • Tue, January 13 /* is not IndieWeb / IndieWebCamp */ pointing people to what we are doing.
  • Tue, January 13 adding a section on planned products
  • Tue, January 13 changing to history
  • Tue, January 13 /* History */ no need for the repetition
  • Tue, January 13 citation needed and Undo revision 16627 by [[Special:Contributions/|]] ([[User|talk]])
  • Tue, January 13 /* History */ add some citations

7 edits by


5 edits by,,,


5 edits by,
  • Thu, January 15 move past event to 2015 section, add 2015-02-28 event, strike Portland, Chicago from tonight
  • Thu, January 15 /* Upcoming */
  • Thu, January 15 IWC Brighton - renaming IWC UK now that we have Edinburgh!
  • Thu, January 15 move last night's HWC to recent
  • Thu, January 15 add Social Web WG Face to Face Meeting at MIT (F2F2)


5 edits by,,


4 edits by
  • Thu, January 15 /* Why */ expand Publishing integrity with detail about requiring HTTPS, add Reduce carrier level tracking e.g. Verizon X-UIDH
  • Thu, January 15 /* Why */ add separate secure link to check
  • Thu, January 15 /* Why */ make the test call-to-action more explicitly visible
  • Thu, January 15 /* Why */ add zombie cookie article for another reference

image proxy

3 edits by,,


3 edits by


3 edits by,


3 edits by,
  • Sat, January 10 /* See Also */ add articles about, what is your (post)
  • Sat, January 10 /* Additional 2015-01 launches */ colintedford improved archive pages
  • Thu, January 15 /* Additional 2015-01 launches */ colintedford enabled shortlinks


2 edits by


2 edits by,


2 edits by,
  • Mon, January 12 add kylewm with specific date, others dates unconfirmed, or note PESOS
  • Mon, January 12 Adding myself to bookmark examples


2 edits by


2 edits by
  • Mon, January 12 add dfn, restructure to why, how, subheadings for various clusters, friendly services
  • Thu, January 15 /* Friendly Services */ add a stub for withknown


2 edits by
  • Sun, January 11 add myself to indieweb examples, add some design steps for further clustering of adjacent likes of the same person's stuff
  • Mon, January 12 /* Brainstorming */ source clustering with additional authorship connection information


2 edits by
  • Thu, January 15 /* Feeds */ add detail of using Google's appspot PuSH hub
  • Thu, January 15 /* Itches */ re-order a bit, add client side search


2 edits by
  • Mon, January 12 /* Kinds of Posts */ emojicons for a few more post kinds, re-order and cluster by apparent indieweb examples, note two only or one only
  • Mon, January 12 /* Kinds of Posts */ adjust order since more folks posting bookmarks


2 edits by
  • Sat, January 10 /* Markup */ use u-in-reply-to h-cite in anticipation of microformats2 parsing changes
  • Sat, January 10 /* Markup */ u-in-reply-to h-cite


2 edits by
  • Fri, January 9 Background - Tim Bray used sharecropper in reference to building apps for a proprietary platform instead of the web
  • Fri, January 9 document history of use of the term sharecropper in reference to the web. modern definition started with Shane Becker's usage AFAIK. citations provided.

1 edits by


1 edits by
  • Tue, January 13 /* Twitter */ add another attempted multi-reply tweet that's kind of like a follow-up + reply to another tweet


1 edits by

own your data

1 edits by


1 edits by
  • Mon, January 12 use case, Connecting Authors As One, to (further) cluster like posts


1 edits by
  • Mon, January 12 tweak emojicon to indicate the output - a note - instead of the process - writing

domain name registrar

1 edits by
  • Mon, January 12 /* Registrars */ add info about privacy protection


1 edits by


1 edits by
  • Mon, January 12 explicit p-summary, explicitly include identity as part of ownership


1 edits by


1 edits by
  • Thu, January 15 add explicit search requirements to Level 3 and Level 4, thoughts on what Level 5 search could be


1 edits by


1 edits by


1 edits by
  • Fri, January 16 issues, hierarchical vulnerability, unreliability. FAQ needs fixing

Main Page

1 edits by


1 edits by
  • Thu, January 15 clarify Camridge MA, split UK into Edinburgh and Brighton!

IRC People

1 edits by


1 edits by
  • Tue, January 13 /* Features */ add "followers you know" and red link a few others


1 edits by

2015/Germany/Guest List

1 edits by


1 edits by

1 edits by

1 edits by


1 edits by
  • Wed, January 14 linky, add issues section with feature request for microformats2, features section to cluster a couple of items, see also