I watched Tantek’s presentation Take Back Your Web from Beyond Tellerrand during lunch. Great presentation. From it I added Mattias Ott’s blog post and this one by Aaron Parecki to Unmark to read later. Via Jeremy Keith.
Neat feature from Micro.blog. Here is Manton Reece, from his personal blog, on the new feature:
You can now follow blogs in the Micro.blog timeline, even if the blogger hasn’t yet registered on Micro.blog.
Manton describes this feature as another type of “username”. I understand why he’s framing it that way but I’m unsure if it is the best way to describe it. A blog’s content being syndicated through Micro.blog, unwitting of the owner, isn’t a username. In fact, any interaction with those posts by the Micro.blog community may very well go wholly unnoticed by the owner of the site unless their site supports Webmentions. So these are hardly Micro.blog users.
Be that as it is, I am struggling myself with a better way to fully describe the different ways in which someone can use Micro.blog.
At current, here they are:
A powerful service!
This brings back memories of two services that had some interesting tip-toeing to do as a result of syndicating the content of another persons without their permission.
One, I had a lot to do with, which was 9rules. We crawled the content of all of the blogs within the community and kept a copy of a lot of their content. This allowed a few things. We had categories on the 9rules web site that made it easy for people to find blogs that interested them such as Tech, Culture, Food, etc. It also made search possible – so in a way, we had our own blog search engine. It was one of the first services of its kind on the web.
However, 9rules’ main income came from ads. Our homepage featured a few primary ad spots and some of our subsequent pages did as well. A few of the members wondered if we were profiting off of their content. A valid concern, one we didn’t intend, and I remember it being a topic of debate.
Another service I had nothing to do with, Get Satisfaction. This service created forums for people to ask questions and get answers and rate their favorite products and services. One reason it caused a kerfuffle was because the companies had no idea these conversations were happening and it made them look bad when a big issue with one of their products went unanswered. Many asked to be removed from it.
I don’t think Micro.blog will end up with ads but never say never. Also, I trust Manton and his team to be mindful of how they use this content and how they notify site owners of anything that is happening with that content on their platform. So far they’ve proven themselves to be careful, purposeful and altruistic.
I hate doing this type of stuff, but I feel like this idea is so important it’d be foolish of me not to try. Even if this Kickstarter ends up being unsuccessful, I won’t be able to live with myself if I didn’t do everything in my power.
We can help him. We have blogs, accounts on Twitter, Micro.blog, Mastodon etc. Take two minutes to review Bokeh’s Kickstarter, back it if you’d like, but please write a short post to help him spread the word. And perhaps directly message a few people you know that could help as well.
As a community we can all help each other with our audiences – even if they are tiny. I always try to promote things people are building with my blog and even if I only help move the needle a very small amount – together perhaps we can make a difference for Tim and Bokeh and for others in our community building things and putting them out into the world.
Steven Johnson, in Beyond the Bitcoin Bubble:
The true believers behind blockchain platforms like Ethereum argue that a network of distributed trust is one of those advances in software architecture that will prove, in the long run, to have historic significance.
I’m very late to the game in reading Johnson’s piece in the NYT. I’ve had it stored in Pocket for far too long. I’m glad I took the time this morning while drinking my coffee to read it. It is very good. It includes many things I think about most; the open web, how tech giants are so important in what the future will look like, and what we can do to mitigate the downsides of them owning the future.
I’ve been buying BTC lately. Partly because the price is rather low at the moment but also partly because I have a completely different goal in 2019. I’m not prospecting. If my wallet’s value appreciates, excellent. If it doesn’t, I don’t care. My goal in 2019 is to use crypto currency (likely Bitcoin or Ether?) to pay for some every day mundane things. My goal is to transact the equivalent of around $10,000 USD in some form of crypto during the course of the year. That could be accepting crypto or spending crypto. It is my hope that by not being a hodlr, and also not trying to get rich, that I will help the crypto financial ecosystem in some small way.
Going back to Johnson’s piece. He writes a lot about the open web and the open protocols that are in place and how on top of those certain companies own things like our identity. He doesn’t quite go so far as to mention the Building Blocks of the indie web but I wish he had. But I think we’re starting to see decentralization on many fronts happen. I think 2018 was a big year for this and I think the shift is only going go accelerate.
I’m not going to make any predictions specifically for 2019 since I believe it will take longer than that. However, with blogging being easier than ever, with Mastodon and indie web protocols, and Solid and many other projects happening – I think we’ll start to see the power of Facebook and Google splinter. Even if it only splinters a little it will be a good thing for the open web.
My indie web goal is to bring my personal site a little more inline with indie web principles. As you long time readers will know, supporting the indie web exhausted me. I gave up. It was too hard. But, the beginning of such things is hard and I should buck up and figure it out. If I do and somehow help make it easier for the next person the web will be a better place.
I recommend reading Johnson’s entire piece.
Go ahead and read Matt Haughey’s post on why he left Twitter. But I wanted to pull out this bit:
I didn’t like that everything I wrote ended up being hard to find or reference, and even hard for me to pull up myself when I wanted, where a blog makes it pretty dang easy to see everything you wrote about in the past.
If I’m analyzing my reasons for blogging and/or microblogging on my own domain this is likely #1. I love having a history of my thoughts, guesses, observations, and photos. And I love that I own it.
I have fond memories of the very early days of WordPress (when it had just been forked from b2/cafelog), of Twitter, of Brightkite, of App.net, of Mastodon… just to name a few. The early days of any platform or so important to what they will become. They are the most fun to watch.
The early days of any platform can be frustrating too. Services sometimes go down, features aren’t released as quickly as you’d like, and small bugs can hamper your workflow.
I liken it to watching art be created. It can be a bit messy, it can sometimes confuse you, but when you see the final product you have the privilege of knowing how the platform got to that final state.
Yesterday I volleyed back and forth via email with Manton Reece, the founder and creator of Micro.blog. Micro.blog is in that same relatively early stage where new features are released with regularity, where the community is growing steadily, and where the users have the strongest voice.
He kindly answered a few questions. But here are a few highlights that I plucked from his answers:
Here is the interview and his responses in their entirety.
First, thank you for making Micro.blog. For me personally it is surfacing some excellent independent microbloggers that I wouldn’t have found otherwise. Now that Micro.blog is open to the public, is there anything that you see happening on the platform, either now or during the beta period, that has surprised or delighted you?
Thanks for being part of the Micro.blog community! I’ve loved how people not only embrace the platform, but in many cases get back to writing at an old blog that they had accidentally neglected, or get inspired to start up a new microblog at their own domain name. So many beautiful photos have been posted, which we like to highlight in the Discover section, and the tone of conversations has remained thoughtful and respectful even as the platform has grown.
I’m also happy to see that many Micro.blog users have warmed up to some of the early decisions we made to not copy every feature from other popular social networks. For example, not showing follower counts or worrying about how many likes a post has received.
People seem to really enjoy the new emoji-based topics we introduced recently, to collect posts about books or music or sports. Little experiments like these are a reaction to what the community is already doing. The best thing we can do is build features that support what people are posting about — to encourage the kind of posts that make Micro.blog a nice place to be — and then see which of those features resonates.
Have you been surprised at all by the number of photos that people are posting? Or, did you always think that Micro.blog would be a great place for people to share photos? And, do you think you’ll see audio or video shared more on Micro.blog in the future?
I’ve always thought photo-blogging would be a perfect fit for Micro.blog, and we’ve tried to build good support for it in the iOS app, such as having built-in photo filters. Many people are frustrated with Twitter and Instagram and want to post photos to their own web site again. But I was still happily surprised to see so many photos. There was also some help from the community, such as Doug Lane running a 7-day photo challenge.
Our plan was to start with photos, with good photo hosting, and then expand to natively support audio and podcasts. After that, video. I think video can quickly become kind of overwhelming and busy when shown in a timeline — especially with auto-playing video, which we don’t want to do. So I’m comfortable expanding this support fairly slowly to make sure we get it right.
I see Micro.blog as two parts: 1. A community of syndicated microblog posts that are populated by people’s independent web sites using RSS or JSON feeds. And, 2. A blogging platform that allows you to create a simple blog (with an emphasis on microblogging). Is this the right way to look at Micro.blog now and into the future? And if so, why tackle both problems rather than simply #1?
That’s the right way to think about it. What I found while developing Micro.blog is that just building a more open social network-like platform wasn’t enough. If we wanted to encourage people to blog more, we needed to make blogging itself much easier. The best way to do that is to also offer to host someone’s blog for them directly on Micro.blog.
Blogs hosted on Micro.blog started with an emphasis on microblogging, but they have improved significantly since we initially launched, and now offer many features competitive with other dedicated blog hosts. There are Micro.blog users who have their full web site hosted by Micro.blog because it’s just more convenient.
This second part of Micro.blog is also very important to grow the service as a business. I want to run Micro.blog for decades to come. The only way to do that — to pay for all the servers and other supporting services — is for Micro.blog to be profitable. Since we never want to show ads, offering paid plans such as blog hosting is a great way to go.
Would you be willing to share any interesting stats? Some that I’d personally be interested in tracking would be the most number of posts in an hour, the greatest number of signups in a day, stats like that.
And as a follow-up: As the platform (meaning the software, hardware, underlying services, backup routines, databases, etc.) become more complex surely you’ll need to expand from being the two-person team Micro.blog is currently. What position do you think the next full or part-time team member of Micro.blog will fill?
I don’t currently have many stats to share. We have been so busy improving the platform that we haven’t built anything to track things like spikes in the number of posts. There is a 500-user limit on new registrations per day. When we opened it up to the public, the limit was just 100 which was reached pretty quickly as people would share a link to their friends.
There are so many areas that we could use a larger team for, like system administration and planning how to scale the platform. As you noted, the first person to join Micro.blog was Jean MacDonald, our community manager. I hope that the community will continue to grow such that we’ll need additional curators to help manage features like the Discover section.
Facebook recently announced they were hiring 10,000 moderators, and I know Twitter has a large staff as well. I expect one mistake that these larger social networks made early on was hiring too many programmers, and not enough curators. For Micro.blog we always want people who can interact with the community and stay ahead of any issues.
Discover has already seen a few iterations. First, it was a simple list of users. Then it expanded to include photos posted by the community. After that, a human-curated list of posts was added. And now, hashtag-like emoji’s allow you to find posts on topics like books, music, and football. Did I miss anything? This must be a fun part of Micro.blog to tweak and see how the community responds. I know I’ve found it to be very fun to have open a few times during the day. Can you share a little about how posts end up in the Discover tab? Who is making those selections and what are the next steps?
I feel like the current iteration of Discover is by far the best yet. There were a couple problems with just featuring a list of users. You can only feature so many users, so we randomly selected users to show from the featured list. Those users would get a lot of attention but unless we continually update the list, it might not be enough people to fill your timeline with interesting posts if you just pick a few people to follow. The list got stale quickly as new people were joining the platform.
Now, throughout the day we skim through posts and replies and put them in Discover. This is a better reflection of the activity on the platform. It’s not all posts, but it’s a good snapshot of the kind of things people are posting about. It looks good and isn’t overwhelming. It’s a great way to find new users who just joined Micro.blog, too.
Emoji topics are a little different. Whenever Micro.blog sees a new post, it checks it for emoji and adds it to a collection. If an inappropriate post shows up, we can just remove it from the collection without effecting anything else about that post or user on Micro.blog. There are a limited number of emoji, which keeps everything simple. I don’t think it will get out of control like Twitter hashtag search results often do.
One aspect I’ve always loved about microblogging was that it could be consumed and participated with in realtime. A few examples that come to mind are backchannels for live TV events like awards shows, or for conferences and meetups, etc. Is this something the Micro.blog team thinks about much? Are there any apps, features, or other considerations that would be made specifically to foster realtime interactions for things like this?
I agree this is a natural fit for indie microblogging. Something like live sports might not appeal to everyone, so it would be useful for both tuning into those feeds or filtering them out. Over the weekend, we put the football emoji in the Discover section for people who were posting about the NFL playoffs, as a simple experiment for making current topics more discoverable.
There are myriad other things we could talk about like Pins, third-party applications, indieweb building blocks like Webmention, and the all new Micro.blog logo and app icon. Is there anything you’d wish to highlight? If so, please do. And lastly, what is something you wished I asked but didn’t that maybe you’d like to make sure people reading this interview know (feel free to allow this to be nothing)?
The third-party ecosystem and larger IndieWeb community are both really important. There are several third-party apps for Micro.blog in development now, for iOS and Android. When I was designing the Micro.blog API, I based it on JSON Feed, Micropub, and other common APIs so that third-party Micro.blog apps could also be adapted for other platforms. And likewise, Micro.blog benefits from many existing IndieWeb tools and open source software like WordPress. The more we can push forward the user experience for indie microblogging, making blogging more approachable, the stronger the open web will be.
Thanks Colin! It was great to have a chance to share some of our thoughts behind Micro.blog.
Thanks to Manton for taking the time to write thoughtful responses. If you haven’t yet given Micro.blog a try head on over to there and give it a whirl. You could very well make an impact on the type of place it becomes.
I would never outsource my content to some third party. I blog on my own domain using open source software (WordPress) that I run on a shared server that I can move if I want to. It is a bit of work to set this up but the benefits you get are enormous.
The above quote is coming from someone who was a major investor in, and active user of, Twitter. You can have both. You can tweet and enjoy using Twitter. You don’t have to boycott it to own your own content.
Over the last few months I’ve found the right balance for myself. I’m not syndicating anywhere* but publishing on my blog. I tweet from time-to-time, I post some photos to Instagram and Facebook from time-to-time, but I do all of that manually. I do so full-well-knowing that any of that content can disappear at any time. And I’d totally fine with it if it did, because everything I want to last is here on cdevroe.com.
* All of my posts do end up on micro.blog but that service is simply ingesting my RSS/JSON feed. I do not have to do anything special for that to work. If Twitter, Facebook, or Instagram did that I’d likely turn that on there too. But I’m tired of trying to keep up with their platform changes to write my own plugins, or even use plugins to do so. So I choose to manually POSSE and keep my sanity.
I went a bit crazy with Indieweb plugins and services to begin with. The fervour of the new follower. I’m cutting out the stuff I don’t need now or the the things that just don’t work the way I want them to. Manual seems best for some things.
My first impression is that micro.blog could be the new, simpler Technorati for the rising IndieWeb tide – a nice centralised way for people to discover each other’s posts and sites without losing the decentralised, own-your-data nature of the indieweb.
I have very fond memories of Technorati so I do not mind this comparison. Technorati helped expose people to the power of the indieweb at the time because it was a jumping off point to find some of the best content all over the web. It wasn’t a platform so much as a service. As Micro.blog grows, particularly out of the small blogger audience it currently has, it could fill this role very nicely – while at the same time being a solution for many to publish their own blogs.
/via Jonathan Lacour.
Chris Lovie-Tyler, from the other side of our planet:
After reading a handful of Colin Devroe’s posts (links at the bottom), I’ve made a few decisions.
I’m glad my posts, in which I was just thinking out loud and forming my own opinions on these matters, helped him to form his. I believe everyone should do whatever is right and sustainable for themselves.
There has to be a line, a point where a comment is just that and not a reply. It’s a question of semantics but not everyone’s answer to “what is a comment and where does it belong?” will be the same.
I struggle with this a lot.
It is likely the point I should have made in my post regarding Micro.blog becoming a commenting service (and the fact that I don’t like that). I don’t want to reply on my blog to every reply to my posts on M.b because then I would have dozens and dozens of posts on my blog that would be very tough for readers to follow contextually. I believe the commenting mechanism that has been around for decades, even un-threaded, is far more useful than dozens of desperate posts stitched together loosely with a link that says “in reply to”.
Webmention attempts to bridge that gap between post and reply but that also is tough to follow along if the thread gets unwieldy.
However, I also don’t want to reply to every reply on my posts directly on M.b either (though, I do from time-to-time) as that isn’t much better than using any other silo like Twitter or Facebook. Should M.b go away, all of those conversations would be lost.
This isn’t a new issue nor is it exclusive to M.b. If I replied on my own blog to other people’s posts on their own blogs (like I am in this post to Colin Walker’s blog) then one side of the conversation could disappear at any time. I can only control my side of the equation. But at least if I have my own blog I have control of that one side.
I think it is good that these topics are being discussed again. The same debates have been swirling since blogging began, they swelled again when the indieweb movement began to take shape, and I think they are happening again as a result of M.b’s growing community. I do not believe there is one single answer to many them. You have to do what is right and sustainable for you.
For now, here are my personal rules for replying to posts. These will most definitely change over time.
As an aside: I know some of you do not want to leave a public comment. I love getting reader emails. I get a fair number of them. And some of them have been excellent conversations. So please don’t hesitate.
* I no longer have a Twitter or Facebook account. I do have a M.b account but I’m beginning to wonder if I need one as I have my own fully functional weblog. If I didn’t and I wanted a microblog and didn’t want to use Twitter, I could see having an account. If I wanted a more fully featured blog I still believe WordPress is the best tool for that. Also, I’m sure as the M.b community grows it could mean that my content would be discovered by more people. I think M.b may end up being a thriving, well run, community and service. It is why I backed Manton’s efforts via Kickstarter. But, if I have my own blog, and if I really don’t care much about my content being discovered, then I see little reason to syndicate to it. For the time being I’m still going to as I want to see how the service matures.
As my own little corner of the web uncermoniously turned ten years old this year, it’s really starting to feel more like a garden than a piece of software. I certainly enjoy tending to it. I can plant what I like and with proper care it can grow into something useful.
First, how cool is his last name?
I like this analogy of comparing a personal web site to tending to your own personal garden.
I have only one reservation about the development of this IndieWeb stuff. While it is in progress, most of these websites have disabled regular comments, if they ever had them. Often there is also no contact information given, or it takes a lot of hunting on their websites to find it. So if one doesn’t have webmentions working on one’s own website, there is no obvious way of communicating with these folks about things they post. I have found that if they’re also on the Microblog website, one can post a message there, addressed to them. But that seems pretty round about, when an old school place to post a comment on their original post would be very easy to leave.
Please go to his site and read his entire post.
I read Ron’s post before making my decision to turn comments back on. Also, my email address is available on every page of my site. So if anyone would like to comment on anything on my site they should be able to do so both publicly and privately with ease.
Side note: One of the reasons we all turned off comments, aside from the benefits of disabling comments like more traffic to your site (I wrote this post 10 years ago!), is that people claimed that moderating comments is too much work. I no longer think that is an issue. Even if my blog became a popular place to comment I think I’d be able to keep up with it with the tools we have available now.
We’ve been improving Micro.blog’s support for Webmention. When you reply to a post on Micro.blog, from the web or iOS app, it will ping the site you’re replying to, giving that site a chance to include the comment.
Kudos to Manton as Webmentions seems to work beautifully is Micro.blog. The improvements show and the value is starting to show too. So I guess I just need to stop complaining. I’ve been harping on webmention for a little while. I feel terribly about it. Because I want it to work so badly and I’ve just been frustrated that is seems so inconsistent! So I plan to shut up now and sit down and get it working properly. I’ll likely do that within the next few weeks.
To see Micro.blog’s webmentions in action you can see a few on my posts there and here on my blog. I’m looking forward to their presentation being much more valuable on my blog. My email inbox is open for suggestions.
Yet there is still a problem, and that is the apparent insistence on the implementation of specific technologies as implied by the guides and documentation.
Go read his entire post. There are all sorts of “problems” with the IndieWeb and Walker lays some of them out nicely. (Remember, I told you to subscribe to his site.) He mentions that the entire thing can be confusing to non-developers. Well, I am a developer and while the protocols themselves aren’t impossible to grok if you spend some time reading or visiting the IndieWeb IRC chat, I have completely given up trying to support it because it is far too time consuming and nothing ever seems to work for every long.
I’m writing that out of frustration. Sorry. I know it can work. Look at Jeremy Keith’s site. I’m so jealous. He’s put tons of time into making so many of these things work. I want what he has. I simply have chosen not to spend nearly as much time as Jeremy has to get all of this stuff to stick together.
Here is just one example. I have webmention turned on for my site via the “official” WordPress plugin. It doesn’t work. Colin Walker has linked to my site several times. And I to his. His webmentions have yet to show up on my site. Mine have yet to show up on his. And his site isn’t the only site that has linked to me and the only way I’ve found out is via my Jetpack Stats (which I dislike having on but I keep it on for this very purpose). I’m certain that there is a logical reason webmentions aren’t working but I don’t feel like looking under the hood again (and again and again) to figure it out.
I’m not the type of person that needs everything to be easy. I don’t mind some configuration here and there from time-to-time and if something is really worth the effort I’ll even write the code myself. But supporting the IndieWeb (even just a single piece of it like Webmention) has exhausted this developer to the point of giving up.
Not exactly sure what Colin Devroe means when he says he’s “just going to publish her on my blog”. I guess that means he’s not interested in people, like me, publishing our comments on our blogs. Of course there’s no compulsion to POSSE to be part of the #indieweb, and if you don’t want to, you shouldn’t. But I hope he’ll still accept webmentions.
On the contrary, I’d much prefer people publish on their blogs in response to my posts rather than on social media. Which is why I do not plan to continue to POSSE. If people find my posts or subscribe to my blog great. If they don’t, that’s ok with me too.
I’ll agree with Jeremy that you don’t need to syndicate content or even backfeed to be a part of the Indieweb. Particularly when you’re already doing the primary tenets: own your domain, own your data, publish on your own site. (Ideally this is what everyone should be doing in conjunction with webmentions and then all the social networks would be superfluous.
Exactly. If I publish here and people link to it in response, I don’t need any social networks.
So, I’m going to support webmention. Not just accepting them and sending them (as I do now), but displaying them also. I need to find a little time to do that since web mentions generally look terrible by default but when I do I’ll report back.
Thanks to Jeremy and Chris for chiming in.
You may have noticed a slight uptick in my publishing. That’s because I am, once again, coming back to my blog as the central place that I publish. Except this time I care far less about any of the content getting to any social networks.
It is simply too exhausting to get working correctly. And once you have everything sort of working right, something about these networks change or a new one arises (like Mastodon). So rather than stifle my publishing based on getting each gear properly greased I’m giving up. Sorry indiewebbers. I’m just going to publish here on my blog.
I don’t care if anyone on Twitter or Facebook or Instagram sees or reads any of this. I just want my blog back.
So does Dave Winer:
Before 2010, on my blog, I could have long and short items. I could use HTML. Link to as many places I wanted, where ever I wanted. There was no character limit, so the short items could grow if they needed to. The same format could accommodate post-length bits with titles that were archived on their own pages. Every item appeared in the feed, regardless of length, regardless of whether it had a title.
I plan on turning off a bunch of the code I have running here on my blog to support these networks too. I’m going old school.
If you like my blog subscribe. If not, that’s OK too.
I love that blogs can scale from the trivial to the important. The microblog post about what you had for breakfast. The half-baked rant about something you’re passionate about. And sometimes, the rare essay that really hits the mark and makes people think.
Publishing most of my “tweets” here first has led to some frivolous posts. But, I wouldn’t have it any other way. Takes the pressure off of me to have every post be significant before hitting publish.
Last night Tucker Hottes, Den Temple and I held the first Homebrew Website Club at The Keys in Scranton, PA. I really appreciate that HWC will force me to set aside some time to work on my personal site since it is often neglected for more pressing projects.
During HWC I began trying to fix my crufty URLs for post format filtering on WordPress. Unless I’m missing something, it doesn’t appear that WordPress has “standard” post format filtering out of the box. It can filter by every other post format – statuses, audio, images – but doesn’t for standard posts. I’m almost sure I am missing something. If anyone knows how to do this more elegantly please let me me know. However, I’ve added this functionality myself months ago and now those URLs are cruft free. You can see them in my sidebar.
To do this isn’t trivial. Here are the steps you need to follow:
I’m glad HWC gave me the time to finally fix this as it had been bothering me for a few months. Looking forward to the next HWC where I’ll tackle a few more Indieweb things I’ve been meaning to bolt on.
I’m looking forward to tonight’s first Homebrew Website Club in Scranton. Details here: https://indieweb.org/events/2017-02-08-homebrew-website-club
I tried to fix this by unfollowing just about everyone I know personally and following as many talented photographers as I could find. The result of that decision: enormous inspiration to get out of the house and travel, but also to a confidence-shattering reflection on my own photos. Now, instead of posting what I thought was one of my best photos, I opt to hold back because it doesn’t measure up.
His example of how his neighbor’s photo of their morning coffee garners more likes than his carefully curated vacation photo is also another type of pressure or anxiety that can come from using networks like Instagram. It is why I hate “likes”. I’ve always hated likes. When I post to Instagram I turn off commenting (same for my blog). If I could turn off likes too I would. “Likes” create a false sense of value. I’m still struggling with whether or not I want to be pulling the “likes” and “shares” back to my blog from Twitter and Facebook like I have been using the Indieweb Backfeed. I have it on right now but I’m considering turning it off. I may also turn off POSSE soon but I fear my audience will shrink substantially. This is a topic for another post.
If I could turn off commenting on Facebook I would. It isn’t because I don’t want to read people’s comments, on the contrary, I want quality comments (like the one I’m linking to from Josh right now or the one from Chris Aldrich on this same topic). Open network discussion hasn’t fostered quality discourse.
One other note about Instagram and “likes”; their feed algorithm is wreaking havoc with people’s expectations when posting to the service. People that used to get 10,000 likes per photo are now getting very disparate results. One will get a few thousand, the next 10 thousand, some nearly zero. The algorithm is choosing which photos get popped into people’s feed. Some photos are never seen by your followers. So if you were valuing your work based on “likes” you no longer can. And if you think this isn’t a problem imagine someone that makes their living based on having 7M Instagram followers that suddenly cannot guarantee their sponsors any metric at all.
I think this is why I like Instagram Stories so much. When I post to stories I see exactly who viewed each post (good) and if someone wants to reply their reply comes to me privately (also good). The drawback, however, is that the discourse that happens in private isn’t of any value to the public. I’m not sure how to fix that without reintroducing the issues we see on Facebook and Instagram.
Next Wednesday I’ll be hosting the first Scranton-based Homebrew Website Club at Condron Media‘s headquarters on Penn Avenue. There are other locations HWC will be happening on that day too. If you have your own site and I you care to work on it in anyway at all please do stop by.
Homebrew Website Club is not a typical meetup, like say a WordPress meetup, in that you stop by to learn a particular topic (although I have no doubt you will learn if you attend one). It is more a reoccurring time that is set aside to allow you to work on your personal web site. Perhaps you’ve been meaning to finish up a blog post that has been in draft for weeks, or you need to fix a theme issue, or you want to do something more complex – whatever it is, HWC is your opportunity to do that while sitting next to other people that are trying to do the same.
I’ll be using the this time, each meeting, to fit more Indieweb building blocks into my personal site. I’ve recently added Backfeed, POSSE, Webmention, and others. And I plan on continuing to tweak them to get them just the way I’d prefer. Also, I plan on pushing my code and work back out into the world through this blog, my Github account, and #indieweb on IRC.
So, if this is something you’re into. Drop by.
Jonathan LaCour, SVP, Product & Technology at Dreamhost:
We’d like to make it as easy as possible to launch a WordPress-powered microblog on DreamHost that integrates well with Manton’s upcoming Micro.blog service. In order to support that mission, DreamHost is kicking in a $5,000 pledge to the Kickstarter.
Nice move Dreamhost.
This year all of my posts, replies, and retweets on Twitter will be coming from this blog and not using the Twitter app (#OwnYourData). That probably means doing it at the end of the day. I’m hoping that will make them more considered (something we may all want to be in the coming years).
I have most notifications off (and have for years). And I plan on keeping it that way.
But, I’m not doing so well on what he’s talking about in the quoted bit above. POSSE, as the indiewebbers call it, is posting on my site here and then syndicating it elsewhere. My blog posts are syndicated to Twitter the way I’d like but not Facebook or Instagram (the other two networks I use the most). And I also find myself lazily posting directly to Twitter rather than through my site because the apps are so easy to use. I wish I did better.
Here is what I would need to do to pull this off personally:
I wouldn’t have to do all of these to be happy, but I’d at least like to push the content to those networks. Maybe I’ll start there.
Manton Reece has added a thoughtful stretch goal to Micro.blog’s Kickstarter campaign:
If the Kickstarter reaches $80,000, I will use some of the money to make my very first part-time hire for Micro.blog: a community manager. The community manager will help set the tone for the service, work on documentation and best practices, and be responsible for curation when Safe Replies fails to automatically catch emerging problems.
Safe Replies sounds like something Twitter should have had a long time ago. Run over there and help Manton reach this new goal.
Manton Reece recently published an update to Micro.blog’s Kickstarter showing a video demonstration of the iPhone app he’s creating for the service. He mentions a really important point that I think many are missing (as I mentioned just a few moments ago). He says (at 53 seconds into the video):
Now, you can have Micro.blog host a microblog for you. That’s what the paid plan is about that is mentioned in some of the reward tiers on Kickstarter. It is super easy to get started that way. But you can also bring an existing blog. My personal blog, for example, uses WordPress. And so, when I use Micro.blog the iPhone app for the first time it asks me where my WordPress blog is and then I can post directly to my own site.
I’ve been following along with this project since Manton first mentioned it nearly two years ago so I’ve been aware of what he was building. I just don’t think the information on the site or on the Kickstarter has made that clear for people that don’t totally understand the underpinnings of the web. (Though, Micro.blog is arguably be built for those that do.)
The iPhone app looks very nice. Especially for a first public release.
We envisioned a pool of differentiated, fast-growing third-party applications would sustain the numbers needed to make the business work. Our initial developer adoption exceeded expectations, but that initial excitement didn’t ultimately translate into a big enough pool of customers for those developers.
I’ve been a paying subscriber to App.net for the entire life of the platform (that is, until they cancelled my subscription this week).
When App.net launched many were drawing a line of comparison between it and Twitter. And since this announcement I’m seeing many drawing a line of comparison between App.net and Micro.blog. This isn’t an apples-to-apples comparison.
If you read Dalton’s vision above, it doesn’t read anything at all like Twitter or Micro.blog.
App.net was an API for application developers to build on top of. Yes, something Twitter-like could be build on top of it. But so could so many other things. It had a data storage service, a push notification service, and even a crowd-funding feature called Backer that would, presumably, allow developers to pre-charge for new features for apps.
App.net was a very ambitious platform that, I believe, got pigeon-holed into a Twitter comparison because they created Alpha – a Twitter-like microblogging platform – as a demonstration of their own API. I think this muddied their messaging to the point where most people would describe App.net as a Twitter alternative.
Manton Reece’s forthcoming Micro.blog is not anything at all like App.net. Though, many are confused about Micro.blog similar to how many were confused about App.net. (I’ve had at least three conversations about Micro.blog where people have no idea what it will do.) They are comparing it to Twitter even though Manton doesn’t usually draw that line himself. And I think he will have to find a way to communicate its decentralization and the fact that it will work with your existing blogging platform so it too doesn’t get packaged and framed as simply a Twitter replacement.