Tag: rss

Where Have All The Bloggers Gone? [en]

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.

Anil Dash Writes About The Web We Lost [en]

[fr] Le web qu'on a perdu. Nostalgie.

Yes, there are people who have been blogging for longer than me. Quite a few of them, actually. Anil Dash is one. You should read him.

His most recent article (found thanks to danah, who has also been blogging for longer than me, and whom you should also read) is titled The Web We Lost. It hits right on the nostalgia that has been creeping up on me these last years, expressed for example in A Story About Tags, and Technorati, and Tags or Ye Olde-School Blogs Are Still Around.

Twitter and Facebook and Tumblr and Pinterest are all great, but they tend to suck us in, and I feel we are all collectively high on real-time content and interaction. I miss the slower days. I miss the sense of “community” I felt with other bloggers in the old days, as I mention in the wrap-up post to my “Back to Blogging” challenge. I feel that on Twitter and Facebook community has been replaced with network. Networking is great. I love spending time with my network. But it’s not the same thing.

Most of all, the timeline we now live in is made up of transient content. It’s there and gone. It’s the world of orality, of the spoken word which evaporates once pronounced, even though we are typing. We are going back to an oral tradition. Blogs and wikis, however, are still part of the written tradition. We are losing searchability. We are also using content portability due to the lack of RSS feeds on certain platforms, and increasingly restrictive API access. APIs seem to be the promise for more holes in our buckets, but they seem more and more to be a way to control tightly what happens to the content locked in a given platform.

That’s sad. That’s not the way I hoped things would go.

There is more. Go and read Anil’s piece. And leave a comment there through Facebook.

Survivre à l'heure du trop d'informations [fr]

Lors du très sympathique Bloggy Friday d’hier soir, la conversation est à un moment donné partie sur les fils RSS, Twitter, le temps que ça prend, et la quantité d’informations à s’enfiler chaque jour, si on rentre là-dedans.

Je vous présente donc ma recette pour survivre à l’heure de la pléthore d’informations à portée de nos souris qui est la nôtre. Elle est très simple, la recette:

  • lâcher prise et abandonner tout espoir d’être “à jour” ou de “tout lire”
  • mettre l’accent sur les connexions et le réseau (quelles personnes je suis sur Twitter, connexions facebook, abonnements RSS)
  • considérer que tous ces flux sont comme une rivière où l’on fait trempette de temps en temps, ou comme une station radio diffusant en continue et qu’on allume lorsqu’on en a envie.

Quelques éléments supplémentaires:

  • si l’information est importante et que le réseau est de qualité (voir le point ci-dessous), elle vous parviendra par de multiples chemins (exit donc l’angoisse de “rater” quelque chose de vital)
  • la qualité du réseau est cruciale: ce n’est pas juste une question de quantité de connexions ou de contacts (même si cette dimension joue un rôle), et chacun est entièrement responsable du réseau qu’il construit et maintient autour de lui.

Pour ma part, j’ai depuis longtemps accepté que je ne suis pas une lectrice régulière de blogs. Je sais, cette information en surprend plus d’un, car je suis perçue comme une personne très connectée et “au courant”. Mes lectures sont des butinages, incités par ce que je vois passer dans ces différents flux (Twitter, Facebook, Tumblr, surtout). De temps en temps, je vais expressément voir le blog de telle ou telle personne, ou son compte Facebook, ou son Twitter — parce que j’ai envie d’en savoir plus sur ce qu’elle raconte récemment.

Mais je ne cherche pas à “tout lire”, oh non, au grand jamais. Et je m’en porte fort bien!

Feedly: More Than a Newsreader, Maybe Your Search Engine of Tomorrow? [en]

A bit over a year ago, I switched from Google Reader to Feedly. I have a troubled history with newsreaders: I tend to not use them, partly because I don’t really read blogs. But I used Google Reader for some time, and then Feedly. I really like Feedly. Really. (Plus, it saved 4 months of posts for CTTS after the dropped database disaster.)

All this to say that for many months, I have not really opened Feedly, and I feel kind of sad/bad about it. Twitter and Tumblr are my main sources of “new information”, and I’d love to find a way to use Feedly in a way that works for me. But it just doesn’t seem to happen.

A couple of weeks back, I saw this tweet from Ewan:

Twitter _ Ewan McIntosh: Over the hols I managed to ...

He says that he has sorted his feeds into “30 must-read-daily RSS feeds, with the other 2000 sitting behind as personal search engine”.

