We met at Charlie’s Coffee House, 266 Monterey Road, South Pasadena, CA, where we stayed until closing at 8:00. Deciding that we hadn’t had enough, we moved the party (South Pasadena rolls up their sidewalks early) over to the local Starbucks, 454 Fair Oaks Ave, South Pasadena, CA where we stayed until they closed at 11:00pm.
Quiet Writing Hour
Angelo manned the fort alone with aplomb while building intently. If I’m not mistaken, he did use my h-card to track down my phone number to see what was holding me up, so as they say in IRC: h-card++!
Needing no introductions this week, Angelo launched us off with a relatively thorough demo of his Canopy platform which he’s built from the ground up in python! Starting from an empty folder on a host with a domain name, he downloaded and installed his code directly from Github and spun up a completely new version of his site in under 2 minutes. In under 20 minutes of some simple additional downloads and configuration of a few files, he also had locations, events, people and about modules up and running. Despite the currently facile appearance of his website, there’s really a lot of untapped power in what he’s built so far. It’s all available on Github for those interested in playing around; I’m sure he’d appreciate pull requests.
Along the way, I briefly demoed some of the functionality of Kevin Marks’ deceptively powerful Noterlive web app for not only live tweeting, but also owning those tweets on one’s own site in a simple way after the fact (while also automatically including proper markup and microformats)! I also ran through some of the overall functionality of my Known install with a large number of additional plugins to compare and contrast UX/UI with respect to Canopy.
We also discussed a bit of Angelo’s recent Indieweb Graph network crawling project, and I took the opportunity to fix a bit of the representative h-card on my site. (Angelo, does a new crawl appear properly on lahacker.net now?)
Before leaving Charlie’s we did manage to remember to take a group photo this time around. Not having spent enough time chatting over the past few weeks, we decamped to a local Starbucks and continued our conversation along with some addition brief demos and discussion of other itches for future building.
We also spent a few minutes discussing the upcoming IndieWebCamp LA logistics for November as well as outreach to the broader Los Angeles area dev communities. If you’re interested in attending, please RSVP. If you’d like to volunteer or help sponsor the camp, please don’t hesitate to contact either of us. I’m personally hoping to attend DrupalCamp LA this weekend while wearing a stylish IndieWebCamp t-shirt that’s already on its way to me.
In keeping with the schedule of the broader Homebrew movement, so we’re already committed to our next meeting on September 7. It’s tentatively at the same location unless a more suitable one comes along prior to then. Details will be posted to the wiki in the next few days.
Thanks for coming everyone! We’ll see you next time.
Live Tweets Archive
Though not as great as the notes that Kevin Marks manages to put together, we did manage to make good use of noterlive for a few supplementary thoughts:
Thoughts on post types/kinds relating to reading within the Indieweb construct
This morning while breezing through my Woodwind feed reader, I ran across a post by Rick Mendes with the hashtags #readlater and #readinglist which put me down a temporary rabbit hole of thought about reading-related post types on the internet.
I’m obviously a huge fan of reading and have accounts on GoodReads, Amazon, Pocket, Instapaper, Readability, and literally dozens of other services that support or assist the reading endeavor. (My affliction got so bad I started my own publishing company last year.)
READ LATER is an indication on (or relating to) a website that one wants to save the URL to come back and read the content at a future time.
I started a page on the IndieWeb wiki to define read later where I began writing some philosophical thoughts. I decided it would be better to post them on my own site instead and simply link back to them. As a member of the Indieweb my general goal over time is to preferentially quit using these web silos (many of which are listed on the referenced page) and, instead, post my reading related work and progress here on my own site. Naturally, the question becomes, how does one do this in a simple and usable manner with pretty and reasonable UX/UI for both myself and others?
Currently I primarily use a Pocket bookmarklet to save things (mostly newspaper articles, magazine pieces, blog posts) for reading later and/or the like/favorite functionality in Twitter in combination with an IFTTT recipe to save the URL in the tweet to my Pocket account. I then regularly visit Pocket to speed read though articles. While Pocket allows downloading of (some) of one’s data in this regard, I’m exploring options to bring in the ownership of this workflow into my own site.
For more academic leaning content (read journal articles), I tend to rely on an alternate Mendeley-based workflow which also starts with an easy-to-use bookmarklet.
I’ve also experimented with bookmarking a journal article and using hypothes.is to import my highlights from that article, though that workflow has a way to go to meet my personal needs in a robust way while still allowing me to own all of my own data. The benefit is that fixing it can help more than just myself while still fitting into a larger personal workflow.
A Broader Reading (Parent) Post-type
Philosophically a read later post-type could be considered similar to a (possibly) unshared or private bookmark with potential possible additional meta-data like: progress, date read, notes, and annotations to be added after the fact, which then technically makes it a read post type.
A potential workflow viewed over time might be: read later >> bookmark >> notes/annotations/marginalia >> read >> review. This kind of continuum of workflow might be able to support a slightly more complex overall UI for a more simplified reading post-type in which these others are all sub-types. One could then make a single UI for a reading post type with fields and details for all of the sub-cases. Being updatable, the single post could carry all the details of one’s progress.
Indieweb encourages simplicity (DRY) and having the fewest post-types possible, which I generally agree with, but perhaps there’s a better way of thinking of these several types. Concatenating them into one reading type with various data fields (and the ability of them to be public/private) could allow all of the subcategories to be included or not on one larger and more comprehensive post-type.
Not including one subsection (or making it private), would simply prevent it from showing, thus one could have a traditional bookmark post by leaving off the read later, read, and review sub-types and/or data.
As another example, I could include the data for read later, bookmark, and read, but leave off data about what I highlighted and/or sub-sections of notes I prefer to remain private.
A Primary Post with Webmention Updates
Alternately, one could create a primary post (potentially a bookmark) for the thing one is reading, and then use further additional posts with webmentions on each (to the original) thereby adding details to the original post about the ongoing progress. In some sense, this isn’t too far from the functionality provided by GoodReads with individual updates on progress with brief notes and their page that lists the overall view of progress. Each individual post could be made public/private to allow different viewerships, though private webmentions may be a hairier issue. I know some are also experimenting with pushing updates to posts via micropub and other methods, which could be appealing as well.
This may be cumbersome over time, but could potentially be made to look something like the GoodReads UI below, which seems very intuitive. (Note that it’s missing any review text as I’m currently writing it, and it’s not public yet.)
Ideally, better distinguishing between something that has been bookmarked and read/unread with dates for both the bookmarking and reading, as well as potentially adding notes and highlights relating to the article is desired. Something potentially akin to Devon Zuegel‘s “Notes” tab (built on a custom script for Evernote and Tumblr) seems somewhat promising in a cross between a simple reading list (or linkblog) and a commonplace book for academic work, but doesn’t necessarily leave room for longer book reviews.
I’ll also need to consider the publishing workflow, in some sense as it relates to the reverse chronological posting of updates on typical blogs. Perhaps a hybrid approach of the two methods mentioned would work best?
I’ll keep thinking about the architecture for what I’d ultimately like to have, but I’m always open to hearing what other (heavy) readers have to say about the subject and the usability of such a UI.
Please feel free to comment below, or write something on your own site (which includes the URL of this post) and submit your URL in the field provided below to create a webmention in which your post will appear as a comment.
Angelo showed off some impressive python code which he’s preparing to opensource, but just before the meeting had managed to completely bork his site, so everyone got a stunning example of a “502 Bad Gateway” notice.
At the break, we were so engaged we all completely forgot to either take a break or do the usual group photo. My 1 minute sketch gives a reasonable facsimile of what a photo would have looked like.
Peer-to-Peer Building and Help
With a new group, we spent some time discussing some general Indieweb principles, outlining ideas, and example projects.
Since Michael was very new to the group, we helped him install the WordPress IndieWeb plugin and configure a few of the sub-plugins to get him started. We discussed some basic next steps and pointers to the WordPress documentation to provide him some direction for building until we meet again.
We spent a few minutes discussing the upcoming IndieWebCamp logistics as well as outreach to the broader Los Angeles area community.
For a new group, there’s enough enthusiasm to do at least two meetings a month, in keeping with the broader Homebrew movement, so we’re already committed to our next meeting on August 24. It’s tentatively at the same location unless a more suitable one comes along prior to then.
Thanks for coming everyone! We’ll see you next time.
A push notification (AKA client notification) is a notification that shows up on one or more of your client devices without you having to explicitly request it — it’s “pushed” to you, instead of you having to poll for it. –Source: IndieWeb.org
Today I came across a beta web service called Pushpad that provides easy-to-install push notifications. As a result, for people who spend a lot of time in front of their screens, they can now subscribe to updates on the site here via web browser push notifications. Subscribers will get a small toaster-like pop up notification in real time on their screen to indicate that new content was published.
The service was quick and simple to set up with lots of documentation. While geared at large corporations looking for a simple turnkey implementation for push notifications on most major web browsers, it’s also easily usable by smaller sites. Even better it’s free for providing less than 10,000 notifications a month, which covers most small sites.
They provide an “Express” version that requires no serious technical skills and sets up in just a few minutes and a separate “Pro” version which provides a lot of additional customization (including a white labeled version) for those with the development skills to implement it.
For those on WordPress, they also have an easy to use plugin.
Pushpad supports the Push API for Chrome and Firefox and APNs for Safari.
Pushpad also supports integration with Zapier (currently in beta), which means that any of the hundreds of applications that are integrated with Zapier can be used to create push notifications on the desktop. Hopefully they include IFTTT.com soon too. I’m already using Pushbullet with IFTTT for integration between my Android phone and my desktop, but additional integrations for personalized notifications could be cool.
Roll Your Own
But maybe you’re hard core? If you prefer not relying on outside services, you can always build your own push notifications! In particular, IndieWeb.org provides some thoughts and tips about how to implement these for yourself based on open web standards.
Push Notifications for BoffoSocko.com
Now that we’ve been talking about them, would you like to try receiving them in the future? You can subscribe to push notifications for my blog by simply clicking on the icon below and then authenticating your subscription:
Bioinformatics is a broad discipline in which one common denominator is the need to produce and/or use software that can be applied to biological data in different contexts. To enable and ensure the replicability and traceability of scientific claims, it is essential that the scientific publication, the corresponding datasets, and the data analysis are made publicly available [1,2]. All software used for the analysis should be either carefully documented (e.g., for commercial software) or, better yet, openly shared and directly accessible to others [3,4]. The rise of openly available software and source code alongside concomitant collaborative development is facilitated by the existence of several code repository services such as SourceForge, Bitbucket, GitLab, and GitHub, among others. These resources are also essential for collaborative software projects because they enable the organization and sharing of programming tasks between different remote contributors. Here, we introduce the main features of GitHub, a popular web-based platform that offers a free and integrated environment for hosting the source code, documentation, and project-related web content for open-source projects. GitHub also offers paid plans for private repositories (see Box 1) for individuals and businesses as well as free plans including private repositories for research and educational use.
A hearty band of six gathered to work on their own websites
Tonight was the beginning of a new group of indiewebbers meeting up on the East side of the Los Angeles Area, in what we hope to be an ongoing in-person effort, particularly as we get nearer to IndieWeb Camp Los Angeles in November.
We met at Starbucks, 575 South Lake Avenue, Pasadena, CA.
Quiet Writing Hour
The quiet writing hour started off pretty well with three people which quickly grew to 6 at the official start of the meeting including what may be the youngest participants ever (at 6months and 5 1/2 years old).
#indieweb@ChrisAldrich: Quiet writing hours for the first Homebrew Website Club in Pasadena, CA are in full swing. 4 people already here.
Jervey Tervalon, a writer, and his 6 month old daughter
Evie (5 years old, private site)
Following introductions, I did a quick demo of the simple workflow I’ve been slowly perfecting for liking/retweeting posts from Twitter via mobile so that they post on my own site while simultaneously POSSEing to Twitter. Angelo showed a bit of his code and set-up for his custom-built site based on a Python framework and inspired by Aaron Schwartz’s early efforts. (He also has an interesting script for scraping other’s sites searching for microformats data with a mf2 parser that I’d personally like to see more of and hope he’ll open source it. It found a few issues with some redundant/malformed rel=”me” links in the header of my own site that I’ll need to sort out shortly).
Bryan showed some recent work he’s done on his photography blog, which he’s slowly but surely been managing to cobble together from a self-hosted version of WordPress with help from friends and the local WordPress Meetup. (Big kudos to him for his sheer tenacity in building his site up!) Jervey described some of what he’d like to build as it relates to a WordPress based site he’s putting together for a literary journal, while his daughter slept peacefully until someone mentioned a silo named Facebook. 5 year old Evie showed off some coding work she’d done during the quiet writing hour on the Scratch Platform on iOS that she hopes to post to her own blog shortly, so she can share with her grandparents.
At the break, we managed to squeeze everyone in for a group selfie.
Peer-to-Peer Building and Help
Since many in the group were building with WordPress, we did a demo build on Evie’s (private) site by installing the IndieWeb Plugin and activating and configuring a few of the basic sub-plugins. We then built a small social links menu to demonstrate the ease of adding rel-me to an Instagram link as an example. We also showed a quick example of IndieAuth, followed by a quick build for doing PESOS from Instagram with proper microformats2 markup. Bryan had a few questions about his site from the first half of the meeting, so we wrapped up by working our way through a portion of those so he can proceed with some additional work before our next meeting.
Summary & Next Meeting
In all, not a bad showing for what I expected to be a group of 5 less people than what we ultimately got! I can’t wait until the next meetup on either 8/10 or 8/24 (at the very worst) pending some scheduling. I hope to do every two weeks, but we’ll definitely commit to do at least once a month going forward.
Including Time Out, Time Further Out, Time Changes, Countdown: Time in Outer Space, and Time In, this series of albums commonly known as the Time Series from Dave Brubeck and the Dave Brubeck Quartet is a masterclass in how important time is in music as well as how it can evolve.
Here you’ll find Brubeck experimenting with time signatures including recordings of “Take Five” in 5/4 time, “Pick Up Sticks” in 6/4, “Unsquare Dance” in 7/4, “World’s Fair” in 13/4, and “Blue Rondo à la Turk” in 9/8.
This is a great way to spend the day/night when you have some active listening time.
Changes in the Facebook algorithm are about to hit major publishers pretty hard.
Should I be adding major media outlets to my Facebook feed as family members? Changes by Facebook, which are highlighted in this New York Times article, may mean this is coming: The Atlantic can be my twin brother, and Foreign Affairs could be my other sister.
After reading this article, I can only think that Facebook wrongly thinks that my family is so interesting (and believe me, I don’t think I’m any better, most of my posts–much like my face–are ones which only a mother could “like”/”love” and my feed will bear that out! BTW I love you mom.) The majority of posts I see there are rehashes of so-called “news” sites I really don’t care about or invitations to participate in games like Candy Crush Saga.
While I love keeping up with friends and family on Facebook, I’ve had to very heavily modify how I organize my Facebook feed to get what I want out of it because the algorithms don’t always do a very good job. Sadly, I’m probably in the top 0.0001% of people who take advantage of any of these features.
It really kills me that although publishers see quite a lot of traffic from social media silos (and particularly Facebook), they’re still losing some sight of the power of owning your own website and posting there directly. Apparently the past history littered with examples like Zynga and social reader tools hasn’t taught them the lesson to continue to iterate on their own platforms. One day the rug will be completely pulled out from underneath them and real trouble will result. They’ll wish they’d put all their work and effort into improving their own product rather than allowing Facebook, Twitter, et al. to siphon off a lot of their resources. If there’s one lesson that we’ve learned from media over the years, it’s that owning your own means of distribution is a major key to success. Sharecropping one’s content out to social platforms is probably not a good idea while under pressure to change for the future.
Psst… With all this in mind, if you’re a family member or close friend who wants to
have your own website;
own your own personal data (which you can automatically syndicate to most of the common social media sites); and
be in better control of your online identity,
I’ll offer to build you a simple one and host it at cost.
Advances in computing power, natural language processing, and digitization of text now make it possible to study our a culture's evolution through its texts using a "big data" lens. Our ability to communicate relies in part upon a shared emotional experience, with stories often following distinct emotional trajectories, forming patterns that are meaningful to us. Here, by classifying the emotional arcs for a filtered subset of 1,737 stories from Project Gutenberg's fiction collection, we find a set of six core trajectories which form the building blocks of complex narratives. We strengthen our findings by separately applying optimization, linear decomposition, supervised learning, and unsupervised learning. For each of these six core emotional arcs, we examine the closest characteristic stories in publication today and find that particular emotional arcs enjoy greater success, as measured by downloads.
Even in 2016, publishers and authors are still struggling when it comes to re-releasing decades-old books, but Penguin had a unique problem when it set out to publish a 30th anniversary edition of Richard Dawkin's The Blind Watchmaker.<br /><br />The Bookseller reports that Penguin decided to revive four programs Dawkins wrote in 1986. Written in Pascal for the Mac, The Watchmaker Suite was an experiment in algorithmic evolution. Users could run the programs and create a biomorph, and then watch it evolve across the generations.<br /><br />And now you can do the same in your web browser.<br /><br />A website, MountImprobable.com, was built by the publisher’s in-house Creative Technology team—comprising community manager Claudia Toia, creative developer Mathieu Triay and cover designer Matthew Young—who resuscitated and redeployed code Dawkins wrote in the 1980s and ’90s to enable users to create unique, “evolutionary” imprints. The images will be used as cover imagery on Dawkins’ trio to grant users an entirely individual, personalised print copy.
As a researcher, I fully appreciate the pro-commonplace book conceptualization of the first post, and the second takes things amazingly further with a plugin that allows one to easily display one’s hypothes.is annotations on one’s own WordPress-based site in a dead-simple fashion.
This functionality is a great first step, though honestly, in keeping with IndieWeb principles of owning one’s own data, I think it would be easier/better if Hypothes.is both accepted and sent webmentions. This would potentially allow me to physically own the data on my own site while still participating in the larger annotation community as well as give me notifications when someone either comments or augments on one of my annotations or even annotates one of my own pages (bits of which I’ve written about before.)
Either way, kudos to Kris Shaffer for moving the ball forward!