IndieWebCamp October 17-24, 2014

This is an automatically-generated summary of the IndieWebCamp wiki edits from October 17-24, 2014

Table of Contents

New Pages

Changed Pages

New Pages

mp-config

Created by Ben.thatmustbe.me on October 20




mp-config is a method of using a query to a micropub endpoint to allow you indie website to discover user support for webactions.

Contents

Detail

mp-config provides a server-side 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.

Along the same lines as micropub#Discovering_Supported_Syndication_Targets, external sites could query the micropub endpoint for a list of action handler URLs.

1. Aaron signs in to Barnaby's site with the "config" scope.

2. Barnaby's site issues a GET request to Aaron's micropub endpoint, which replies with a url-encoded list of actions and their associated handler URL

GET /micropub_endpoint?q=actions
Authorization: Bearer xxxxxxxxx

reply=http://aaron.com/reply?u={url}&repost=http://aaron.com/repost?u={url}

3. When Barnaby renders indie-action elements, he substitutes Aaron's configured action handlers for Twitter intent URLs or whatever fallback he would normally use.

IndieWeb Examples

  • Kyle Mahan Supports mp-config on https://kylewm.com as of 2014-10-19. When a micropub-enabled user signs in, kylewm.com will use their /micropub?q=config endpoint to determine web action handlers, that are used in place of Reply/Repost/Like indie-actions on each post permalink page.
  • Ben Roberts Supports mp-config on ben.thatmustbe.me as of 2014-10-20. This will add Like, Reply, Repost, and Bookmark actions if available. It will also offer Edit and Delete on any post comments owned by the user.

Brainstorming

Response format

Micropub in general uses application/x-www-urlencoded to pass information back and forth. Some implementers prefer to return action -> URLs as a JSON object. Kyle Mahan will currently handle either one based on the value of the Content-Type header.

Authorization not needed to get list

There is no real secure information given in the list of endpoints. In fact you want this to be as readily available as possible. As such I think the Auth header on the request to q=actions should be dropped. - Ben Roberts

  • I tend to agree. The only reason I can think of that a micropub access-token might be necessary is if someone has "secret" admin URLs (i.e. instead of a real authorization mechanism). Does anyone do this? If so, do we care about supporting it? Kylewm.com 21:43, 20 October 2014 (PDT)
    • If authorization isn't necessary, it makes me wonder if this isn't really micropub at all. A <link rel="indie_config"> would work just as well and would be a much lower bar for most sites to implement Kylewm.com 21:43, 20 October 2014 (PDT)

Micropub endpoint as indie-config page

Rather than have a separate config for indie config Ben Roberts queries ?q=indie-config to pull up configs formatted for use with [indie-config]

Micropub configuring of list

In order to modify the list and allow different micropub clients to act for different actions, we could add some ability for a micropub client (when given "config" scope) to offer itself as a new client for an action. so it submits ?q=config&action="reply"&url="microedit.com/reply?url={url}"

squiso

Created by Indieauth.christoffer.me on October 18


Contents

Squiso

This text is a mirror from the official page.[1]

header.png

What is Squiso?

Squiso wants to create a decentralized open social web, by allowing users to host their own social data or trust a service provider of their choice.

Table of contents

  • Squiso basics
  • Why is this a good thing?
  • Basic components in Squiso
    • Data files
    • Browsers
    • Hosters
  • Getting started as a user
  • Getting started as a developer

Squiso basics

All your public social data (such as your activities, notes, photo-albums, blog posts, etc) are stored in well structured JSON files on the web.

You can host and maintain your own data files (such as on your Dropbox, or via your own web server), yourself or find a Squiso service provider you trust if you don't want to avoid all the technical hassle.

your_social_data.png

Each user has a "main data file". This file basically acts as an entry point for your data (for any Squiso tools). In this file you have your basic social data, such as a name, description, any personal links, other users your might be following, etc.

This file can however link to other files (with a similar structure) that contains additional data, such as all your blog posts or photos. Using this principle we are slowly building an open web of social data.

web_of_files.png

Given everything is on the world wide web, your "main data file" will get its own URL. The address to this is totally based on how and where you want to host your data. Some examples could be though:

However since the solution is decentralized, if you want to give away the location of your data to someone who wants to follow you, or if you want to follow someone else, you use the address to social data (compared to your username at a centralized solution).

That's about it!

Why is this a good thing?

