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.
Homewood campus performance space now expected to reopen in early 2019 with improved sound system, seating, and much more.
The Shriver Hall renovation project, now slated for completion in early 2019, includes replacing the auditorium’s uncomfortable and often broken seating. Seat removal took place in the fall.
A few years ago they actually took out the awesome sound system because it didn’t “fit in” with the new orchestra shell and handicapped elevator access to the stage that the HSO felt made it too “cramped”. I have no expectation that this will make it a better place for film screenings. I’m also sure the seating capacity will be far less than it was before. Alas…
Replied toa 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!
@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
Just as I was getting sick last week, Colin Walker wrote “There has to be a better way to subscribe to sites.” He’s definitely hit the nail right on the head. The process is currently painful and disorganized, it’s also working on technology that’s almost two decades old and difficult for newcomers at best.
I’ve always posited that one of the reasons that social media silos have been so successful is that they’ve built some fantastic readers. Sure their UI is cleaner and just dead simple, but to a great extent 95% of their product is an evolved feed reader while the other 5% is a simple posting interface that makes it easy to interact. To compare, most CMSes are almost completely about posting interface, and spend very little time, if any, worrying about providing a reading experience.
The IndieWeb has been making some serious strides on making cross-site interactions easier with the Webmention and Micropub protocols, but the holy grail is still out there: allowing people to have an integrated feed reader built into their website (or alternately a standalone feed reader that’s tightly integrated with their site via Micropub or other means).
For those watching the space with as much interest as I have, there are a couple of interesting tools in the space and a few on the immediate horizon that are sure to make the process a whole lot easier and create a new renaissance in the open web.
SubToMe: a Universal Subscribe Button
First, for a relatively simple one-size-fits-all subscribe button, I recommend people take a look at SubToMe which touts itself as a “Universal Follow button” because it “makes it easy for people to follow web sites,because browsers don’t do it.” The button is fairly straightforward and has an awful lot of flexibility built in. In the simplest sense it has some solid feed detection so it finds available feeds on a web page and then provides a handful of recommended major readers to the user. With two clicks, one can pretty quickly and almost immediately subscribe to almost any feed in their reader of choice.
For publishers, one can quickly install a simple button on their site. They can further provide a list of specific feeds they want to advertise, and they can even recommend a particular feed reader if they choose.
For consumers, the service provides a simple browser bookmarklet so that if a site doesn’t have a button, they can click a subscribe button in their browser. Then click on a provider. Done. One can also choose a preferred provider to shorten the process.
Since last June there’s been a quietly growing new web spec called Microsub that will assuredly shake up the subscription and reader spaces. In short it provides a standardized way for clients to consume and interact with feeds collected by a server.
While it gets pretty deep pretty quickly, the spec is meant to help decouple some of the heavy architecture of building a feed reader. In some way it’s analogous to the separation of content and display that HTML and CSS allows, but applied to the mechanics of feed readers and how readers display their content.
There are already a few interesting projects by the names of Together and Indigenous that are taking advantage of the architecture
I can’t wait to see how it all dovetails together to make a more integrated reading and posting interface as well as the potential it has for individual CMSs to potentially leverage the idea to include integrated interfaces into their products. I can’t wait for the day when my own personal website is compatible with Microsub, so that I can use any Microsub client to read my timeline and follow people.
I’m also sure that decoupling the idea of displaying posts from actually fetching remote feeds will make it easier to build a reader clients in general. I hope this has a Cambrian explosion-type of effect on the state of the art of feed readers.
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.
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.
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 Benreferenced. 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.
Where to publish something has becoming a difficult decision for a lot of businesses. You read so many stories about using various channels to distribute content and grow traffic, it’s hard to know what does and doesn’t work. Medium, in particular, has become a major player in the world of startup content, but is it really that great?
The numbers just didn’t make sense. Yes, I could put more into Medium and try to build up readership even more. The guys at Basecamp regularly get 250k+ views on their content. But doing that helps Medium the most in the long run. They’ve been fumbling left and right trying to figure out how to make Medium sustainable, and I’m just not convinced they’ll always do what’s best for us and our business.
Now I didn’t want to throw out distribution on Medium entirely. There can definitely be some benefit to syndicating content there. It’s essentially another distribution channel to expose people to our content.
So we needed a game plan on how we could still make use of Medium as a distribution channel without cannibalizing our own readership or SEO work.
This is 100% on the mark, you should definitely own your own content. Syndicating it out to Medium is a great idea, particularly when you can get a rel=”canonical” tag for the original on Medium. Incidentally Medium has their own WordPress plugin that will allow you to quickly and easily syndicate your site’s content directly to Medium without needing to separately import it. It’s also available on a per post basis.
But, even with this, you’re only getting 50% of the value of having your own website because you’ve only got one way communication out. Next you’ll need communication back in. What if I said you could get a lot of the comments, likes, and interactions from those other silos back into your website too? This way the conversations others are having relating to your content also come back to your site and enrich it there? What if you could own all (or almost all) of the conversation around your content?
Think about it, what if there was an @mention functionality that worked from website to website instead of being stuck inside Twitter, Facebook, Google+, Instagram, Flickr etc.? Interestingly, it exists! And you can set it up for free with last year’s new W3C Webmention protocol which already has WordPress plugins ready to go. Roughly for WordPress you’ll need the Webmentions plugin, the Semantic Linkbacks plugin, the Syndication Links plugin, a few strategically placed rel=”me” tags on your site, (maybe some tweaks to your microformats on your theme), and a free Brid.gy account. Details for setting it up can be found on the WordPress pages of the indieweb.org website. I suspect if you’re strong enough to have figured out the tech for your article, you could probably have it up and running in under an hour or so. Then instead of feeding content from your blog to the black hole of social media, you could have actual two-way communication with many social silos! Now you won’t need to pay as much attention to those other sites as you can use your WordPress site as an “app” to interact with them instead.
I’m happy to help walk you through it if you’re interested and need help. My own personal site has some documentation of some of the above as well as examples of how it works.
In some sense, hopefully this post on my site will be an interesting exemplar. I own it and “loaned” or syndicated copies to Disqus and Twitter. Comments, likes and reposts you make to the Twitter copy will automatically be ported back here after the fact using Brid.gy. (Sadly, Disqus isn’t supported–yet.)
...the issue for me was Known was contextless for social media. I often post across various sites in response to things and share my photos as part of a conversation, so doing it through Known seemed a bit like working in a vacuum. I use Twitter less and less for discussion, so I wonder if I would feel different about this now, but what I wanted from Known was a way to also view and respond to Tweets, Facebooks statuses, photos on Flickr, Instagram, etc. A kind of reader for my content that would collapse those various conversations for me, and I could respond through my Known as if I was within those apps. I increasingly thought Known would make an awesome read//write feed reader if it had such a feature. The main reason Known fell by the wayside for me was I was not using it to publish in all these spaces, rather doing it post-facto if at all. Does that make sense?
Interestingly, Known had a lot of these features hidden in code under the hood. Sadly they weren’t all built out. It in fact, did have much of a reader (something which Ben indicated they were going to take out of the v1.0 release to slim down the code since it wasn’t being used). It also had a follow/following block of code (and even a bookmarklet at /account/settings/following) so you could follow specific sites and easily add them to your reader. Also unbeknownst to most was a built-in notifications UI which could have been found at /account/notifications.
It’s a shame that they put many of these half-built features on hold in their pivot to focus on the education market and creating a viable cash flow based company as this is the half that most CMSs lack. (If you think about what makes Twitter and Facebook both popular and really simple, I think it is that they’re 95% excellent feed readers with 5% built-in posting interfaces.)
I’ve managed to replace some of that missing functionality with Woodwind, a reader at http://woodwind.xyz, which one could connect with Known to do the reading and then integrate the posting, commenting, and replies to complete the loop. I do have a few very serious developer friends who are endeavoring to make this specific feed reader portion of the equation much easier to implement (and even self-host) to make the hurdle of this problem far lower, but I suspect it’ll be another 3-6 months before a usable product comes out of the process. For those looking to get more social into their feed readers, I often recommend Ryan Barrett’s appspot tools including https://twitter-atom.appspot.com/ which has instructions for extracting content from Twitter via Atom/RSS. It includes links at the bottom of the page for doing similar things with Facebook, Instagram and Google+ as well.
Interestingly there are now enough moving pieces (plugins) in the WordPress community to recreate all of the functionality Known has, one just needs to install them all separately and there are even a few different options for various portions depending on one’s needs. This includes adding reply contexts for social media as well as both the ability to syndicate posts to multiple social sites for interaction as well as getting the comments, etc. backfeed from those social sites back into the comments section of your post the way Known did. Sadly, the feed reader problem still exists, but it may soon be greatly improved.
Today we’re introducing a search collection using emoji, starting with books. Just include the books emoji with your microblog text about a book you’re reading or related topic, and your post will automatically be collected on /discover/books.
@Manton has added an interesting new feature to micro.blog. He’s created a special book discovery page which users can use to see what others are reading or recommending.
Simply by including the books emoji 📚 in one’s post, the page will collect all those posts and display them at http://micro.blog/discover/books. In a sense, he’s using an emoji almost like a hashtag, though the mechanics of how things work are slightly different. I’m curious to see how it evolves.
Based on what I’m able to discern, I have the proud place of ownership for being the fourth book post to micro.blog with “The Library is finally unpacked” from several months ago. It isn’t a book recommendation, but it’ll give you and idea about what I think about books.
The sad part for me though is that he chose the books emoji 📚 . Why sad? Because for quite a while now I’ve been posting updates on my own site about what I read using various book-related emoji to indicate where I’m at with a book. I’ll use the bookmark emoji 🔖 to indicate things that I want to read. I use a green book emoji 📗 to indicate that I’ve started reading something, an open book emoji 📖 to indicate that I’m making progress, and a red book emoji 📕 to indicate that I’ve just finished or stopped reading a particular book. Most of my book status updates also have some notes or thoughts about what I’m reading as well as quotes, highlights, and other marginalia.
Since micro.blog’s discover page only uses one emoji, it’s missing out on all my past updates. For those who’d like to see them on my site, this link should have the entire archive. Not all of them are syndicated to Twitter, but this link will give folks an idea what these posts all look like there.
In a similar vein, I also often post what I’m reading online with glasses 👓 emoji. One of the things that’s always bothered me about Twitter was that people often share articles, but research has shown that very few actually bother to read them before sharing. (I’ve always gotten the impression that many don’t even bother to read the headlines.) Thus, following reading.am’s lead, I post everything I actually read online to my own website, but to indicate that it was read (from start to finish), I add the glasses emoji to the title. If I haven’t read it yet, it’s more likely hidden on my back end or, if it’s something I really want to advertise, promote, or highly expect I’ll come back to later, it will have a bookmark emoji 🔖.
I don’t publish all my reads publicly, a large number are published privately. You can find all of the public read posts here.
Lastly, for movies and television I’m watching, I include either TV emoji 📺 or film emoji 🎞️. I find that these emoji do really well for microblogging spaces which often have space restrictions.
Overall, I’ve quite enjoyed the evolution of micro.blog’s discovery features. While there are a few follow recommendations available, the service has a page with recent photos, so one can scan photos as a means of finding interesting people to follow on the service.
I can’t wait to see how the reading discovery page works out or what other new discovery tools Manton implements in the future. It’s nice to see a service that continues to evolve and change in reaction to its community.