This looks interesting, a script to post from WordPress to Mastodon by Jan Boddez. I am not ready to post from WP as AP and have it be its own Mastodon account. I want to be able to post from WP into my existing Mastodon instance. This as I use Mastodon as a semi shielded channel and WP would for now be fully public. So will have to try this out.
A metaphor and a an addition related to my earlier wonderings about Mastodon and upload filtering:
It’s as if because of a law requiring hammers to be registered, you’re wondering if you’re going to register your screwdriver. Just because some people use the handle of their screwdriver to hit a nail occasionally, and ignore its primary functionality.
Yes there are very large Mastodon instances, the top 3 hold over 50% of all users. These instances might well fall within scope of the EU Copyright Directive. But ‘fixing’ the underlying ActivityPub protocol or federation isn’t the issue here. Fixing big instances is. In fact most Mastodon users, as they are on the biggest instances, don’t use federation at all because most of their interaction is within the same instance. Mastodon.social, pawoo.net and mstdn.jp, the 3 biggest instances, I’d argue are hardly part of the fediverse, despite e.g. mastodon.social being its poster child and point of entry for most.
Don’t make someone’s bloated instance’s issue to be a huge issue for the fediverse as a whole
He says that these decentralised federated applications are trying to mimic the existing platforms too much.
They are attempts at rebuilding decentralized Facebook and Twitter
This tendency has multiple faces
I very much recognise this tendency, for this specific example, as well as in general for digital disruption / transformation.
It is recognisable in discussions around ‘fake news’ and media literacy where the underlying assumption often is to build your own ‘perfect’ news or media platform for real this time.
It is visible within Mastodon in the missing long tail, and the persisting dominance of a few large instances. The absence of a long tail means Mastodon isn’t very decentralised, let alone distributed. In short, most Mastodon users are as much in silos as they were on Facebook or Twitter, just with a less generic group of people around them. It’s just that these new silos aren’t run by corporations, but by some individual. Which is actually worse from a responsibility and liability view point.
It is also visible in how there’s a discussion in the Mastodon community on whether the EU Copyright Directive means there’s a need for upload filters for Mastodon. This worry really only makes sense if you think of Mastodon as similar to Facebook or Twitter. But in terms of full distribution and federation, it makes no sense at all, and I feel Mastodon’s lay-out tricks people into thinking it is a platform.
This type of effect I recognise from other types of technology as well. E.g. what regularly happens in local exchange trading systems (LETS), i.e. alternative currency schemes. There too I’ve witnessed them faltering because the users kept making their alternative currency the same as national fiat currencies. Precisely the thing they said they were trying to get away from, but ending up throwing away all the different possibilities of agency and control they had for the taking.
Dump mimicry as design pattern
So I fully agree with Jerome when he says distributed and federated apps will need to come into their own by using other design patterns. Not by using the design patterns of current big platforms (who will all go the way of ecademy, orkut, ryze, jaiku, myspace, hyves and a plethora of other YASNs. If you don’t know what those were: that’s precisely the point).
In the case of Mastodon one such copied design pattern that can be done away with is the public facing pages and timelines. There are other patterns that can be used for discoverability for instance. Another likely pattern to throw out is the Tweetdeck style interface itself. Both will serve to make it look less like a platform and more like conversations.
Tools need to provide agency and reach
Tools are tools because they provide agency, they let us do things that would otherwise be harder or impossible. Tools are tools because they provide reach, as extensions of our physical presence, not just across space but also across time. For a very long time I have been convinced that tools need to be smaller than us, otherwise they’re not tools of real value. Smaller (see item 7 in my agency manifesto) than us means that the tool is under the full control of the group of users using it. In that sense e.g. Facebook groups are failed tools, because someone outside those groups controls the off-switch. The original promise of social software, when they were mostly blogs and wiki’s, and before they morphed into social media, was that it made publishing, interaction between writers and readers, and iterating on each other’s work ‘smaller’ than writers. Distributed conversations as well as emergent networks and communities were the empowering result of that novel agency.
Jerome also points to something else I think is important
In my opinion the first step is to build products that have value for the individual, and let the social aspects, the network effects, sublime this value. Value at the individual level can be many things. Let me organise my thoughts, let me curate “my” web, etc.
Although I don’t fully agree with the individual versus the network distinction. To me instead of just the individual you can put small coherent groups within a single context as well: the unit of agency in networked agency. So I’d rather talk about tools that are useful as a single instance (regardless of who is using it), and even more useful across instances.
Like blogs mentioned above and mentioned by Jerome too. This blog has value for me on its own, without any readers but me. It becomes more valuable as others react, but even more so when others write in their own space as response and distributed conversations emerge, with technology making it discoverable when others write about something posted here. Like the thermometer in my garden that tells me the temperature, but has additional value in a network of thermometers mapping my city’s microclimates. Or like 3D printers which can be put to use on their own, but can be used even better when designs are shared among printer owners, and used even better when multiple printer owners work together to create more complex artefacts (such as the network of people that print bespoke hand prostheses).
It is indeed needed to spend more energy designing tools that really take distribution and federation as a starting point. That are ‘smaller’ than us, so that user groups control their own tools and have freedom to tinker. This applies to not just online social tools, but to any software tool, and to connected products and the entire maker scene just as much.
The Mastodon community worries about whether the new EU copyright directive (which won’t enter into force for 2 years) will mean upload filters being necessary for the use of the ActivityPub protocol.
I can’t logically see why that would be, but only because I don’t compare Mastodon to e.g. Twitter or Facebook. Yet if you do then the worry is logical I suspect.
Mastodon is a server and a client for the ActivityPub protocol. In a fully distributed instance of Mastodon you would have only a small group of users, or just one. This is the case in my Mastodon instance, which only I use. (As yet the Mastodon universe isn’t very distributed or decentralised at all, there’s no long tail.)
The ActivityPub protocol basically provides an outbox and inbox for messages. In your outbox others can come get messages you make available to them and your server can put messages in your outbox into someone else’s inbox itself.
The Mastodon server can make what you put into your outbox publicly available to all that way. Others can put messages for you in your inbox and the Mastodon client can show publicly what you receive in your inbox.
But making anything public isn’t necessary at all. In fact I don’t need my public facing profile and message timeline on my Mastodon instance at all. They are non-essential. Without such pages there’s no way to argue that the messages I receive in my inbox are uploaded by others to a platform, and falling within scope of a potential need for an upload filter.
My Mastodon instance isn’t a platform, and the messages others send to it aren’t uploads. The existence and form of other ActivityPub clients and servers demonstrates that neatly. I currently send ActivityPub messages from my weblog as well, without them being visible on my blog, and I can receive them in my Mastodon, or any other AP client without them being visible for others, just as I can read any answers to that message on the back-end of my blog without it being visible to anyone but me and the sender(s). Essentially AP is more like one-to-one messaging with the ability to do one-to-many and many-to-many as well.
The logical end game of decentralisation is full distribution into instances with only individuals or tight knit groups. Federated where useful. The way the Mastodon client is laid out (sort of like Tweetdeck) suggests we’re dealing with a platform-like thing, but that’s all it is: just lay-out. I could give my e-mail client a similar lay-out (one column with mail threads from my most contacted peers, one with mails just to me, one with all mails sent through the same mail server, one with all mails received from other mail servers by this one.) That would however not turn my mail server plus client into a platform. It would still be e-mail.
Mastodon’s lay-out is confusing matters by trying to be like Twitter and Tweetdeck instead of being its own thing, and I posit all ‘upload filter’ worries stem from this confusion.
I just deleted my previous account on Mastodon.cloud, which completes the move to email@example.com, my personal Mastodon instance.
I think this is a false dilemma, Bernd.
I’d say that it would be great if those extremists would see using a distributed tool like Mastodon as the only remaining viable platform for them. It would not suppress their speech. But it woud deny them any amplification, which they now enjoy by being very visible on mainstream platforms, giving them the illusion they are indeed mainstream. It will be much easier to convince, if at all needed, instance moderators to not federate with instances of those guys, reducing them ever more to their own bubble. They can spew hate amongst themselves for eternity, but without amplification it won’t thrive. Jotted down some thoughts on this earlier in “What does Gab’s demise mean for federation?”