For multiple reasons:

  • This allows anyone to control, maintain and host their own social data if they want.
  • Since this is open, any developer can create any tool for any platform, using any business model (free, open source, commercial, etc), which ultimately will lead to a huge range of excellent tools competing for the most users.

Basic components in Squiso

Data files

Basically a user's data files that contains their social data

Browsers

Tools that can interpret data files and show them in a fancy way for other users. Here is a demo:

https://dl.dropboxusercontent.com/u/8183146/temp/squiso_viewer/index.html

Hosters

Services that allow users to host and maintain their social data using their solution.



Getting started as a user

Getting started as a developer

Small Computers

Created by Dunlaps.net on October 23

  • Thu, October 23 dunlaps.net Created page with "{{stub}} These '''<dfn>Small Computers</dfn>''' are low-power computers that are useful as servers and special-use controllers for a variety of applications. They can all run we..."
  • Thu, October 23 dunlaps.net /* Hardware */
  • Thu, October 23 dunlaps.net /* Hardware */
  • Thu, October 23 dunlaps.net /* Hardware */
  • Thu, October 23 dunlaps.net /* Hardware */



These Small Computers are low-power computers that are useful as servers and special-use controllers for a variety of applications. They can all run web servers and related software, though with limited capability.

Criteria

Your server needs to be capable enough to handle the tasks you ask of it, but also should consume very little power when idle. Depending on your application, different storage and Input/Output options may be important. There are many questions to ask when choosing a Small Computer, but here are a few to start:

  • How much code do you want to write: none, some, lots?
  • How much are you willing to pay?
  • Are you willing to "build" the computer hardware?
  • What jobs will this Small Computer do? What software will you run on it?
  • What software is required by your CMS or website technology?

Hardware

Raspberry Pi $40 http://www.raspberrypi.org
Beagle bone Black $65 http://beagleboard.org/black
Intel Galileo $85 http://www.intel.com/content/www/us/en/do-it-yourself/galileo-maker-quark-board.html
Intel NUC $150 - $400 http://www.intel.com/content/www/us/en/nuc/overview.html
pico-ITX Systems $120 - $400 http://en.wikipedia.org/wiki/Pico-ITX
nano-ITX Systems $150 - $500 http://en.wikipedia.org/wiki/Nano-ITX
mini-ITX Systems $150 - $700 http://en.wikipedia.org/wiki/Mini-ITX

Varnish

Created by Thierry.marianne.io on October 19

  • Sun, October 19 thierry.marianne.io Created page with "Varnish is a caching [http://en.wikipedia.org/wiki/Reverse_proxy HTTP reverse proxy]. It is also known as an HTTP accelerator. Cacheable responses served by a web application w..."
  • Sun, October 19 thierry.marianne.io /* updated Varnish page */
  • Sun, October 19 thierry.marianne.io
  • Sun, October 19 aaronparecki.com add dfn tag

Varnish is a caching HTTP reverse proxy, a.k.a. an HTTP accelerator.

Cacheable responses delivered by a server (e.g. nginx, Apache HTTP server, Lighttpd) are cached by Varnish, provided a set of requirements defined as HTTPFeatures.

Cached responses are served to client applications (browsers) by Varnish when they are considered fresh enough.

See also

Template:dariusdunlap

Created by Dunlaps.net on October 20

  • Mon, October 20 dunlaps.net Created page with "== my indie web setup == * http://dunlaps.net/darius is my primary home where I post ** [[notes]] and [[POSSE]] them (abbreviated if necessary) to: *** [[Twitter]] - https://twi..."
  • Mon, October 20 dunlaps.net /* my indie web setup */
  • Mon, October 20 dunlaps.net /* my indie web setup */

my indie web setup is a work in progress



More later...

real-time comments

Created by Tantek.com on October 20




real-time comments are the display of comments on a view of a post (typically on its permalink) as they are received by the post (presumably via webmention), without needing any explicit user reloading, refreshing, or any other tapping/clicking etc.

Real-time comments are one of several real-time interactions.

Contents

IndieWeb Examples

Aaron Parecki

Aaron Parecki uses p3k on aaronparecki.com post permalinks to show real-time comments since 2013-10-13.

Silo Examples

Real-time comments are a silo innovation.

Facebook

Facebook was perhaps the first silo to implement real-time comments since 2012(?) at least, on both post permalinks, and sometimes on posts in a stream or in a collection.

Twitter

