Reply to Justin Heideman on Twitter

Replied to a tweet by Justin Heideman (Twitter)
There are some interesting thoughts here about archiving news pages online. It also subtly highlights the importance of having one’s own domain to be able to redirect pages from their originals to archived versions, possibly containing different technological support. This article is sure to be of interest to folks in the Journalism Digital News Archive/Dodging the Memory Hole Camp (#DtMH2017)
Replied to Chris Jones on Twitter (Twitter)
A1. Personally I have multiple Wordpress sites, and I'm working on a stand-alone domain for my higher-end, highest-value #content .. all are candidates to aggregate relevant insights, yes? Pros/Cons? #smchat #contentseries
@sourcePOV I like @jgmac1106‘s general idea, but having less overhead to manage and administer appealed to me a lot. Here’s some thoughts on what I ended up doing: http://boffosocko.com/2016/12/18/rss-feeds-a-follow-up-on-my-indieweb-commitment-2017/

tl;dr: Having fewer sites to deal with seemed like a stronger idea. I still wanted to feature the richer content over the smaller tidbits while also not overwhelming people who had subscribed in the past. I also took into account trying to make it relatively easy for people to subscribe to the particular data they want/need out of my website. My home page has a list of various post kinds available which may be useful to think about as well.

@mrkrndvs has played around in this area of aggregation as well with a few different websites and may have some insight too.

Whatever you decide, be sure to have some fun along the way.

Replied to a tweet by Heather SearsHeather Sears (Twitter)
4. I signed up for a pilot account immediately. There were a host of apps to experiment with. I was particularly delighted to hear that I’d finally have institutional space and easy to use WordPress to run #10DoT https://10daysoftwitter.wordpress.com/ #pressedconf18
I’ve done something similar to #10DoT for independent authors before to promote their books, but it could also be an interesting model for helping people to set up #IndieWeb or #DoOO websites as well.

The underlying idea is also reminiscent of some strong advice to a beginner I saw in the IndieWeb chat last week: “Start small, then make incremental steps. Don’t eat the whale all at once.” – Scott Merrill

And then, just as I’m about to make this post and syndicate it out, I notice that Taylor Jaydin is doing something similar as an in-person laboratory for their project:

This Open Domains Lab sounds very similar in nature to the long-running Homebrew Website Club concept.  It makes me wonder if we couldn’t help to better dovetail some of the IndieWeb and DoOO communities’ efforts? Perhaps we could utilize pieces of the IndieWeb wiki like IndieWeb for Education, DoOO, or similar pages. Perhaps the IndieWeb community might consider sucking the hashtag into the chat there as well? If Taylor is open to it, perhaps it’s worth listing their Open Domains Lab on the IndieWeb wiki’s schedule of upcoming events? They might also use the IndieWeb chat functionality for the virtual portion of their program to increase interaction. I’d certainly welcome them to have interested parties stop by on either the wiki or via the simple-to-use webchat 24/7 if they need help, resources, or motivation of any kind.

Incidentally, I’ll note that Taylor very naturally POSSEd a copy of the post from his own website to https://knight.domains/thinkdeeper/open-domains-lab/ as well.

Replied to a tweet by Matt Reed (Twitter)
Wish Twitter would distinguish between "favorite" and "save for later." People could infer some pretty misleading things...
Intent on Twitter is often so muddled, this is the last thing some might worry about. (Yet it’s still a tremendous tool.) Pocket has browser extensions, and I know the one for Chrome has settings one can toggle an icon to appear on Twitter to allow bookmarking things to read for later directly within your Pocket account, which is generally a reasonable experience.

Pocket’s browser extension can add a much better “save to read for later” button to one’s Twitter feed.

I think the much stronger and better solution for one’s personal commonplace book is to simply add these intents to one’s own website and either favorite, bookmark, mark as read, repost, reply to, annotate, highlight, or just about “anything else” them there and syndicate the appropriate response to Twitter separately. (Examples: bookmarks and reads.) This makes it much more difficult to muddle the intent. It’ll also give you a much more highly searchable set of data that you can own on your own website.

Why wait around for Twitter or another social service to build the tools you want/need when it’s relatively easy to cobble them together for yourself on a variety of opensource platforms? While you’re at it, remove some of the other limitations like 280 characters as well…

Replied to A post on Mastodon by wiobyrnewiobyrne (Scholar Social)
@mrkrndvs I've really been interested in the collection/curation I see from you & @chrisaldrich - I'm in the process of figuring out how to build up a WordPress site to serve as the "commonplace book" on the WordPress site, keep it simple, and have it pump into my weekly newsletter. Any links/guidance/plugins on how to make this happen is definitely appreciated. I want to keep this as simple/lightweight as possible. :)
@wiobyrne@scholar.social @mrkrndvs@mastodon.cloud

