User:Ben.thatmustbe.me

From IndieWeb
Jump to: navigation, search

Ben Roberts Is a sysadmin and developer at a small company in Boston, MA who dreams of world domination.

I am currently developing my personal site.

  • I'm a sysadmin / Developer at a small company in Boston, MA.
  • I have my Masters in Computer Science from the University of Rhode Island.
  • I run Funtoo Linux on my main workstation.
  • I play DDR.
  • I am crazy.


Contents

Projects

InkStone

Main Aritcle: InkStone - github

IndieID

Main Aritcle: IndieID - github

TODO

  1. Twitter support
  2. CSS, currently very plain

mpTweet

Main Aritcle: mpTweet - github

TODO

  1. Get micropub chaining working (is not finding mp endpoint on last attempt, i think i can remove code and go straight to sending token / removed mpTweet token endpoint)
  2. CSS, currently still just a copy of relmeauth's index.php
  3. Make self documenting (errors tell you what parts you need to fix on your site)

Postly

Main Article: Postly - github

This is going to be my personal site and an MVC framework to build off of for others. Currently in its initial stages, it is based on system libraries from OpenCart

TODO

  1. cache external images and also get https working on everything (no external images at all)
  2. Add cookie to keep me logged in
  3. Create Indie Events (and receive RSVPs)
  4. Improve notifications system, probably break this out in to a proper notification system not just based on all interactions.
  5. Add some sane way to dismiss notifications system wide (would involve write ability in the webworker)
  6. Store / display like count and comment count (or actual comments?) on replies to my posts (completed possibly?? not really sure, not tested yet)
  7. Scrobble listens from last.fm
  8. display/receive/send/remove person-tag
  9. Contacts List (see below) / Unified Author records
  10. auto-linking @mentions. Ideally this will be once contact list / unified authorship is complete and thus would link to the indieweb-page (if available). Hopefully bridgy can handle this in some way so that syndicated version on twitter uses twitter user links, and indie-web post uses indie-web links.
  11. context messages to store both short and full urls to save extra polling.
  12. Deduplication (or better yet: prefer original posts) of incoming webmentions, (and display posse'd copy links of context-history and replies) (see https://ben.thatmustbe.me/note/2014/9/12/1/_ )
  13. webactions
  14. Fix caching of archived pages. Should not cache current month/day or should clear on edit/create for that month

Contacts List

This is just my ideas for an IndieWeb based contacts application. I will host my contact info on my own site as h-card but only public information. If a user visits the site with a key (custom to them) in the GET value, they get additional info such as mailing address, phone number, etc. Once I have have access to other's contact info, I build my contact list in a private section of my site. I could then access this information from an app on my phone or other device or directly through my website.

For key negotiation my current idea is to use webmention on the author page. Alice wants to get Bob's info in her contact list.

  1. Alice inputs Bob's URL in to her site.
  2. Alice's site gets Bob's site to discover his Author page (perhaps she had to put in his author URL directly)
  3. Alice's site parses Bob's h-card and adds this information to her contact list.
  4. Alice's site sends a webmention to Bob's author page saying that he has been added to her contacts.
  5. Bob's site receives this request and finds Alice's H-card on her site.
  6. Bob's site records this information for Bob to review later.
  7. Later Bob logs in to his site and sees that Alice has requested his information.
  8. Bob decides to give Alice all his contact information.
  9. Bob is asked to review Alice's URL to be sure that this URL is actually her site.
  10. Optionally Bob can add this info to his contacts, generating a request in the other direction.
  11. Bob approves her request and grants full access.
  12. Bob's site sends a web-mention to Alice's site that includes a generated key for Alice.
  13. Alice's site uses this key to get the updated contact information from Bob's site (with the key in the URL)

Other ideas/considerations:

Use Push notifications rather than h-card on author page. This would mean a complex push structure and people would know the second you remove access possibly. Not sure I would like that.

Ability to grant access to specific pieces to certain people. I might want a close friend to have all my information but others to have only a subset.

Friends without webmention systems can just ask for a URL that I can e-mail them. I can still specify the key and thereby control their level of access.

Sites should be able to receive keys before they make a request. (I know my friend will want my full info, so i just send him a link right away)

Side Projects

Trying to keep documented the specification as I extend it to complete webmention. Basically the asynchronous stuff was never specified.

See Also

  • todo: create a pubsubhub hub
Personal tools
Namespaces
Variants
Actions
Recent & Upcoming
Resources
Toolbox