Twitter, as of their mid-2014 front-end redesign, now supports (sometimes) showing real-time comments on tweet permalinks:

See Also

incremental authorization

Created by Tantek.com on October 18




incremental authorization is the practice, even pattern, of only requesting permissions when they are needed for the current user-action, for example, when requesting OAuth authorization, read, write, delete permission, or similarly with Micropub.

Contents

Why

The incremental authorization pattern is important to the indieweb by way of Micropub client design.

Micropub clients should follow the incremental authorization pattern, and only ask for the absolute minimal permissions they need for any particular user action, when the user attempts the action, rather than at sign-up / install time.

Silo Encouragement

The practice of incremental authorization is being encouraged by more and more silos.

Facebook

Google

Silo Examples

Various silos have begun to explicitly implement incremental authorization, and make it clear that they do, and why they do.

all use Twitter for log-in, but none of them require write-access up-front.[1]

Premature Write Permissions Antipattern

(this may deserve its own page if it grows significantly)

Incremental authorization practices are largely a reaction to recognizing that requesting all or many permissions up front was rude and disrespectful of users, and thus an antipattern.

Articles about this misbehavior:

Silo Antipattern Examples

See Also

photos-of

Created by Tantek.com on October 17




photos-of is a feature on various silos that shows a list of photos that have been person-tagged with a particular person (typically most recent first).

Contents

IndieWeb Examples

  • no known examples currently.

Silo Examples

Facebook

Facebook appears to have this feature, but not clear if it works without login.

Flickr

Flickr has had this feature for a few years at least.

Instagram

Instagram has a "photos of" feature that is accessible in their native mobile applications, but it's not clear if it can be used on the web.

See Also

tragedy of the comments

Created by Tantek.com on October 20




"Tragedy of the comments" is a phrase coined by Kevin Marks

see:

See Also

User:Fiatjaf.alhur.es

Created by Fiatjaf.alhur.es on October 18

  • Sat, October 18 fiatjaf.alhur.es Created page with "[http://fiatjaf.alhur.es fiatjaf] is an economist, anarchist, conservative, olavete, programmer from Lagoa Santa, MG."
  • Tue, October 21 fiatjaf.alhur.es add indieweb-related projects

fiatjaf is an economist, anarchist, conservative, olavete, programmer from Lagoa Santa, MG.

Projects

  • coisas (GitHub) is a multipurpose website engine that runs totally in the browser and deploys to GitHub Pages (or any thing with a similar API -- today none), the deployed website features infinitely nestable pages, with a hierarchy organization. As they are static, the websites generated by coisas don't support webmentions or any of these complex things.
  • microanalytics (GitHub) is a CouchApp that you can host (in fact, you need to) in your own CouchDB and does website-analytics. It is easy to set-up, it gives you a nice javascript snippet which loads a small library, loads quickly and is very flexible, working with custom events. It's also nice, for the command line lovers, to visualize the data, as it comes with a humble Python command line client.
  • scrapboard (GitHub) is a CouchApp that replicates the functionality of the old Orkut scrapbook, but in a decentralized way, as every person that wants her personal scrapboard has to host it in their CouchDB. However, scrapboard is not an island. It is configured to work with identification based on any personal website with a h-card and webmentions, and with anonymous postings (identified by an optional name).

Orkut scrapbook

Created by Fiatjaf.alhur.es on October 21

  • Tue, October 21 fiatjaf.alhur.es Created page with "The '''scrapbook''' was a feature of the late [[silo]] orkut (see [[site-deaths]]) still, to this day, a kind of messaging platform unseen in any other social network or hosted s..."
  • Tue, October 21 fiatjaf.alhur.es

The scrapbook was a feature of the late silo orkut (see site-deaths) still, to this day, a kind of messaging platform unseen in any other social network or hosted service.

The scrapbook provided a hybrid between the personal messaging and the publishing, it was somewhat similar to posting at a friend's wall on Facebook, or tweeting to a friend, or commenting at a blog post, but different in the following senses:

  • the content was public;
  • any person could post at others' scrabooks;
  • the posted content wasn't mixed with totally unrelated contents (in a Twitter or Facebook stream, for example);
  • the posted content wasn't perishable;
  • the posted content wasn't streamed to anywhere, so it wasn't a big deal to send someone a scrap, it would not be shown to a lot of unrelated people, except if they went looking after it;

