2018-01-16 UTC
# 
Loqi [superfeedr] "Made it to my destination safe & sound.
Figured out the next big thing I want to build for my site, specifically for the #newwwyear:
* POSSE issues^1 & replies to GitHub
as part of my #indieweb 2018 stretch goal of owning/POSSEing all my public posts with content (not counting likes^2, reacji^3 etc.).
I’m specifically postponing edits (like edits to wiki pages, pull requests), realtime chat (like IRC, Slack), and contributions to various commons^4 sites such as Wikipedia, wiki.mozilla.org, and the indieweb.org wiki, where they both show clear authorship, and their licenses do not prevent me in any way from using or backfilling that content to my own site eventually.
^1 https://indieweb.org/issue — the IndieWeb community has both thought about and built examples of how to post issues to your own site and syndicate them to GitHub. I’ll be using and contributing any improvements to that work.
^2 https://indieweb.org/like - though I’ve implemented like posts on my site (see that page for a lot of my design thinking), and have owned all my Twitter favorites for a while, more/better "likes" is not a priority for me in 2018.
^3 https://indieweb.org/reacji - similar to like, there is a lot more UX work to do to make the indieweb experience of posting reacji or reactions (indieweb.org/reaction) in general even close to as smooth as on silos. Or perhaps that’s more work than using those existing UIs with services like OwnYourGram to PESOS reactions to my site. Or good reaction UX may require first building an integrated reader (indieweb.org/reader) into my site.
^4 https://indieweb.org/commons" by Tantek on 2018-01-16 http://tantek.com/2018/015/t1/made-destination-figured-out-newwwyear