Micro.blog has some cool features that many users are not aware of. (They’re not really hidden, but that made for a better title than “not especially well-known.”) Here are some of my favorites:
Tag: Micro.Blog
David Shanske from david.shanske.comAfter a gap of over a year, we resumed our IndieWeb podcast and got together to discuss what has been going on, how we have been building the community during the pandemic, and about our topic of micro.blog. There is also a video attached this time.
https://archive.org/download/indieweb-podcast-e…
Great to have you both back. I agree with you David about Micro.Blog in regards to being able to easily write back responses to your own self-hosted blog. I also don’t mind the off the cuff style.
Some interesting changes to WordPress functions.
Social media can be a great space to share ideas, however not every space is helpful with connecting the dots. Although you can trace a thread through a series of Tweets, you are not always able to link to points of context and clarification. For me, this is one thing that I like about Micro.Blog’s use of Markdown. Clearly, not as rich as WordPress, but much better than Twitter or Google+(rip).
Chris Aldrich is a modern-day cyberneticist, a trained biomedical and electrical engineer, and a talent manager/producer who has a “horrible IndieWeb hobby that probably takes up more time than it should.”
We talk about how he got into the entertainment business by building a 3D heart, and how he came to the IndieWeb via one of Leo Laporte’s shows on TWiT. We commiserate about the difficulty of getting people to move from Facebook to the IndieWeb, especially our parents.
Chris, I feel kind of boring after listening to your Micro.Blog conversation. Although I also wonder if I was just born at the wrong time? Maybe that needs to be another itch, be more interesting.
We’ve been talking for a while about offering a “teams” plan on Micro.blog that would be great for small businesses, schools, and family blogs. With more people working from home, we’re already adding podcast hosting to all plans through April, and we think that podcasts and short videos could be valuable tools for teachers who are adapting their lesson plans for online classes.
This is a great initiative Manton.
Just a quick question for the future, what would happen to accounts at the end of the 6-months? Or at the end of the month of free podcasting? Do those posts and podcasts get hidden in the backend? Just wondering.
You can now optionally have your replies on your own blog, with reply permalink URLs at your own domain name.
Manton, what if anything does this mean for self-hosted users?
I’m going to figure out the right way to incorporate this into my flow now. I think I’ll start by trying to import my Instagram archive. Then I’ll need to work out a mobile solution and determine how this may all fit as a separate piece from my main site.
The update to this IndieWeb plugin provides better support for use with Micro.blog syndication along with a handful of additional improvements
Thank you Chris for the explanation on the change. I had seen David Shanske’s post about the update to Syndication Links, but was confused how this was different from using a particular tag as a sort of trigger.
We need a new approach. Not controlled only by algorithms, but also not a walled garden that limits distribution of content. We need a system that prioritizes curation while preserving the freedom to publish outside of silos, with APIs based on the IndieWeb that are open by default instead of locked down with developer registration.
Manton Reece builds on the metaphor of the web as a garden. Discussing the development of Micro.Blog, Manton Reece discusses the idea of open garden as an answer to the walled garden.
If you’re a blog author and you’re adding any significant commentary, the RSS feed should point back to your site.
If you’re an RSS client developer, the difference between link posts and full posts should be exposed in the UI.
I find it interesting to read about the ‘evolution’ as I am not sure I ever considered either of these scenarios. I started by experimenting with post formats and then post kinds. It makes me wonder how deliberate some of these developments are?
Domain names are the key to content ownership. This is a fundamental part of Micro.blog’s architecture, not something that was tacked on as an afterthought. I’ve written more about owning your content here, which is one part of the solution to moving beyond today’s social networks.
At least with the option of webmentions there is the possibility of being notified, even if you do not have an explicit identity in Micro.Blog. There is not even the possibility of knowing what conversations you are a part of in spaces like Facebook.
does micro.blog provide users any feeds (RSS, JSON, etc.) of the sites the’re subscribed to for reading in a reader that isn’t necessarily micro.blog’s primary interface?
Chris Aldrich (boffosocko.com)I might suggest that while some people might be framing micro.blog as a replacement for Facebook or Twitter, the better framing is that micro.blog is really what you were hoping it might be. It is a traditional web host with its own custom content management system that supports web standards and newer technologies like Webmention, Micropub, WebSub, and pieces of Microsub. Or similarly and more succinctly, Micro.blog is a turnkey IndieWeb CMS that allows users to have a website without needing to manage anything on the back end.
Last week we launched support for the ActivityPub API in Micro.blog.
A self-hosted, single-user, ActivityPub powered microblog. – tsileo/microblog.pub
I rolled out a few Webmention improvements to Micro.blog today
Kicks Condor (kickscondor.com)I don’t really see the difference between using FTP to pass your stuff ‘in’/‘out’ of a public_html folder and using Micro.blog’s API to pass your stuff ‘in’/‘out’. If you can get your stuff ‘in’ and ‘out’—isn’t that the key? The API is just a different kind of FTP.
I just joined @manton micro.blog community. Been syndicating to micro.blog but with @Twitter API changes announced and the total inaction on approving new dev apps or unsuspending my current syndication application it is clear Twitter won’t be the place for #IndieWeb POSSE model.
Greg, are you syndicating to Twitter from Micro.blog or have you started a hosted blog there?