So, as it wasn't such a big deal as posting at a friend's wall on Facebook, it:

  • encouraged quick message exchanges, regarding any subject, big or small, even between strangers;
  • encouraged public discussion of themes that, at first, could be seen as unworthy, because they were not being displayed at everyone's computers, they were shown just to the interested people;
  • allowed other people to include themselves in the conversation.

fiatjaf is trying to bring the Orkut scrapbook to the web with scrapboard.

real-time interactions

Created by Tantek.com on October 21




real-time interactions are the display of interactions on a view of a post (typically on its permalink) as they are received by the post (presumably via webmention), without needing any explicit user reloading, refreshing, or any other tapping/clicking etc.

Typical real-time interactions include:

Contents

IndieWeb Examples

Aaron Parecki

Aaron Parecki uses p3k on aaronparecki.com post permalinks to show since 2013-10-13:

Silo Examples

Real-time interactions are a silo innovation.

Facebook

Facebook was perhaps the first silo to implement real-time interactions since 2012(?) at least, on both post permalinks, and sometimes on posts in a stream or in a collection. In particular, both:

Twitter

Twitter, as of their mid-2014 front-end redesign, now supports (sometimes) showing real-time interactions on tweet permalinks:

  • real-time likes (favorites in particular - seen once 2014-10-21, but then not when window wasn't frontmost, nor when re-activated)
  • real-time comments (@-replies - seen previously)

Possibly:

  • real-time reposts (retweets in particular - presumably since their display is very similar to favorites, yet a retweet on an item that showed a real-time favorite, did not itself show up).

See Also

gif

Created by Joel.franusic.com on October 23


gif is a bitmap image format introduced by CompuServe in 1987.

'Oh, incidentally, it's pronounced "JIF"'

Retrieved from "http://indiewebcamp.com/gif"

User:Joskar.se

Created by Joskar.se on October 21

  • Tue, October 21 joskar.se Added a user page
  • Wed, October 22 aaronparecki.com /* Things I am thinking about, but don't care enough to ask (for now) */ answering anyway

Johnny Oskarsson is a student living in Gothenburg, Sweden.



Johnny Oskarsson

Projects

  • A microformats2 parser, written in C (utilizing gumbo-parser for HTML parsing). Will most likely be open-sourced one day. A day when I don't care about how ugly the code is.
  • https://joskar.se -- my personal website. Mostly written in Bourne Shell (/bin/sh) and C (see above).

Working On

"Identity transform" for MF2/HTML

A way to do an "identity transform" on my MF2/HTML-pages. Currently I'm losing some meta-data when editing pages using my CMS. This will also help when I want to add data (such as webmentions) to an existing page.

Webmention support

Currently one can send webmentions to my webmention endpoint, and they will be validated (asynchronously). The webmentions will not show up anywhere since I need to solve the above task first ("Identity transform").

Microformats2 parser

  • The above-mentioned mf2 parser. It is almost feature-complete now, except for backwards compatibility with the older microformats. It will most likely be open-sourced some day.
  • I am also working on a tool for extracting MF2 from the command-line (I am coding my website in /bin/sh after all...), aptly codenamed `mfget' (for now). It is simplistic by design, and it can currently do these things:
    • Get a value (or several) from the parse-tree: mfget <file.html /items/entry/name [...]
    • Encode the values in hexadecimal: mfget <file.html x/items/entry/name (This way it is easier to use `cut' and other command-line tools without worrying.)
    • Iterate over one arbitrary parameter: mfget <file.html /items/entry[]/name

Content Management System

I have built a "simple" CMS using a sort of templating system. The templates are basically HTML files with some shell script sprinkled throughout. The "identity transform" described above is a milestone in this project, which I have yet to complete.

Itches

DRY

I am trying to operate on the data already stored in my MF2/HTML as much as possible. See the "Identity transform" section above.

  • I don't have any explicit links to alternate pages or syndication in the <body> of my pages. I do however use CSS to show the <link>-elements which are residing in <head>. This is because most crawlers only look for rel="alternate" in head, and putting the same link in <body> for the sake of navigation would be a violation of DRY.
    • As a side note, text browsers such as lynx already show <link> elements in <head> if they have a title-attribute set. Why modern graphical browsers don't allow this by default is beyond me.

Bilingual support

For some reason I thought it would be cool to have bilingual support on my website. Perhaps mostly because I thought it would be silly to host primarily English content on a Swedish ccTLD (.se). Obviously communication with the Indieweb community will mostly be English, so that leaves me with no choice. Who knows, if I keep using a frontpage with an obscure language then perhaps people will be more willing to code in language detection on their websites as well :)

  • All translated pages on my website have the lang-attribute set on the html tag, and a link to a translation with rel="alternate", hreflang="...", and href="..." set.

