Für das SCREENGUIDE Magazin (Ausgabe 26) wurde Aaron Parecki zum Thema Indie Web (Camp) interviewt. Das abgedruckte Interview ist aus Platzgründen und für ein besseres Verständnis aber leicht gekürzt und ins deutsche übersetzt worden.

Mit freundlicher Genehmigung von Nicolai Schwarz (Projektleiter SCREENGUIDE Magazin) und Aaron Parecki, darf ich euch hier das Original präsentieren:

SCREENGUIDE: Hi Aaron, what are the reasons for founding IndieWeb respectively organizing the first IndieWebCamp?

Aaron Parecki, @aaronpk CTO bei Esri R&D Center, Portland Mitgründer IndieWeb & IndieWebCamp
Aaron Parecki, @aaronpkCTO bei Esri R&D Center, PortlandMitgründer IndieWeb & IndieWebCamp

Aaron Parecki: In 2010, Tantek Çelik and I attended the "Federated Social Web Summit" in Portland, Oregon. After the event, we walked away feeling somewhat dissatisfied, and decided we wanted to take a slightly different approach. We wanted to focus on:

  • creators instead of talkers – prioritize and encourage people who create things (design, UX, or code) instead of just talking about it
  • use your own tools – if you are building something you expect other people to use, you should be using it yourself on your own website
  • own your data – own your content online by publishing it first on your own website, and afterwards copying it to silos like Twitter and Facebook

We took these and several other principles, joined forces with Amber Case and Crystal Beasley, and organized the first IndieWebCamp unconference in 2011. The goal of the conference was to create a space for like-minded individuals to experiment with owning their content and identity on the Web.

SG: In 2011 there was one IndieWebCamp in Portland. For 2015 there are nine different Camps planned. Did you expect that kind of success?

AP: I never expected there would be IndieWebCamps in nine different cities so quickly! It's been a pleasant surprise to see so many people excited about it, and it's been fun to visit other cities to help organize the camps as well!

SG: Do you have any idea how many people have implemented IndieWeb-features on their website? (Maybe you have a number how many sites did log into indiewebcamp.com or how many are using Bridgy?)

AP: It's great to see new people show up in our IRC channel or make their first POSSE post from their website, and I'm constantly amazed at how many people show up every day! It's hard to get a good sense of how many people have implemented indieweb features, since by definition, there is no central directory or registry we can look at. However, there are over 170 people who have added their websites to our "IRC People" page which is used to display profile photos in our IRC logs. If you look at the stats of Bridgy, a popular service that sends webmentions from activity on various silos like Twitter and Facebook, there are over 1.200 people signed up!

SG: What is so fascinating about the community?

AP: The best part about the community is how positive and productive everyone is! The community is extremely friendly, we often get visitors in our IRC channel who have some simple questions and lots of people jump to help them out. People start out by building their own web presence, either by writing their own custom software or installing someone else's software such as WordPress or Known. Having everyone working on their own websites leaves a lot of room for experimentation and trying out multiple approaches to solving problems. We encourage a diversity of approaches and implementations. This makes the IndieWeb stronger and more resilient than any one approach or project.

SG: You wrote the software p3k for your own website aaronparecki.com. What does p3k do?

AP: p3k is the name of the software that powers my website, aaronparecki.com. It allows me to create many different kinds of posts, everything from simple text notes and photos, as well as my bike rides and what I'm eating. All the posts are marked up with Microformats so they show up in peoples' readers. If you write a reply to one of my posts, you can send a webmention and your reply will show up as a comment. p3k also supports Micropub which means I can post from many other apps.

While some people choose to develop their websites or CMSs entirely as open source, I've been taking a slightly different approach while building p3k for myself. Instead of building an open source CMS, and expecting people to use it the way I've built it, I instead develop small components and libraries that I use in my website, and I make those open source. For example, you can use the php-comments library I've written to parse comments from external websites, or you can use the date-formatter library to render dates and date ranges in a human-readable format, so you'd see "December 9-12, 2015" instead of "2015-12-09 through 2015-12-12".

This approach allows me to make small pieces that are more likely able to be useful to others, and avoid the hassles of building a polished install and configuration process. In fact many of these libraries are in use by other indieweb sites currently!

SG: The IndieWeb focuses on owning your content. How do you use social media personally?

AP: I use social media similar to most people, to keep in touch with my friends. I post photos, notes and articles on my website, and syndicate them to silos like Twitter or Facebook. When I'm reading other peoples' websites or Twitter feeds, I reply to posts from my site, or "like" them from my site. For an example of what I mean by "liking" something from my site, you can see all the things I've "liked" here: aaronparecki.com/likes I enjoy seeing photos my friends are sharing, so I follow people on Instagram or see photos they post on their own sites.

I don't normally read the full timelines of sites like Twitter or Facebook, since there is often too much content to keep up on. Instead, I typically read things by searching specific hashtags or terms. In fact I have a persistent Twitter search running all the time that sends results to several IRC channels I am in. I have searches running for projects I'm involved with, such as "indiewebcamp" or "webmention", as well as for my name or other more private search terms. This makes it easy for me to follow topics I care about without getting lost in the noise of all the other posts.

SG: What are currently the big (advanced) topics for the IndieWeb?