I’ve written in a little bit of depth before about Organizing my research related reading.

My favorite piece of the puzzle is using the Post Kinds Plugin for WordPress which has some useful browser bookmarklets for quickly saving what I read, bookmark, and interact with online. Having the ability to add categories, tags, and other behind-the-scenes metadata also helps a lot.

You can then turn around and add all this to a newsletter at your leisure.

Happy to share more, but this should be a good start.

Replied to a post by Jeff Doshna (facebook.com)
I have a real problem. I HATE FACEBOOK, what they are doing with our data, how they control access to information and news for millions of people, and the fact that they've insinuated themselves into every aspect of our lives.

So I'm inclined to walk away from it entirely.

But....

There's real information on here that I need, about people I care about, about things going on in my communities, and keeping connected with folks who've been part of my life over the years.

So, what to do?
You can add people to custom Facebook lists and just read those, but then you’re not necessarily getting all the data you want given the Facebook algorithm deciding what you see.

There’s lots more I could advise doing, but if you’re only using Facebook for reading content you want to get out of Facebook, then lock the whole thing down as best as you can (privacywise) and then use https://facebook-atom.appspot.com/ to suck the data you want out as a feed and pipe it into a feed reader.

You can unsubscribe or unfollow folks to limit your feeds to the bare minimum. The atom feed the appspot tool gives you will be everything and it will be reverse chronological. Good feed readers like Feed.ly and Inoreader will allow you to filter out posts you don’t want to see using a variety of keyword filters.

If you need specific help in setting it up or the instructions are unclear, let me know; I’m happy to help.

If you want to set up and run your own custom private system/server for close family, I can make some suggestions for doing that too.