POSSEing to (unsupported)

I am not a big "blogger", but I do like movies. So I want to POSSE some small thoughts I have on the subject of film to some film-reviewing silo, such as MUBI. I already have an account there, so I might just as well try to incorporate support for it.

  • On 2014-10-16, I managed to import all of my "reviews" from MUBI to my site using their (unfortunately undocumented) snowflake API.

Things I am thinking about, but don't care enough to ask (for now)

  • Why does reply-context suggest using a p-in-reply-to instead of u-in-reply-to? I thought the in-reply-to was supposed to be a URL?
    • The prefix indicates to the parser where to find the value. If the value is in an href attribute, then you'd use "u-". If the value is plain text or a nested mf2 object, you'd use the "p-" prefix. Aaron Parecki 14:42, 22 October 2014 (PDT)
    • Also, it seems like its conjunction with h-cite is important. But when parsed, wont the in-reply-to and h-cite become siblings in the parse-tree? Then they are not inherently related...

User:Guerillero.net

Created by Guerillero.net on October 23


me

2014/Cambridge/Demos

Created by Kylewm.com on October 23


until proper notes are posted, here is the beginning of demos in IRC: http://indiewebcamp.com/irc/2014-10-12#t1413148186862

2015/

Created by Tantek.com on October 18

  • Sat, October 18 tantek.com start with list of 2015 camps being planned, and how to start planning one in your city

Welcome to the planning page for 2015 IndieWebCamps!

The following are currently being planned:

Want to help out with one of those? Say something in IRC and add yourself to the page.

Want to organize a 2015 IndieWebCamp in your town and don't see it above?

Start with:

  1. Find at least one committed co-organizer. This is the most important step.
  2. Add a link above to [[2015/YourCity]]
  3. Click it and create the new page, and continue with the steps listed in:



IndieWebCamps
2015 DCProvidenceSFNYCPortland/NYC/BerlinUKCambridge
2014 SFNYCPortland/NYC/BerlinUKCambridge
2013 PortlandUKHollywood
2012 PortlandUK
2011 Portland



food

Created by Aaronparecki.com on October 17




Food is a post type that represents eating or drinking particular food or drink. Its content is often similar to a note or can be easily represented as plain text.

IndieWeb Examples

Contents

Aaron Parecki

Aaron Parecki uses his open source Teacup web and Pebble app to track food and drink consumption and publish to his website since 2014-10-03, with his backlog imported back to 2013-08-19.

Examples:

See Also

User:Indieauth.christoffer.me

Created by Indieauth.christoffer.me on October 19


My name is Christoffer. Squeakytoy in the IRC. This is my Website.

User:Thierry.marianne.io

Created by Tantek.com on October 21




Thierry Marianne

User:Shiflett.org

Created by Shiflett.org on October 21


Hi, I'm Chris.

Changed Pages

events/2014-10-22-homebrew-website-club

14 edits by tantek.com, kylewm.com, dunlaps.net, kartikprabhu.com

Micropub

5 edits by tantek.com, kylewm.com, werd.io

IRC People

4 edits by fiatjaf.alhur.es, indieauth.christoffer.me, thierry.marianne.io, shiflett.org

Events

4 edits by tantek.com, werd.io

Nginx

3 edits by jeena.net

file-storage

3 edits by tantek.com

Twitter

3 edits by shanehudson.net, joel.franusic.com

principles

3 edits by tantek.com

invitation

3 edits by tantek.com
  • Tue, October 21 tantek.com expand invitation definition to event+invitation(s), invitation(s) post, RSVP+invitation(s)
  • Tue, October 21 tantek.com /* Publish an RSVP with invitations */ /a
  • Tue, October 21 tantek.com move Why to top, subsections for each type of invitation, IndieWeb Examples none so far

Webmention

2 edits by joskar.se

indie-config

2 edits by kodfabrik.se

projects

2 edits by indieauth.christoffer.me
  • Sun, October 19 indieauth.christoffer.me added squiso to the project page
  • Sun, October 19 indieauth.christoffer.me added Used and primary developed by Squeakytoy in IRC

authorship

