Social media, blogging, tweeting, facebooking, web design, and all the stuff that isn’t here yet. Subcategories highlight some areas of particular expertise.
Je suis en train de regarder Micro.blog — un service super simple qui permet de poster des choses qui ressemblent à des statuts facebook ou même des articles de blog si on veut s’étendre, avec liens et photos. Et les choses publiées “apparaissent” comme des publis dans les réseaux sociaux “fédérés”, autres que facebook donc: Mastodon, Bluesky, Threads.
On peut s’abonner pour suivre d’autres microblogs mais aussi n’importe quoi qui produit un fil RSS (comprendre: n’importe quoi ressemblant un peu à un blog, généralement, sorry pour le jargon technique).
Ça coûte entre 1 et 5 dollars par mois pour les versions de base (micro.one est à 1$).
Pour les gens qui cherchent une alternative “techniquement simple” à une page facebook ou même à un profil facebook, ça vaut la peine de regarder.
Bien sûr, ce qu’on n’y trouve pas, c’est tous les liens sociaux existants qu’on a sur facebook, on ne peut pas les “exporter”. Mais on peut aller dans ce sens: déjà, il y a des tas de gens avec qui on est connectés sur facebook qui sont déjà sur threads, mastodon, bluesky ou autre – on peut donc s’y connecter là. Ensuite, il faudrait que je regarde s’il y a moyen “d’importer” un microblog dans une page facebook, comme je le fais pour mon blog Climb to the Stars (cette page-là elle se fait toute seule, par exemple; chaque fois que je publie quelque chose sur mon blog, ça fait une publi sur la page facebook).
Mais quel intérêt, à ce moment-là, me direz-vous? Si c’est pour publier ailleurs un truc qui finit quand même dans facebook pour toucher les gens qui y sont? Eh bien, c’est que le jour où facebook vous tire la prise, comme ils ont fait pour moi le 22 août, les dégâts sont bien moindre. Aussi, au fur et à mesure que les gens se détachent de facebook et quittent la plateforme (croyez-moi, c’est en train de venir), eh bien vous serez déjà “là ailleurs” pour les accueillir.
En passant, cet article de blog a commencé comme une publi facebook. C’est un exemple typique de ce dont je parle dans ma série “Rebooting The Blogosphere“: on est sur facebook (ou Mastodon, ou LinkedIn, ou autre), on se dit qu’on va vite écrire un petit truc, et on finit par pondre une demi-douzaine de paragraphes. En tous cas, c’est ce qui m’arrive régulièrement à moi.
Les gens me disent souvent: un blog, j’y pense, mais bon je sais pas quoi y écrire, ou je sais pas si j’arriverais… beaucoup d’entre vous sur facebook, vous le faites déjà en fait. Vous êtes déjà en train de “bloguer”, si on veut, sauf que vous le faites quelque part où ce que vous écrivez ne vous appartient pas. La distinction semble académique jusqu’au jour où, justement, Facebook décide pour xy raisons que vous êtes persona non grata, et refuse de répondre au téléphone quand vous souhaitez réclamer…
De mon côté, je réfléchis sérieusement à utiliser micro.blog pour les pages facebook de mes chats, par exemple (voir celle d’Oscar et celle de Julius).
Si ça vous parle et que vous souhaitez un coup de pouce pour vous y mettre, faites-moi signe!
Et si vous avez des questions sur ce que je raconte, y compris parce que ce n’est pas convainquant… questionnez, questionnez…
Et si vous avez sur votre radar des services autres que micro.blog qui pourraient faire l’affaire, dites-moi – ceci n’est qu’une réflexion préliminaire 🙂
(J’ai numéroté cet article parce que je pense faire une série “sortir de facebook”.)
In parts 1 and 2 of this series, I covered some types of activities (reading, writing, responding, sharing) that come into play in the text-driven social web, as well as the different flavours of interaction that make up our online relations (more or less synchronous, and related to that, contribution length in those exchanges).
What this is all about is figuring out how blogging can learn from what made “The Socials” (which became the big capitalist social networks we all know) so successful, to the point that many die-hard bloggers (myself included) got sucked up in the socials and either completely abandoned their blog, or left it on life-support. I believe that understanding this can help us draft a vision for how things in the “open social web” (I’ll keep calling it that for the time being) can work, now or in the near future, to give us the best of both blogging and the socials, without requiring that we sell our souls or leave our content hostage to big corporations.
So today is part 3, which I’ve called “Integration” (initially tried “Friction”, a key part of the story), which is about bringing all of this together.
Part 1 already kicks off this idea: what the socials do really well is remove friction, in particular by bringing in the same interface writing/posting, commenting, reading. They do it really well, but inside their walled garden. If we try and start with blogging as the centre, what would it look like? Let’s try.
Start with reading
First of all: reading and following. RSS works, and we still have RSS readers despite Google almost making the ecosystem go extinct when it killed Google Reader. What we need is two things:
make it super easy to subscribe to a blog, wherever I stumble upon it – as easy as following somebody on the socials – and make it visible
from my “reading interface” (ie, the RSS reader), make it super easy to comment, share, react or link to a publication and start writing something new
Frictionless subscribe is well on the way, as far as I can see: I recently installed NetNewsWire, and since then, I can “share” any site I have open in my browser to the app (on my computer or my phone) and it will look for the feed and add it to my subscription list. The desktop and phone apps sync through iCloud. That works for me. It’s easy enough. I see a blog I like, I click twice and confirm, we’re good.
FeedLand makes it super easy to subscribe inside its own ecosystem (just tick a checkbox next to a feed you see in somebody else’s subscriptions), and has a bookmarklet, but it’s not as seamless. For example, after using the bookmarklet, I’m not “back on the page I was reading”, I’m inside FeedLand. I’m sure this kind of thing can be fixed. This is just to illustrate the kind of thing we need: some integrated way, ideally through the “share” menu (assuming it also exists in non-mac environments?), to “stupid-subscribe” to an RSS feed.
What FeedLand does that is great is make the subscriptions public, just like the people I’m following or connected to on the socials are visible to others. I can even embed them in my blog to use as a blogroll.
So, let’s say the subscription problem is pretty much solved, or nearly so. The second one is much, much trickier, and I think it’s the key to everything. (At least, one of the keys.)
In my “reading interface”, be it NetNewsWire or my FeedLand river (the “newsfeed”), I’m seeing the blog posts I’ve subscribed to. Let’s assume for now that how they are displayed is a question of user/tool preference and something we know how to do. For example, do I want to see the posts “mailbox-style” (with headers that I click on to display the post), or “newsfeed-style” (like a facebook newsfeed, with more or less long excerpts)?
Add reacting
Let’s concentrate on the next step: reacting, commenting, sharing. Can I do that easily? The screenshots above show that there is some intention in the right direction, but not enough. The desktop app gives me a share icon. FeedLand allows me to reshare inside FeedLand. I can star/like, but it remains local to the “reader software”.
This is where we need more. When I read a post I’m subscribed to, it should be trivial to:
“like” it, if the tool producing the post supports it
“comment” upon it, if the tool producing the post supports it
“share” to a tool of my choice, be it the socials, a bookmarking service, or my blog – with or without extra content on my part (I could write a whole blog post with a reference to the link in it, or I could just post the naked link to Bluesky if I wanted to)
While we are at it, I should also be able to see if there are comments visible to me, as well as likes/shares.
All this should be possible without leaving the reading interface.
Of course, this requires a slight mindset change for us bloggers: it shouldn’t matter so much if people read our post on our website or through the feed. In that respect, the feed should contain a complete version of the blog post: untruncated, with links and media. (I don’t know why I keep stumbling upon blog feeds with the links stripped out, by the way, it’s super annoying!)
So, I write a blog post with my blogging software of choice. This blog post can be liked, commented upon, or linked to (shared). I can choose whether likes and comments are active or not. This blog post is published to my blog, and in the RSS feed. In some cases, it also goes out by e-mail (not to be forgotten). Whether people read the blog post on the blog, in the feed reader, or in their e-mail, they can easily “interact” with it, where they are (less true with e-mail, so let’s leave it aside, but not forget it’s there). As the post author, I can of course choose to moderate comments before publication, so they are displayed with the blog post only if I choose to.
Maybe the feed reading software should also be capable of displaying existing comments if requested, to give context to the person wanting to comment. Or we could consider that this is where the integration ends, and where a visit to the blog post itself is in order. To be discussed, in my opinion.
There is really something about having to leave the reading space to interact with something you’re reading that is extremely problematic. Super users who juggle tabs and apps all day might not think it matters, but normal people who can’t tell their browser from the internet or a search engine will be lost. We need spaces where we can read-like-answer-share without being teleported to some strange new place without having wanted it.
Some practical considerations: let’s say we start implementing this. The technical details are beyond me, but I understand enough to know that not all blogs (or subscribable publications) will be “compatible” with the system from the get-go. No problem: grey out those interaction buttons that won’t work in the reader, and leave the link allowing the user to head out to the blog proper to comment or like. Sharing should always be possible, as each post has a permalink (at least we have that now).
Write where you read
This was for starters. Now for the first big idea: integration with the blogging software.
In other words: maybe all this “subscribing to things” should happen in the blogging tool – or the RSS reader needs to become a blogging client. Take your pick.
Here’s why. As I mentioned before, in the old, old days of blogging, blogs did not have comments. People linked to each other when they had something to respond. Some blogs, still today, do not have comments. And that is fine, it’s a personal choice. For me, the soul of the blogosphere is people reading each other and linking to each other. And we need tools that encourage that.
I think this is also something that can help fight against the “loneliness” some of us feel around blogging, compared to the busy experience of taking part in the socials. Think about this: on the socials, you’re writing your tweet, facebook post, toot, update or whatever on a page (whether on the web interface or in an app) that is filled with stuff your contacts have published. You are producing content that is going to go on and be part of this stream of updates. It feels like part of the newsfeed already. Even though everybody has a different newsfeed, it doesn’t feel like sending something out into the void. It feels like contributing to a collective space. And this is what blogging should feel like.
So my reading tool should allow for three things (at least), in that respect:
create a blog post (mention or response) based on the one I’m reading, as already mentioned previously; bonus points if it makes it easy to quote part or parts of the post (think how easy forum software makes this)
write a blog post from scratch, just like we normally do today in our blog admin interfaces (think “facebook post” here rather than “tumblr” for the vibe: a space a the top of your reading list that is there waiting for you to write a post, not nagging but inviting and tempting…)
convert a comment you are writing on somebody else’s blog post into a blog post of your own, with a link to the original post – I’m pretty certain I’m not alone in regularly thinking “I just have a sentence or two to say” and lifting my nose up after having written 5 paragraphs; happens on the socials too, particularly facebook, as it doesn’t have any character limit (this is a nice way to make blog interlinking easier)
WordPress Reader is on the right track, although it feels a bit like a rough draft (I particularly don’t like the web interface – too much empty space and not enough content). It shows the newsfeed of the blogs I’ve subscribed to, and an inviting box at the top to “write a quick post”. How the editor expands and what features it offers in this context leaves room for improvement, but the idea is there. It’s also missing easy-peasy subscription outside the wordpress.com platform, as far as I can see, but let’s note that it allows the user to switch between mailbox and newsfeed views, has a share button (Facebook and X), a repost button (which unfortunately opens the editor in another window, but in a nice move presents the reposted blog post in card format – why not?), a like button (internal to WordPress), and in-reader commenting.
Right. So far we have:
a better “reader” experience, including frictionless subscription
a more integrated way of reacting to what we’re reading
reading and writing brought together in once place.
Bring in the socials
What is still missing (the second big idea) is how to tie this in with the socials. As I argued in part 2, interaction and conversation come in varying forms. Socials do not make blogging redundant, and neither does embracing blogging again make the socials redundant. Just as we still have a use for e-mail in the era of instant messaging, or phone calls in the era of voice messages.
We touched upon this issue earlier when mentioning that any post being read should be shareable to whatever platform we want. That’s pretty trivial and already somewhat possible (we have permalinks, remember, and on our phones at least, sharing to socials is always just a touch away). But that is not sufficient.
I see three key aspects in integrating the socials with the blogging experience I’ve been describing:
Tying “comments/shares on the socials” to the relevant post (this is the neverending Trackback/Pingback/Backtype/Webmention story)
Posting blog content to the socials (POSSE) or, more interestingly from my point of view, backfeeding from the socials to the blog (tools like Bridgy and TootPress are also in this space)
Allowing the blogging/reading tool to function as a client for the socials.
The first one is an old story, but what it means is that what people are saying on the socials about what I wrote on my blog is part of the conversation related to what I wrote, and it might be desirable to have a way to point the readers of the blog post to it. It’s the argument for having comments on the blog. Or a list of Webmentions (if I’ve understood correctly that they are the Trackbacks of today). Or not. The conversation is there, and the blogger should have the ability to make it visible from the core content. Beneath a blog post, you could have comments (some made from inside an integrated tool for reading/reacting/writing, some made directly on the site), links to other blog posts which mention it, and links (or quotes? TBD) to public content on the socials about it. As I understand it, Bridgy does this.
The second one is three-pronged: I might want to share my blog posts on the socials when I publish, publish to the socials using my blog (with a separate post-type or category for example), or I might want to repost/archive on my blog whatever I have shared on the socials. The first two are outwards-going. The third is inward-coming, but instead of being centred on a piece of content (the blog post) like described above, and therefore on the content of what was published on the socials, it is centred on the person (the blogger), and therefore a specific account (or accounts).
I see two reasons for wanting to do this: first, for safekeeping (create an archive or mirror of whatever you post on Bluesky on your blog, for example) or for resharing to another audience, maybe in a slightly different form, whatever one posted elsewhere. I want to elaborate on the second case, which is in my opinion more interesting (obviously, because it’s a need I have).
I’ve already mentioned before that participating on the socials is very frictionless. The barrier is low. We are in conversation mode. It is “speaking” more than it is “writing”. Therefore, my hypothesis is that however much we love our blogs and everything, it’s still always going to be easier to quickly throw out a link on the socials, or jot down a thought, share a photo, respond to somebody and find ourselves coming up with an idea. To me, there is a lot of raw material there which might be worth preserving. Sure, if you’re having a back-and-forth about getting ready to go to the gym, maybe not, but if you’re sharing links or bite-sized thoughts or commentary on the world or whatever, that’s different.
It would make sense to be able to gather that daily production from the various socials one is active on, and organise it in what would be the “socials” equivalent of a post on a link blog. How exactly will be the topic of another post, because I think it requires going into lots of little details. But suffice to say, for now, that the idea would be to give the blogger an option to repatriate whatever has leaked from the bloggers brain to the socials in a form that could be either publishable as-is, or edited before publishing, or why not, broken down into more than one post if needed. “Today on the socials”, or something like that.
So, at this point we want to be able to create a two-way path between the blog and the socials, to push posts to the socials, bring back commentary or mentions to the blog posts, and the blogger’s updates to the socials.
We can go a small step further and integrate into our reader/blogging tool a client for the socials. We’re already reading RSS feeds, why not also read the social newsfeeds?
Openvibe is a client that combines different socials and allows the user to also subscribe to RSS feeds within the same interface. This would be the corollary. And if we’re reading, and we have the ability to write blog posts from there in addition to comments, why not also be able to publish to the socials? I like the way Openvibe manages cross-posting: you can choose where you want to cross-post each time; when you mention somebody, a little dialog open so that you can mention them on the different socials you’re posting to – or just enter text if they aren’t everywhere.
I could start composing something to share to the socials, and partway through decide it should be a blog post: I’d select the blog as a destination (this would be somewhat similar to converting a comment I’ve started writing to a blog post, as described earlier), the interface would adapt, the cross-posting to the socials would become a “blog post share” in the background. This allows me to dynamically adapt where I’m going to post what I’m writing, as I’m writing it.
Having a reading interface with RSS feeds and the social newsfeeds together (with filters, obviously) replicates what actually happens on the socials when people share their blog posts (or even have an account for their blog) on the socials. This is more elegant, because it’s the actual subscription to the actual blog content, and doesn’t depend on the blogger making their content available through the socials.
Loose ends: comments elsewhere, web interface, modular
At this point we’ve got something that is really nicely integrated, but one thing is missing: comments made on other blogs. I dwelled on this a bit in part 1: this is one of the issues that coComment or Disqus tried to solve.
If the comment is made through the blogging-reading tool, it’s quite easy to capture (content and permalink, even title to the blog post it’s on). The only question would be how to display these comments (if desired, of course). In the sidebar (“my comments elsewhere”)? Collected in round-up posts like what comes from the socials (“my comments on other blogs this week”)? People will want different things, but it should be part of the package to make this possible.
What about comments made directly on other blogs? In an ideal world, the receiving blog would “notify” (webmention?) the commenter’s blog of the comment just made. But there would also have to be a way for the commenter to “secure” their comment, in case the blog in question doesn’t have the notification feature. I guess there are ways to do that with bookmarklets, browser extensions, or the like. Or why not by “sharing” the page one commented upon to the blogging-reading tool, with a way to indicate “there’s a comment of mine on this page”?
Throughout this post I’ve spoken about this integrated “tool” (or maybe app at times). As I see it, it should definitely have a web interface, like my WordPress blog has. Or Discourse. And be something that can be self-hosted, or managed. Apps are nice, but I think it’s clear today that tools or services should be available both through a “website” and an app.
It may seem like I’m describing “one more app/tool to rule them all”, but in my mind it’s not like that. I’m describing a set of principles. Just like we have various tools which allow blogging or reading RSS today, or various clients for Mastodon, this should not be a lock-in for a particular tool. Those with better understanding than me of ActivityPub, RSS, APIs and the like are most welcome to elaborate on how various protocols or frameworks could work together or be extended to make this kind of thing possible.
As I see it, with an agreement of how these different general features function, we could even go towards more modular tools, where I could use a WordPress base for blogging, which would be compatible with something derived from Openvibe for the socials integration, and have the choice between a future iteration of FeedLand or WordPress Reader or NetNewsWire for the reading part – and they would all integrate seamlessly in such a manner that I will not feel like I am using multiple tools, but one. There could even be add-ons/plugins (I heard this idea in this OTM interview of Jay Graber) to manage how you filter your RSS+socials timeline (algorithm? no algorithm? labelling?), how you mashup your socials of the day into pretty blogs posts – or not, etc.
I have the intuitive hope that something approaching my present pipe dream can be built around WordPress – particularly after hearing Dave Winer invite us to think differently about WordPress. I’m curious to see if what he’s cooking us with WordLand brings us in the kind of direction I’m thinking about. And of course, if you know of anything that makes what I’m talking about here reality, comment away!
PPS everyone: I didn’t proofread and I feel my writing is more clunky than usual today, sorry – brain still recovering. Point out the typos and broken sentences and I’ll go and fix them!
PPPS: might do a part 4 on privacy, and need to cover non-text content better, in addition to going into more detail regarding “Today on the socials” posts, so chances are there will be more in this series, at some point…
Another interesting observation following my return to Facebook: when somebody responds to one of my posts there, it definitely feels like the audience for this response is primarily the people I am connected to. What I mean by that is that I expect that my contacts have a chance of seeing that response, because responses are closely tied to the original content (“comments and post“ format).
On Bluesky or Mastodon (or Twitter for that matter, and it could partly explain why I drifted away at some point and started spending more time on Facebook), when somebody responds to one of my updates, I do not expect the people connected to me to see it. And indeed, if they are not following the person who responded, if they do not specifically open up my update to see if there are responses or if it is part of the thread, they will not see it. On those platforms, responses are much more “their own thing” than on Facebook or on a blog.
On Facebook, there is an immediate and visible feeling of micro-community around a publication, when people start commenting. It feels like we’ve just stepped into a break-out room. Participants get notifications, and come back to see responses. If the conversation becomes lively, it is made visible to more people. People will end up connecting to each other after having “met” repeatedly in a common friend’s facebook comments.
Bluesky, Mastodon and Twitter (yeah, and Threads) feel more fragmented. It’s more difficult to follow for lots of people. They are faced with bits and pieces of conversations flying about, and access to the context of those is not frictionless. Part of this, I think, has to do with how publication audience is managed (I’ll definitely have to do a “part 4” about this in my Rebooting the Blogosphere series). And another, of course, is the primacy of non-reciprocal connections on those platforms.
What Facebook also does that blogs do not at this stage, is that Facebook makes my comments on other people’s publications candidates for appearing in the news feeds of people who are connected to me. Every now and again, something of the form “Friend has commented on Stranger’s post” will show up. The equivalent in the blogging world would be having a “reading tool” (now RSS readers, but we need to go beyond that, that’s the Rebooting the Blogosphere part 3 post that I’m actively not writing these days) which will not only show me the blog posts that the people I’m following have written, but also that they have commented here or there, on another blog. This tightens the connection between people and contributes to discovery – ie, finding new people or publications to follow.
In summary: there is something fundamentally different in how Facebook, the other socials, and blogs make visible to a person’s network the comments/responses they have made elsewhere. And the “feeling of conversation/community” of multi-person exchanges also varies from one platform to another.
What is happening for me right now is interesting. During my Facebook exile, I reconnected with the social networks that I had been present on in a very passive manner these last years. I also wrote more on my blog (here!), and made an effort to get back into reading other blogs, even though I have never been a really huge blog reader in my past. I installed an RSS reader, and started subscribing, process which is now pretty frictionless. To my surprise, there are lots of blogs! Lots of people still blogging! Lots of people who took up blogging way after the Golden Era of Blogs! I see them show up here and there on Mastodon and Bluesky, and of course, in blog posts.
In the few days since I’ve been back on Facebook, I have been struck by the pretty much total absence of blogs in my newsfeed over there. And when I think about how little visibility my Facebook updates pointing to my blog posts get, unless I jump through hoops like posting a screenshot, writing some text, putting the link in the first comment (talk about friction!), I realise that it is not so much because of blogs or bloggers, but because of how Facebook treats outgoing links, and how the algorithm prioritises things.
It reduces the visibility of blogs, therefore inciting people to post directly on the platform rather than on their blog (definitely what happened to me) or go elsewhere to share their blog links and abandon Facebook (what others have done).
Another thing that blogging more these days has made me realise is that, as I mentioned previously, I do not like blogging on my phone. Even though the WordPress app is nice and everything, the length and nature of the blog post is something which, to me, lends itself much more to being typed out on a keyboard in front of a decent screen. But since I went through the exercise of writing a blog post on my phone the other day, I have done it again. In particular, I have written drafts, started blog posts which I then finished on my computer. And at one point in that process, as my thumbs were tiring, I switched to dictation. And that is the key. Dictating on the phone.
Dictation is not perfect. But it is something I know how to do. Over 20 years ago, I spent nearly a whole year without touching a keyboard. During that year, I not only blogged and participated in online life, but I wrote my dissertation, worked in a telecom company, and sat for my final university exams. Dictation on my phone today does not allow me to “speak corrections” in the text I am writing, but it does now allow seamless transitions between dictation and keyboard, and the recognition quality is pretty good.
One of the things that happened during the Rise of The Socials is that our online activities became more and more “phone first”. And for me at least, blogging being primarily a “desktop computer” activity, and the socials being extremely well calibrated to mobile phone use, that definitely encouraged my drift away from blogging and into the socials.
So, clearly, for me, starting blog posts on my phone, even if I finalise them on the computer, and using dictation to write stuff down is definitely a way to remove friction from blogging, by bringing it to my phone, and providing it some of the immediacy of the facebook post.
Previously, I would spend my time having ideas like “oh, I need to blog about this!” but it was never the right moment to sit down at the computer and spend an hour or two typing it out. Not because I am a slow typer – on the contrary – but because I am not exactly concise, and I like putting links in my blog posts, so I often go down rabbit-holes looking for the right link for this or that.
Now, as I did this morning, I open up my WordPress app, and start dictating a blog post into it. Right now, I am pacing back-and-forth in my apartment and dictating this, instead of preparing my breakfast, but that is another story. At least I am capturing my idea. It will be 90% written and ready by the time I put down my phone, and all I will have to do on the computer a little bit later is make a bunch of corrections (I am“dirty dictating” without correcting much so that I can go fast), add links and a photograph (because I like photographs, and the WordPress app has made it super easy to add them to my posts from my phone), and publish it.
So, the bloggers are there. But if you live on Facebook, you might just not be seeing them.
Maintenant que j’ai de nouveau (contre toute attente) accès à mon compte Facebook, ma première mission est de préserver, sous une forme ou une autre, ce que j’ai contribué là-bas depuis 18 ans. Cette mésaventure (on va dire ça maintenant que ma “disparition” n’aura duré que trois semaines) aura eu le bénéfice de me faire sentir dans mes tripes à quel point il est important de ne pas laisser du contenu auquel on tient uniquement dans les mains de grosses entreprises capitalistes qui gèrent leur plateforme à peine mieux que le ferait un régime totalitaire.
Première étape, demander un export de toutes mes données. Je voulais le faire ce printemps, j’ai baissé les bras devant les 52 fichiers de 2Gb chacun qu’il fallait télécharger à la vitesse de pointe de la limace et qui faisaient planter mon réseau. Mais là je suis prête. Je câblerai mon ordi, je prendrai la journée pour le faire s’il le faut.
Si vous n’êtes pas prêt·e à voir disparaître à tout jamais les publications, photos et vidéos que vous avez confiées à Facebook, prenez le temps de le faire aussi. La liste de vos contacts, aussi, c’est là-dedans. Je rappelle que la suspension de mon compte Facebook (qui aurait aussi bien pu être une suppression définitive, j’ai eu de la chance sur ce coup) est l’équivalent d’une erreur judiciaire. Ça peut vous arriver à vous, aussi.
Ce que Facebook ne vous permet pas d’exporter, ce sont les échanges, conversations, et discussions que vous avez avec d’autres dans les fils de commentaires. A qui appartient une discussion? La discussion (comme la relation) est plus que ce que chacune des parties y met – le tout est plus que la somme de ses parties. Même si on peut exporter toutes ses publications, tous ses commentaires, on va perdre quelque chose. Imaginez, un commentaire qui dit “c’est exactement ça!” sans qu’on sache à quoi ça répond, ça ne veut rien dire. Il manque le contexte.
Quand quelqu’un supprime une publication ou un commentaire, toutes les réponses d’autres personnes partent avec. C’est comme si on vivait dans un monde où le droit de faire disparaître était très étendu, mais pas le droit de préserver.
Je vous donne un exemple. Dans la communauté Diabète Félin, nous avons une publication, que j’ai faite, qui est un fil de présentations. Il y a plus de 300 commentaires sous cette publication. Depuis des années, les gens prennent la peine et le temps d’écrire un commentaire, parfois long, qui les présente. Il y a des réponses, du partage, des échanges. Quand mon compte a été suspendu et que tout mon contenu a été “disparu” de Facebook (et ce serait le cas si je décidais, pour je ne sais quelle raison, de supprimer définitivement mon compte), tous ces commentaires ont disparu avec. Ils ne m’appartiennent pourtant pas – mais j’ai un “droit de mort” sur eux.
Il y a donc certains fils de commentaires qu’on peut souhaiter préserver – soit pour ses propres archives personnelles et souvenirs, soit parce que l’échange en question a de la valeur pour la communauté ou les personnes qui y ont pris part. Le jour où la communauté Diabète Félin déplace son centre d’activités hors de Facebook, peut-être qu’il y a une partie de nos huit ans d’histoire qu’on aimerait pouvoir prendre avec nous. Et il n’y a rien de prévu pour ça. Chacun peut supprimer ou exporter son contenu, mais une communauté en tant que collectif ne le peut pas.
Comment faire, alors?
Tout d’abord, il y a une extension Chrome qui s’appelle SingleFile. Une fois installée (ce n’est pas compliqué, c’est l’équivalent d’installer une app sur son téléphone, juste que c’est dans son navigateur web – Chrome) l’extension permet de faire une sauvegarde (une archive) de n’importe quelle page web, en HTML (le format de base du web, donc lisible dans n’importe quel navigateur). Cette sauvegarde est statique: on n’enregistre que ce qui est chargé et visible sur la page. Mais c’est bien mieux qu’une capture d’écran, car ce n’est pas une image, et ça couvre toute la longueur de la page.
Ce qui va nous embêter, c’est que Facebook ne “déroule” pas entièrement les fils de commentaires quand on charge une page. Avant de trouver la solution dont je vais vous parler dans un instant, j’ai passé des heures et des heures à cliquer sur chaque commentaire de longs fils de commentaires pour les ouvrir tous avant de sauvegarder la page avec SingleFile. Horrible!
Une autre extension, Tampermonkey, permet d’installer et même d’écrire des scripts utilisateurs pour son navigateur. C’est un peu technique, je sais, mais pas si compliqué. En gros, on installe l’extension Chrome Tampermonkey (si vous êtes dans Chrome, ce lien devrait vous donner accès à la gestion de vos extensions), et ensuite, dans Tampermonkey, on va installer un script qui s’appelle Facebook Comment Sorter, via la librairie Greasy Fork. Ce script fait deux choses (qui peuvent aussi servir en-dehors du cas de figure dont je parle aujourd’hui):
activer “voir tous les commentaires” (au lieu des plus récents, plus pertinents, ou ce que Facebook a choisi comme ordre par défaut ce mois-ci) pour afficher tous les commentaires et pas juste une sélection
charger et dérouler tout le fil de commentaires et de sous-commentaires.
Ça ne marche pas parfaitement, parce que c’est un peu du bricolage – ce genre d’outil finit d’ailleurs tôt ou tard par casser car Facebook fait sans cesse des changements à son code et à son interface, donc si ça se trouve, le temps que vous lisiez cet article, cette solution sera obsolète. C’est pas parfait, mais c’est nettement mieux que tout ouvrir à la main.
L’extension SingleFile, elle, permet de sauvegarder soit l’onglet en cours, soit tous les onglets ouverts. On peut aussi spécifier dans les réglages qu’on souhaite que l’onglet soit fermé une fois la sauvegarde faite. Jetez un oeil aux réglages – pour Facebook Comment Sorter aussi, on va modifier la ligne “expandReplies: false,” du script pour que ce soit “expandReplies: true,” et qu’il s’applique également aux commentaires qui ne sont pas dans la partie visible du navigateur web.
Voici donc comment je procède:
j’ouvre une série de publications que je veux archiver dans une série d’onglets, en faisant bien attention de cliquer sur la date pour ouvrir la publication, et qu’elle s’affiche seule sur la page
je laisse bosser Facebook Comment Sorter, ça prend un peu de temps, je vérifie que les fils de discussion se déroulent bien jusqu’au bout, j’ouvre les quelques commentaires qui auraient passé entre les gouttes
quand tous mes onglets sont bien ouverts et chargés, je lance SingleFile sur tous les onglets, et je vais faire autre chose pendant que tout se sauvegarde dans mon dossier téléchargements.
Voilà! Pensez-y donc, s’il y a des discussions auxquelles vous avez pris part sur la plateforme que vous souhaitez pouvoir assurer contre une disparition involontaire.
Evidemment, si vous êtes en train de préserver des échanges qui n’étaient pas publics, vous devez prendre soin de les stocker quelque part où ils seront en sécurité…
My Facebook account is back, with as little explanation as when it was taken down. I had finished the dishes after lunch and was preparing to get to work writing part three of my thoughts on rebooting the blogosphere, when I saw a message from a friend telling me that I was back on Facebook.
I checked, and indeed I was. In my emails, I found this explanation, as enlightening as the one that was given upon my suspension. I am sure that you, as I, will appreciate the heartfelt apologies.
Understandably, I am relieved. I have no idea if my account simply went through the standard appeal and review process, albeit in three weeks rather than one day as announced, or if my plight reached the right eyes or ears thanks to my extended network. I will probably never know. In any case, I really would like to thank everybody who helped spread the word about my situation. And if somebody somewhere intervened, I am extremely grateful.
As you can imagine, all is not clean and pink and shiny. The top thing on my list now is to back up my content. Unfortunately, that option is not available to me, as of now. Hopefully this is just a systems lag and I will be able to get things rolling tomorrow.
Upon logging in, the first thing I noticed was that all of my “disappeared“ Pages were not there. The Pages for my cats, past and present, for my diabetic cat community: not there. Thankfully, I quickly discovered that I could reactivate them. It was a bit tedious, but it functioned. I then immediately added a trusted friend as administrator with full powers to each of my Pages. Also little tedious, but worked.
Cats with Facebook Pages? Indeed. The current ones are Oscar and Juju. They mainly speak French, though. But photos (particularly cat photos) know no language barriers.
That being done, I figured I would check my account status. Well, no big surprise, it is still “at risk“ — still orange. The nine or so “false positive spams“ are still there on my Facebook criminal record. So, I’m assuming I am just another fast positive way from seeing my account suspended again. You are not going to see me posting much.
The information about my “crimes” is naturally as enlightening as before, with no way to appeal what are obviously false positives.
Feeling slightly bullied into doing it, I bit the bullet and signed up for Meta Verified for my Facebook account, having already done it for my Instagram account just after the suspension. Trying to contact a human being through there was one of my possible avenues of action to try and get my Facebook account properly reviewed.
Anyway. If I still cannot download my content tomorrow, I will try out their enhanced support. And I will also see if there is anything this “enhanced support“ can do about those nasty stains on my Good Facebook Citizen record.
But above all, here is what’s important: what happened here is wrong. A company should not hold such arbitrary power of life or death over such a large part of our digital existences.
I’m lucky my account is back up. I’m lucky I didn’t lose any business during the three weeks it was down. I’m lucky that I didn’t rely on Facebook or Messenger at the time for anything critical, and that I had good teams in place for managing my active facebook groups. I’m lucky that Facebook is not the only store for my photos, and that I had downloaded my Live Videos previously. But even with that, the way I was suddenly and unexpectedly disappeared from the platform was traumatising. I was in shock. I lost sleep and for a significant number of days, regressed in the recovery from my accident. I spent countless hours and days doing whatever I could in the hope I might get my account back.
This should not happen. Even if we are not paying customers, even if we are “the product”, all the cash that is rolling into the company is thanks to us. We get something in return, sure – and therefore we willingly allow Meta and others to exploit our data. But we are not just data. We are living, breathing, feeling humain beings behind our screens. And we deserve to be treated as such.
Yesterday I started writing “a blog post” to capture my coalescing thoughts about the open web and how to remove friction from blogging. Not all of it: some friction is good. But enough that people like me don’t get so easily drawn away from their blogs by “The Socials”.
Today, I’ll focus less on the actions an individual carries out, and more on the interaction between individuals. The wonderful thing about blogs is that they lowered the barrier to personal expression online, which in turn makes dialogue possible. But dialogue can take many forms.
I love what Dave describes doing in the very early days, if I understood it right: write something, send it by e-mail to handful of people, and have a first round of discussion with that smallish group before publishing, and including value-adding responses to the publication. All this, scripted so that it was as frictionless as possible for him. This reminds me of Bruno Giussani‘s “Promote Comments Plugin” idea. It also fits with the idea I insisted upon yesterday that there is an added value to making the discussion about something available in the same place as that thing.
It is also reminding me of one aspect that I hadn’t thought about covering in this post-become-series: managing who the audience is. I firmly believe that allowing conversations to take place in closed or semi-public spaces is vital (cf. context collapse) – proof the number of people who take part in closed groups on Facebook or who share updates to “friends only“. I might have to make this a fourth part…
Dave describes a future tool in which comments (responses) get posted to the commenter’s blog and sent privately to the author of the original blog post, who can then decide whether to make it visible or not. For me, the second part of this process is already widely implemented in blogging tools, and has been for over a decade: its upfront comment moderation. Some people activate it, some don’t. On this blog, for example, if you’re a first-time commenter, your comment is not published. It is sent to me and I decide whether it’s worth publishing or not.
The first part is more interesting. It addresses the “ownership” issue of the comment, as tools like coComment or Disqus have tried to by providing a place all a person’s comments are collected. But it goes one step further and says: that place is the commenter’s blog. This is great and has been long needed. It would be interesting examine why previous attempts to do this across platforms have not stuck.
And this leads us to the topic of today: show my comments on my blog, but in what way? My comments are not the same kind of content as my posts. I don’t want my posts to be mixed up with my comments, everything on the same level. I’ll explain why.
Finally, Dave identifies some of the challenges with blog comments that I covered in yesterday’s post, but I’m not sure the current situation is as “broken” as he thinks. All that is missing, really, is a way to collect-own-display the comments I make all over the place in a space that is mine. Moderate comments upfront, or not? Or even, not have comments? That’s already possible, and up to the blogger. And yes, moderating comments or limiting who can comment directly cuts down tremendously on the spam and other bad behaviour issue.
Comments are about interaction – so are links between blogs. And as I mentioned yesterday, one thing the socials are really great at is interaction. You can spend your whole day on there (don’t I know it) interacting.
A way to look at interactions
I’m going to start by sticking with 1-1 interactions, to make it simpler, but I think this can be applied to interactions with more actors.
I think we all agree that exchanging letters with somebody (which I’m old enough to have done in my youth) is very different from talking on an instant messaging system. The key dimension that varies here is how (a)synchronous the interaction is. This drives a lot of the features we have in our social tools, and what makes them different from one another – just like in martial arts, the distance between the practitioners constrains the kind of techniques, and therefor the kind of fighting (interaction) that can take place.
I’d like to summarise it this way:
The length of contributions in an interaction is inversely proportional to how synchronous, or how conversational it is. And vice-versa.
Let’s unpack this a bit.
When Twitter showed up with its 140-character limit (which didn’t come out of nowhere, it was SMS-based), and constrained how much we could write in one go, it quickly became a place where we were “talking” more than “writing”, as we had been doing on our blogs. It was not quite as immediate as instant messaging, but somewhere in between. Like text messages.
In the early days of Facebook, if my memory serves me right, there was a distinction between sending a message to somebody (sorry, I can’t remember the terminology that was used, I’m not even 100% sure I’m remembering right) as some kind of internal mail, and chatting (or maybe they transformed the former into the latter and it changed the way we used it). In Discourse, you have both: you can send a message to somebody, or chat. Like you can e-mail somebody, or instant message them.
And I suspect I am not the only person to feel some degree of annoyance when I receive an “instant message” that should have been “an e-mail”, because it requires me to sit down, absorb a “speech”, and then figure out how on earth I’m going to respond to all that was said in one go, particularly now the person who sent it is not online anymore, because I had to wait until I had enough time to properly read it, digest it, and figure out my response.
Instant messaging works when it’s used for short things that you can take in at a glance (or barely more) and answer without having to think too much. It is conversation, with an asynchronous twist. When both parties are connected and interacting (synchronous), it is very close to in-person (or “on the phone”) synchronous conversation, but with this “optional asynchronicity”, as there is a blind spot regarding the context of the other party, and how it impacts their availability to read or respond right now, or even, to keep the conversation going. (If you’re on the phone with them or in the same room: they are available.)
When in “conversation mode”, contributions can become a bit longer, but not too long: if you throw a 3-page essay at somebody in an instant message or chat conversation, chances are you’ll lose them. Just like in-person conversation: if you monologue for 10 minutes at the person you’re talking with, you don’t have a conversation anymore. And actually, this pretty much never happens: there are non-verbal cues that the person opposite you is going to give that will either interrupt your monologue, or reveal that it is in fact a dialogue, when taking into account non-verbal contributions of the listener. But when you’re typing in an instant-messaging box, there is none of that.
Back to blogs. A blog post does not have the same conversational qualities as a response to a tweet. Blogs live in a more asynchronous interaction space than the socials or chatting. Comments are generally more conversational than blog posts. But probably less than updates on the socials.
“Allowed length” of contribution plays a role in shaping the kind of interaction, as well as design. If you’re typing in a tiny box, you’re less likely to write an e-mail or a blog post. If you’re typing in a box that uses up the whole screen, you’re less likely to write only one sentence.
Why did so much conversation move from blogs and chats to socials? I think that it is because they are in some sweet space on the (a)synchronicity continuum. They allow belated responses, but also real-time interaction. Notifications are key here, as is the fact that writing/responding are pretty much the same thing (same on Twitter or Bluesky or Mastodon, not-quite-same on Facebook, but close enough) and in the same space as reading/listening. It’s super easy to jump in and out of conversation. Frictionless.
So, it’s not just about reducing friction around reading blogs, writing blog posts, and commenting on them: it’s also about how we integrate the blogosphere and the socialsphere. One cannot and should not replace the other. There will always be people who like writing stuff. And others who are just happy to interact or react. And it doesn’t make sense to corral them into separate spaces.
Does anybody remember Backtype? I didn’t. Well, I do now after reading my blog post. The idea was to find a way to bring “back to the blog post” conversation about it that was happening on the socials (gosh, I really hope it’s not too annoying for you all that I’ve started saying “the socials”, it’s just really practical; my apologies if it grates on you). What about Diigo comments?
There is a common theme here: somebody writes a blog post. There is discussion about it or prompted by it – in the comments, on other blogs, on Bluesky, Facebook, Twitter and Mastodon, even Threads. How do we give easy access to these fragmented conversations (I think conversation fragmentation is now something that we have accepted as inevitable and normal) to those who are reading the post? And how do we do that in a way that a) leaves some control in the blogger’s hands over what to show and not to show (less spam) and b) allow people participating in the conversation to keep ownership of their content, in the sense that even if it can be made invisible in a given context (e.g. on the blog post), it cannot be outright removed by a third party, and remains “on the record” of the person who wrote it?
Who owns the conversation?
There is a lot of talk about retaining rights or ownership to one’s content. But who owns a conversation? Or beyond that, a community? The whole is more than the sum of the parts. When people come together to create something together (including relationships), who owns that? I mentioned previously that when facebook allows you to “download your content”, that doesn’t seem to include comments (wait, I have a doubt now – I think the export used to, but not anymore, correct me if I’m wrong, as I can’t go and check easily). Or comments by others made on your posts. In any case, say you can download your comments: a lot of them are contributions to conversations, and make little or no sense without their context – the publication the conversation took place about, other people’s comments.
I think there needs to be some kind of “collective ownership” understanding, which is more nuanced than “I wrote it, I have power of life or death over it”. When does something you offer up to the collective cease to be completely yours? In my opinion, it remains yours in the sense that it cannot be taken away from you against your will. Corollary: if contributions to a conversation or a community also “belong” to the conversation or community, then it should not be possible to take it away from them unilaterally. This is something that needs to be thought out further: does it mean that I should not be allowed to remove my blog from the web?
What is clear at this point: we need to think beyond “atomic” contributions and also think about how our tools manage the collective creations that are conversations and communities.
So, let’s sum up today: interaction is not a monolith. Online conversations occur at varying speeds and are made up of contributions of varying nature. Reclaiming and rebooting the blogosphere and the open web needs to take that into account and embrace it, and figure out how to bring it together in an open way, with frameworks, standards, protocols or the like, not yet another “One Platform to Replace Them All”.
Some thoughts (part 1 of 3) following exchanges on Bluesky with Dave, amongst others. My Facebook exile is clearly bringing to a boil my preoccupation with our reliance on big capitalist platforms for our online presence and social life. Though I never “stopped blogging”, I clearly poured a lot more energy over the last decade into what I now think of as “The Socials” (Twitter, Facebook, Bluesky, Mastodon and the like).
I am pondering a lot on what I am “missing”, having lost facebook. On what is “difficult” about blogging, in comparison. Where is the friction?
Very clearly, one thing that The Socials (I’ll drop the uppercase soon) do very well is:
bring everything (reading, writing, responding) together in one seamless interface/site/app
shift interaction closer to real-time and what we perceive as “conversation”.
The rest of this blog post covers the first point. A second one will cover the second one. And finally, in a third post I’ll try and put together a proposal for how we can use our understanding of how the socials manage “so well” to remove friction from blogging and help reboot the blogosphere.
As I was writing this post I poked around in my archives to link to where I’d spoken about some aspects of the topic, so here are a some of those I dug up, in addition to those linked in the text itself (realising I wrote so much about this stuff it makes my head hurt):
I see three main “activities” for taking part in the text-based social web, and a fourth that may be worth distinguishing from the third:
Reading or consuming: basically, taking in things that others have put there.
Responding, commenting, reacting: expressing oneself based on something somebody else has provided.
Writing: making available to others ideas, stories, in a broad sense, our creations.
Sharing or boosting: highlighting for our network/readership things that are not by us.
Some comments regarding this typology (bear with me, it will come together in the end).
Reading
RSS does a good job of allowing us to collect things to read from different sources into one place. Many different tools make RSS feeds available. Many different tools read/collect/organise RSS feeds. However, they usually keep this collection of feeds private.
As Dave says, subscribing to an RSS feed generally requires too many steps. Too much friction. The socials make it 1-click (sometimes two) to follow or friend (connect to) somebody. And it’s right there in front of you, a button that calls you to do it. Inside blogging platforms like WordPress.com or Tumblr, you have some kind of 1-click subscription, but it keeps you in their internal reader (just like the socials do, by the way).
Commenting
Responding/commenting is a can of worms, in my opinion. When I started blogging, blogs had no comments. We responded to each other’s publications by writing on our own blogs and linking to what we were responding or reacting to. I actually wrote about this a couple of days back.
second, the way comments are designed invite shorter contributions or reactions – this makes the exchange more conversational and less epistolary, tightening the relationship between the different parts of the exchange provided by different people and quickening the pace
comments link back to the commenter’s blog, therefore creating an incentive to comment for visibility and not just for what one has to say
the visibility incentive leads to people commenting while adding little value (in the best cases) and outright spam (in the worst, widespread case)
the lack of a frictionless system to be informed of responses to comments (think “response notifications” on the socials) leads to interrupted interactions (I liked the term “drive-by commenting“)
the widespread presence of comments on blogs raises the bar for what is perceived as “deserving” to be a blog post, possibly contributing to the idea that writing a blog post is a “big thing” that you might need to make time for (or that might suck up half your day), in comparison with just “leaving a quick comment” after reading something
the visibility of comments led to it becoming a measure of blogging success, increasing a kind of competitiveness in the space, and, in some cases, even its commercialisation.
I see comments as solving two main problems:
attaching the “discussion” about a publication to that publication: all in one place, instead of spread out in blog posts you might not even know exist
lowering the barrier to entry for participating in said discussion: you don’t need any sort of account to comment.
Over the years, many tools have attempted, in some way, to “fix” the problems that come with comments. A few examples:
In a world without comments, people who read a post will not necessarily know there is a “response” somewhere else out there in the blogosphere. The blog author might see it if the person responding tells them (some way or another), or if they check their referrers (didn’t we all use to do that). But the reader cannot know, unless the blog post author knows, and links to the response. Trackback and Pingback came in to solve this issue, creating a kind of automated comment on the destination post when somebody linked to it (with all the spam and abuse issues one can imagine).
Tags and Technorati also played a role in “assembling” blog posts around a specific topic, which could be seen as some kind of loose conversation.
But it’s not the same thing as having the different contributions to a conversation one below the other on the screen at the same time.
Writing
This one is simple. There are many good tools (many open-source) to write blog posts. You can create an account somewhere and get started, or install software on a server somewhere – with a hosting company or in your basement. They work on mobile, in the desktop browser, or even in apps. There are generally ways to export your content and move to another tool if you want. Some are full of bells and whistles, others are pared down.
Blogging has no character limit – the socials do. This, implicitly, encourages writing different things. Design also does that: is the box I’m writing in something that takes up the whole page (like the one I’m typing this blog post in) or is it a little box that might expand a bit but not that much, like on Facebook (which also doesn’t have character limits)?
I think this is a crucial aspect which should not be ignored. The blog posts I wrote in 2000-2001 are, for many of them, things that would be updates on the socials today. They are not the same as blog posts, and we need to keep that. The way we interact with “updates” or “blog posts” is also different (I’ll come to that below if you’re still reading by then). They generate a different kind of interaction. And sometimes, we start writing an update (or even a comment/reply) and it transforms into something that could be a blog post. How do we accommodate for that?
Sharing
Sharing is trickier, and this is why I’ve separated from writing. If writing can be thinking out loud or telling a story I have in my head, sharing is “I saw something and you should see it too”. Maybe I want to add an explanation to why I’m sharing it, or “comment” (hah!), but maybe I just want to put it out there, nearly like a shared bookmark. Of course, if what I write about what I’m sharing starts taking up a lot of space, I’m probably going to be writing a blog post with a link in it. And if I’m just sharing a link to something, I might as well be using some kind of public bookmarking tool (remember delicious?)
Bringing it all together
This is what I said the socials were great at. When I’m on Facebook, I am on my news feed (reading). I can 1-click-share and 1-click-comment on what I see, in addition to 1-click-subscribe if something new I want to track crosses my radar. If I want to write something, the box to do so is in the same view as my news feed – or pretty much any “reading” page I’ll be looking at (a group, for example; groups are another thing to talk about, but that’ll be another post).
I don’t really have to determine if I want to read, write, share, comment – I go to the same place. Whatever I want to do, the tool and environment remains the same. Tumblr does that well too.
Whereas look at blogging:
I want to write a post, I go to my blogging software
I want to read stuff, I open my RSS reader (confession: I’ve never been good at this) or conjure up a blog URL from somewhere (memory? bookmark? blogroll? link in another post?)
I’m done reading something (in my RSS reader) and want to comment: I need to click over to the blog itself to do that – or wait, do I want to comment, or write a whole blog post? I have no clue how much I’m going to want to write once I get going, I just know I have something to say.
I read a great blog post (or other thing online, for that matter) and want to share it, I need to pick up the link and write a blog post. Or maybe, instead, I just stick the link in a toot on Mastodon? There are “blog this” bookmarklets, but what about if I’m on my phone?
Yeah, I could post my “statusy updates” to my blog like it’s summer 2000, but do my blog subscribers really want to see “spent a lot of time feeding the sick old cat” in their RSS reader?
Think about community platforms like Discourse: want to post, want to respond, want to read? All in the same “place”. You get notifications, you can configure them. I think there is a lot to learn from this type of platform and the socials to bring “blogging stuff” together.
And before somebody says: “your blog should replace your socials” or “you should just blog on mastodon”, wait for the post I plan on writing tomorrow about what I see as a very important distinction in between these two types of online “social” spaces: exchange intensity and pace.
Comments changed that: it became less about linking to others, more about leaving your link on other people’s blogs.
Less invitations for your neighbours to join you, more peeing on the bushes in their garden.
Comments aren’t all bad of course. It’s great to have a space for discussion that is strongly connected to the post that sparked it. But they can be subverted and it can go overboard.
When it comes all about the comments, we end up with Facebook, Twitter (RIP), Bluesky, Mastodon, Threads and the like.
This is a shortcut and it’s debatable. What I’m getting at is the respective importances of « writing » versus « discussing » on various platforms/tools. Just like with martial arts (bear with me), the distance between the protagonists determines the style.
How immediate and interactional are our online spaces? And how do those characteristics make us more or less likely to default to using a given medium or platform, or drift away?
One thing that is very clear to me is that I use « the socials » on my phone a lot, but I never blog from my phone. I’m doing it now, to try to understand this better — but that really never happens. I’ll write comments on my phone, I’ll write blogpost-length entries on LinkedIn or Facebook (well, before I was disappeared) that should have been blog posts, but when I think of something to write here, I want my keyboard and the digital environment my computer provides.
Because it’s more « I have something to write » and less « oh, I have something to tell you or share with you ».
On the socials, it’s a quick passing something in my mind that I want to catch and make available to whoever is around right now. On my blog, it’s something that I feel deserves a longer shelf-life. But I think that distinction in my gut is a bit of a fallacy: otherwise I wouldn’t be so broken up about losing 18 years of « stuff » on Facebook.
What I’ve wanted for a long time is the easiness and immediacy of « social sharing » with a way to « transform » some or all of it into blog posts, or blog post material. Something parallel to what I’ve done with my voice memos (I need to blog about this) which allows me to capture snippets of passing thoughts throughout the day in a frictionless manner, and then nearly automatically merge all those tiny audio files into one, that gets transcribed and digested.
I would like Openvibe (or whatever client I happen to be using, ideally seamlessly synced between phone and desktop, like the « Facebook experience » was) to allow me to mark posts (by me or others) as « for the blog » in some way, and also « switch to blogging » if I realise mid-writing that « this should be a post (too) ».
So, how was writing this on my phone? Not that bad. Is it just a question of habit? The small size of the screen, which means I do not have a « zoomed out » view of what I’ve written, bothers me. Adding links is OK (now I’ve realised I can just « paste » the link on selected text) but it seems to sometimes shift the link one character to the right (super annoying). Writing… well, it’s writing in a phone. My thumbs complain. It’s slower. I need to correct more mistakes than when I’m typing.
The appeal, predictably, didn’t yield any results. No response, no e-mail, no change, nothing. I have no other “official” appeal routes, as I cannot access the platform at all. So I wrote up my appeal in a blog post.
What you can do to help: share my story or my appeal, give visibility to my situation – including on Facebook where I have become inexistant. If you know people who might know people, please ask. It seems pretty clear that unless a case manages to gather the attention of the right people (including, it seems, through the media), not much will happen. Going public helps. A huge thanks to those of you who have already shared my posts or updates, reached out to your networks, etc. Facebook is where I had the most reach, and without it, I am struggling to raise awareness on my situation. The reach I have in normal times is, of course, abnormal. A working system should not depend on people having a platform or connections to work right and be fair.
with scale, false positives in identifying abuse of a social site create a huge problem to deal with, even when the detection methods are “very good”; Kellan runs through some numbers, and it’s way beyond what I could have imagined (and the article was written nearly 15 years ago)
early adopters (like me!) are outliers in the data and are at higher risk of “looking funny” to abuse detection algorithms; indeed, we are not “normal users”; I share huge quantities of links; my account goes back nearly two decades so there are lots of publications to sift through and which might be flagged; I am at times extremely active in (human) ways which could seem “unhuman”: amount and type of content, speed, etc.
Even at my social “scale”, when I think about the main community I run (diabetic cats, 7k members), we run into scale issues where it becomes more and more difficult to treat everybody fairly and in a human way. And when I think of how to improve things from a management perspective (because volunteer ressources are limited, always will be) I find myself thinking in terms of automation, how to use AI to support the team doing content moderation or to improve the “member journey” in the community. Less personal, less human.
With automation, you get scale (and with scale you end up needing automation), but with that, you lose personal connection and at some point it comes crumbling down.
Life Without Facebook
How have I been coping with being un-facebooked? Well, beyond the shock and the hurt and the grief and the anger and the injustice of it all, and setting aside the extra “admin work” this is adding to my plate, being forced off Facebook has done two things for me:
regroup on my blog and other platforms, and in the process, get to experience different “connection spaces” than the main one I had on Facebook
imagine a life without/after Facebook: less connection maybe, a slower pace – I am getting to measure how “caught up” I get in the platform and how good it is at keeping me there.
Before we go all “silver linings”: this sucks. I didn’t need this. It has been extremely distressing and has had a negative impact on my health, in particular my recovery from post-concussion syndrome after my accident. I feel more disconnected and isolated, because I have lost my access to the people I was in touch with on a daily basis (some of them “online-only” friends, many of them not). Life on Facebook continues without me. I’m not being flooded with mails and messages of people asking me what’s going on or how I’m doing. It’s mainly silence.
Losing my content is also dreadful. I’ve spent some time this week-end going through my various archives from various platforms and tools over the years, organising them somewhat, checking they actually work, and exporting recent archives of the places I’m still at. My last proper facebook export is nearly 10 years old. I mentioned before, I think, that I tried to do an export in June, but gave up because it required me to manually download 52 files weighing 2Gb each, at a snail’s pace, and which made my network drop. The “export to Google Drive” didn’t work. So, my stuff on Facebook is a 104Gb export. Outliers in the data, anybody?
Why I’m Fighting
I made the choice to try and fight this, instead of sitting back and saying “oh well, that’s that”. I made the choice to fight because it is meaningful to me in different ways:
I care about my content locked up in the platform and would like to get it back.
I run a busy support group there, thankfully with a wonderful team who is holding the fort, despite being worn out by six months of my post-accident absence and a couple more years of me struggling to make time for the community amidst the other stuff going on in my life; I also have two decades worth of connections on the platform, which I do not want to just “cut off” like that – be it regarding the community or my network, real relationships are at stake, and if the future is away from Facebook, I want to be able to manage the transition and not be thrown off the plane in mid-air.
I am not alone: this is not just about me, but about a systemic, structural issue that has real impact on thousands of people’s lives; I’m lucky I don’t have a business that depends on my facebook presence anymore, but it could have been the case. Others aren’t that lucky. We are innocent casualties in the war against the bad actors of online social spaces, and deserve some kind of justice.
Meta, as a company, and Facebook, as a platform, want to play an important role in shaping our world. They want to be an indispensable tool for businesses, and also for normal people, without which they have no value for businesses. To me, it is unethical to have such ambition regarding their role in society and not provide even a semblance of support to those who make it possible – even if, as the saying goes, they “are the product”, because they do not pay. In my small modest way, taking a stand against enshittification.
This means that for the last 11 days, in addition to dealing with the impact of this suspension, I have been looking up articles, searching for solutions, writing blog posts, posting on a bunch of social media platforms I am normally dormant on, DMing friends and vague contacts, drawing up an action plan in my head, and putting my poor injured brain through the ringer to try to figure out what to do, where to start, what to prioritise, who to contact or speak to, in hopes of getting this suspension reversed. All that, knowing that chances are extremely slim and that it is probably useless.
Reconnecting Elsewhere
So, now that you’ve read all that, and without losing sight of it, what has been interesting? Clearly, reconnecting with my blog and feeling motivated to invest in ways of connecting to others and building community where I am not ceding control of everything to the Borg. (No, not that Borg – the new one.) That was already underway, but it has now been prioritised.
It has also made me aware of how facebook encourages a certain type of writing/publication and a certain type of discussion. Not so much in terms of content, but in terms of form. And there is value in doing it differently. I actually wrote some e-mails to people, since my suspension. I shared shorter snippets of stuff (passing thoughts, comments on links I found, ideas, daily anecdotes) because on LinkedIn, Bluesky, Twitter and Mastodon, for example, there are character limits. On my blog there are none, so I have had a chance to ramble along more. I have rediscovered people who left the Facebook boat already and with whom I had lost touch, because I poured almost all my sharing and connecting energy into Facebook.
I also published a couple of videos on Youtube, and plan to do more.
Shared Content
One thing I have become acutely aware of is that even when platforms allow you to export your content, one’s content in a social space is not just one’s publications. It is also comments, participation in the shared content that is a conversation, or a community. All the comments I ever made on Facebook have gone with my suspension. There are conversation threads with holes in them now. All the comments and conversations that took place because I published something, or because I commented and somebody answered – gone. Once people interact with your content, build upon it, it is not 100% yours anymore.
This has been an ongoing preoccupation of mine in shared social spaces. I remember, many many years ago, when blogs were young, a blogger I was actively following deleted their blog one day. And with it, all the comments I had taken the trouble to leave on their posts. “Leaving a comment” does not adequately reflect it, actually. It makes it feel like a small gesture done for the benefit of the other, but it’s not that. A comment can have as much value as a blog post. What makes it a comment is that it is a response, not that it is small or insignificant. It can be something valuable given to the community, and it should not be the right of another person to unilaterally destroy it.
I do not remember who the blogger was. It happened more than once.
Some years back, a few of my contacts on Facebook started a kind of automatic removal of their posts after a certain amount of time had gone by, taking my shares and comments with them. I stopped sharing and commenting on those posts.
I know, the lesson is: if you don’t want something you write to disappear, write it on your blog. But context matters.
Content and Community
This “it’s my content, I’m allowed to delete it” mindset is also an issue in Facebook groups. In the diabetic cat group, it thankfully didn’t happen very often, but when it did, it was infuriating. Somebody would post with an issue. People would expend time and energy in providing good answers and support. Then the person would delete their post, and all the answers with it. The whole point of a support group is that what is said to one person may also help another, who is reading. As a community, we also get to know our members and connect to them, and in that respect, their history in the group is important. Being able to refer back to that history is what allows a support community to function at a certain scale. Facebook does not allow group admins to prevent members from deleting posts and comments – something the platform I’m looking at for the future, Discourse, allows. It’s not all black and white of course, if you post something stupid and want to remove it an instant later, you can. But you can’t take down whole comment threads because you don’t like your post anymore. Participating in a community comes with a certain amount of responsibility towards other members of that community.
So, back to Facebook, what has been lost – for me, but also for others – is not just my posts and the pages of my cats, but it’s also a shared history, through discussions in comment threads and reposts on other people’s walls.
If we were connected on Facebook, and you would like to stay in touch, think about subscribing to this blog, and find me on the socials of your choice: Bluesky, Mastodon, Threads or LinkedIn. I’m still on the bird site but not very active there. I want to do more videos on Youtube, so it might be a good move to subscribe to my channel. I haven’t managed to recover my Tiktok account, so that’s that for the time being. I also have Instagram and Flickr (dormant, maybe it needs waking up), and I’ve created a little WhatsApp community – mainly francophone – where you can get announcements when I publish something here and a little chat-space with others and me, a kind of weird version of my Facebook wall off Facebook (ask me to join).
Of course, I always like it when people leave comments. I promise not to delete my blog.
![Sortir de Facebook? 1. Micro.blog [en]](https://i0.wp.com/climbtothestars.org/wp-content/uploads/sites/8/2025/09/Screenshot-2025-09-30-at-13.43.15.png?fit=1200%2C680&ssl=1)
![Rebooting The Blogosphere (Part 3: Integration) [en]](https://i0.wp.com/climbtothestars.org/wp-content/uploads/sites/8/2025/09/img_3878.jpg?fit=1200%2C900&ssl=1)
![Who Will See My Comment? [en]](https://i0.wp.com/climbtothestars.org/wp-content/uploads/sites/8/2025/09/img_3301.jpg?fit=1200%2C900&ssl=1)
![Where Have All The Bloggers Gone? [en]](https://i0.wp.com/climbtothestars.org/wp-content/uploads/sites/8/2025/09/img_1812.jpg?fit=1200%2C900&ssl=1)
![Sauvegarder des publications et fils de commentaires Facebook [en]](https://i0.wp.com/climbtothestars.org/wp-content/uploads/sites/8/2025/09/Screenshot-2025-09-13-at-13.18.09-scaled.png?fit=1200%2C862&ssl=1)
![Facebook Account Back After 21 Days [en]](https://i0.wp.com/climbtothestars.org/wp-content/uploads/sites/8/2025/09/Screenshot-2025-09-12-at-23.11.29.png?fit=1200%2C877&ssl=1)
![Rebooting The Blogosphere (Part 2: Interaction) [en]](https://i0.wp.com/climbtothestars.org/wp-content/uploads/sites/8/2025/09/img_3213.jpg?fit=1200%2C900&ssl=1)
![Rebooting The Blogosphere (Part 1: Activities) [en]](https://i0.wp.com/climbtothestars.org/wp-content/uploads/sites/8/2025/09/img_3156.jpg?fit=1200%2C900&ssl=1)
![Blogging On My Phone (Facebook Suspension Day 17) [en]](https://i0.wp.com/climbtothestars.org/wp-content/uploads/sites/8/2025/09/image.jpg?fit=1200%2C900&ssl=1)
![Facebook Suspension: Day 11 [en]](https://i0.wp.com/climbtothestars.org/wp-content/uploads/sites/8/2025/09/img_2824.jpg?fit=1200%2C900&ssl=1)