AP: This year is shaping up to be the year of the Reader. Now that there are quite a lot of people publishing content on their own sites, the missing piece is having one place where you can read the posts of everyone you're following, and reply to the posts from within the same interface. Facebook and Twitter have shown us that an integrated reading and commenting experience is what people really want, and this is something that previous readers such as Google Reader didn't do.

There has already been some great progress made on readers this year, and lots of interest from people using them! Once there are a few readers to choose from, it will be easy to avoid going to Facebook or Twitter to read things at all! The great part of the way these readers are being built is that you can use them to reply to the things you're reading, but the replies are actually sent from your own site! This is made possible by Micropub, so if your site has a Micropub endpoint, readers can use it to create posts on your site. For example, I wrote this reply inside a reader app, and my site even shows the app used to post it: http://aaron.pk/r4_i5

There are also many Micropub apps in the works right now, which will enable you to post to your site from a mobile app, desktop app, or other web apps. Why limit yourself to your built-in posting interface such as the WordPress admin page, when you could be using more streamlined apps for posting photos or audio! Micropub is exciting because it enables a whole ecosystem of apps to be developed, so that people have many choices for how to post content to their own websites.

Mein erster Titelthema Artikel 🙂

…über ein Thema das mich gerade sehr beschäftigt:

Die IndieWeb-Bewegung hat gerade in den letzten Jahren enorm an Popularität gewonnen. Kein Wunder: Posterous wurde von Twitter gekauft und eingestellt, Google Buzz durch Google Plus ersetzt und MySpace hat seine Blogging-Plattform geschlossen. Alleine mit Geocities wurden 2009 knapp 23 Millionen Seiten unwiderruflich vom Netz genommen. Riskieren Sie keinen weiteren Datenverlust, schließen Sie sich dem IndieWeb an und machen Sie sich unabhängig.

Es freut mich sehr, dass das SCREENGUIDE Magazin im Allgemeinen, und Nicolai im Speziellen, der IndieWeb Idee so viel Platz eingeräumt haben!

Neben meinem Artikel über das IndieWeb, gibt es noch einen kleinen Abschnitt über IndieTech, ein Interview mit Aaron Parecki (einem der vier Gründer des IndieWebCamps) und einen Artikel über Known, DER IndieWeb Platform von Ben Werdmuller (dem Gründer von Elgg).

Ich würde mich diesmal sehr über Feedback freuen… also kaufen! Sofort!

LinkedIn möchte Sie dabei unterstützen, im Beruf produktiv und erfolgreich zu sein. […] Dabei stellen Sie sich vielleicht die Frage, wem gehören eigentlich die Rechte an den Inhalten, die Sie auf LinkedIn veröffentlichen? Die Antwort ist, einzig und allein Ihnen. Zum weiteren Schutz Ihrer Rechte aktualisieren wir mit Wirkung vom 23. Oktober 2014 unsere Nutzervereinbarung.

Gerade kam ein Newsletter von LinkedIn… Anscheinend wollen sie die Nutzervereinbarung zu Gunsten ihrer User abändern… Aha! Ich bin gespannt!

Und dann auch noch:

Außerdem können Sie jetzt Ihre LinkedIn Daten exportieren, wie z. B. Updates, die Sie mitgeteilt haben, Ihre Aktivitäten sowie Informationen zu Ihrem Zugriffsverhalten.

Facebook kauft WhatsApp und ich hab nur wenig Möglichkeiten meine Konsequenzen daraus zu ziehen. Leider sind alle aktuell populären "Chat" Systeme direkt an die App gekoppelt und ich "muss" zwangsläufig die App benutzen die mein Freundeskreis bevorzugt.

WhatsApp benutzt intern das XMPP-Protokoll und arbeitet dadurch ja theoretisch dezentral und auch Telegram hat beispielsweise eine Art offenes Protokoll gebaut… Das Problem: Woher wissen auf welchem Server der Andere angemeldet ist.

Seit WhatsApp die Identifizierung über die Telefonnummer (statt einer z.B. E-Mail Adresse) eingeführt hat, sind viele anderen diesem Beispiel gefolgt und es gibt nichts Verwerfliches daran. Jeder der eine solche App nutzt hat zwangsläufig ein Telefon, was bedeutet dass er auch eine Telefonnummer hat und die Wahrscheinlichkeit dass in seinem (Telefon-)Adressbuch mehr Telefonnummern als E-Mail Adressen stehen ist auch sehr hoch. Prinzipiell also eine gute Idee! Leider kann man aber anhand einer Telefonnummer nicht auf einen Server (mal abgesehen vom Telekommunikations-unternehmen) schließen und das bedeutet, dass das Verfahren leider auch nur zentral funktionieren kann. Nutze ich WhatsApp, kann man mich nur über die WhatsApp-Server erreichen, für Telegram läuft die Kommunikation nur über die Telegram-Server usw.

Um mit XMPP oder anderen Protokollen wirklich dezentral arbeiten zu können, müsste man über die Telefonnummer erfahren können welchen Chat-Server der Andere benutzt. Vielleicht über so eine Art Tel to Id – Service oder über andere Protokolle wie z.B. SMS. Damit könnte sich jeder selbst den Client seines Vertrauens aussuchen und alles wäre gut besser 😉