Whee! For some time now, I’ve been convinced that the future lies with allowing search in subsets of the web. There’s too much stuff out there, right? Also, in this era of partial attention (which I don’t consider to be a bad thing, in the “keeping a distracted eye on” sense), you often end up trying to “refind” something you know you’ve seen (but where?) — just like I had to dig out Ewan’s tweet ten days after I’d seen it in passing.

That’s why I like Lijit, for example (I’ve put the search box back here on CTTS, by the way): it allows me or my readers to do a search on “my stuff”, including CTTS, Digital Crumble, Twitter, del.icio.us… Sometimes I know I’ve said something, but I can’t for the life of me remember where (see this? having to search your own words…)

Feedly is pretty good at allowing you to search all the stuff you’ve subscribed to:

feedly | explore facebook

It offers a mix of a little bit of generally popular stuff with “your sources”. I like that. So, I like Ewan’s idea of feed subscription as “add this to my search sources” rather than “oooh, I’m going to read this every day”.

I have to say I’m interested in hearing about how you use Feedly or Google Reader (particularly the social aspects) if you’re not a “religious-daily” newsreader enthusiast. There has to be something between “keeping up with my feeds” and “never opening my feedreader”.

De la lecture des blogs [fr]

[en] I'm not a regular blog reader. I check a small handful of blogs religiously, and that's (with one or two exceptions) because they belong to close friends. I go on blog-reading binges, either person-centred ("well, I wonder what such-and-such has written about lately, or how she is doing") or topic-centred (digging deeper into an issue, or trying to solve a problem I'm facing).

Do you find it paradoxical for a blogger to not have a "blog subscriber" profile?

Ça m’embarrasse parfois un peu qu’à cause de ma réputation en tant que blogueuse, on parte du principe que je suis une lectrice de blogs assidue.

Bien sûr, je lis des blogs. Mais pas comme certains.

Je n’ai pas une liste de blogs que je lis religieusement. J’ai un lecteur RSS (j’aime Google Reader, et encore mieux, feedly) mais depuis six à huit mois, j’avoue que je l’ai à peine ouvert.

Il y a une poignée de blogs appartenant à des amis proches que je lis régulièrement. Ce sera peut-être vexant pour certains, mais les blogs que je lis, je les lis plus parce que j’ai une relation personnelle avec leur auteur, que parce que leur contenu me faisait revenir (quelques exceptions notables: Kathy Sierra, Zeldman, Tom Reynolds).

Pourtant, je lis des blogs. Mais comment?

De temps en temps je fais une crise de lecture. Il y en a deux sortes:

  • les thématiques
  • les personnelles.

Les crises de lectures “personnelles” (ou centrées sur la personne) sont de l’ordre de “oh, je me demande ce que devient tel et tel, ou ce qu’il a écrit récemment, hop, un petit tour sur son blog”.

Le problème avec les blogs (enfin, je dis ça, mais c’est une de leurs qualités) c’est qu’une fois qu’on commence à lire, on n’en finit pas. On suit un lien qui nous emmène ailleurs, on plonge dans les archives, bref, parfois, une heure plus tard, je lis encore.

Ou bien du coup, je me mets à rédiger un billet sur un sujet qui m’aura interpellé.

Quant aux crises de lecture “thématiques”, je pars sur un sujet qui m’intéresse (souvent lié à un problème à résoudre ou un enjeu concret dans mon présent, mais pas forcément), et je fais du blog-hopping pour en faire le tour. Google, Technorati, articles en rapport, tout y passe.

En résumé, je n’ai pas le profil “abonné” ou “lecteur fidèle”, mais plutôt “butineuse” voire “boulimique”. Twitter a en grande partie remplacé mon lecteur RSS, même si celui-ci n’est pas mort.

Et vous, comment lisez-vous les blogs? Trouvez-vous paradoxal qu’on soit blogueur mais non lecteur régulier d’autres blogs? A plus forte raison si l’on prêche, comme c’est mon cas, que la lecture de blogs est indispensable à leur écriture? Est-ce que je nage en plein paradoxe?

Démarrer avec Google Reader [en]

[fr] Getting started with Google Reader, for my French readers.

Comme ces temps je n’arrête pas d’initier des gens de mon entourage à Google Reader, je me suis dit, allez, hop, quelques instructions par écrit.

Google Reader, c’est un lecteur RSS (ah oui, c’était en 2003 que j’expliquais ça, un peu trop en avance, pour changer) auquel vous avez accès si vous avez un compte GMail (qui n’en a pas?). En bref, ça permet de centraliser en un seul endroit toutes vos lectures de blogs et de nouvelles.

Dans votre GMail, cliquez sur “Reader” en haut à droite. Ça ressemble à ça:

Google Reader: accueil

Première chose à faire: ajouter un abonnement.

Google Reader: ajouter un abonnement

Définissez (si vous le désirez) un dossier pour votre abonnement. Vous pouvez ainsi séparer vos lectures par centre d’intérêt. C’est utile, car ensuite vous pouvez regarder toutes les “nouveautés” dans une seule catégorie sans vous soucier des autres. Exemples: blogs, mes amis, trucs préférés, nouvelles, horticulture, technique… bref.

Google Reader: s'abonner à un blog

Ajoutez autant d’abonnements que vous voulez:

Google Reader: détail d'ajout d'abonnement

Voilà, c’est aussi facile que ça!

Google Reader: tour du proprio

Au prochain épisode, je vous montrerai comment profiter des fonctionnalités “sociales” de Google Reader, et je vous présenterai Feedly, une extension Firefox qui “habille” Google Reader de tout un tas de trucs sympas (sans compter que c’est beaucoup plus agréable à l’oeil).

Google Reader: changer la langue

A bientôt!

Le futur n'est pas encore ici de façon homogène [fr]

[en] What I'm doing these days: getting my "offline crowd" acquainted with newsreaders (Google Reader and Feedly, in particular).

Ces temps, je me retrouve régulièrement à initier les gens à Google Reader ou Feedly. C’est où en sont gentiment ceux de mon entourage qui sont moins connectés que moi, mais qui par contagion, s’y mettent gentiment. Il y a deux ans, c’était les comptes GMail, Skype, et doucettement GTalk.

Please Don't Be Rude, coComment. I Loved You. [en]

[fr] J'étais une inconditionnelle de la première heure de coComment. Je les ai même eus comme clients. Aujourd'hui j'ai le coeur lourd, car après le désastre de la version 2.0 "beta", le redesign du site qui le laisse plus confus qu'avant, les fils RSS qui timent out, le blog sans âme et les pubs qui clignotent, je me retrouve avec de grosses bannières autopromotionnelles dans mon tumblelog, dans lequel j'ai intégré le flux RSS de mes commentaires.

Just a little earlier this evening, my heart sank. It sank because of this:

Steph's Tumblr - rude cocomment

That is a screenshot of my Tumblr. And what coComment is doing here — basically, inserting a huge self-promotional banner in their RSS feed — is really rude.

I’m really sad, because I used to love coComment. I was involved (not much, but still) early on and was a first-hour fan. They were even my client for over six months, during which I acted as a community manager, gave feedback on features to the team, and wrote a whole bunch of blog posts. This ended, sadly, when coComment finally incorporated, because we couldn’t reach an agreement as to the terms of my engagement.

Inserting content in the RSS feeds is only the latest in a series of disappointments I’ve had with the service. I used to have a sidebar widget to show the last comments I’d made all over the place on my blog, but I removed it at some point — I can’t remember when — because it had stopped working. I tried adding it again, but for some reason WordPress can’t find the feed. It seemed very slow when I tried to access it directly, so maybe it’s timing out — and I think I recall that is what made me remove it in the first place.

I’m sad also to see blinking ads on the coComment site, confusing navigation, pages with click here links, and a blog which has no soul, filled with post after post of press-release-like “we won this contest”, “we’re sponsoring this event”, “version xyz released”, “we were here too” — all too often on behalf of a mostly faceless “coComment Team”. CoComment used to have something going, but to me it now seems like an exciting promise that lost its way somewhere along the line.

Last August, the version 2.0 beta disaster made me cringe with embarrassment for my former love (who on earth takes all their users back to beta when 1.0 was stable?) and left many blogs paralyzed, including my own. I started writing a blog post, at the time, which I never published, as other things got in the way. Here’s what I’d written:

I reinstalled the extension yesterday (I’d removed it a few months ago because I suspected it might be involved in a lot of browser hang-ups) but had to uninstall it a couple of hours later:

  • too many non-comment textareas get the coco-bar
  • blacklisting seems broken
  • pop-up requesting info confirmation for website blocking form submission of non-comment forms, even though coco-bar was removed AND extension was deactivated for the page.

It would be nice to be able to read some clear and detailed information about these issues and their resolution on the blog, so that I know when it’s worth trying the extension again.

Also, a major issue is that when the coComment server isn’t responding, people cannot leave comments on integrated/enhanced blogs (like this one, or my personal blog). I had to remove coComment integration from my blog so that coComment downtime doesn’t prevent my readers from leaving comments.

Update: in case this wasn’t clear first time around, these problems have since then been solved and coComment apologized for the mess. It doesn’t erase the pain, though.

So, coComment — and Matt — are you listening?

You’re in the process of alienating somebody who was one of your most passionate users — if you haven’t lost me already. I cared. I forgave. I waited. I hoped. But right now, I don’t have the impression you care much about me. I’ve seen excuses, I’ve even seen justifications, and now I see large ugly banners in my Tumblr. What happened to you?

You’ll have understood, I hope, that this is not just about me. This is about the people who use your service. The service you provide is for us, right?

Blog Host Ugliness [en]

[fr] Une amie Serbe s'est vu poser un ultimatum par son hébergeur de blogs: 24 heures pour supprimer commentaires d'un autre blogueur et liens vers ses sites, ou voir son blog disparaître.

L'hébergeur en question (qui utilise WordPress multi-utilisateurs, comme WordPress.com) avait en outre désactivé la fonction d'exportation de blog.

On s'en est sortis comme on a pu (voir ici).

Mis à part le côté technique de l'affaire, il est absolument scandaleux qu'un hébergeur de blogs se permette d'agir ainsi. Certes, tout hébergeur est libre de "virer" des clients -- mais déactiver au préalable la fonction d'exportation des blogs, cela atteint des sommets de mesquinerie. A bon entendeur.

Edit: sur Seesmic, l'histoire en français et en vidéo.

Note: I’ve updated this post as I gathered information allowing me to see more clearly in this whole mess. Please read the comment if you’re going to jump in the conversation or blog about this.

Wednesday night, my friend Sanja from BlogOpen (she was my very kind and competent hostess) pinged me on IM. She had less than 24 hours to export her blog before her blog host shut it down.

It was a blog hosted by WordPress multi-user [Edit: not WPMU]. Easy enough, I thought. There is an export function. Unfortunately, when I logged in (the interface was in Serbian, but I can find my way through WordPress with my eyes closed), this is what I found:

WordPress (MU?) with no Export

Even if you don’t understand Serbian, you can see there is a missing tab. I tried calling /wp-admin/export.php directly, but the file had been removed.

Well, after a bit of poking, prodding and thinking, this is what I came up with (reminder: WPMU means that you can’t there was no possibility to install plugins and no direct access to the server):

Last Hope Export of WordPress MU Blog

I went into Options > Reading. I set the feeds to “entire post”. As there were 110 posts in this blog, I set the home page to display all of them, with a little margin for error. There were more than 1400 comments, so I set the maximum number of items in a feed to 1500.

Then I did three things:

  • saved /feed (an RSS dump of the blog posts)
  • saved /comments/feed (an RSS dump of the comments)
  • scraped the blog (with single blog post pages) as an extra backup by running wget -r -l1 -w1 BLOGURL (thanks, John) from my server (also to save the images).

The blog was saved. I couldn’t import the RSS dump of blog posts into WordPress.com, where I told Sanja to open a new blog account, so I quickly set up a regular WordPress install on my server, imported it there, and exported it in WXR format. Great.

Comments, however, are another story. If you’re in a hackish mood, any help would be appreciated.

We’ll probably have to deal with the images too once the blog has been completely wiped off the 381.com server — for the moment it seems like it was disabled, but the images are still there (see this one for example).

There, that was for the technical part.

Now for a personal comment. I find it utterly disgusting and shocking that a blog host owner would give people an ultimatum to leave and disable the export function in the blogging software. Sanja tells me that they had the export function until a few days before the ultimatum.

Of course, a blog host can choose not to host certain people. But trying to lock people in by disabling export of their own data is simply evil. If you’re kicking people off your system, you damn well better make sure they can take their data with them.

Edit, 27.01, 12:00: I’m happy to learn that it seems the disabling of the export function was not related to the ultimatum, and that the blog381 people were not actually trying to actively lock people in. However, it remains that it’s pretty delicate in a conflictual situation to tell people to “submit or leave” when they don’t have a way to export their data on their own.

So, people, please. If you need a blog host, choose a serious one. WordPress.com for example. Or Blogger. Or Typepad. Putting your precious blog between the hands of an individual is risky (weblogs.com, anybody? and if you remember, people on weblogs.com at least had the guarantee they could export their data…)

How did this happen?

I got some details about the situation, but a word of warning about that, first. The source material to this Serbian blogosphere drama is all in… Serbian. I’m relying here on what my friend Sanja told me about the situation, and I do not doubt her good faith. I know, though, that stories do have multiple sides, and that there might be more to the background than what I’m telling you here — but whatever the background story, it cannot justify the behaviour of this blog host.

From what I gathered, what brought about this crisis is a quarrel between two bloggers: Tatjana aka Venus aka Lang (Update: Tatjana is not happy that I’m linking to her and has redirected visitors to this site elsewhere; to see her blog, copy-paste the link http://www.laluve.com/ in your browser), the owner of the Serbian blogging platform blog381.com (not the Tatjana who organized BlogOpen!), and another pretty popular blogger. At some point, Tatjana decided to forbid the people using her platform from linking to this other blogger or harbouring his comments.

Here is the warning she posted on the community forums:

Vlasnik blogova

http://bruh.org/ludizmaj/,

http://www.blogoye.org/pecina/,

http://www.blogoye.org/Mudrosti/,

http://www.blogoye.org/sujeta/

(ima verovatno jos ali ne mogu da trazim)

je ovom blog sistemu naneo stetu laziranjem glasova oko izbora za najblogera (na kom je on bio ‘pobednik’), ‘miniranjem’ sledeceg izbora, sirenjem neistina, traceva, vrbovanjem novih blogera sa tri osam jedan sistema, a sve u cilju da se naskodi ovom sistemu a poveca sopstveni traffic i “ugled”.

Za one koji nisu dovoljno informisani i sve ostale koji su slusali ili nisu, samo jednu stranu price od gore pomenutog, necu dodatno iznositi nikakve detalje, niti vise imam nameru da se borim sa provincijalizmima pojedinih ljudi koji su bili ili jesu na neki nacin u komunikaciji sa blogom381 i njegovim korisnicima.

Slobodna volja svakog od nas da pise kako i gde hoce, ali oni koji se odluce da i dalje pisu ovde nece moci da imaju linkove ka ovim blogovima niti komentare vlasnika istih.

Ukoliko imate zelju,nameru ili potrebu da ostanete na ovom blog sitemu, obrisite linkove i komentare gore pomenutog blogera u roku od 24h.

Translation (Sanja was a bit tired, so forgive the wobbliness):

The owner of these blogs
http://bruh.org/ludizmaj/,
http://www.blogoye.org/pecina/,
http://www.blogoye.org/Mudrosti/,
http://www.blogoye.org/sujeta/

has caused damage to this blog system by faking votes for the election of “The best blogger” (where he was “the winner”), and was undermining the next election by spreading gossip, lies, and recruiting new 381 bloggers, with only one aim: to damage this community and increase his own blog traffic and “reputation”.

For those who are not informed well enough, and all others who were listening or didn’t, only one side of the story of the person mentioned above, I will not give any additional details, nor do I have the intention to fight with provincialism of some people who were or in some way are connected to blog381 communication and their users.

It is the free will of each of us to write how and where we want to, but those who decide to keep writing here, will not be able to have links to these blogs or comments by their owner.

Those of you who have the wish, intention or need to stay on this blog system, should delete links and comments of the blogger (mentioned above) within 24 hours.

Sanja learnt about this because the owner of the blogging platform left a comment on one of her posts (not the most recent) to let her know about it. Given that the “other blogger” in question is a friend of Sanja’s, she wasn’t going to comply.

Other bloggers have also seen their blogs deleted, or at least de-activated (actually, before the 24-hour limit was up). A dozen or so, says Sanja.

If you want to chime in on the “political” side of this story (particularly if you’re involved in this story or a direct witness), you’re welcome to use my comments. However, I ask (as always) that everybody remain civil and refrain from personal attacks (commonsense blogging etiquette, y’know).

Update: It seems that since Sanja’s blog was deactivated, the whole blogging platform has been shut down, with a message that people can e-mail the administrator to get an export of their blog. This message was not there during the ultimatum period.

In a comment to this post, Tatjana aka Lang asked me to remove the link to her blog, http://www.laluve.com/ , which I had placed upon her name. As I have refused to remove it (linking to the people involved in this story is perfectly relevant, and on the web, you can link to who you want, anyway), she has set up a redirection which sends visitors from this site straight off to CNN. So, I’ve left the link in, of course, but provided you with a handy copy-paste if you want to go and visit her all the same.