IndieWebCamp is a 2-day creator camp focused on growing the independent web

events/2014-01-29-homebrew-website-club

Contents

Homebrew Website Club Meeting

Details

When

at -

Where

San Francisco
Quip SF, 988 Market St. (at 6th), 7th Floor, San Francisco, CA
Portland
Mozilla PDX, 1120 NW Couch St., Suite 320, Portland, OR

What

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, whatever...

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

URLs

San Francisco:

Portland:

RSVP

SF:

Portland:

Sorry to miss you!

  • ...

Notes

Notes from the meeting.

Blog posts

live-tweeted notes

Andy Sylvester's notes from the Portland meeting

Portland P2P Section

Brief list of topics OH in the discussion section:

SF P2P Section

Brief list of topics OH in the discussion section. (We expect there's plenty of prior art for most of these.)

  • protecting your domain from hijacking
  • "indie mobile." self-published personal or small group mobile apps, often sideloaded instead of distributed through an app store
  • animating SVG dynamically on a web site
  • POSSE for semi-public, private, one-to-one (e.g. messaging), and single-user (e.g. health) data
    • we'd like to see more examples of automated private and semi-public POSSE in the wild
  • private indieweb posts: users have to login/auth somehow. what's the least auth you can get away with? one-time login, e.g. with a cookie that doesn't expire, is pretty little. could you do zero auth by checking that referrer is POSSEd post? or by sniffing silo credentials?
  • link-less (and permashortcitation-less) original post discovery. if you already know the person's domain, you can fetch the front page, parse it, and search rel-syndication links for the POSSE post URL. use case: avoid annoying silo users but still support backfeed, etc.
    • you can even try to do this without rel-syndication links by fuzzy matching on timestamps and text in original posts.
  • lots of people POSSE/PESOS *within* silos: they may think of one account as their "primary," cross-post to others for wider reach, and include links back to the primary silo posts. interesting opportunity for research and maybe shortcut for outreach and explaining ideas.
  • Android/iOS app ideas: want indieweb friendly mobile publishing/sharing apps similar to existing indie reply browser extensions and bookmarklets?
    • micropub client that supports a number of intents, so it's easy to send text, URLs, images, etc. to it?
    • similar client that sends web intents/actions instead of micropub?
    • looked at Open Link In App (GitHub) as a jumping-off point.
  • indie reader: one of the biggest differences from traditional feed readers is replying to/interacting with a post. can you decouple the reader from your site and still get that? ideas:
    • register your site's web intent/action endpoints with reader, its reply (etc) UIs point there.
    • reader renders each post as iframe to original post. reply browser extension operate on "current" iframe.
    • reader extracts and includes mf2 in each post, including fully qualified URLs. reply browser extension operates on that.

Photos

Portland

PDX meetup

San Francisco

SF meetup

Homebrew Website Club
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