2 edits by adactio.com
  • Sat, October 18 adactio.com /* Use Cases */ Fallback to rel="icon" for author photo (as a last resort)
  • Sat, October 18 adactio.com /* Fallback to icon for photo */ List examples

Vouch

2 edits by tantek.com

Postly

2 edits by ben.thatmustbe.me
  • Sat, October 18 ben.thatmustbe.me /* Current Features */ send and receiving with vouch
  • Sat, October 18 ben.thatmustbe.me /* =Searching for a domain to use for a vouch */

subdomain

2 edits by tantek.com
  • Tue, October 21 tantek.com dfn, indieweb examples, silo examples, path alternative with silo examples
  • Tue, October 21 tantek.com /* Silo Examples */ LJ switched read why

MediaWiki:Sidebar

2 edits by tantek.com
  • Sat, October 18 tantek.com add building blocks, just after projects, for those looking to see what pieces you can use/build to make an indieweb site
  • Sat, October 18 tantek.com next indiewebcamp - is 2015 planning - which one will get planned first?

SNAP

2 edits by david.shanske.com

User:Tantek.com

2 edits by tantek.com
  • Thu, October 23 tantek.com move process h-card issues to top of community working on, expand invitation per IRC brainstorm
  • Thu, October 23 tantek.com /* working on */ invitation - incorporate / bi-directional merge with uf wiki coverage

annotation

2 edits by tantek.com

Getting Started

1 edits by dunlaps.net

DigitalOcean

1 edits by guerillero.net

venue

1 edits by tantek.com

2014/Cambridge

1 edits by tantek.com
  • Sat, October 18 tantek.com /* Blog Posts */ attempt at a tag aggregation via seen.co

WebRTC

1 edits by tantek.com

private posts

1 edits by tantek.com

comment

1 edits by fiatjaf.alhur.es

DNS

1 edits by tantek.com
  • Fri, October 17 tantek.com centralized/hierarchical vulnerability/bottleneck

federation

1 edits by tantek.com

User:ShaneHudson.net

1 edits by shanehudson.net

database-antipattern

1 edits by tantek.com
  • Sat, October 18 tantek.com /* Why discuss storage plumbing */ UX impact categories, example

Ello

1 edits by tantek.com

exercise

1 edits by aaronparecki.com

advocacy

1 edits by tommorris.org

WordPress

1 edits by david.shanske.com

Smallest Federated Wiki

1 edits by fiatjaf.alhur.es

multiple-reply

1 edits by tantek.com
  • Wed, October 22 tantek.com /* Ben Werdmuller */ add another multi-reply with a slightly different variant

wiki-projects

1 edits by fiatjaf.alhur.es

Posts about the IndieWeb

1 edits by tantek.com
  • Wed, October 22 tantek.com adactio building blocks, benwerd webmention introduction

IRC

1 edits by grant.codes
  • Tue, October 21 grant.codes /* Web */ Leafychat appears to be dead so deleting

User:Bret.io

1 edits by bret.io

language

1 edits by tantek.com

Twitpic

1 edits by tylerfontaine.me

Atom

1 edits by cweiske.de

www

1 edits by tantek.com

Web sign-in

1 edits by kylewm.com
  • Sun, October 19 kylewm.com /* Implementations */ add cweiske's IndieAuth-OpenID

IndieAuth

1 edits by kylewm.com
  • Sun, October 19 kylewm.com /* RDFa */ copy gist of solution here in addition to linking to the mail archive

User:David.shanske.com

1 edits by david.shanske.com

distributed-indieauth

1 edits by kylewm.com
  • Sun, October 19 kylewm.com /* Sites that support distributed IndieAuth */ add me

Facebook

1 edits by kylewm.com
  • Mon, October 20 kylewm.com /* Duplicate Events Created without Confirmation */

checkin

1 edits by aaronparecki.com
  • Wed, October 22 aaronparecki.com /* IndieWeb Examples */ add URL for benwerd checkin

short-domains

1 edits by tantek.com
  • Mon, October 20 tantek.com /* Email IM SMS print */ split into: Entry length limitations (add scenarios), and Easier to use

User:Kodfabrik.se

1 edits by kodfabrik.se
  • Mon, October 20 kodfabrik.se Added a working on / itches part to my profile

code-of-conduct

1 edits by tantek.com
  • Wed, October 22 tantek.com /* Respect */ medical conditions - calling out explicitly even though it could (sometimes is) interpreted as subset of / related to disability