WeChat ID
aaronpk_tv
#indieweb
-
Registration for IndieWeb Summit is open! http://2016.indieweb.org Pretty thrilled to be doing this for the 6th year in PDX! -
New @W3C Webmention draft! Minor clarifications + linked to the http://webmention.rocks test suite. https://www.w3.org/TR/webmention/#changes-from-20-april-2016-wd-to-29-april-2016 #RoadToCR
-
Monocle is Offline
When I first built Monocle, I modeled it after the "timeline" or "stream" view now common in social networks, but made it possible to subscribe to h-entry feeds as well. The main UI showed a stream of posts, with the full post contents rendered inline, along with the author info and favorite/repost/reply buttons.continue reading... -
Having finally given myself a way to reply and like posts from my "reader" (IRC), I am still amazed at how important it is to have a way to reply inline. I'm suddenly replying to way more things because it's so much easier now.
-
Just published a new @W3C Webmention working draft today, with all technical issues closed! https://www.w3.org/TR/webmention/ #indieweb #socialweb
-
Attempting to pass the new update test! https://webmention.rocks/update/1
And updated to include https://webmention.rocks/update/1/step/2 -
New integrated authorization server for p3k
I just launched an update to p3k which adds an integrated authorization server. This means that now when I sign in to Micropub apps like Quill, it will redirect me to my own server where I can have more fine-grained control over the access I am granting the application.continue reading... -
Micropub Spec Updates
Since publishing the latest W3C draft of Micropub on March 1, there have been a few minor updates based on feedback from people who have implemented it.Simpler update syntaxThe update syntax had an extra nesting that was not necessary. The syntax changed from:replace[properties][content]=Hello+Moonto replace[content]=Hello+MoonMoving a postIf the update operation caused the post to be moved to a new URL (such as when the URL scheme is based off of the post's date, or has a custom slug that is editable), the Micropub client needs a way to know the new URL of the post.The Update Response section now includes HTTP 201 as a possible response, along with:If the update operation caused the URL of the post to change, the server must respond with HTTP 201 and include the new URL in the HTTP Location headerMore InformationYou can read the latest editor's draft of the spec here: http://micropub.net/draft/ as well as see the change log. The git commit history shows the full detailed changes.Thanks to Greg for providing feedback on his Micropub implementation.As always, feedback from implementation experience is appreciated! Feel free to file an issue, or join the #indiewebcamp chat!continue reading... -
Our IRC chat is archived at https://indiewebcamp.com/irc/today which is also where you can join the chat room from the web page. (You can also join via Slack, we like to give people many options.)
> Most communities won't take the time
We have 5+ years of taking the time to archive the important pieces in the wiki, so take that for what you will. I think it's a sign of the strength of a community if people care enough to do that. -
Email is *one* way for open source communities to communicate. An even better way is what we're doing over at Indie Web Camp. We intentionally have no email list, instead we use IRC (with web and Slack gateways) for day to day discussion, and anything important gets categorized and archived on the wiki. This leads to better organization of information over the long term (have you ever tried to actually go find something in email list archives?) as well as provides a better medium for quick conversation.
-
Several Days of Server Migrations Later...
I just spent two days finishing migrating the last of my old websites and services off my old server and into new homes. This project has been on my todo list for over two years, and I've been making slow progress since then, mostly by spending a day on it here and there.I finally finished moving the last things off the server today. The last two things left were my Twitter streaming search script and a really old MediaWiki website. Both were running on a 6-year old operating system, and under deprecated versions of Ruby and PHP. The MediaWiki instance had been EOL since 2012. The OpenSSL library was so old the Heartbleed bug hadn't even been written yet. Other things on that server were a Gitlab install (which I replaced with Gogs in February), my own SSL root authority (which is significantly less useful now that Letsencrypt makes certificates free and easy), an old web app I haven't used since 2009, and many cobbled together scripts.This was quite a painful process all told, and I would like to avoid getting into this this situation in the future. Here are some things I'm planning to do that will help make the upgrade process easier in the future.Upgrade regularlySpend the time it takes to upgrade the whole server (OS as well as application dependencies) every 3-6 months, instead of letting the machine get to be several years old. The whole reason I got into this situation in the first place is the OS was so old incremental upgrades were no longer possible. Updating the OS, PHP/Ruby versions, and applications regularly means smaller incremental changes rather than getting into a situation where your app no longer runs because the scripting language changed so much since the last upgrade.Separate the web and database serversI've had a separate database server for a long time. The main benefit this gives me is I'm able to move the source code for a website to a new server without having to also worry about migrating the database at the same time. It's one less moving part in the migration process, and I will continue to do this in the future.Productize everythingSome of these projects and websites were so old that I didn't actually have them in Git repos yet. Some of them were in Subversion, some were just piles of files on disk. A few of them shared a common set of files on the server, rather than using any sort of package management and proper dependency chain. Of course my more recent projects are much better packaged, but I had forgotten I had not always done things this way. Making each project a self-contained application with its own Git repo makes it easier to move them around to new servers later.Avoid using servers in the first placeThese days, we have many options for running applications without dealing with the underlying operating system. Google AppEngine (on which I currently run indiewebify.me and xray.p3k.io), Amazon Lambda (where I run ca3db), and Heroku to name a few. Once a service is running in infrastructure such as these, you can forget worrying about the underlying operating system updates, and focus on your application logic. The service providers will handle everything under the hood and you can forget that upgrading OpenSSL is a thing that needs to happen.continue reading... -
Need an excuse to spend some time on your personal website? Come to Homebrew Website Club tomorrow! http://calagator.org/events/1250470073 #indieweb