Replied to Support for importing syndication links for Mastodon Autopost · Issue #75 · dshanske/syndication-links by Chris Aldrich (GitHub)
Now that SL has the Mastodon icon (#66), I'll also note that the latest version of Mastodon Autopost plugin should now also support importing the URL for the last successful toot to allow the closure of automating the POSSE loop.
I’m verifying, for the tape since I know you don’t use Mastodon Autopost, that this works as expected now.

Reply to ravisagar on Twitter

Replied to ravisagar on Twitter (Twitter)
@ChrisAldrich Just found your blog after searching more about implementing #POSSE and #Webmention Great content. Thanks for sharing.
If you’re building in Drupal, I’m sure you’ll also find some valuable help from @hongpong, @mlncn@dries, and @swentel.
Replied to Updates broke query variable fill · Issue #158 · dshanske/indieweb-post-kinds (GitHub)
The adding of kindurl= no longer works. Fix needed.
@mrkrndvs I’ve found that if there’s an emoji within any of the metadata sucked into the meta box fields, the filter that sits on these fields to prevent malicious code, can then remove ALL of the data from them when you either save as a draft or try to publish the post.

If you’re finding that it doesn’t seem to work or does so sporadically, you might take a look for things like emoji or other potential unrecognized characters for the URLs you’re trying to use to see if that’s what is causing the bug.

Replied to Support GitHub · Issue #56 · dshanske/bridgy-publish (GitHub)
Bridgy now supports stars (likes), replies and new issues in early beta. I believe the Issue kind is coming to post-kinds. Forgive me if this is already being worked on.
@snarfed and @dshanske are brilliant!

With any luck, this will be my first POSSE reply to Github via my WordPress site using Bridgy Publish.

Reply to @Vasta about podcasts

Replied to a post by Sameer Vasta (vasta.micro.blog)
Just unsubscribed from all 324 podcasts I was trying to keep on top of every day; starting with a clean sheet, again. If you have one or two podcasts you think are must listen, please do let me know. (Looking for endorsements, more than just recommendations.) Thanks!
@vasta I think that the 14 part Seeing White series(Scene on Radio) was stunning storytelling, introspection, and history. My other must listen is the fantastic Eat This Podcast by @jeremycherfas which is about science and culture via the lens of food.

Reply to Jon Mitchell on reading bots

Replied to Are you familiar with Reading.am by Jon Mitchell (Everything is ablaze!)
@brentsimmons Are you familiar with Reading.am and/or the many homespun varieties of feeds people use to share what they′re reading online with minimal friction? For me this solved the problem of wanting RSS to have a social component, but it needs no centralized back end. People build a reading bot however they want, and they fire it off when they want to tell the internet “I am reading this.” For example, I trigger mine by using Pinboard just the way I normally would, and its RSS feeds feed the bot.For me this solved the problem of wanting RSS to have a social component, but it needs no centralized back end. People build a reading ...
I like the general idea behind what you’re talking about here Jon, though I may be missing part of the conversation as I came across it via a GitHub issue and it’s taken some time to find even a portion of the conversation on micro.blog, though I suspect I’m missing what I’m sure might be a fragmented conversation.

I too love the idea of indicating what I’ve been reading online. The problem I see is that very few platforms, social or otherwise are focusing on what people are actually reading. Reading.am is the only one I’m aware of. Pocket and Instapaper let people bookmark things they want to read, but typically don’t present feeds of things after they’ve been checked off as having been read.

Most others are systems meant for a specific purpose that are being bent to various other purposes and it’s rarely ever explicit so that everyone knows their intention. As an example, I know people who star, like, favorite or do something else on various platforms to indicate what they’re reading. Some also use these to indicate bookmarks. As a personal example, on Twitter, I sometimes “star” a tweet to indicate I “like” it or it’s a “favorite” while most other times I’m really using the functionality to quickly bookmark an article and use an IFTTT.com recipe to automatically add the URLs of these starred posts to my Pocket account for later reading.

The overarching issue with these is that the general concept is painfully spread out and the meaning isn’t always concrete or explicit. Wouldn’t it be better if it were vastly more specific? In an attempt to do just this, I use my own website, in linkblog-like fashion, to indicate what I’m physically reading. It has an RSS feed that others could subscribe to if they wish to read it elsewhere. I also “syndicate” copies to places like Reading.am or occasionally to Twitter, Facebook, etc. for those who prefer to follow in those locations. Incidentally on Twitter, mine often look a lot like your Twitter feed with visual icons to indicate specific intents.

For something like Evergreen, or any reader really, I’d much prefer if there was UI and functionality to allow me to directly interact with the content I’m reading and post that interaction to my own website (and own it) in a relatively frictionless way. This would be far better than using things like stars to do something that others may not grasp.

In the reading case, it would be cool if I could physically mark something explicitly as “read” in Evergreen, and the reader would post to my website that I’ve actually read the thing. While there are many ways to do this (including RSS), perhaps one of the most interesting currently is the open web standard called Micropub. So my WordPress site has a micropub endpoint (via a plugin) and apps that support it could post to my site on my behalf. If the reader could post to my site via micropub, I could use it to collect and create a feed of everything I’m reading. Similarly readers could also do similar things to explicitly indicate that I mean to bookmark something, or I could use the reader to compose a reply directly in the reader and post that reply to my website (which incidentally could send webmentions to the original website to publish those replies as comments on their site.)

As an example we’re all familiar with, micro.blog has micropub support, so I can use micro.blog’s app to post and micro.blog uses micropub to send the post to my own website.

With the proper micropub support, a reader could allow me to post explicit bookmarks, likes, favorites, replies, reads, etc. to my own website. All of these could then have individual feeds from my site back out. Thus people could subscribe to any (or all) of them as they choose. Want to know what I’m reading? Easy. Want to know what I’m bookmarking or liking? Which events I’ve RSVP’d to? Shazam!

My homepage has a full list of post types I’m currently supporting, and each one of them can be subscribed to individually by adding /feed/ onto the end of the URL.

In summary, let’s try not to impute too much meaning onto a simple star’s functionality when we can be imminently more specific about it. Of course, for completeness, for most readers, we’d also need to change the meaning of the traditional “mark as read” which in reality means, “mark as done” or “don’t show me this anymore”.

For more detail on how this could work in an advanced reader-based world I’ve written a more explicit set of details here: Feed Reader Revolution

And to quote Brent back:

…it’s okay if this is a work in progress and isn’t ready for everybody yet. It’s okay if it takes time. We don’t know how it will all work in the end.

We’re discovering the future as we build it.

Reply to “To PESOS or to POSSE?” by Dries Buytaert

Replied to To PESOS or to POSSE? by Dries BuytaertDries Buytaert (dri.es)
Comparing two different approaches that help you take control back over your own data on the web. [...] The goal of this analysis was to understand the pros and cons of how I can own my own content on https://dri.es. While PESOS would be much easier to implement, I decided to go with POSSE. My next step is to figure out my "POSSE plan"; how to quickly and easily share status updates on my Drupal site, how to syndicate them to 3rd party services, how to re-organize my mailing list and my RSS feed, and more. If you have any experience with implementing POSSE, feel free to share your takeaways in the comments.
What a fantastic breakdown of the concepts of POSSE vs. PESOS, though to be sure there are also additional variations for syndicating, cross-posting, or moving content around to reach various audiences.

One thing that I think you’ve only briefly touched upon is the ability to also have likes, replies/comments, etc. also come back to your site as native content via webmentions. I’ve been able to get rid of five apps and their incessant notifications and trim it all back to just using my own site to handle everything instead. Using something I choose to use instead of something I’m forced to, while also owning my data, is really very liberating.

Like you, I too have always wanted to own my own content on the web, and there are some easier and some harder methods. Not being as strong a developer as many, I’ve taken a more hybrid approach to things which is still evolving. To some extent I began at the easy end with some PESOS based workflows and relying on simple tools like IFTTT.com to at least begin owning all my content. For many content management systems, this is nearly dead easy, and could even be done with something as simple and flexible as Tumblr without much, if any, coding experience.

Over time, as I’ve been able, I’ve  moved to a more direct POSSE method as either I or, more often, others have managed to master making the simple posting interfaces easier and easier. I think in the end, POSSE is the strongest of the methods, so that has always been my ultimate goal.

From a Drupal-centric approach, you might be able to gain an interesting perspective on the multitude of ways POSSE/PESOS can be done by looking at the various ways that are available in WordPress ecosystem. It’s probably easy to discern that some are far easier than others based on one’s facility with coding. In general, I’ve noticed that the more freedom and flexibility a particular method or plugin has, the longer it takes to code and/or configure. The less flexibility a plugin offers, the easier. (So one could compare something like SNAP at the more comprehensive/difficult end to something simpler like JetPack for POSSE.) The difficulty is in the administrative tax of keeping up with the panoply of social media platform APIs to keep things working smoothly over time, particularly when you want your posts to be able to leverage the broad arrays of posting options and display outputs platforms like Facebook and Twitter offer. The other difficult questions can sometimes be: am I just replacing one or two social platforms, or am I trying to replace 20? and am I doing them with one plugin or with 20? and finally, how DRY is that process? Sometimes manually cutting and pasting is just as good.

As you do, I write first and foremost for myself and then a distant second for reaction and conversation with others. Thus I think of my personal site as just that: personal. To some extent it’s a modern day version of a commonplace book where I collect a variety of thoughts in a variety of means, while still trying somewhat to keep it in an outer facing form to look what people might expect a site to look like. This means that I have a good number more than the traditional types of posts most social media sites have. I try to own all my own bookmarks and even post what I’m reading both online and in physical form. I keep highlights and annotations of things I find interesting. I naturally keep longer posts, status updates, and photos like many. I even log scrobbles of music and podcasts I listen to as well as film and television I watch. Interestingly there’s a tremendous amount I only publish privately to myself or a small circle of others that’s hidden on my site’s back end. Depending on how far and deep you want your experience to go you might want to consider how all these will look or be represented on your site. To  a great extent, I think that WordPress’s attempt to copy Tumblr (text, photo, quote, link, chat, audio, video) with their Post Formats was interesting, it just didn’t go far enough. Naturally, this may take a different form for you depending on whether you’re building just for yourself or if you’re planning something more modular for the larger Drupal community to leverage.

Screencapture of my homepage with a list of the various post types my site supports including: articles, notes, bookmarks, jams, checkins, watches, RSVPs, etc.
A few of the post types my website supports.

The best part of all this is that I’ve not done any of it alone. While I try to maintain a list of some of my experiments to help others (you’ll probably appreciate the ones on mobile posting and RSS based on your outline), there’s also a wealth of other examples on the IndieWeb wiki and a terrifically stellar group of people around almost 24-7 in the IndieWeb chat to help spur me along. I’ll echo Tantek’s welcome to what I think is a more thoughtful and vibrant open web.

I hope others also find these resources so they’re not fumbling around in the dark as I was for so long. Since you’re obviously building in Drupal, I can recommend you take a look at some of the examples provided by the WordPress and the Known communities which Ben referenced. Since they’re all .php based and open-source, you may get further faster in addition to being able to iterate upon and improve their work. Many of the developers are frequently in the IndieWeb chat and I’m sure would be happy to help with ideas and pitfalls they came across along the way.

Like others, I’m posting my reply first on my own website, and manually cross-posting it to yours (manually until you support Webmention–perhaps via the Vinculum plugin?) as well as automatically to Twitter and others.