Rebooting Indigenous for iOS, adding multiple user support to the Drupal IndieWeb module and kickstarting ActivityPub module thanks to a grant as part of @NGI4eu by the @NLnetFDN.
Many common content management systems support Webmention either out of the box or with plugins including: our friend WordPress, Drupal, WithKnown, Grav, and many others.
(Ownership of your Open Pedagogy Anyone? Who needs invasive corporate social media to interact online now?)
NEW #Drupal #indieweb release— scrappy new year - think creatively (@HongPong) January 14, 2020
Microformats for Drupal 8. v 1.0-alpha1https://www.drupal.org/project/microformats
Many thanks to @mlncn @agaric @drutopiaforgood for contributing time and patches to complete this initial feature set which provides configurable H-card sitewide markup
With the rise of social platforms and an uptick in threatening comments, the newsroom is taking reader engagement in a different direction.
We analyzed our Disqus data and we found that roughly 17,400 comments were made on our site in 2019, but 45% came from just 13 people. That data tells us that social media, email, phone calls, letters to the editor, our Crosscut events and an occasional visit to the newsroom are far better tools for us to hear about your concerns, story ideas, feedback and support.❧
The Disqus data statistics here are fascinating. It also roughly means that those 13 people were responsible for 600+ comments on average or roughly 2 a day every day for the year. More likely it was a just a handful responsible for the largest portion and the others tailing off.
Sadly missing are their data about social media, email, phone, and letters to the editor which would tell us more about how balanced their decision was. What were the totals for these and who were they? Were they as lopsided as the Disqus numbers?
Annotated on January 08, 2020 at 04:33PM
In the meantime, stay in touch with Crosscut by:
Liking us on Facebook
Following us on Twitter
Following us on Instagram
Chatting with us on Reddit
Signing up for one (or all) of our newsletters ❧
It seems like they’ve chose a solution for their community that boils down to pushing the problem(s) off onto large corporations that have shown no serious efforts at moderation either?
Sweeping the problem under the rug doesn’t seem like a good long term answer. Without aggregating their community’s responses, are they really serving their readers? How is the community to know what it looks like? Where is it reflected? How can the paper better help to shape the community without it?
I wonder what a moderated IndieWeb solution for them might look like?
Annotated on January 08, 2020 at 04:42PM
It would be cool if they considered adding syndication links to their original articles so that when they crosspost them to social media, at least their readers could choose to follow those links and comment there in a relatively continuous thread. This would at least help to aggregate the conversation for them and their community while still off-loading the moderation burden from their staff, which surely is part of their calculus. It looks like their site is built on Drupal. I would suspect that–but I’m not sure if–swentel’s IndieWeb Drupal module has syndication links functionality built into it.
Rather than engaging their community, it almost feels to me like they’re giving up and are allowing a tragedy of their commons when there may be some better experimental answers that just aren’t being tried out.
The worst part of this for me though is that they’ve given up on the power of owning and controlling their own platform. In the recent history of journalism, this seems to be the quickest way of becoming irrelevant and dying out.
An in-depth analysis of how Drupal's development was sponsored between July 1, 2018 and June 30, 2019.
I’ve been running versions of both for many years and they each have their pros and cons. In terms of IndieWeb support they’re both very solid. Why not try them both for a bit and see which appeals to you more? Depending on your skill level and what you’re looking for in your site you may find one easier to run and maintain than another.
Personally I’ve used WithKnown (I’ve used it for multiple sites since it started) in a more “set it and forget it” mode where I just post content there and worry less about maintenance or tinkering around. On my WordPress site I tend to do a lot more tinkering and playing around, particularly because there is a much larger number of plugins available to utilize without writing any of my own code. Lately I am kind of itching to play around with Drupal again now that it has a pretty solid looking IndieWeb module (aka plugin).
Building toward an independent web isn’t something one does overnight anyway. Small incremental steps will eventually win the day. I like the way that Brent Simmons describes what he’s working on and why. Perhaps that could be a useful model in addition to the related idea of itches?
If it helps you might take your passions for “diversity, inclusion, equity & justice” and inject them into the space? I would always welcome help in those areas for the broader community.
Doing maintenance on Display Suite today, thanks to @dropsolid ! One day a month does make an impact, so let's talk to see if I can get more days :) #drupal
I'm pulling the plug on Facebook because of their recent privacy violations — which got me thinking about what is next for the Open Web.
While it still has a lot in common with Drupal, it has reconfigured the core to include some of the most commonly used and requested plugins and they’ve done their best to make it prettier and easier to use for hobby-ists and bloggers as well as small businesses and non-profits that don’t need all the additional overhead that Drupal brings. It’s also got a small but very dedicated community of developers and users.
I’ve also been hearing some great things about Craft CMS, which you highlight, as well as Perch by Rachel Andrew and Drew McLellan.
It’s nice that there are mass-scale projects like WordPress, WithKnown, Get Perch, Grav, Drupal, and a few others which have one or more “IndieWeb-centric” developers working on them that allow those without the coding skills to jump in and enjoy the additional freedom and functionality. The occasional drawback is that those big-hearted developers also fit into the broader fabric of those massively distributed projects and sometimes their voices aren’t as well heard, if at all.
I’m aware of the disruption of the Gutenberg Editor within WordPress v5.0 and how it applies to those using IndieWeb technology on WordPress. I’m sure it will eventually get sorted out in a reasonable fashion. Sadly, throwing out the baby out with the bathwater as it comes to WordPress and IndieWeb may not be the best solution for many people and may actually be a painful detriment to several hundreds.
While it would be interesting to see a larger group of developers converge on building an open and broadly used IndieWeb system as you suggest, it takes a massive amount of work and community collaboration to get such a thing moving. I think this bears out if you look at the lay of the land as it already exists. Just think of the time effort and energy that the core IndieWeb community puts into the tremendous amount of resources that exist today.
Looking back on the past 4+ years of IndieWeb within the WordPress community, I’m really amazed to see exactly how far things have come and where things currently stand. There used to be a dozen or more pieces that required custom code, duct tape, and baling wire to get things working. Now it’s a handful of relatively stable and well set up pieces that—particularly for me—really makes WordPress deliver as an open source content management system and next generation social medial platform that aims to democratize publishing. In terms of building for the future, I suspect that helping to bring new people into the fold (users, developers, designers, etc.) will increase and improve the experience overall. To some degree, I feel like we’re just getting started on what is possible and recruiting new users and help will be the best thing for improving things moving forward. IndieWeb integration into large-scale projects like WordPress, Drupal, etc. are very likely to be the place that these ideas are likely to gain a foothold in the mainstream and change the tide of how the internet works.
While it may seem daunting at times, in addition to the heroic (part-time, it needs to be noted) developers like Mathias Pfefferle, David Shanske, Micah Cambre, Michael Bishop, Ashton McAllan, Jack Jamieson, Ryan Barrett, Peter Molnar, Amanda Rush; enthusiastic supporters like you, Greg McVerry, Aaron Davis, Manton Reece; and literally hundreds of others (apologies to those I’ve missed by name) who are using and living with these tools on a daily basis, there are also quieter allies like Brandon Kraft, Ryan Boren, Jeremy Herve and even Matt himself, even if he’s not directly aware of it, who are contributing in their own ways as well. Given the immense value of what IndieWeb brings to the web, I can’t imagine that they won’t ultimately win out.
If it helps, some of the current IndieWeb issues pale in comparison to some of the accessibility problems that Gutenberg has neglected within the WordPress community. Fortunately those a11ys are sticking with the greater fight to make things better not only for themselves, but for the broader community and the world. I suggest that, like them, we all suit up and continue the good fight.
Of course part of the genius of how IndieWeb is structured: anyone is free to start writing code, make better UI, and create something of their own. Even then they benefit from a huge amount of shared work, resources, and simple standards that are already out there.
After months of reading, experimenting and a lot of coding, I'm happy that the first release candidate of the Drupal IndieWeb module is out. I guess this makes the perfect time to try it out for yourself, no? There are a lot of concepts within the IndieWeb universe, and many are supported by the module. In fact, there are 8 submodules, so it might be daunting to start figuring out which ones to enable and what they exactly allow you to do. To kick start anyone interested, I'll publish a couple of articles detailing how to set up several concepts using the Drupal module. The first one will explain in a few steps how you can send a webmention to this page. Can you mention me?