organization:internet engineering task force

  • The Rise and Demise of RSS
    https://motherboard.vice.com/en_us/article/a3mm4z/the-rise-and-demise-of-rss

    Before the internet was consolidated into centralized information silos, RSS imagined a better way to let users control their online personas.

    The story of how this happened is really two stories. The first is a story about a broad vision for the web’s future that never quite came to fruition. The second is a story about how a collaborative effort to improve a popular standard devolved into one of the most contentious forks in the history of open-source software development.

    RSS was one of the standards that promised to deliver this syndicated future. To Werbach, RSS was “the leading example of a lightweight syndication protocol.” Another contemporaneous article called RSS the first protocol to realize the potential of Extensible Markup Language (XML), a general-purpose markup language similar to HTML that had recently been developed. It was going to be a way for both users and content aggregators to create their own customized channels out of everything the web had to offer. And yet, two decades later, after the rise of social media and Google’s decision to shut down Google Reader, RSS appears to be a slowly dying technology, now used chiefly by podcasters, programmers with tech blogs, and the occasional journalist. Though of course some people really do still rely on RSS readers, stubbornly adding an RSS feed to your blog, even in 2019, is a political statement. That little tangerine bubble has become a wistful symbol of defiance against a centralized web increasingly controlled by a handful of corporations, a web that hardly resembles the syndicated web of Werbach’s imagining.

    RSS would fork again in 2003, when several developers frustrated with the bickering in the RSS community sought to create an entirely new format. These developers created Atom, a format that did away with RDF but embraced XML namespaces. Atom would eventually be specified by a standard submitted to the Internet Engineering Task Force, the organization responsible for establishing and promoting the internet’s rules of the road. After the introduction of Atom, there were three competing versions of RSS: Winer’s RSS 0.92 (updated to RSS 2.0 in 2002 and renamed “Really Simple Syndication”), the RSS-DEV Working Group’s RSS 1.0, and Atom. Today we mostly use RSS 2.0 and Atom.

    For a while, before a third of the planet had signed up for Facebook, RSS was simply how many people stayed abreast of news on the internet.

    Today, RSS is not dead. But neither is it anywhere near as popular as it once was. Lots of people have offered explanations for why RSS lost its broad appeal. Perhaps the most persuasive explanation is exactly the one offered by Gillmor in 2009. Social networks, just like RSS, provide a feed featuring all the latest news on the internet. Social networks took over from RSS because they were simply better feeds. They also provide more benefits to the companies that own them. Some people have accused Google, for example, of shutting down Google Reader in order to encourage people to use Google+.

    RSS might have been able to overcome some of these limitations if it had been further developed. Maybe RSS could have been extended somehow so that friends subscribed to the same channel could syndicate their thoughts about an article to each other. Maybe browser support could have been improved. But whereas a company like Facebook was able to “move fast and break things,” the RSS developer community was stuck trying to achieve consensus. When they failed to agree on a single standard, effort that could have gone into improving RSS was instead squandered on duplicating work that had already been done. Davis told me, for example, that Atom would not have been necessary if the members of the Syndication mailing list had been able to compromise and collaborate, and “all that cleanup work could have been put into RSS to strengthen it.” So if we are asking ourselves why RSS is no longer popular, a good first-order explanation is that social networks supplanted it. If we ask ourselves why social networks were able to supplant it, then the answer may be that the people trying to make RSS succeed faced a problem much harder than, say, building Facebook. As Dornfest wrote to the Syndication mailing list at one point, “currently it’s the politics far more than the serialization that’s far from simple.”

    #RSS #Histoire_informatique #Politique_algorithme #Normalisation

    • J’apprécie, comme toi, qu’il fasse remarquer que les décisions
      techniques ont des conséquences politiques. Il est clair que l’abandon de facto de la #syndication SS a accéléré le passage d’un web décentralisé vers un web polarisé par les GAFA. Je suis moins convaincu par ses explications sur les raisons pour lesquelles la syndication n’a pas tenu sur le long terme :

      – dire que RSS n’est pas user-friendly est franchement débile. RSS est un format. L’utilisateur ne le voit pas. Quasiment aucun utilisateur
      de RSS, que ce soit côté producteur ou consommateur, n’a regardé à quoi ça ressemblait en utilisant vi ! Un logiciel peut être
      « user-friendly » ou pas. Pour un format, ça n’a pas de sens.

      – je trouve qu’il exagère le rôle des disputes au sein du monde de la
      syndication. Certes, ces disputes ont pu contribuer à semer le trouble mais n’exagérons pas : ça se passait dans un tout petit microcosme et la grande majorité des webmestres et des lecteurs n’en ont jamais entendu parler. (Au passage, le camp vainqueur est nettement celui qui voulait un format simple : les sites Web n’utilisent qu’une petite partie du format.) Et, d’une point de vue pratique, ces disputes n’ont eu aucune conséquence : tous les logiciels de lecture comprennent les trois formats. Le webmestre peut donc publier ce qu’il veut, sans inquiétude.

      – par contre, il parle trop peu des raisons politico-marketing de
      l’abandon de la syndication : propagande effrénée des médias et
      autres autorités en faveur des solutions centralisées, notamment.

  • Net of Rights - YouTube
    https://www.youtube.com/watch?v=m1U0Ebix-aQ

    Net of Rights is a short documentary film which explores the relation between Internet protocols and the promotion and protection of Human Rights. Internet Engineers have defined the Internet as a network of networks, providing connectivity for all users, at all times, for any content. Internet connectivity increases the capacity for individuals to exercise their rights, the core of the Internet, its architectural design is therefore closely intertwined with the human rights framework. However, the assertion that technology and the design of standards and protocols is a ethically neutral task are still commonplace. The series of interviews recorded during the 92nd meeting of the Internet Engineering Task Force (IETF), held in Dallas, Texas, in March 2015, demonstrated that this belief in the neutrality of standards and protocols is starting to change. It is becoming more apparent that promoting an open, secure, unfiltered and reliable Internet is essential for the rights to privacy, expression and assembly. But how can these concepts be addressed on the protocol level? Without taking human rights into account while developing protocols, the human rights-enabling characteristics of the Internet are at risk. While the Internet was designed with freedom and openness of communication as core values, as the growth in scale and commercialization of the Internet have caused a shift in those values. The influence of such world-views started to compete with other values. The rights-enabling characteristics of the Internet will be endangered if they are not properly defined, described and protected. The reverse is also true: if we don’t protect human rights online, we risk loss of functionality and connectivity of the Internet itself.

    #Internet #Droits_humains #Protocoles