Static webpages

Thanks to the help of Amy Guy, I finally understand what the indieweb
people are wanting out of static websites.  It seems that the goal is
something like Disqus, where you can embed it on a static website and a
combination of off-site processing and javascript allows you to let
someone else worry about the dynamic parts.

I thought about how to accomplish this within the scope of the
ActivityPump spec.  I think that no more adjustments are needed other
than the ones we were planning given discussions in this WG!  So:

 - The main page is maybe at http://dustycloud.org/ which let's assume
   is a static website.

 - The inbox/outbox endpoints of this page "follow your nose" off-site,
   so maybe I am using the site http://federateme.example/cwebber/.
   In ActivityPump, you can specify the inbox/outbox endpoints anyway:
     http://oshepherd.github.io/activitypump/ActivityPump.html#actors
   So why not just put them at http://federateme.example/cwebber/inbox/
   and http://federateme.example/cwebber/outbox/

 - "But wait!" you say.  This is a *static* site!  That means that we'll
   never use the API at all to post to http://dustycloud.org/, which is
   true.  But, just as feedburner and some other sites can take a feed
   and serve it for you, maybe my off-site federateme.example account
   scrapes
     http://dustycloud.org/blog/index.xml
   (which is atom, which could work, but heck, my static site generator
   could aldo produce a
   http://dustycloud.org/blog/.scrape-these-activities.json or something)

 - So, negotiating the importing is actually *out of scope* of the
   activitypump spec, but still *feasible within it*.

 - If you wanted, the federateme.example site could also provide a
   javascript widget for embedding federated communication on that page.

 - This does mean for the most part, only the *secondary* CRUD stuff
   (comments, favorites, etc) are happening through
   http://federateme.example/ but the CRUD done by this user is done
   manually through their editor and command line scripts and whatever.
   http://federateme.example/cwebber/ acts as a kind of proxy system for
   endpoints, but as far as I can tell, since we should be able to
   follow-your-nose off-site for those endpoints, why not?

Elf, tantek, does this satisfy the static site stuff you were bringing
up?
 - Chris

Received on Tuesday, 7 April 2015 16:35:49 UTC