Page

· · zu lesen

(Die Idee zum Header-Bild habe ich mir von Nico Hagenburger geliehen)

Zum Impressum oder zur Datenschutzerklärung.

Zwei Informationen vorweg:

  1. Dies ist ein privates Blog über das „open, portable, interoperable, social, synaptic, semantic, structured, distributed, (re-)decentralized, independent, microformatted and federated social web“, ich hab kein Interesse an bezahlten Guest-Posts oder Affiliate-Links. Wenn du mir etwas gutes tun möchstes, dann schau einfach auf meiner Donate-Seite vorbei.
  2. Solltest du Fragen, Probleme oder Feature-Requests zu einem meiner Plugins oder anderem Code haben, dann schreib mir bitte über WordPress.org oder GitHub Issues.

E-Mail

Die einfachste Kontaktmöglichkeit ist über E-Mail:

<vorname> @ <nachname> .org

(Bitte ersetzt die Platzhalter in den spitzen Klammern… Bevor ihr fragt: ja es ist schon passiert!)

Telegram

Ihr könnt mich auch gerne per Telegramm anschreiben: https://t.me/pfefferle

notiz.Blog hat übrigens auch einen Channel, über den ihr meine Artikel abonnieren bzw. mich erreichen könnt: https://t.me/notizblog

IRC

Mein Nickname auf IRC ist pfefferle. Wenn du mit mir über das IndieWeb oder Microformats diskutieren möchtest, dann ping mich einfach über folgende Channels an:

105 Kommentare
Schlagwörter

105 Kommentare zu “Kontakt”

  2. You know it was an awesome Indieweb Summit for WordPress, when you log in and see all these awesome updates!
    Just some of the WordPress related updates that were built and released at the Indieweb Summit this weekend in Portland.Congratulations and Thank You to Matthias Pfefferle, David Shanske, Ryan Barrett, Michael Bishop, Asher Silberman, Brandon Kraft, Lillian Karabaic and all of the others in the Indieweb community who provided the setting, conversation, thinking, and underpinning that made all this possible!
    Syndicated copies to:
    Related

    Author: Chris Aldrich

    I'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history.


    I’m also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.
    View all posts by Chris Aldrich

    Antworten

  3. You know it was an awesome Indieweb Summit for WordPress, when you log in and see all these awesome updates!
    Just some of the WordPress related updates that were built and released at the Indieweb Summit this weekend in Portland.Congratulations and Thank You to Matthias Pfefferle, David Shanske, Ryan Barrett, Michael Bishop, Asher Silberman, Brandon Kraft, Lillian Karabaic and all of the others in the Indieweb community who provided the setting, conversation, thinking, and underpinning that made all this possible!
    Syndicated copies to:
    Related

        Author: Chris Aldrich


        I\\\'m a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history.&#xD;


    I\\\’m also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.
    View all posts by Chris Aldrich

    Antworten

  7. There are a bunch of ways for using WordPress with Mastodon, so tonight I thought I’d start experimenting with some.
    Straightforward syndication/POSSE plugins (requires an account on a Mastodon instance):
    Mastodon Autopost
    Mastodon Share
    More advanced plugins (shouldn’t require an account as they make your site behave like a standalone instance of Mastodon):
    Ryan Barrett‘s Fed.Brid.gy – allows one to let their own website federate directly into Mastodon and other networks in various ways. I’ve tinkered with it a bit but haven’t gotten all the pieces working yet. This was just recently released, but Ryan has gotten some interesting pieces working well based on tests I’ve seen.
    Matthias Pfefferle‘s OStatus – supports a variety of post kinds on Mastodon; it includes a handful of sub-plugins (Webfinger, Salmon, Activity Streams, etc.) to get everything working. I hope to get around to testing this out shortly too, but has many more moving parts.
    Do you know of any other interesting methods for using these two systems in combination with each other in a straightforward manner? I’d love to hear about them.
    Syndicated copies to:
    Related

    Author: Chris Aldrich

    I’m a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history.

    I’m also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.
    View all posts by Chris Aldrich

    Antworten

  8. Reaktionen sichtbar machen

    Der Austausch über Blogartikel steht für mich schon immer im Mittelpunkt. In den Artikeln werden Ideen, Gedanken und Erfahrungen beschrieben, diese stehen jedoch nicht nur für sich selbst, sondern werden von den Reaktionen der Leserinnen und Leser ergänzt. Anfangs wurde engagiert kommentiert. Durch Twitter und Facebook fand schließlich der Austausch meist auf den entsprechenden Plattformen statt, und beschränkte sich in vielen Fällen auf den Ausdruck des Gefallens. Viele Kommentarspalten blieben leer, und die Artikel wirkten leblos. Die Reaktionen darauf war im Blog selbst nicht sichtbar. Social-Buttons mit ihren Tracking-Skripten stellten für mich keine Lösung dieses Problems dar. Den Austausch über die Inhalte verwandeln sie in Zahlen, die Qualität desselben bleibt jedoch weiterhin verborgen. Einen Mehrwert für das Blog und dessen Community stellen sie nicht dar, sondern dienen vor allem den Plattformen als Datenlieferanten.
    Bereits vor einigen Jahren erfuhr ich von der IndieWeb-Bewegung, die vernetzte Inhalte sichtbar machen wollte, den Zugriff auf die eigenen Daten betonte und an vielen Stellen interessante Projekte hervorbrachte. In diesem Zusammenhang las ich bei Jeremy Keith über Webmentions.
    Die Annahme über zu wenig Wissen und Zeit zu verfügen um mich selbst an die Implementation von Webmentions zu machen, führte dazu diesen Bereich ruhen zu lassen, und schließlich nichts dergleichen zu unternehmen. Erst als ich im Nachklang der Smashing Conference in Freiburg den Artikel »Implementing Webmentions« von Drew McLellan las, fasste ich den Entschluss die Reaktionen auf Inhalte in Blogs endlich wieder sichtbar zu machen.
    Da ich gerade an ein paar Projekten arbeite die auf WordPress basieren und ich meine eigenen Blogs ebenfalls damit betreibe, widme ich mich an dieser Stelle der Implemantation von Webmention in mit WordPress betriebene und selbst gehostete Blogs.
    Was ist zu tun?
    Um Webmention mit WordPress zu benutzen sind vier Schritte nötig.
    Installation des Webmention-Plugins
    Installation des Plugins für Semantic-Linkbacks
    Social-Media-Profile via Bridgy mit dem Blog verbinden
    Das eigene Comment-Template anpassen
    Das Webmention-Plugin
    Das Webmention-Plugins von Matthias Pfefferle erweitert die Diskussion-Einstellung eines WordPress-Blogs, und legt die Grundlage dafür, dass ein Blog Webmentions senden und empfangen kann.
    Nachdem das Plugin heruntergeladen, installiert und aktiviert ist stehen unter Einstellungen > Diskussion ein paar weitere Einstellungen zur Verfügung. Achte auch darauf, dass die allererste Einstellung »Versuche, jedes in Beiträgen verlinkte Weblog zu benachrichtigen« ausgewählt ist.
    Unter Webmention Settings befinden sich vier Checkboxen und eine Auswahl mit deren Hilfe sich das Verhalten der Webmentions einstellen lassen.
    Das Plugin für Semantic-Linkbacks
    Das Plugin für Semantic-Linkbacks bietet die Möglichkeit die empfangenen Webmentions je nach Typ unterschiedlich zu behandeln. Es weist den empfangenen Erwähnungen einen entsprechenden Typ – beispielsweise Like, Repost oder Mention – zu, der als Filter und für die Styles zur Verfügung steht.
    Eine Übersicht der Einstellungen bringt dieses Plugin nicht mit, es verrichtet seine Dienste sobald es aktiviert ist. Im IndieWeb-Wiki erfährst Du etwas über die Möglichkeiten die zugewiesenen Typen in Deinem Theme zu verwenden. Wie ich die Typen verwende beschreibe ich etwas später in diesem Artikel.
    Update 15.10.2017:
    Seit Version 3.5.0 unterstützt dieses Plugin die Darstellung von Likes, Mentions und Reposts in eigenen Listen. Dadurch wurde die Anpassung meines Comment-Template obsolet.
    Brücken bauen
    Der Dienst Bridgy baut die Brücken zwischen Deinen Social-Media-Profilen und Deinem Blog. Er überwacht die verbundenen Social-Media-Profile und sendet Erwähnungen ans Blog. Deine Social-Media-Profile müssen öffentlich sein und die URL Deines Blogs muss dort hinterlegt sein. Wichtig ist auch, dass die Post öffentlich sind, nur so können sie von Bridgy ausgelesen werden.
    Auf brid.gy wählst Du also die Social-Media-Kanäle aus über die Du Erwähnungen empfangen möchtest. Sobald Du Bridgy den Zugriff auf Deine Profile gestattet hast, beginnt es damit alle 30 Minuten nachzusehen ob es dort eine Erwähnung Deines Blogs gibt. Wird es fündig sendet es die Erwähnung als Kommentar an Dein Blog.
    Das Comments-Template
    Um die Erwähnungen zu Bündeln habe ich mein Comments-Template und das Stylesheet etwas angepasst. Zur Anpassung meines Comment-Templates habe ich mich an diesem Code von Michael Bishop orientiert. Mein aktuelles Comments-Template kannst Du in diesem Gist ansehen.
    Likes und Reposts sammle ich in einer Liste und verlinke lediglich die Profilbilder mit den jeweiligen Accounts. Danach gebe ich eine Liste der Kommentare aus – in dieser Liste erscheinen bei mir Antworten von Twitter, Kommentare von Facebook und die klassischen Kommentare. In einer Liste unter den Kommentare gebe ich Erwähnungen des Artikels in anderen Blogs aus.
    Verbesserungen
    Bei meinen ersten Schritten mit Webmention sehe ich Verbesserungspotential in den folgenden Punkten:
    Links auf den Namen der Autor_inn_en korrigieren
    Baumstruktur der Kommentare darstellen
    Profilbilder optimieren und auf den eigenen Server speichern
    Den Callback der manuellen Webmention-Eingabe optimieren
    Ich freue mich von Euch zu hören wenn Ihr Ideen habt wie einer dieser Punkte gelöst werden kann, aber auch wenn Euch noch weitere Verbesserungen einfallen.

    Veröffentlicht am 15.09.2017 von Daniel in Blogs, IndieWeb, Internet, WordPress.

    Antworten

  9. I really love that I can post an event on my website and people can use their own websites to RSVP to it. It’s so simple, but it feels so magical.
    Even better, the Webmention plugin and the Semantic Linkbacks plugin allows for a beautiful display of the responses.
    #IndieWeb FTW!
    Facepiled RSVPs for vHWCThanks David Shanske, Matthias Pfefferle, Ryan Barrett, and everyone else in the IndieWeb community who has either helped to create and/or  supports the web standards that allow for the internet to work the way one expects it should.
    Want to try it out? Visit the event post for instructions. You can also RSVP on the copy I syndicated to Facebook and your response will show up on the list on my site as well.
     
    Syndicated copies to:

    Author: Chris Aldrich

    I'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history.


    I’m also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.
    View all posts by Chris Aldrich

    Antworten

  11. Introduction to what one would consider basic web communication
    A few days ago I had written a post on my website and a colleague had written a reply on his own website. Because we were both using the W3C Webmention specification on our websites, my site received the notification of his response and displayed it in the comments section of my website. (This in and of itself is really magic enough–cross website @mentions!)
    To reply back to him I previously would have written a separate second post on my site in turn to reply to his, thereby fragmenting the conversation across multiple posts and making it harder to follow the conversation. (This is somewhat similar to what Medium.com does with their commenting system as each reply/comment is its own standalone page.)
    Instead, I’ve now been able to configure my website to allow me to write a reply directly to a response within my comments section admin UI (or even in the comments section of the original page itself), publish it, and have the comment be sent to his reply and display it there. Two copies for the price of one!
    From the comments list in my Admin UI, I can write a reply and it not only lives on my site but it can now be sent as a comment to the site that made the original comment! As an example, here’s my first one and the resultant copy on the site I was replying to.This means that now, WordPress-based websites (at least self-hosted versions running the WordPress.org code) can easily and simply allow multiple parties to write posts on their own sites and participate in multi-sided conversations back and forth while all parties maintain copies of all sides of the conversation on their own websites in a way that maintains all of the context. As a result, if one site should be shut down or disappear, the remaining websites will still have a fully archived copy of the entire conversation thread. (Let’s hear it for the resilience of the web!)
    What is happening?
    This functionality is seemingly so simple that one is left wondering:
    “Why wasn’t this baked into WordPress (and the rest of the web) from the start?”
    “Why wasn’t this built after the rise of Twitter, Facebook, or other websites which do this as a basic function?”
    “How can I get it tout suite?!” (aka gimme, gimme, gimme, and right now!!!)
    While seeming simple, the technical hurdles aren’t necessarily because there had previously never been a universal protocol for the web to allow it. (The Webmentions spec now makes it possible.) Sites like Facebook, Twitter, and others enable it because they’ve got a highly closed and highly customized environment that makes it a simpler problem to solve. In fact, even old-school web-based bulletin boards allowed this!
    But even within social media one will immediately notice that you can’t use your Facebook account to reply to a Twitter account. And why not?! (While the web would be far better if one website or page could talk to another, these sites don’t for the simple economic reason that they want you using only their site and not others, and not enabling this functionality keeps you locked into what they’re selling.)
    I’ll detail the basic set up below, but thought that it would be highly illustrative to have a diagram of what’s physically happening in case the description above seems a bit confusing to picture properly. I’ll depict two websites, each in their own column and color-coded so that content from site A is one color while content from site B is another color.
    A diagram of where comments live when sent via webmention.
    Each site composes and owns its own content and sends the replies to the other site.It really seems nearly incomprehensible to me how this hasn’t been built into the core functionality of the web from the beginning of at least the blogosphere. Yet here we are, and somehow I’m demonstrating how to do this from one WordPress site to another via the open web in 2017. To me this is the entire difference between a true Internet and just using someone else’s intranet.
    Implementation
    Prerequisites
    While this general functionality is doable on any website, I’ll stick to enabling it specifically on WordPress, a content management system that is powering roughly 30% of all websites on the internet. You’ll naturally need your own self-hosted WordPress-based website with a few custom plugins and a modern semantic-based theme. (Those interested in setting it up on other platforms are more than welcome to explore the resources of the IndieWeb wiki and their chat which has a wealth of resources.)
    Plugins
    As a minimum set you’ll want to have the following list of plugins enabled and configured:
    Webmentions
    Semantic Linkbacks
    IndieWeb Plugin (optional)
    Other instructions and help for setting these up and configuring them can be found on the IndieWeb wiki, though not all of the steps there are necessarily required for this functionality.
    Themes
    Ideally this all should function regardless of the theme you have chosen, but WordPress only provides the most basic support for microformats version 1 and doesn’t support the more modern version 2 out of the box. As a result, the display of comments from site to site may be a bit wonky depending on how supportive your particular theme is of the microformats standards. As you can see I’m using a relatively standard version of the TwentySixteen theme without a lot of customization and getting some reasonable results. If you have a choice, I’d recommend one of the following specific themes which have solid semantic markup:
    Sempress
    ZenPress
    Independent Publisher
    Plugin
    The final plugin that enables sending comments from one comment section to another is the WordPress Webmention for Comments plugin. As it is still somewhat experimental and is not available in the WordPress repository, you’ll need to download it from GitHub and activate it. That’s it! There aren’t any settings or anything else to configure.
    Use
    With the plugin installed, you should now be able to send comments and replies to replies directly within your comments admin UI (or directly within your comments section in individual pages, though this can not require additional clicks to get there, but you also don’t have the benefit of the admin editor either).
    There is one current caveat however. For the plugin to actually send the webmention properly, it will need to have a URL in your reply that includes the microformats u-in-reply-to class. Currently you’ll need to do this manually until the plugin can properly parse and target the fragmentions for the comments properly. I hope the functionality can be added to the plugin to make the experience seamless in the future.
    So what does this u-in-reply-to part actually look like? Here’s an example of the one I used to send my reply:
    <a class="u-in-reply-to" href="https://islandinthenet.com/manually-adding-microfomats-markup/">Khürt</a>
    The class tells the receiving site that the webmention is a reply and to display it as such and the URL is necessary for your webmention plugin to know where to send the notification. You’d simply need to change the URL and the word (or words) that appear between the anchor tags.
    If you want to have a hidden link and still send a webmention you could potentially add your link to a zero width space as well. This would look like the following:
    <a class="u-in-reply-to" href="http://www.example.com">&​#8203;​</a>
    Based on my experiments, using a <link> via HTML will work, but it will send it as a plain webmention to the site and it won’t show up natively as a reply.
    Sadly, a plain text reply doesn’t work (yet), but hopefully some simple changes could be made to force it to using the common fragmentions pattern that WordPress uses for replies.
    Interestingly this capability has been around for a while, it just hasn’t been well documented or described. I hope now that those with WordPress sites that already support Webmentions will have a better idea what this plugin is doing and how works.
    Future
    Eventually one might expect that all the bugs in the system get worked out and the sub-plugin for sending comment Webmentions will be rolled up into the main Webmentions plugin, which incidentally handles fragmentions already.
    Caveats
    In addition to the notes above, I will say that this is still technically experimental code not running on many websites, so its functionality may not be exact or perfect in actual use, though in experimenting with it I have found it to be very stable. I would recommend checking that the replies actually post to the receiving site, which incidentally must be able to accept webmentions. If the receiving website doesn’t have webmention support, one will need to manually cut and paste the content there (and likely check the receive notification of replies via email, so you can stay apprised of future replies).
    You can check the receiving site’s webmention support in most browsers by right clicking and viewing the pages source. Within the source one should see code in the <head> section of the page which indicates there is a webmention endpoint. Here is an example of the code typically injected into WordPress websites that you’d be looking for:
    <link rel="webmention" href="http://example.com/wp-json/webmention/1.0/endpoint" />
    <link rel="http://webmention.org/" href="http://example.com/wp-json/webmention/1.0/endpoint" />
    Also keep in mind that some users moderate their comments, so that even though your mention was sent, they may need to approve it prior to it displaying on the page.
    If you do notice problems or issues or have quirks, please file the issue with as full a description of what you did and what resulted as you can so that it can be troubleshot and made to work not only for you, but hopefully work better for everyone else.
    Give it a try
    So you’ve implemented everything above? Go ahead and write a reply on your own WordPress website and send me a webmention! I’ll do my best to reply directly to you so you can send another reply to make sure you’ve got things working properly.
    Once you’re set, go forward and continue helping to make the web a better place.
    Special Thanks
    I wanted to take a moment to give special thanks to Aaron Parecki, Matthias Pfefferle, and David Shanske who have done most of the Herculean work to get this and related functionality working. And thanks also to all who make up the IndieWeb community that are pushing the boundaries of what the web is and what it can accomplish. And finally, thanks to Khürt Williams who became the unwitting guinea pig for my first attempt at this. Thank you all!
    ​​​​​​
    Syndicated copies to:

    Author: Chris Aldrich

    I'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history.


    I’m also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.
    View all posts by Chris Aldrich

    Antworten

  19. As I am wrapping up my two week experiment with going all-in on #IndieWeb WordPress I have had the pleasure of learning from so many great people. I recently discussed session ideas with David Shanske and Matthias Pfefferle about different ideas as we brainstormed sessions.
    My ultimate goal is to provide the documentation support to David and Mathias and other people who work on the technical side. I want to provide as David suggested, “a functional solution.” Here were some ideas I had:
    A WordPress Theme Developers Guide to to the #IndieWeb
    As I finish my two week WordPress experiment I am using Alan Levine’s new theme publishing posts under a variety of conditions and then checking out how microformats2 get rendered based on post kind. Be cool with folks to work on best practices to creating IndieWeb child themes. Each we can focus on our favs or the most popular. I chose Dimensions because I think the whole #rhizo #ds106 and Virtually Connecting crowd would dig how #IndieWeb stuff works. Many of them will use what Alan build because when the cogdog barks you howl back.
    I also want to try to do the same with Hueman. I like that theme and I think it will just be a matter of removing bad microformat classes. This could have great benefits for the WordPress #IndieWeb community. Creating some rules for folks would rock.
    You Rock – You Rule flickr photo by Skyflash shared under a Creative Commons (BY-NC-ND) licensePost-Type Discovery Pages
    Text structure matters as much on the front end as it does in the back end. During my experimenting folks shared the Post Discovery Pages on the wiki. Anyone trying to learn how to update their blog with microformats2 would love this resource. We can make it better. The pages describing each post kind lack parallelism. Compare the page on note, article, and bookmark. Some post kind discovery pages like article stubs while others could pass Kerouac novels. Any easy but important update to the wiki would involve designing a template and make each post-kind that links from the post-discover page to match each other. We need to make the layout of wiki articles as predictable as basic math.

    What I build
    In #IndieWeb spirit you showcase something you have hacked together. For me I am working on three pieces academics and teachers could use. A static page for a professional organization, a syllabus, and a course website. Each resource will use CSS Grid and microforamts2. I am trying to keep the HTML as plain as possible to encourage sharing and remixing. Some day not in the distant future I hope to use these as th backbone for a decentralized LMS and professional network.

    Antworten

  20. GitHub – pfefferle/wordpress-semantic-linkbacks: More meaningfull linkbacks

    This is the semantic linkback plugin. It adds more context to pingbacks. If the site linking to your site has microformats more info may come alongThanks Matthias PfefferleI do wonder if theme develops could add this functionality native or just recommend an install.It does have a mf2 parser and those are actively developed so a plugin may make more sense.#WordPress#Indieweb#WordPressTheme

    Antworten

  23. I’m starting out even more behind, at least in terms of micropub and webmentions. Surprised I’d never seen this during my lifelogging time.
    But WP themes and plugins I do know! Maybe I can help


    Antworten

  24. Replied to New Communities Can Be Overwhelming by David Wolfpaw (davidwolfpaw.com)

    I’ve been paying a lot more attention to the IndieWeb space this year, with the intention of revamping my lifelogging site to both include more services that I still use (and remove the fitness tracking that I decided to stop), as well as become a repository for webmentions.

    David, Welcome! Come on in, the water’s fine…
    I remember lurking for over a year and a half before dipping a toe in for the first time myself. Everyone I’ve met has been so kind, thoughtful, supportive, and helpful that I now regret having let so much time pass before jumping in with both feet.
    Since it looks like you’re playing in the WordPress world, feel free to drop into the #WordPress channel (or any of the others for that matter) anytime to ask questions, help others solve problems (we can always use help with UX/UI, and themes especially), talk about what itches you’re working on, or even just to say “hi”. If you haven’t yet, I’m sure you’ll enjoy meeting some of the WP regulars including pfefferle (Germany), GWG (New York), miklb (Florida), snarfed (San Francisco), jgmac1106 (Connecticut), jeremycherfas (Rome), and me: chrisaldrich (Los Angeles).
    I hope that the most overwhelming part isn’t getting to know the community, but the sheer number of things that are becoming possible to do with one’s website that weren’t as easily possible just a few years ago. My biggest problem reading the chat logs usually comes in the form of saying, “That sounds/looks cool, I want that too!” about 8 times a day. My best advice for “eating the whole whale” is to do it one bite at a time.
    I’ll also personally extend an invitation to the upcoming IndieWeb Summit in Portland at the end of the month. If you can’t make it in person, there should be enough support to allow a lot of direct participation via chat and live streaming video–it’s not quite as much fun as attending in person, but you can participate to a level higher than most conferences typically allow.
    Welcome again!
     
    Syndicated copies to:

    Author: Chris Aldrich

    I'm a biomedical and electrical engineer with interests in information theory, complexity, evolution, genetics, signal processing, theoretical mathematics, and big history.


    I’m also a talent manager-producer-publisher in the entertainment industry with expertise in representation, distribution, finance, production, content delivery, and new media.
    View all posts by Chris Aldrich

    Antworten

  27. Replied to a tweet by Morten Rand-Hendriksen (Twitter)

    I’ve long felt that webmentions would be a perfect fit for #WordPress core. This article makes me even more sure. Let’s get to work! https://t.co/hBofSwJruR— Morten Rand-Hendriksen (@mor10) July 23, 2018

    Mathias Pfefferle, David Shanske, and 700+ others have been self-dogfooding Webmention for a while. Feel free to join us in the IndieWeb #WordPress chat to talk about some remaining work and support it might require to do so.
     
    Syndicated copies to:

    Antworten

  30. (or: a hurray for open source)
    Wow, what a headline! :-))
    There was a tiny issue with the display of „webmention“ reactions in my theme that annoyed me a little bit: On older posts, the summary of that post (for example in archive view or search results) would show in the meta-info something like „23 reactions“ when this post had received comments or webmentions from other sources, like reposts or likes. but on the detail view, only comments were shown and the ammount of (visible) reactions didn’t match the number stated in the meta-info. I have activated a WordPress default feature to disable comments after a couple of weeks automatically, since most comments coming in on old(er) posts used to be like 99.9% spam.
    Now what happened on these older post with disabled comments and already received webmentions: Only comments were displayed, but the ammount of webmentions/reactions were counted and displayed in the meta-info. Which led to some posts who had only received webmentions to be „announced“ with „23 reactions“, but then, on the post’s detail page, nothing regarding the webmentions showed — which slightly puzzled me.
    For quite a while that puzzlement was not enough to actually have a look why this was happening, but two days ago I tried to find what was causing this.
    And after I thought I had an idea why this was happening (but no means to fix it by myself), I created an issue in the Semantic Linkback github, not really expecting a reaction since this issue seemed rather special, only showing when several factors like disabled comments and already received mentions came together…
    but once again open source surprised me — only a day later the issue had been fixed, a new version released and NOW MY FRICKING FACEPILES are back even on older posts! Ha!
    Lots of love once again to Matthias (notiz.blog, @pfefferle) and all his work in and around the indieweb tools.
    And once again this shows me: No matter how small or unimportant things seem to me, it is worth to put in some time and effort, and the outcome may very well be positivly surprising.

    Antworten

  31. @pfefferle Hi there! I just came across your Ostatus plugin and was wondering about that over ActivityPub? I’ve heard things about both and was just wondering which I should opt for for joining federated network? Sorry for any confusion, and thanks for making this!

    Antworten

  32. In just over a week I will be joining the Nuremberg IndieWebCamp, together with Frank Meeuwsen. As I said earlier, like Frank, I’m wondering what I could be working on, talking about, or sharing at the event. Especially as the event is set up to not just talk but also build things.
    So I went through my blogpostings of the past months that concerned the indie web, and made a list of potential things. They are of varying feasibility and scope, so I can probably strike off quite a few, and should likely go for the most simple one, which could also be re-used as building block for some of the less easy options. The list contains 13 things (does that have a name, a collection of 13 things, like ‘odd dozen’ or something? Yes it does: a baker’s dozen, see comment by Ric below.). They fall into a few categories: webmention related, rss reader related, more conceptual issues, and hardware/software combinations.

    Getting WebMention to display the way I want, within the Sempress theme I’m using here. The creator of the theme, Matthias Pfefferle, may be present at the event. Specifically I want to get some proper quotes displayed underneath my postings, and also understand much better what webmention data is stored and where, and how to manipulate it.
    Building a growing list of IndieWeb sites by harvesting successful webmentions from my server logs, and publish that in a re-usable (micro-)format (so that you could slowly map the Indieweb over time)
    Make it much easier for myself to blog from mobile, or mail to my blog, using the MicroPub protocol, e.g. using the micropublish client.
    Dive into the TinyTinyRSS datastructure to better understand. First to be able to add tags to feeds (not articles), as per my wishlist for RSS reader functionality.
    Make basic visualisation possible on top of TinyTinyRSS database, as a step to a reading mode based on pattern detection
    Allow better search across TinyTinyRSS, full text, to support the reading mode of searching material around specific questions I hold
    Adding machine translation to TinyTinyRSS, so I can diversify my reading, and compare original to its translation on a post by post basis

    Visualising conversations across blogs, both for understanding the network dynamics involved and for discovery
    Digging up my old postings 2003-2005 about my information strategies and re-formulate them for networked agency and 2018
    Find a way of displaying content (not just postings, but parts of postings) limited to a specific audience, using IndieAuth.
    Formulate my Networked Agency principles, along the lines of the IndieWeb principles, for ‘indietech’ and ‘indiemethods’

    Attempt to run FreedomBone on a Raspberry Pi, as it contains a range of tools, including GnuSocial for social networking. (Don’t forget to bring a R Pi for it)
    Automatically harvest my Kindle highlights and notes and store them locally in a way I can re-use.
    These are the options. Now I need to pick something that is actually doable with my limited coding skills, yet also challenges me to learn/do something new.

    share
    share
    share
    tweet
    share
    e-mail

    Antworten

  37. Replied to Blog Engines and Indieweb Controlling Upstream by Brad Enslen (Brad Enslen)

    All this WordPress 5.0 Gutenberg stuff got me thinking. With WordPress it seems like the Indieweb starts making serious and cool progress and the WordPress people come along and knock the game board and pieces off the table. And it sounds like the disruption from WordPress is going to continue f…

    Brad, I like and agree with your general thoughts, but I think that looking at the long term broader picture, most of what you’re describing is covered under the umbrella principle of plurality. For things to grow and thrive, we all need plurality to flourish. As a result there are several hundred projects within the broader IndieWeb which are growing and thriving. It seems far slower because a large number of the projects are single-maintainer single-user ones which are being built for personal use.
    It’s nice that there are mass-scale projects like WordPress, WithKnown, Get Perch, Grav, Drupal, and a few others which have one or more “IndieWeb-centric” developers working on them that allow those without the coding skills to jump in and enjoy the additional freedom and functionality. The occasional drawback is that those big-hearted developers also fit into the broader fabric of those massively distributed projects and sometimes their voices aren’t as well heard, if at all.
    I’m aware of the disruption of the Gutenberg Editor within WordPress v5.0 and how it applies to those using IndieWeb technology on WordPress. I’m sure it will eventually get sorted out in a reasonable fashion. Sadly, throwing out the baby out with the bathwater as it comes to WordPress and IndieWeb may not be the best solution for many people and may actually be a painful detriment to several hundreds.
    While it would be interesting to see a larger group of developers converge on building an open and broadly used IndieWeb system as you suggest, it takes a massive amount of work and community collaboration to get such a thing moving. I think this bears out if you look at the lay of the land as it already exists. Just think of the time effort and energy that the core IndieWeb community puts into the tremendous amount of resources that exist today.
    Looking back on the past 4+ years of IndieWeb within the WordPress community, I’m really amazed to see exactly how far things have come and where things currently stand. There used to be a dozen or more pieces that required custom code, duct tape, and baling wire to get things working. Now it’s a handful of relatively stable and well set up pieces that—particularly for me—really makes WordPress deliver as an open source content management system and next generation social medial platform that aims to democratize publishing. In terms of building for the future, I suspect that helping to bring new people into the fold (users, developers, designers, etc.) will increase and improve the experience overall. To some degree, I feel like we’re just getting started on what is possible and recruiting new users and help will be the best thing for improving things moving forward. IndieWeb integration into large-scale projects like WordPress, Drupal, etc. are very likely to be the place that these ideas are likely to gain a foothold in the mainstream and change the tide of how the internet works.
    While it may seem daunting at times, in addition to the heroic (part-time, it needs to be noted) developers like Mathias Pfefferle, David Shanske, Micah Cambre, Michael Bishop, Ashton McAllan, Jack Jamieson, Ryan Barrett, Peter Molnar, Amanda Rush; enthusiastic supporters like you, Greg McVerry, Aaron Davis, Manton Reece; and literally hundreds of others (apologies to those I’ve missed by name) who are using and living with these tools on a daily basis, there are also quieter allies like Brandon Kraft, Ryan Boren, Jeremy Herve and even Matt himself, even if he’s not directly aware of it, who are contributing in their own ways as well. Given the immense value of what IndieWeb brings to the web, I can’t imagine that they won’t ultimately win out.
    If it helps, some of the current IndieWeb issues pale in comparison to some of the accessibility problems that Gutenberg has neglected within the WordPress community. Fortunately those a11ys are sticking with the greater fight to make things better not only for themselves, but for the broader community and the world. I suggest that, like them, we all suit up and continue the good fight.
    Of course part of the genius of how IndieWeb is structured: anyone is free to start writing code, make better UI, and create something of their own. Even then they benefit from a huge amount of shared work, resources, and simple standards that are already out there.
    Syndicated copies to:

    Antworten

  40. Replied to Joe’s Syndicated Links Considered ‘Spam’ By Some Mastodon Instance by Kicks Condor (kickscondor.com)

    I actually kind of understand this—only because I think Mastodon is at odds with the Indieweb.

    I don’t think that what Joe is seeing is an anti-IndieWeb thing. It is something we’ve seen before from a handful of instances and will assuredly see again.
    The other example of this behavior I’ve seen was when Greg McVerry, a college professor and member of the IndieWeb community, tried to join a Mastodon instance that was specific to researchers and professors in higher education. Sadly he found out, like Joe, that syndicating content from other locations was not acceptable there. As I recall, they also required an automatic content warning on almost everything posted to that particular instance which seemed an additional travesty to me. I think he ultimately joined mastodon.social and found he didn’t have any similar issues there and anyone who wanted to follow him from any other instances still could. I’m sure he can provide some additional details and may have posted about it sometime in the summer of 2018 when it happened.
    The tough part is that each instance, though federated among many others, can have its own terms of service and set up. Some instances can be and certainly are run by their own tyrannical administrators, and I suppose that it’s their right since they’re paying for the server and the overhead. The solution is to do some research into some instances and find one that isn’t going to ban you for what would otherwise seem like average use to most. I’ve found mastodon.social to be relatively simple in its terms and its massive size also tends to cover up a lot of edge cases, so you’re unlikely to run into the same problems there. (It is also run by the creator of Mastodon, who has generally been IndieWeb friendly.)
    The issue Joe has run into also points out a flaw of the overall Fediverse in that just like each real-world country can have its own laws and there is a broader general international law, the international laws aren’t as well codified or respected by each individual country. When you’re operating in someone else’s country, you’re bound to follow their local laws and even customs. Fortunately if you don’t like them there are lots of other places to live. And this is one of the bigger, mostly unseen, benefits of the IndieWeb: if you have your own website, you can create your own rules/laws and do as you please without necessarily relying as heavily on the rules of others.
    I’ll note that some in the IndieWeb (Aaron Parecki, Ryan Barrett, Mathias Pfefferle, Jacky Alcine, et al.) have been playing around with or thinking about adding the ActivityPub protocols so that their own websites act as stand-alone members of the Fediverse. Since I know Joe has recently moved to WordPress, I’ll mention that there are two separate projects to help WordPress sites federate:
    * ActivityPub plugin for WordPress from Mathias Pfefferle
    * Bridgy Fed from Ryan Barrett
    Naturally neither of these (yet) supports all of the protocols so some functionality one would find on Mastodon won’t necessarily work, but I suspect that over time that they eventually will. It’s been a while since I tried out BridgyFed, but I’ve had the ActivityPub plugin set up for a bit and have noticed a lot of recent work by Mathias Pfefferle to use it for himself. I still have to tweak around with some of my settings, but so far it provides some relatively useful results. The best part is that I don’t need to syndicate content to Mastodon, but users there can subscribe to me at @chrisaldrich, for example, instead of @chrisaldrich. The results and functionality aren’t perfect yet, but with some work we’ll get there I think.
    Good luck finding (or creating) an instance that works for you!

    Antworten

  41. I discovered yesterday that when I added a # (or hash, pound sign, octothorpe, et al.) in front of any word on my site, it created a native version of something akin to Twitter’s #hashtag functionality, but it was working on my own website. The primary difference was that the hashed word on the page was, upon publishing the post, automatically wrapped with a URL for that tag on my own website, and it was also automatically added to the list of tags for the post. (As an illustrative example, I’m doing the same thing with the word hashtag earlier in this paragraph.)
    I had previously considered adding this type of functionality myself to make syndicating posts (via POSSE) from my own website to sites like Twitter or Mastodon easier. There are a small handful of plugins in the WordPress repository that will add that type of functionality already, but I had eschewed them generally, not wanting yet-another-plugin.
    I spent some time trying to track down the plugin that was effecting this change. I couldn’t remember having installed something that would have done this sort of functionality, and I had noticed it only by complete happenstance. I eventually gave up my search halfway through only to later get a message from Matthias Pfefferle that his ActivityPub plugin was the likely culprit. I probably should have guessed as I had literally spent part of that very day looking at the code in his IndieWeb News plugin on GitHub which had code that essentially did the exact same thing, but for a narrower set of results.
    The upside of the entire process is that the functionality is now built into a plugin which I’d be using otherwise. As of today’s update, there’s now also a setting for the plugin that will allow one to turn the functionality on or off–I, for one, am definitely keeping it. Of course if you’re looking for the functionality without the extra overhead of the ActivityPub code, I believe you can use Matthias’ WordPress hashtags plugin which does only this.

    I’ve never quite liked that Twitter uses @names highlighted within posts. All the additional cruft in Twitter like the “@” and “#” prefixes, while adding useful functionality, have always dramatically decreased the readability and enjoyment of their interface for me. So why not just get rid of them?!

    Of course I also remember myself railing against the addition of the symbols @ and # in general text not too long ago, so I’m also now brainstorming and contemplating how one might more quickly (and even in a DRY manner) do this sort of tagging using some other (probably easily accessed, but infrequently used) symbol which could be hidden visually, but which would allow one to add these sorts of tags and the appropriate microformats markup. I suspect there may be some sort of clever CSS I may be able to use too, though it would be better not so that it works easily via syndication and in feed readers with different styling. The goal should be that it would work as plain text from a Micropub client too. With any good luck someone may have thought of it already, otherwise I may be able to hack something simple together to do roughly what I want. The upside would be that simply by writing your post, you could simultaneously be tagging it as well and not need to bother going in and separately adding additional tags!

    Antworten

  44. I’m continually astounded by Matthias Pfefferle’s (or I might alternately tag: @pfefferle) excellent work with the ActivityPub plugin for WordPress! It’s simply brilliant that my IndieWeb powered WordPress website can act much like a standalone version of Mastodon and reasonably federate with other platforms that use the ActivityPub protocol.
    You can follow me at @chrisaldrich and apparently read my 8,000+ posts via Mastodon and other platforms.
    While the plugin doesn’t support everything (yet) and doesn’t compete with Mastodon, Friendi.ca, or GNU.social, it extends WordPress with some reasonably solid fediverse features. I can’t wait to see how it continues to grow and add additional functionality.
    Syndicated copies to: Twitter icon

    Antworten

  48. @pfefferle I’ve been setting up my website to work with open/indie/decentralized web stuff, and your name keeps popping up again and again. Your work, particularly your wordpress plugins, is fucking awesome! Thanks for doing what you’re doing mate!

    Antworten

  51. I’ve taken the decision to switch my site away from the custom theme called “K” I was building, and for now I’m using the excellent Autonomie by Matthias Pfefferle instead1. Development of K had already slowed to a standstill, and realistically, I’m not going to go back to it anytime soon. It feels a little like a failure, a little like giving up, but I think it’s ultimately the right thing to do.
    I made a lot of mistakes while building K, which overcomplicated things, made development more difficult, and ultimately led me into a dead-end. I thought “for simplicity” that I would use the Bootstrap frontend framework, as it would give me a robust foundation to build on. It did, but I had to bend and twist WordPress in increasingly hacky ways to get the output to “play nice.” A large chunk of the K codebase was being taken up by code solely tasked with massaging the output of WordPress to add the right Bootstrap classes or container markup. It felt increasingly fragile and hacky, and it was a bad sign. K would work for my setup, but I couldn’t ensure it would work for everyone.
    Bootstrap added other complications: to properly manage my CSS “overrides” I had to create a build system that would compile a whole lot of SASS files together. When I started K, the CSS was stripped down to the bare minimum needed, and came to a few KB. After a while I ended up including the whole Bootstrap framework, just to make the build process easier.
    There were no “options” to speak of, so it couldn’t be tailored to suit someone else using the WordPress customiser. I didn’t even want to think about Gutenberg support.
    Microformats always felt like whack-a-mole. I’d get them working, then make adjustments somewhere else, and promptly see things break again. I put this on my need to make so many adjustments to the WordPress output – inadvertant issues kept creeping in.
    Then there were the visual design choices. K grew out of the simple design I employed when I was writing 1-2 short posts a month, in the traditional format. In that scenario it worked fine. Once I started to use the various post kinds, things became more problematic. Now I was posting several posts per day, most of which weren’t in a traditional blog format. The home page became cluttered; it started to remind me of a badly thought-out notification area, rather than a well designed blog. The archive page was a disaster and I had no good ideas on how to fix it. There were a thousand other little niggles.
    None of this is meant as a knock against Bootstrap, or WordPress, or build systems, or any other tool or technology I used to get to this point. K failed because of my decisions, rather than deficiencies in the tools. There were things I liked about K… it used zero JavaScript, and I did my best to stop unnecessary plugin resources from loading. Markup was as minimal as I could make it (within the constraints of what I could remove from WordPress output, microformats, and what Bootstrap needed). It worked well across browsers and devices (thanks Bootstrap!), and the accent colours were fun. I learned a lot about the excellent Post Kinds plugin during the development process. I’m filing it away as a failed experiment, which I’ll learn from and apply the lessons to the IndieWeb WordPress theme I’m still intending to create. One that will hopefully work for more people than just me 😅
    I put the source code to K on GitHub right back near the start of the project. If you want to take a look, steal any code, rework it into something usable – feel more than welcome to!
    1 As a result, a couple of things that were setup specifically for K are broken. I’ll look into fixing those over the next few days. ⤴️

    Antworten

  53. @pfefferle huhu, wann wird dieser error getriggert?
    es ist definitv kein kommentar/webmention in der db, der von der src url kommt.
    error kommt, wenn ich am webmention formular unterm post die url eintrage (also genau da, wo @xwolf vorhin mit den texten hing)

    Antworten

  55. @pfefferle Sach mal, kann es sein, daß das Webmention-Plugin bei normalen Kommentaren das Mailformat ändert?
    Als ich die drei Plugins für Webmentions Indieweb,Semantik Web und Webmention) an hatte, wurde das Template auf englisch gesetzt und war ohne Autordaten und Content.

    Antworten

  57. I had a wonderful time at @IndieWebSummit last weekend. Meant to write up some thoughts on the event sooner, but I’ve been enjoying some time away from my computer this week.
    That said, I’d like to note some highlights.
    June 28: Pre-summit social
    This was my third IndieWeb summit in as many years, and over the past year I’ve gotten to know several people in IndieWeb’s community by chatting on IRC, working together on software (mostly on GitHub), and long conversations on Skype. So, whereas my first IndieWeb was marked by a lot of introductions, this year felt like getting to see old friends. Not too much to say about the pre-summit social, except that it drove home the value of IndieWeb’s community. Behind IndieWeb’s specs and technical building blocks are some really interesting people committed to building a positive space.

    June 29: Talks and unconference sessions
    Today began with explanations of IndieWeb’s code of conduct, as well as Mozilla’s community participation guidelines since the summit took place at Mozilla’s Portland office.
    We then moved on to a series of excellent keynotes. The keynotes stuck with me, so I’ll spend a bit of time with them. Below are some summaries on parts that stood out to me, and in some cases tangents where they led to me to related trains of thought:
    Tantek Çelik — State of the IndieWeb
    Tantek ran through a number of accomplishments and changes from the past year. Specifically, Facebook severely restricted its API, preventing tools like Bridgy from automatically syndicating between one’s personal website and Facebook account. And WordPress (the CMS running this very blog) continues to present numerous challenges. I’m of the opinion that it’s worth investing time to improve the IndieWeb experience on WordPress. And I think we’ve made big leaps forward in the past year. A lot of people have contributed to WordPress’s IndieWeb ecosystem, and particularly appreciation is warranted to David Shanske and Matthias Pfefferle.

    Kitt Hodsden — On Contractions & Expansions
    Kitt’s keynote was a beautiful and captivating oration about contractions and expansions through life, and how these connect to our online lives. I don’t think I can do it justice in a summary, but here’s an excerpt and it’s well worth checking out the full talk:

    When we own our own data, We can look back at who we were who we thought we were. We can see who we really were, who we are, and, most importantly, the trend of our becoming who we want to become. With our own data, we can curate, we can shed who we were to become who we want to be, and we can write the end of our own story.
    For this is the true power of owning our own data: to understand the cycles of contractions and expansions, to understand our hero’s journey, and to write our own story.

    Most of all, I felt that Kitt’s keynote emphasized how the IndieWeb goes far beyond the technical. We spend a lot of time debating protocols, writing markup and/or code, and sitting at our computers. But the reason we care enough to put in this effort is that these technical features shape how we live our lives. Efforts to protest overstepping by platforms have often emphasized retreat or opting-out (e.g. #deletefacebook). But I don’t want to contract. I want to expand, and I want to do so in a way that is inclusive, fair, and kind. Kitt’s talk put this eloquently.

    mJordan — Changing My Domain
    mJordan’s recounted a frustrating experience. While job-hunting, she found that it was difficult to find opportunities, and then discovered that opportunities came much easier when she created online profiles that masked her gender and experience with organizations like Women Who Code. It’s shameful but not surprising that women have such a hard time in tech. Quote from mJordan’s talk:

    So, I ended up really having to do all-in and change my identity absolutely everywhere. I created a new domain name. I had to change my Twitter. Get a new Twitter. New GitHub, new Instagram.
    All the things. Just to get a job.
    And, that is such bullshit.

    Certainly not a problem that can be addressed with protocols or other technical work, but rather through constant vigilance in how we work with others, confront our biases, and work hard to make whatever field we work in better.

    Marty McGuire — Own Your Mobile Experience
    Marty demonstrated how he uses IndieWeb tools on his phone, showcasing his workflow for posting to his own website and following other IndieWeb sites from his phone.
    There’s something really personal about putting one’s phone screen on the projector, and one of my favourite moments from this talk was right at the beginning:

    Welcome to my phone. Oh, gosh. All right.

    Most of all, I really enjoyed getting to see such an thorough look at someone else’s IndieWeb experience. Since there are so many ways to do different things with IndieWeb tools, I found it really useful to learn by Marty’s example.

    Jacky Alciné — Making the IndieWeb for All
    Jacky engaged squarely with what I think is one of the most urgent questions for any sort of decentralized web: How do we make this accessible for everyone? It’s common for a bunch of like-minded people to build something they find useful for themselves, but which struggles to meet the needs of people with different backgrounds. Lots of meet in this talk, and well worth watching. One thing that stood out to me was Jacky’s recommendation for “more anthropocentric (less tech knowledge) demos.” Marty’s mobile demonstration right before this was a great example, and Jacky spent part of the summit working a page on his site describing how he interacts with the IndieWeb.
    This struck a nerve with me based on some reading I’ve been doing lately about activity theory. Specifically, Kaptelinin and Nardi use an example of driving lessons to describe learning processes from an activity theory lens:

    For instance, when new drivers start learning to drive a car in a specially equipped training car, they may appear responsible for the driving (since they carry out basic operations such as pressing pedals and turning the steering wheel). But much of the driving may in fact be done by the instructor, who sets the direction, monitors the overall situation, and makes most decisions. With time, the learner can assume responsibility for more and more tasks and eventually develop the ability to drive on his own.

    My first attempt to Indiewebify my site was aided by a rich technical infrastructure. Since I run WordPress I could easily install a variety of plugins and a theme that took care of many of the technical details. And I could verify that things were working using IndieWebify.me. However, it took me some time to understand how to use my website’s newfound powers. In other words, it was like getting in a fully loaded new car, but not having a sense of how to make decisions with it. Where should I go? Which lane should I take? etc. IndieWeb’s wiki is full of examples, and many people have written blog posts, but this sometimes led to too much information. Peronsal demonstrations (here’s how *I* do it, here’s what *I* would do) are really useful for helping people learn to make decisions. In other words, anthropocentric demonstrations can help ease new Indieweb folks into their new vehicles.

    Whew, this is already getting long and I’m barely into day one. I’m going to take a break for now and will write a bit more about the rest of the summit later.
    In summary, the keynotes provided a rich set of perspectives and prompts for driving discussion and projects throughout the weekend. I was particularly struck by how each keynote presented a unique perspective, and that inclusivity was so well represented.

    Antworten

  63. Read The escape from Instagram by Jeremy Felt (jeremyfelt.com)

    I’ve been thinking through how to leave Facebook’s Instagram service since June, when I finally deleted my central Facebook account. This should be easy, because I don’t post that much on Instagram, but it always seems hard because it’s the best user experience (IMO) on mobile for writing a …

    An interesting method of leaving Instagram. I still read content there, but I had used dsgnwrks-instagram-importer by Justin Sternberg to rescue all of my Instagram posts back into my WordPress site since it gave me a huge amount of control over porting over the metadata as well. I’m noticing that the repository lists it with a warning “This plugin has been closed as of August 10, 2019 and is not available for download. Reason: Licensing/Trademark Violation.” though I can’t imagine what that would have been for unless Instagram is trying to nudge Justin out. (There’s a copy of the plugin on Github for those who may still want it.) Other than a small issue I’d seen with some emoji in Instagram, the plugin always worked like a charm for me.
    Prior to that I’d always been a big fan of Aaron Parecki’s OwnYourGram, though I understand that Instagram was limiting his crawler, so the service may not be taking new accounts.
    While I know some of the people behind Pixelfed and generally trust them, I don’t think I would use it as a solution unless I was standing up my own instance of the service. Far too many Mastodon instances have gone down for me to trust a particular sites’ admins. Apparently Mastodon has made it easier to move from one instance to another, but I’m not sure how this may or may not apply to Pixelfed.
    Presently, my money is on Matthias Pfefferle’s ActivityPub plugin which adds support to a WordPress site to act as a stand-alone member of the Fediverse. While it’s beta software, it works fairly well and is evolving impressively over the past year or so. I suspect that photo support will improve to put it on par with solutions like Pixelfed, particularly when combined with the ease of use of some of the Micropub photo posting applications that are out there.
    I’d feel remiss if I didn’t mention that another option for exiting Instagram (or at least backing it up to your own site even if you don’t leave completely) is to try Beau Lebens’ Keyring Social Importers plugin. I know a few who have used and liked it for its Instagram and other social silo support.
    I’m sure there are other methods out there as well and many might be found on the IndiwWeb wiki pages for “Instagram” or “photo”.
    Syndicated copies to:

    Antworten

  64. I love that WordPress has some built-in functionality within WordPress.com and many themes to allow one to easily build and display a social media menu on a website. Frequently these are displayed in headers, footers, or even sidebars of websites. I have one in the footer of my website that looks like this:

    The RSS icon and links are automatically generated for me by simply putting in any RSS feed that has a /feed/ path in its URL.
    While this is great, clicking on the RSS icon link goes to a page with a hodgepodge of markup, content, and meta data and typically requires multiple additional steps and prior advanced knowledge of what those steps should be to do something useful with that link/page. In other words the UI around this (and far too many other RSS icons) is atrocious, unwelcoming, and generally incomprehensible to the general public. (Remember those long and elaborate pages newspapers and magazines had to define RSS and how to use it? It’s a HUGE amount of cognitive load compared to social media following UI in Facebook, Twitter, Instagram, et al. which just works™.)
    Fortunately Julien Genestoux and friends have created an elegant solution in SubToMe, described as a Universal Follow button, that is open, non-intrusive, protects privacy, and works with virtually any feed reader. It uses some JavaScript to create a pop-up that encourages users to use any of various popular feed readers (or the one of their choice). The UI flow for this is far superior and useful for the casual web-user and has the potential to help along the renaissance of feed readers and consumption of web content in a way that allows readers more control over their reading than social media platforms like Twitter, Facebook, and Instagram that mandate their own proprietary reading algorithms.
    While one can embed SubToMe directly into a website (I do this with a Follow button in my site’s top right sidebar, for example) or using Julien and Matthias‘ WordPress plugin, I suspect it would be far easier if some of this functionality were built directly into WordPress core in some way. Or alternately, is there an easy way to put data into one of the common fields (or wrap it) in these social links menus, so that when a user clicks on the relatively ubiquitous RSS icon in those social links menus, that it triggers a SubToMe-like subscription workflow?
    I would suspect that WordPress.com might try something like this and naturally recommend their own beautiful reader, which was relatively recently redesigned by Jan Cavan Boulas et al., using a bit of functionality which SubToMe kindly provides.
    I think that the simplification of this RSS reader subscription workflow would go a LONG way toward making it more successful and usable. It could also provide massive influence on increasing the use of feed readers in general and the WordPress Reader in particular.
    I do note that there is a form of follow functionality built into WordPress.com-based websites, but that’s locked into the .com platform or needs a plugin for self-hosted sites. It also only benefits the WordPress.com reader rather than other readers in the space. Some of the issue here is to fix the NASCAR problem of needing dozens of plugin solutions and widgets to have what amounts to the same functionality on each platform in existence. I think it’s far more important for the open web to be able to do these sorts of simple functionalities in a more standardized way to give users more freedom, flexibility and choice. The standardization makes it easier for competition in a market economy to gradually improve this sort of user interface over time.
    If someone did undertake some development in this area, I’d give bonus development points on this for:
    Is there a way to do this without JavaScript to get around the js;dr potentiality?
    Is there a way for this to find not only the common main and comments feeds for posts, but also for the affiliated /category/feed/ and /tag/feed/ taxonomy feeds on posts to allow for subscriptions to niche areas of websites that cover multiple broad topics? I know David Shanske has done some work on feed discovery in WordPress recently for the Yarns Microsub Server that may be useful here.
    Is there a way to talk major browsers into adding this into their products?
    I wonder if Jeffrey Paul, Jeremy Felt, Matthias Pfefferle, Jeffrey Zeldman or others may have some ideas about broader implementation and execution of something like this for improved UI in these areas?
    Syndicated copies to: Twitter icon

    Antworten

  65. I just updated my blogroll and thought that it might be a great idea to share my workflow to do exactly that.I use Miniflux a lot. Using Miniflux, I read all the blogs and get all the news, get updates from all the YouTubers and even subscribe to some Mastodon accounts (fediverse microblogs). I use multiple categories to sort the feeds. One of those categories is “Blogs” with all the blogs, which I also list on my blogroll.The list of blogs I follow is always evolving. Sometimes I find new sites to follow, so I add their feeds to the list of subscriptions and put them into the “Blogs” category. Sometimes I also unsubscribe from feeds when they are inactive or if I’m not that much interested into them anymore (it can have multiple reasons).To keep my blogroll up-to-date and to avoid having to manually compare and adjust the list with the list from Miniflux when updating it, it is automatically created using a Hugo shortcode.First, I create an OPML export from my Miniflux subscriptions. This can be easily done by going to “Subscriptions” and then clicking on “Export”. I open the download with a text editor and remove all the categories that aren’t “Blogs”. I copy the remaining OPML code and convert it to JSON using this tool. This JSON I store in a file named opml.json in the data folder of my Hugo-based blog.In the layouts/shortcodes folder, I created a shortcode template named blogroll.html with the following content:<ul>
    {{ $opmlJson := index .Site.Data.opml "opml" "body" "outline" "outline" }}
    {{ range sort $opmlJson "_title" "asc" }}
    <li><a href="{{ ._htmlUrl }}" target="_blank">{{ ._title }}</a></li>
    {{ end }}
    </ul>
    This shortcode is then used by adding Anil DashAral BalkanAsh FurrowBeko PharmBen CongdonBen WerdmüllerBrandon NoletChris AldrichDaniel AleksandersenDanny van KootenDavid Heinemeier HanssonDavid PrandziochDerek SiversDesmond RivetDrew DeVaultEmanuel PinaFlorian AnderiaschGarrett DimonHenrique DiasHrvoje ŠimićJames FennJamie AdamsJamie TannaJan BoddezJeff AtwoodJeremy Keith (Articles)Jeremy Keith (Journal)Jessie FrazelleJohn GruberJonathan BorichevskiyJonathan LaCourJustin VollmerKatharina NocunKev QuirkKyle PiiraLaura KalbagLukas RosenstockMatt BaerMatthias OttMatthias PfefferleMax BöckMike KuketzNikita ProkopovNolan LawsonOwen WilliamsPaul Robert LloydPhilipp WaldhauerRahul ChowdhuryRemy SharpStanislas LangeSteven OvadiaSøren BirkemeyerTim ChambersZugreiseblogŽan Černein the blogroll content file.In the end, all I have to do to update my blogroll is update the opml.json file and update the lastmod frontmatter parameter in the blogroll content file.Check out my blogroll!

    Antworten

  66. Sorry, nothing fancy – I just commented out my complete content in style.css :-))
    I think a hook in functions.php and enqueue_scripts with a date comparison would do the trick in a more sustainable way …

    Antworten

  68. This are alphabetically sorted lists of blogs and sites I subscribe to using Miniflux. I started publishing this page in May 2019. When available, I often prefer the JSON Feed over RSS or ATOM. You can also read about how I create the blogroll.BlogsAndre Garzia (Feed)Annoying Technology (Feed)Aral Balkan (Feed)Ash Furrow (Feed)Beko Pharm (Feed)Ben Congdon (Feed)Brandon Nolet (Feed)Chris Wiegman (Feed)Chris Wiegman (Journal) (Feed)CJ Eller (Feed)Daniel Aleksandersen (Feed)Daniele Maltese (Feed)Danny de Vries (Articles) (Feed)Danny de Vries (Notes) (Feed)Danny van Kooten (Feed)Daryl Sun (Feed)David Heinemeier Hansson (Feed)Derek Sivers (Feed)Desmond Rivet (Feed)Drew DeVault (Feed)Ellie Huxtable (Feed)Emanuel Pina (Feed)Florian Anderiasch (Feed)Garrett Dimon (Feed)Henrique Dias (Feed)Horst Gutmann (Feed)Hrvoje Šimić (Feed)Jake Bauer (Feed)James Fenn (Feed)Jamie Adams (Feed)Jamie Tanna (Feed)Jan Boddez (Feed)Jason Fried (Feed)Jeff Atwood (Feed)Jessie Frazelle (Feed)Jonathan Borichevskiy (Feed)Justin Vollmer (Feed)Katharina Nocun (Feed)Kev Quirk (Feed)Kevin C. Coram (Feed)Kyle Piira (Feed)Laura Kalbag (Feed)Marcel Wichmann (Feed)Martin Schneider (Feed)Martin Schneider (der tag und ich) (Feed)Martin Tournoij (Feed)Matt Baer (Feed)Matt Mullenweg (Feed)Matthias Ott (Feed)Matthias Pfefferle (Feed)Max Böck (Feed)Michael Lynch (Feed)Mike Babb (Feed)Mike Stone (Feed)Nils Riedemann (Feed)Nolan Lawson (Feed)Oscar Benedito (Feed)Paul Robert Lloyd (Feed)Philipp Waldhauer (Feed)Rahul Chowdhury (Feed)Remy Sharp (Feed)Roland Szabo (Feed)Ru Singh (Feed)Scott Nesbitt (Weekly Musings) (Feed)Stanislas Lange (Feed)Steven Ovadia (Feed)Søren Birkemeyer (Feed)Tom MacWright (Feed)Žan Černe (Feed)ComicsCommitStrip (Feed)Dilbert (Feed)MonkeyUser (Feed)xkcd (Feed)

    Antworten

  69. Earlier this week Matthias Pfefferle released an update of the Sempress theme I use as a basis for this site. I clicked install in my WordPress dashboard, and then my site became unreachable. I mentioned it in the IndieWeb IRC/Slack channel for WordPress and Matthias kindly offered help in figuring out the issue. He found a small mistake on his side, which he quickly corrected and updated, and he spotted a few differences between my child theme and his original. But it didn’t solve the issue. So I left my child theme turned off, and ran Sempress proper, with the idea I would make time to compare my child theme alterations with the original later in the week. Then I slept on it and the next morning I woke up with the notion that I had changed some function in the original Sempress theme, for my child theme to work.
    That turned out to be the issue. I copied and tweaked a function, that then in the original Sempress file should be wrapped in a conditional statement that checks if that function isn’t already loaded (as the child theme gets loaded first, then the theme). When a function gets loaded twice it causes a clash. Precisely that function isn’t wrapped by default in a check if it already exists. So I added if (!function_exists(sempress_customize_css)): and all was well again.
    Unlike last time, this time I documented that I need to do this after an update of the Sempress theme. (Or suggest a change to the original.)

    Antworten

  71. Ich habe das Thema meines Blogs zu Autonomie (von Matthias Pfefferle) geändert, um die Möglichkeiten des IndieWeb besser nutzen zu können und zugleich mit Gutenberg zu experimentieren. Ich habe noch nicht viel getestet und auch noch nichts konfiguriert. Ich hoffe, dass Lost and Found so etwas weniger obskur wird. Man sieht wenigstens schon, dass es verschiedene Arten von Posts gibt, und welche Posts auch auf Twitter veröffentlicht worden sind. Bei früheren Versuchen, dieses Thema zu verwenden, bin ich gescheitert, weil das Design durch das W3 Total Cache-Plugin zerschossen worden ist, das ich möglicherweise falsch verwendet habe.
    Ein damit zusammmenhängendes inhaltliches Todo: Deutlich machen, wie die Themen Indieweb und Degrowth miteinander verbunden sind. Bisher ist mir das noch nicht wirklich gelungen, und die beiden Communities, die durch diese Schlagwörter bezeichnet werden, sind kaum miteinander verbunden. Ich glaube, dass die Verbindung sowohl für die Degrowth- wie für die Indieweb-Bewegung wichtig ist, weil einerseits die Digitalisierung in ihrer jetzigen Form zu den Treibern des Wachstums und damit ökologischer Katastrophen gehört, und weil andererseits die Kritik am Wachstum auch begründet, warum es sinnvoll ist, auf dezentrale, föderierte Kommunikationsstrukturen und Medien zu setzen.
    Update, 9.12.2020: Ich kämpfe noch damit, das Thema zu verstehen und richtig zum Laufen zu bringen. Inzwischen habe ich das W3 Total Cache-Plugin hoffentlich komplett entfernt, dabei habe ich mich an How to Completely Delete W3 Total Cache Plugin? gehalten. Probleme habe ich, wenn ich ein Beitragsbild als Header-Bild benutzen will (vom Gutenberg-Editor aus), ich bekomme dann die Fehlermeldung Aktualisierung fehlgeschlagen. Die mf2_syndication-Eigenschaft ist mit einem ungültigen Wert gespeichert, und kann nicht auf null aktualisiert werden.

    Antworten

  72. Es gibt mehrere Wege um eigene WP-CLI-Befehle zu nutzen. Dieser Artikel zeigt, wie man in wenigen Schritten eine benutzerdefinierte wp-cli.phar erstellt, die die gewünschten Befehle integriert, die bspw. auf GitHub liegen. Dafür werden ein Shell- und ein PHP-Skript verwendet, die im gleichen Verzeichnis liegen. Diese findet man in diesem Repository.

    Das Entwickeln eines eigenen WP-CLI-Befehls wird in diesem Artikel nicht behandelt.

    PHP-Skript (make-custom-phar.php)

    Das Repository wp-cli/wp-cli-bundle liefert alles mit, um eine Phar-Datei für die offizielle WP-CLI zu bauen. Im Ordner utils/ liegt eine Datei namens make-phar.php. Diese erzeugt die wp-cli.phar im Hauptverzeichnis. Sie wird in den GitHub-Actions des Repositories mit folgendem Befehl aufgerufen:

    php -dphar.readonly=0 utils/make-phar.php wp-cli.phar --version=$CLI_VERSION

    Ist die Phar-Datei gebaut, kann man weitere Dateien hinzufügen, welche für die eigenen Befehle notwendig sind. Das nachfolgende Skript nutzt die make-phar.php, baut damit die wp-cli.phar, findet die gewünschten Dateien und fügt diese der Phar-Datei hinzu.

    .wp-block-code {
    border: 0;
    padding: 0;
    }

    .wp-block-code > div {
    overflow: auto;
    }

    .shcb-language {
    border: 0;
    clip: rect(1px, 1px, 1px, 1px);
    -webkit-clip-path: inset(50%);
    clip-path: inset(50%);
    height: 1px;
    margin: -1px;
    overflow: hidden;
    padding: 0;
    position: absolute;
    width: 1px;
    word-wrap: normal;
    word-break: normal;
    }

    .hljs {
    box-sizing: border-box;
    }

    .hljs.shcb-code-table {
    display: table;
    width: 100%;
    }

    .hljs.shcb-code-table > .shcb-loc {
    color: inherit;
    display: table-row;
    width: 100%;
    }

    .hljs.shcb-code-table .shcb-loc > span {
    display: table-cell;
    }

    .wp-block-code code.hljs:not(.shcb-wrap-lines) {
    white-space: pre;
    }

    .wp-block-code code.hljs.shcb-wrap-lines {
    white-space: pre-wrap;
    }

    .hljs.shcb-line-numbers {
    border-spacing: 0;
    counter-reset: line;
    }

    .hljs.shcb-line-numbers > .shcb-loc {
    counter-increment: line;
    }

    .hljs.shcb-line-numbers .shcb-loc > span {
    padding-left: 0.75em;
    }

    .hljs.shcb-line-numbers .shcb-loc::before {
    border-right: 1px solid #ddd;
    content: counter(line);
    display: table-cell;
    padding: 0 0.75em;
    text-align: right;
    -webkit-user-select: none;
    -moz-user-select: none;
    -ms-user-select: none;
    user-select: none;
    white-space: nowrap;
    width: 1%;
    }
    <?php

    // make-phar.php einbinden und wp-cli.phar bauen
    require 'make-phar.php';

    // Dateien finden, die hinzugefügt werden sollen
    use SymfonyComponentFinderFinder;
    $finder = new Finder();
    $finder
    ->files()
    ->ignoreVCS( true )
    ->name( '/.*.php8?/' )
    ->in( WP_CLI_VENDOR_DIR . '/angelocali' )
    ->notName( 'behat-tags.php' )
    ->notPath( '#(?:[^/]+-command|php-cli-tools)/vendor/#' )
    ->exclude( 'config' )
    ->exclude( 'debug' )
    ->exclude( 'dependency-injection' )
    ->exclude( 'event-dispatcher' )
    ->exclude( 'translation' )
    ->exclude( 'yaml' )
    ->exclude( 'examples' )
    ->exclude( 'features' )
    ->exclude( 'test' )
    ->exclude( 'tests' )
    ->exclude( 'Test' )
    ->exclude( 'Tests' );

    // Dateien hinzufügen
    foreach ( $finder as $file ) {
    add_file( $phar, $file );
    }

    // Optional: Ausgabe hinzufügen
    if ( ! BE_QUIET ) {
    echo "Added Custom Commandsn";
    }
    Code-Sprache: PHP (php)

    In Zeile 14 ist die Angabe des Verzeichnisses, in dem der eigene Befehl liegt. Falls der Befehl Abhängigkeiten zu Bibliotheken hat, werden diese auch auf diese Weise hinzugefügt. Es ist empfehlenswert sich bei der Erweiterung des Skripts an der make-phar.php zu orientieren.

    Die Verwendung der Finder-Klasse ist optional. Sie wurde hier der Einfachheit verwendet, weil diese auch in der make-phar.php genutzt wird.

    Damit sind die Vorbereitungen getroffen, um mit dem Build-Skript eine benutzerdefinierte Phar-Datei zu bauen.

    Build-Skript (build-script.sh)

    Zusammengefasst lädt das Build-Skript das wp-cli/wp-cli-bundle-Repository herunter, konfiguriert das Composer-Projekt, lädt den eigenen Befehl herunter, kopiert die make-custom-phar.php an eine geeignete Stelle und führt den Befehl zur Erstellung der Phar-Datei in leicht abgewandelter Form aus. Die einzelnen Schritte sind im Code-Beispiel erklärt:

    rm -rf wp-cli-bundle

    # wp-cli/wp-cli-bundle herunterladen
    composer create-project wp-cli/wp-cli-bundle

    # make-custom-phar.php in gewünschten
    # Ordner kopieren
    cp make-custom-phar.php wp-cli-bundle/utils/make-custom-phar.php

    cd wp-cli-bundle

    # Composer-Projekt konfigurieren für
    # require eines Custom Repos
    composer config repositories.hello-command vcs https://github.com/angelocali/hello-command.git

    rm composer.lock
    composer require "angelocali/hello-command"

    CLI_VERSION=$(head -n 1 vendor/wp-cli/wp-cli/VERSION)

    # Phar-Datei bauen
    php -dphar.readonly=0 utils/make-custom-phar.php wp-cli.phar --version=$CLI_VERSION
    Code-Sprache: Bash (bash)

    Nachdem die build-script.sh ausgeführt wurde, liegt die wp-cli.phar-Datei im wp-cli-bundle-Verzeichnis.

    Damit ist mein erster Blog-Artikel verfasst. Ich freue mich über eure Kommentare.

    Quellen

    https://github.com/wp-cli/wp-cli-bundlehttps://getcomposer.org/doc/03-cli.md#requirehttps://getcomposer.org/doc/03-cli.md#confighttps://github.com/angelocali/build-custom-wp-cli-pharhttps://github.com/angelocali/hello-command

    Danksagungen

    Vielen Dank an Matthias Pfefferle und Florian Brinkmann für die Inspiration zu dieser Lösung.

    Antworten

  73. Im Dezember 2021 habe ich nach über fünf Jahren Selbstständigkeit als WordPress-Entwickler den Schritt in die Festanstellung gemacht und bin seitdem Software-Developer im WordPress-Dev-Team bei IONOS.

    Ganz kurz: warum ich in die Festanstellung gewechselt bin

    Als Freelancer war ich meist der einzige Entwickler bei Projekten, und irgendwann hatte ich das Gefühl, dass ich so fachlich nur langsam weiterkomme. Die naheliegende Lösung war, mich nach einer Agentur umzuschauen, in der ich dann vielleicht auch gleich ein bisschen mehr mit Laravel zu tun haben könnte.

    Gleichzeitig kam mir das Dasein in der Selbstständigkeit zunehmend stressig vor, und meine lange vorhandene Meinung, Selbstständigkeit sei eigentlich das beste, was mir passieren kann, war dann nicht mehr so ausgeprägt. Und, hey, ein sicheres Gehalt ist auch was schönes 🙂

    Warum IONOS?

    Schließlich wurde es dann IONOS und keine Agentur, weil ich mit Simon (der mich auf die Stelle aufmerksam gemacht hat) und Matthias schon zwei Leute von meinem damals noch potenziellen zukünftigen Team kannte, mit denen ich mir sehr gut vorstellen konnte zusammenzuarbeiten, und auch die Themen klangen spannend.

    Nachdem ich das ganze WP-Team in einem Video-Call kennengelernt habe, hatte ich den Eindruck, dass das mit dem Team und mir gut passen könnte, und zum Glück war ich nicht allein mit dem Eindruck.

    Zwischenfazit nach vier Monaten

    Das wichtigste: der erste Eindruck vom Team hat sich bestätigt. Wir sind ein kleines, feines Team und die Arbeit macht viel Spaß.

    Im März war ein Teil des Teams beim CloudFest Hackathon in Rust, wo ich die meisten meiner da anwesenden Kollegen zum ersten mal live gesehen habe, und wir hatten ein sehr schönes (und produktives) Wochenende.

    Neben mir arbeiten mit Angelo und Marko zwei weitere PHP-Entwickler im Team (wir suchen Kolleg*innen 🙂 ), und unsere Hauptaufgaben-Gebiete sind WordPress-Plugins und Laravel-Apps. Ich programmiere mit Angelo viel zusammen über das Code-With-Me-Feature von PhpStorm auf einer IDE, und ich bin in verschiedenen Themen schon gut weitergekommen, etwa in Laravel, bei der Erstellung von Behat-Tests und der Programmierung von WP-CLI-Commands.

    Ein bisschen schwierig ist für mich mit den langsamen Konzernprozessen zurechtzukommen. Dinge, die ich vorher einfach entscheiden und machen konnte, brauchen jetzt teils langwierige Vorgänge, bis sie dann (vielleicht) umgesetzt werden. Aber was soll man machen, bei Sachen die mir wichtig sind bin ich (manchmal vielleicht ein bisschen nervig) hinterher und versuche zu erreichen, dass sie doch möglich werden (sorry, Team und besonders Matthias 🙃).

    Zusammenfassend lässt sich aber sagen: ich bereue den Schritt nicht, habe schon viel gelernt, arbeite an spannenden Projekten und bin Teil eines tollen Teams ❤️ Und weil ich mich für einen Teilzeitvertrag mit 30 Stunden pro Woche entschieden habe, habe ich nebenher weiter Zeit an eigenen Projekten zu arbeiten, es ist quasi eine Win-Win-Situation 🎉 Oh, und eine Blog-Challenge habe ich auch losgetreten, das hier ist mein erster Artikel dazu, Matthias, Angelo und Daniel sind mit von der Partie.

    Antworten

  74. Die Core Web Vitals sind euch vielleicht schon untergekommen, wenn ihr euch mit SEO und Performance-Optimierung beschäftigt. Dabei handelt es sich um verschiedene von Google eingeführte Messwerte, die Aussagen über die User-Experience einer Seite geben können.

    Diese Werte sind Teil der PageSpeed-Insights-Analyse, lassen sich aber auch per JavaScript ermitteln.

    Warum Web Vitals lokal messen, wenn sie Teil von PageSpeed sind?

    Bei PageSpeed sind die Core-Web-Vitals-Daten nur auf Basis echter Besucher*innen, wenn es innerhalb der letzten 28 Tage genug Traffic von Chrome-Usern auf der analysierten Seite gab, die der Übertragung der Analysedaten zugestimmt haben.

    Andernfalls handelt es sich um Lab-Daten, die weniger aussagekräftig sind als Daten richtiger Besucher*innen. Und selbst wenn genug Daten von echten Usern übertragen wurden, sind es nur Daten einer Teilmenge von Chrome-Usern.

    Messung der Web Vitals mit dem web-vitals-Skript

    Bei einer Recherche zu den Web Vitals habe ich zufällig gesehen, dass es ein web-vitals-Script gibt, mit dem die Web Vitals lokal gemessen werden können. Dabei gibt es ein paar Einschränkungen, sowohl beim Browser-Support, weil einige der APIs zur Messung der Werte nur in Chromium-Browsern unterstützt werden, als auch bei Seiten mit iFrames, weil die APIs keinen Zugriff auf die Inhalte von iFrames haben und diese deshalb nicht berücksichtigen können. Daher gibt es bei Seiten mit iFrames wahrscheinlich Unterschiede bei den mit dem Skript gemessenen Werten zu den PageSpeed-Insights-Werten.

    Auch mit diesen Einschränkungen (iFrames kommen bei mir sowieso nur selten vor) erscheint mir die lokale Messung aber eine interessante Möglichkeit, eine bessere Übersicht über die Web-Vitals-Werte meiner Website und damit zumindest einen Anhaltspunkt zur User-Experience zu bekommen.

    Die grundlegende Einbindung des Skripts kann so aussehen, wenn NPM genutzt wird:

    .wp-block-code {
    border: 0;
    padding: 0;
    }

    .wp-block-code > div {
    overflow: auto;
    }

    .shcb-language {
    border: 0;
    clip: rect(1px, 1px, 1px, 1px);
    -webkit-clip-path: inset(50%);
    clip-path: inset(50%);
    height: 1px;
    margin: -1px;
    overflow: hidden;
    padding: 0;
    position: absolute;
    width: 1px;
    word-wrap: normal;
    word-break: normal;
    }

    .hljs {
    box-sizing: border-box;
    }

    .hljs.shcb-code-table {
    display: table;
    width: 100%;
    }

    .hljs.shcb-code-table > .shcb-loc {
    color: inherit;
    display: table-row;
    width: 100%;
    }

    .hljs.shcb-code-table .shcb-loc > span {
    display: table-cell;
    }

    .wp-block-code code.hljs:not(.shcb-wrap-lines) {
    white-space: pre;
    }

    .wp-block-code code.hljs.shcb-wrap-lines {
    white-space: pre-wrap;
    }

    .hljs.shcb-line-numbers {
    border-spacing: 0;
    counter-reset: line;
    }

    .hljs.shcb-line-numbers > .shcb-loc {
    counter-increment: line;
    }

    .hljs.shcb-line-numbers .shcb-loc > span {
    padding-left: 0.75em;
    }

    .hljs.shcb-line-numbers .shcb-loc::before {
    border-right: 1px solid #ddd;
    content: counter(line);
    display: table-cell;
    padding: 0 0.75em;
    text-align: right;
    -webkit-user-select: none;
    -moz-user-select: none;
    -ms-user-select: none;
    user-select: none;
    white-space: nowrap;
    width: 1%;
    }
    import {getLCP, getFID, getCLS, getTTFB, getFCP} from 'web-vitals';

    getCLS(console.log);
    getFID(console.log);
    getLCP(console.log);
    getFCP(console.log);
    getTTFB(console.log);    Code-Sprache: JavaScript (javascript)

    Die get-Funktionen für die verschiedenen Web Vitals werden abgefeuert, wenn der Wert ermittelt wurde. So wie im Beispiel werden die Daten einfach ins Log der Developer-Tools geschrieben, in dem GitHub-Repo gibt es ein paar Beispiele, wo die Daten an Endpunkte geschickt werden.

    Ich habe mich noch nicht ganz entschieden, wie ich es für meine Site umsetzen werde, aber nach einem kleinen Anstupser von Matthias wird wohl ein WordPress-Plugin dabei herauskommen, mit dem die Web-Vitals-Werte für eine WordPress-Installation lokal gesammelt werden können. Wenn das fertig ist, gibt es wahrscheinlich einen Folgeartikel mit näheren Details.

    Antworten

  75. Ich arbeite gerade mit Marko, Florian, Matthias und Denise an einem Plugin, welches mitunter auf einer Seite ein paar Informationen zu mehreren Themes darstellen soll. Mehrere Requests sequenziell durchzuführen führt in unserem Fall dazu, dass die Seite sehr lange lädt. Deswegen habe ich nach einem Weg gesucht, Informationen zu mehreren Themes und Plugins mit einem Request abzufragen.

    Das Problem konnte ich wie folgt lösen: https://api.wordpress.org/themes/info/1.2/?action=theme_information&request[slugs][]=airi&request[slugs][]=neve&request[slugs][]=vantage

    Für jedes weitere Theme-Slug füge ich ein request[slugs][]=slug Query-Parameter hinzu.

    Falls ihr Informationen zu mehreren Plugin-Slugs benötigt, könnt ihr das auf ähnliche Art lösen. Hier auch ein Beispiel dazu: https://api.wordpress.org/plugins/info/1.2/?action=plugin_information&request[slugs][]=antispam-bee&request[slugs][]=cachify

    Antworten

  76. Links
    In guter Gesellschaft entwickelt mensch sich weiter. Um auf Personen, Unternehmen und Magazine aufmerksam zu machen, die mich inspirieren und von denen ich lerne, habe ich diese Liste angelegt. Sie erhebt nicht den Anspruch auf Vollständigkeit, ist aber ein Anfang. Mit einigen in der Liste arbeite ich gerne und regelmäßig zusammen, von anderen lese ich Blogs und Bücher oder schaue mir regelmäßig an was sie wie machen. A List Apart Alla Kholmatova Andy Bell Brad Frost Cassie Evans CSS Tricks Chris Ferdinandi Clearleft Daniel Wiegand Dirk Breuer Eric Meyer Filament Group Heydon Pickering iA Jeffrey Zeldman Jen Simmons Jens Strobel Jeremy Keith Johannes Kleske Joschi Kuphal Laura Kalbag Lea Verou Matthias Pfefferle Marc Thiele Markus Angermeier Michael Gibis Mike Riethmuller Rachel Andrew Remy Sharp Sarah Drasner Sara Soueidan Scott Jehl Sebastian Schulze Smashing Magazine Sven Schwyn Tantek Çelik Third Wave Berlin Zach Leatherman

    Antworten

  77. Fediverse
    Das Fediverse ist in aller Munde. Spätestens seitdem sich Twitter auf rasanter Talfahrt befindet, schauen sich viele Nutzer*innen nach einem öffentlichen Ort im Internet um, an dem Austausch, Inspiration, aktuelle Meldungen und Quatsch zu finden sind. In der Wikipedia beginnt der Artikel zum Fediverse folgendermaßen:
    »Fediverse (ein Kofferwort aus „federation“ und „universe“) oder Fediversum bezeichnet ein Netzwerk föderierter, voneinander unabhängiger sozialer Netzwerke, Mikroblogging-Dienste und Webseiten für Online-Publikation oder Daten-Hosting.«
    Aus meiner Sicht ist vor Allem der Aspekt unabhängiger und doch miteinander verbundener Instanzen interessant. Über ActivityPub, einem standardisierten Kommunikationsprotokoll, können unterschiedliche Server miteinander kommunizieren. Das Fediverse ist ein dezentrales Netzwerk, in dem über verschiedene Server miteinander kommuniziert werden kann. Mastodon, das sich aktuell großer Beliebtheit erfreut, ist eine Software die auf unterschiedlichen Servern betrieben werden kann. Daraus ergeben sich unabhängige soziale Netzwerke, die jedoch das selbe Kommunikationsprotokoll verwenden was einen Austausch über die Server hinweg möglich macht.
    Da es sich bei ActivityPub um ein vom World Wide Web Consortium (W3C) definiertes Kommunikationsprotokoll handelt, wird es nicht nur von Mastodon unterstützt, sondern beispielsweise von Pixelfed, einer Plattform zum Teilen von Fotos, und über eine Erweiterung von Matthias Pfefferle können WordPress-Blogs, wie dieses hier, als Instanz im Fediverse auftreten. Nutzer*innen können den Artikeln des Blogs auf Mastodon folgen und damit interagieren.
    Aktuell wird diese Art der Kommunikation häufig mit E-Mail verglichen. Bei jeder E-Mail die wir verschicken greifen wir auf das »Simple Mail Transfer Protocol« zurück, das den meisten von uns beim Einrichten einer E-Mail-Adresse auf einem Computer als SMTP begegnet ist. E-Mails basieren ebenfalls auf einem standardisierten Kommunikationsprotokoll über das Nachrichten zwischen unterschiedlichen Servern verschickt werden können.
    Für alle diejenigen, die bei standardisiertem Kommunikationsprotokoll aussteigen wollten, und sich den Scherzen über die Komplexität von Mastodon anschließen wollten, habe ich den kurzen Exkurs zu E-Mails aufgegriffen, dies benutzen noch viele Menschen täglich, und fühlen sich dabei nicht wie Nerds.
    Was mich an dem aktuellen Aufschwung von Mastodon begeistert ist die Tatsache, dass eine Plattform mit Leben gefüllt wird, die auf einem offenen Kommunikationsprotokoll basiert und daher dem offenen und dezentralen Charakter des World Wide Web entspricht. Wie alles andere, ist auch das Fediverse nicht perfekt, und dennoch hat es das Potential den Begriff »soziale Netzwerk« neu zu definieren. Gerade weil Mastodon und Pixelfed Dienste anbieten, die ähnlich einfach zu nutzen sind wie E-Mail.
    Falls Du mir im Fediverse folgen möchtest, kannst Du diese Adressen beispielsweise auf Deinem Mastodon-Server suchen: @depone – für Statusupdates aus meinem Alltag @depone – für Fotos @depone@danielehniss.de – für Posts aus meinem privaten Blog @Daniel – für Posts zu den Themen Internet und Front-End-Development

    Veröffentlicht am 12.11.2022 von Daniel in IndieWeb, Internet.

    Antworten

  78. Brief overview of how I’m active in the fediverse.
    My site
    I would prefer this site to be the centerpoint of my fediverse presence. For now that isn’t fully feasible, but it will be over time. Already the building blocks for WordPress to be a fediverse actor exist. The Activity Pub (AP) plugin and Webfinger plugin by Matthias Pfefferle are useful, just not allowing enough granular control yet to my taste. For one, the AP plugin exposes actual usernames of my WP site, a disclosure I don’t like. I need to be able to set the actor names for AP, through the AP plugin and/or the Webfinger plugin. Second, the AP plugin allows sharing my blogposts but only all blogposts, and I want to be able to only publish certain categories of posts as well as individual posts marked for sharing through AP. Third, the AP plugin doesn’t yet take into account the interaction parts of AP (like follows etc.).
    Mastodon
    I run two Mastodon instances, one hosted at Masto.host. Masto.host has been a very reliable service since I started hosting with them in 2018. I ran a personal instance (m.tzyl.nl) with them until late November 2022, and started one for my company (m.tgl.eu) early November 2022. I run my personal instance of Mastodon on a VPS with Yunohost, at m.tzyl.eu
    Discoverability hack
    I have added simple text files to /.well-known/webfinger to both this site and my company website that allow discovery of my existing Mastodon profiles through my site’s and work e-mail addresses. This is just a hack, and I should replace it with actual functionality to disclose actors on both those sites.
    Bookwyrm
    Bookwyrm is the book reading application on AP. I have an account at the primary instance and supported them financially for a while, but haven’t used it much since spring 2022. This is one of the things I want to do myself through this site.
    Potential AP projects
    As said above I’d like to be able to share my reading through AP from this site. I would also like to be able to share my planned travel and/or check-ins through this site in AP. Specifically travel plans (Dopplr like) are of interest to me. AP, unlike this site, would allow non-public sharing of this information to followers only.

    Antworten

  79. ActivityPub und soziale Netzwerke
    Eben Folge 94 des neunetzcast von Marcel Weiß und Matthias Pfefferle zu Ende gehört. Sehr schön, wie die beiden darin über ActivityPub, Mastodon, Flickr, Twitter, WordPress und in diesem Zusammenhang die Zukunft sozialer Netzwerke sprechen.
    Der Enthusiasmus hinsichtlich Fediverse, über das ich auch kurz hier geschrieben hatte, ist meiner Ansicht nach immer noch da. Vor allem die Möglichkeit etwas mehr Kontrolle über die eigenen Inhalten zu haben, beispielsweise bei Bedarf mit ihnen umziehen zu können, ist ein großer Vorteil gegenüber den proprietären Diensten.
    Bei der Wahl der Nachbarschaft, in denen Nutzer*innen ihre Accounts anlegen, bleibt weiterhin zu bedenken ob mensch dort hinein passt und wie vertrauensvoll die Administrator*innen erscheinen. Der Gedanke im Podcast, dass es für Hosting-Anbieter ein interessantes Feld sein könnte, Managed Hosting für Mastodon anzubieten finde ich ebenfalls sehr spannend.
    Ich, für meinen Teil werde weiterhin im Fediverse aktiv sein, und beobachte die Entwicklungen mit großem Interesse. Falls es Dir ähnlich geht und Dich auch ein Blick auf die Geschichte von ActivityPub interessiert, sei Dir die Eingangs verlinkte Folge 94 des neunetzcast empfohlen.

    Veröffentlicht am 27.11.2022 von Daniel in IndieWeb, Internet.

    Antworten

  80. Viel wird in diesen Tagen geschrieben über Twitter und den ganzen Elon Musk-Irrsinn, viel wird diskutiert über die problematischen Seiten zentraler Kommunikationsinfrastruktur in den Händen von mächtigen Privatpersonen. Da ist es nicht nötig, dass ich – ganz im Sinne von „Es wurde bereits alles gesagt, aber noch nicht von jedem“ – hier das Thema inhaltlich nochmal vertiefe. Mit diesem Post will ich vor allem meine (zugegeben noch sehr überschaubaren) Fediverse-Links sammeln, die für die Leute interessant sind, die sich für mich interessieren. Here we go:

    @dasaweb@wue.social Das ist der Link zu meinem Mastodon-Profil. Ich war vorher auf der beliebten Instanz mastodon.social, an der es an sich auch nichts auszusetzen gibt; allerdings ist mir die Idee der Dezentralität wichtig, daher bin ich unlängst zu wue.social gewechselt. Eine kleine und lokale Instanz, bei der die lokale Timeline dann auch wirklich eine geographische und keine inhaltliche Lokalität abbildet. Die „lokale Timeline“ ist die Sammlung der Inhalte, die Leute auf genau dieser Instanz auch posten. Außerdem wird die Instanz von Ralf gehostet, und Vertrauen zum Hoster ist immer eine gute Sache, siehe die aktuellen Twitter-Debatten… Im Moment ist die Instanz noch so überschaubar, dass Moderation kaum nötig und die Finanzierung auch privat machbar ist. Ralfs gute Gedanken dazu findet man in einem Post von ihm auf dem Würzblog.

    @dasaweb@pixelfed.de Mein Pixelfed-Account. Pixelfed funktioniert wie Instagram, nur eben dezentralisiert und natürlich über das ActivityPub-Protokoll, genau wie Mastodon und alles andere im Fediverse auch. Zugegeben, hier ist noch gar nichts los, bisher habe ich dort nur zwei Testfotos und bin nicht vernetzt. Aber vielleicht werde ich meine Liebe zu Fotos dort wieder ausleben, Instagram ist für mich aktuell leider nur noch eine Plattform für Stories. In der Diskussion um Twitter und Mastodon verstehe ich, dass Mastodon konzeptionell hier und da Schwierigkeiten hat; bei Instagram vs. Pixelfed sehe ich die tatsächlich viel weniger, denn da geht es (jedenfalls in meinem Nutzungsverhalten) doch viel mehr um ein persönliches Netzwerk und weniger um globale Debatten. Wir werden sehen.

    @dasaweb@dasaweb.de Unter diesem Link kann man den Inhalten dieses Blogs hier im Fediverse folgen. Einfach @dasaweb in die Suche z.B. bei Mastodon eingeben und folgen. Möglich ist das durch die ActivityPub-Erweiterung von Matthias Pfefferle für WordPress. Feine Sache. Generell mag ich die Idee, vorhandene Plattformen ActivityPub-fähig zu machen.
    Nachdem jetzt so häufig die Begriffe „Fediverse“ und „ActivityPub“ gefallen sind verlinke ich dazu doch noch ein kurzes Video, falls das jemandem gar nichts sagt. Ist schon etwas älter, was ich ganz gut finde, weil es dadurch nicht von den aktuellen Debatten überlagert ist:

    Ich bin gespannt, wie das alles weiter geht. Mein Optimismus, dass Fediverse-Angebote bisherige Social-Media-Diensten den Rang ablaufen werden hält sich in Grenzen. Aber ich bedauere das, weil ich der Meinung bin, dass die nicht zu leugnenden aktuellen Nachteile (Bsp.: keine globale Suche bei Mastodon) keine Rolle spielen sollten gegenüber den Problemen, die wir uns gesellschaftlich und politisch in den letzten Jahren mit Diensten wie Facebook und Twitter eingehandelt haben. Das größte Problem für einen Wandel scheint mir die Trägheit der Masse zu sein, und dagegen kann ich als Physiker nun wahrlich nichts sagen…

    Antworten

  81. Matthias Pfefferle is head of WordPress development at a hosting company in Europe and the creator of Activity Pub, a WordPress plugin. He joins Cory Miller to discuss the rising need for decentralization in social networking, the current movement, and the future potential available within WordPress.

    Estimated reading time: 37 minutes

    Transcript ↓

    In this episode, Cory Miller talks with Matthias Pfefferle, creator of Activity Pub, about the growing potential for decentralization through innovation within WordPress. Current social networks have stripped creators of agency and power. The threat has been more acutely felt with the recent transitions within Twitter. Recognizing what is at stake and moving towards innovation could not only create needed solutions but could also propel the future of WordPress.

    Top Takeaways:

    Decentralization: So much of the power of WordPress is rooted in decentralization. The silos created by social media platforms leave users without agency. The potential and appetite for decentralization is increasing along with the tools to make it a reality via the Fediverse, Activity Pub, and more.

    Portable Social Networks: If you are blocked or banned from a major social network, you lose your content and contacts. The need to create portable social networks so you can move your audience and retain your content if you opt to or are forced to switch platforms or hosts is crucial.

    Alternative Walled Gardens: The need for alternative social platforms where users have agency and ownership continues to increase. The Twitter debacle has been a huge catalyst for users to transition to other platforms like Mastodon, but the potential for WordPress to solve identifier issues and more could create the largest platform overnight. How can we create tools and empower people to be a part of social networks and retain ownership of all they create? How can WordPress build on the current momentum to create future relevance?

    🙏 Sponsor: A2 Hosting

    A2Hosting offers solutions for WordPress and WooCommerce that are both blazing fast and ultra-reliable. WordPress can be easily deployed on ANY web hosting plan from A2: Shared, VPS, or Dedicated. A2 also offers Managed WordPress and WooCommerce Hosting. Take a look at a2hosting.com today!

    🔗 Mentioned in the show:

    Matthias Pfefferle

    Activity Pub

    Activity Pub Plugin

    Fediverse

    Mastodon

    Pixelfed

    B2

    W3C

    World Wide Web Foundation
    🐦 You can follow Post Status and our guests on Twitter:

    Matthias Pfefferle (Creator, Activity Pub)

    Cory Miller (CEO, Post Status)

    Olivia Bisset (Intern, Post Status)
    The Post Status Draft podcast is geared toward WordPress professionals, with interviews, news, and deep analysis. 📝Browse our archives, and don’t forget to subscribe via iTunes, Google Podcasts, YouTube, Stitcher, Simplecast, or RSS. 🎧

    Transcript

    Cory Miller: [00:00:00] Oh, I just thought I’d start recording, so like, I know we’re gonna get into a good conversation. I don’t wanna miss it . Um, so, um, well first Mattias, could you tell me, um, what you do in WordPress,

    Matthias Pfefferle: um, professionally or, um, my side projects?

    Cory Miller: Oh yeah, that’s right. Well, I know you’re the head of the WordPress development at your company, and then I know you have side projects.

    So I guess professionally what’s your, what’s your, what do you do professionally with WordPress? At

    Matthias Pfefferle: iOS? Yeah. Currently I’m, uh, leading, uh, WordPress development team and we are responsible, um, for the word. Product, um, in, in the hosting environment. So we try to make the WordPress installation as simple as possible for our customers, um, giving them some kind of a [00:01:00] wizard and, uh, better onboarding processes and um, yeah, some guidance, stuff like that.

    Yeah.

    Cory Miller: Gotcha, gotcha. And I, I is a hosting company, is

    Matthias Pfefferle: that right? Yeah, it’s in Europe. It’s a big player.

    Cory Miller: Yeah. Yes. That’s what I learned. I talked to one of your colleagues and I can’t remember his name too, but I was like, gosh, that’s what I love, getting over to Europe in different parts of the world. So many good WordPress things going on that I just don’t know about in life.

    And so it’s always exciting. Um, how long have, have you been with io?

    Matthias Pfefferle: Uh, ma’am, I think it’s, uh, nearly exactly seven years. Okay. Yeah. That’s quite something. Well,

    Cory Miller: yes, yes. Um, well, let’s talk about the subject that I’m very curious about. I know it’s the, I think it’s the side projects you do. Yeah. Um, so I heard about Act Activity Pub, and I was really intrigued and reached out [00:02:00] and wanted to talk to you about this.

    So what really is Activity Pub?

    Matthias Pfefferle: Um, I think the easiest way to explain it is the protocol behind Macedon. I think Macedon is currently, um, in every news, um, at least, uh, now that, uh, Elon Musk is, has taken over Twitter. Um, everyone, uh, tries to, to move his account to, to methadone and, uh, activity Pup is kind of.

    Technical protocol that enables masteron to communi communicate decentralized. And it’s not only masteron, it’s, it’s a whole bunch of different, um, special case platforms. There’s pixel fed that, um, is specialized for, um, images, so kind of the decentralized version of [00:03:00] Instagram and their video platforms.

    There are other micro blogging, um, platforms, and there are also some blogging platforms that are completely activity pub, um, compatible. So yeah, it’s kind of the, the, the base of it’s, um, also called the fedi verse, fed federated universe. That’s kind of the, the summarized, uh, topic. Yeah.

    Cory Miller: And part of this is, uh, Mathias.

    I don’t know how much you know about me, but I’m technical enough. But some of this I’m asking cuz I don’t, I really don’t even know. Okay. But what, why this was interesting. Well, is the, when you said decentralized, that’s, that’s always interesting to me. But the fact that, well I want to ask you, why is this interesting to you to do activity pub?

    Um,

    Matthias Pfefferle: yeah, kind of, [00:04:00] it’s kind of a bit, it’s nostalgic. It’s really nostalgic. I, I started blogging, um, with the predecessor of WordPress, b2 and since then I’ve fell completely fell in love with the blogging and the, the whole. When I started blogging, there was no Facebook and there was no, um, big, uh, social network.

    And I left the decentralized blogging, um, referencing each other and owning your own content. And then when the big players came and everyone closed their, um, their small blogging platform to, to move to Facebook or later to to Instagram, I searched for a lot of alternative or, or for possibilities to keep blogging [00:05:00] important and relevant, and started a lot of projects, all with the focus of being decentralized, kind of having your own part of a bigger social network to keep this status quo alive.

    So, yeah, that, that’s kind of the, the background for that. So I tried a lot of different, um, protocols, a lot of different ideas, and, um, I think with the, the Twitter problem and the, the rise of masteron, it’s kind of the first time I think that the, the dec decentralized version of a social platform really has a chance.

    So I was really, um, I, I thought, yeah. And the, the, the activity pub protocol is also some kind of a, [00:06:00] let’s say the, the most official version of a decentralized protocol ever, because it’s, um, released through the, uh, W three C, the. Word, web foundation. No, the word I know what you’re talking about. Yeah. . Yeah.

    And, um, yeah, and this combination between, um, it’s kind of a official or nearly official, uh, uh, uh, de facto standard. And the, the, the possibility with maam Meg makes a really interesting Yeah. Environment. And I, I thought okay, maybe give it a last try to implement something in WordPress, um, to, to, yeah, keep, keep blogging alive.

    Cory Miller: What is, what does an activity pup actually do though in [00:07:00] WordPress? And I’m asking cuz I, I don’t know. I, I know the buzzwords decentralized and I’m like, okay, tell me, tell me what it really does for WordPress for, uh, a WordPress blogger or word, WordPress site. Um, I,

    Matthias Pfefferle: first, I, I don’t wanted to implement, uh, a full-fledged, uh, social network.

    So I started the, the, the main idea was, okay, how can I build something that b would be a part of the 30 words, but having no, uh, keeping the, the, yeah, the complexity low. So I started with, okay, let’s try. A version where someone on the on Maerk can follow a block or a user on a block and [00:08:00] kind of subscribe to the blog posts.

    And every activity on Maerk will be, um, will be federated to the WordPress block. So it’s kind of a simple, uh, two-way communication, but it’s not that I can use my WordPress block as a, as a social network. I can’t follow someone on, on Master, on, on my WordPress. I think there are better ways or better platforms to do that, but I thought at least this one would be really awesome.

    So, uh, it’s kind of, I can still write my posts where I always have written it and. I can spread them and others can follow my blog. And I don’t have to do the, the, the whole crossposting stuff, which is only one way if I [00:09:00] crosspost my, my blog post to Twitter or, or ma or other platforms. It’s only, yeah, my article lands on that platform, but every communication, every social interaction on that platform will stay there.

    And I have to check all of the platforms to see if there’s something. And with Activity Pub for, um, WordPress, it enables kind of this two, two-way communication. The next step would be if I would write an answer to, to one of the comments on, on the block that this will be also, um, back posted to me.

    Cory Miller: You know, I, I go back to blogging too, and, um, you, you’re earlier than me, but I was 2006 using WordPress. I loved it. You could publish something without having a no code, put it out on the internet, people could [00:10:00] come. R s s was a big deal on whoever mentioned talk to you mentioned like R rss. Everybody had the feed, a feed reader back in the day that slowly kind of died.

    And, um, and then I was like, well, the only way to stay connected is email. But I love this, of course, WordPress and posts too, is we wanna support the open web and decentralized. I’m always gonna be a champion of, because we’ve seen you, you, you’ve evidenced the recent one, which is this debacle with a billionaire buying a social network and running it into the ground potentially.

    But, you know, the other day I was thinking, I’ve got this, I’ve got a Twitter following over here, but it kinda starts to feel little silent over there. And then you go, what’s gonna happen to it? It’s outta my control, which is why I was like, I’ve gotta talk to Mattias to talk about activity Pup. What do you think, um, I wanna ask it like this, but what’s the, what do you think the potential of this [00:11:00] I, I see sometimes, but I wanna really hear it from you, is what’s the potential for activity club and this, you know, the Fedi verse, um, WordPress becomes a player again, it seems like a big player with content creation, which is where I fell in love with WordPress, cuz you could put content up and create it and not have to manage a bunch of HT HTML pages or a database or anything.

    It’s all there. Um, so like, I was like, we’ve gotta have this conversation in WordPress. Um, because you’re gonna see these closed walled gardens like Facebook, Twitter, Lincoln, whatever it is, that are owned and operated by people out of our control. And I think we all fly the flag of, we love the freedom of WordPress.

    So what do you see the potential for this? Not trying to say you need to protect the future, but you see a, a better feature there. Um, that’s linked to, um, the Fedi verse and particularly, um, activity pub. [00:12:00] Um, what’s your hope for it? ?

    Matthias Pfefferle: Yeah. Um, I think, um, well to, to kind of, um, you, you mentioned email, I think, um, with Acti, activity Pub is really, or the, the whole idea is really similar to email.

    So, um, email is decentralized. So you can choose between hosting your own email survey with your own domain. So you are in control of everyth everything. , but you have to know a lot about how email works and you can go to one of the big players or to one of, to, to a host, um, you trust. So you can choose between all of these possibilities.

    And Masteron is kind of the same. So you can choose one of the big Masteron platforms, um, if you trust them, or you can host your own [00:13:00] little platform. And I’m, I was really interested in, in the um, own platform thing because if you join a big masteron instance, it’s not exactly the same as with Twitter, but it’s kind of the same.

    So, Nevertheless, you have to trust the, the platform owner or the, the company that runs the platform. And that could also change something. I just recently read that, um, Elon Musk is also, or, or has also bought one of the biggest maslon platforms. So the, for the users on that PLA platform, it’s kind of the same issue.

    Okay. It’s easier to, to move platforms be because it’s decentralized. So if you, if you say, okay, I, I, I don’t trust the, the, the owner anymore. [00:14:00] I can switch platforms and keep my friends. So it’s easier, but it’s, they’re the same risks as on, on the, the big wallet gardens. Um, and if you, Find a way to make it as easy as installing a WordPress block.

    There’s, yep. There, there is nearly no risk. Okay. Your, your, um, your ster can, can shut off your website, but, um, then you are in, in control of the, the domain you and control of your workforce block. You, you can move that around to everywhere, everywhere you want. So it’s, yeah, the, the easiest, simplest way to control your data and to be independent and nevertheless, [00:15:00] to be part of that big, um, new social network.

    And that’s kind of amazing in my, in my eyes. So that’s why I, I started the, the, the work on activity pub and. I started it four years ago and it w , I had, let’s say, kind of a hundred, uh, a hundred downloads, and in, in the last, let’s say four weeks, it, it, uh, it raised, uh, it’s, it’s amazing. I, I think it’s, uh, 2000 and, uh, rising steadily.

    Um, and a lot of it’s still a bit complicated for, um, installing on, on shed hosting. So I have a lot to do, um, answering support questions and, uh, uh, release some small pack fixes, but yeah. [00:16:00]

    Cory Miller: Okay. So how would, in a perfect world, we’re meeting a year, two years from now, what do you hope happens with everything?

    And I wanna leave it blank like that just to see with I I, with Fed Verse and WordPress’s place in it,

    Matthias Pfefferle: um, I think the, the Fed verse itself has, will, will grow and will improve, um, I think mostly in the part of having portable, um, portable profiles to make it even easier to move platforms. And I think for, for WordPress, my, my hope is that[00:17:00]

    I can manage to implement a full fledged server. So, I hope I, I will find some time to also implement the following part so that in the end you maybe have a, a fully full flavored, um, master on like, um, insulation, um, with your WordPress. Yeah. That, that would be awesome in the end. Yeah.

    So,

    Cory Miller: and this is for my own understanding. So for that to happen, you have to go get a mask on instance. Is that right? No,

    Matthias Pfefferle: no. My, my, my hope, um, and that’s why I, I mentioned the combination. My hope is that, um, mess of the activity pop will improve that way that you [00:18:00] can. Profiles very easily to, to keep your, um, your friend network and to move from one, um, instance to another instance, or from one platform to a completely different platform.

    Um, yeah, without losing anything and without having too much, um, hand work is, is that a word in English too? Too many configuration stuff and, and, um, yeah, redefining things. Um, yeah, because that would allow you to simply switch between your current mn instance to your own WordPress blog, for example. And then the next part would be a way, um, to import, um, your, your complete, uh, social network and to have a.

    Yeah. To to, to support [00:19:00] following others and find a way to, um, yeah, kind of display the, the activity stream you currently have in, in maam,

    Cory Miller: portable social network, so kind of portable social network. Yeah, exactly. Okay. So there’s this growing trend and I go, because we’ve been blogging for you and I have been bloggers for a long time.

    I go, well, this is a new name for blogging, but the creator economy. And you see these Instagram, um, people building up huge followings with the problems and the threats that I see. We, we see. And that they’re gonna change a policy. They go from Instagram, goes from photo to video, and then all of a sudden they use, lose a lot of traffic and all that stuff.

    Then they have this other problem, which is how do you monetize it? You’re under the same rules. Okay. So if I a creator, [00:20:00] it seems like WordPress is a great hub to build all the things we just talked about. It’s yours. You have the, you have the same rights and freedoms. I need an ins uh, Mastodon instance, but like, how would you suggest a creator start using WordPress in the Fed averse to do these outcomes we’ve been talking about,

    Matthias Pfefferle: the way I started building the plugin shouldn’t, does not force you to change anything. So the idea is to keep. Working with WordPress you did before. So it’s still, you publish your, uh, images, you publish your videos. Um, the only difference is others can follow you, not only via r s s or Atom, but on, on a real social network and on Masteron.

    [00:21:00] There, there are possibilities to, um, to change the look and feel of how your, uh, blog post will be displayed on the social networks because masteron in the end is, uh, um, micro blocking service. So it might be useful to, to strip, um, your, your blog posts or to, to use only the excerpt. Um, and, uh, pixel Fed is focusing on, on images.

    So for that platform, it, it, um, It makes sense to, uh, highlight the image, but the how you interact or how you use WordPress does not, uh, that does not change anything. It’s, doesn’t change simply, uh, keep, keep what you’re doing, keep blogging, um, and the rest will be done by the plugin. Okay.

    Cory Miller: Sorry, I’m trying to get clear on my [00:22:00] question.

    Oh, so okay. No, no, no. You helped me a ton. No, that and, and broadening my understanding of it, because what I see is going, here’s a choice, just like we had in the old days. Here’s a choice. Um, proprietary software, closed software, and then here’s the choice called WordPress and open source. So I think the question I’m probably trying to get to is, I think the thesis here is we need to get, we need to get a lot of people embracing the fed averse.

    And understanding it. S see. Yeah. Okay. What do you, but what do you think needs to happen for this to become the new way? We don’t go to Twitter, Facebook closed system. We go to use a tool like WordPress or whatever o other tool, connect it to the fed averse. And you’re, you’re doing the same thing as those creators back on Instagram.

    Cause that’s, is that not the vision here? [00:23:00]

    Matthias Pfefferle: Yeah, that’s the vision. The, the problem is, um, it’s very, very hard to convince someone to do that. So I think the, the, the current situation with Twitter was one of the best thing that could happen for the whole fatty worst muscle on stuff, because I think. It’s still way easier to be on Facebook and to publish things on Facebook because all of your friends are there and the, the whole following part on the Fed verse is still a bit nerdy because you, you have to, you have to understand the, the identifier thing, username at, uh, domain, and you have to know which user is on which platform.

    So you, you have to know the, the [00:24:00] complete handle. And there’s currently no easy way kind of, yeah. Search through this, uh, directory and find all of, all of your friends. They, they tried to do that using Twitter. So if you, um, put the, the melon handle in your Twitter bio, um, there were tools that grabbed these information and, um, added all of these friends you had on Twitter, on the, on the, on, on Macon or something like that.

    But there’s, in the end, there’s again, a centralized platform you are using to find your friends. So, um, I think this is really the, the key change. If you find a way, kind of like the, the email address, if, if it’s common sense to use such [00:25:00] identifiers, Then it would be no pro, the, the, the fairly words would be no problem.

    So maybe it’s a good idea to combine that with, um, email addresses to find or to, to, to convince the big, um, email providers or hosting providers to also run, um, masculine instances, at least for the short term. So that you kind of understand the, how the identifier works or you kind of Yeah. Improve the, the, the, the whole identifier stuff.

    I think that’s the, the, the key part in, in the, in the whole discussion. Yeah.

    Cory Miller: And that’s, it’s like a,

    Matthias Pfefferle: it’s easier or, or, um, TikTok or, or Instagram. It’s easier to say. I, I’m, Mathias at, at Instagram. It’s way [00:26:00] easier than I would say. I’m Mathias at notit dot block, so yeah. Mm-hmm. and there’s currently, there’s currently no search engine that searches through all the different federated platforms.

    So you can’t guess on Instagram. You, you can try to search for, for the whole name and you get su suggestions. But if you search in the and you are on the wrong platform, um, you, you don’t, you, you don’t find the person in, in general, you, you are searching. So

    Cory Miller: kind of because it’s so decentralized. Yeah.

    It’s not, there’s that big lack, which is why I go, I usually use myself as a bar of technical, you know, if I have to go figure out, okay, an instance, what is this and that. But if we smooth that out, the word Christmas hole [00:27:00] equation is, I go, I think it, it’s potential for return to use this amazing tool that’s already the largest, you know, one of the largest software pieces of software on the planet.

    Um, particularly on the web. I mean, but like, so I go, wow, this is an opportunity for WordPress to come back to be the hub. Or a hub or, or a tool for the bigger hub, is that, you know? Yeah. But I saw the same things you’re talking about. It’s, it’s not common sense, like you said, to go and do it for most people.

    Matthias Pfefferle: Yep. But, but maybe, um, WordPress can solve the issue, at least in the WordPress ecosystem to, to maybe have a directory of different users, um, with their domains or their, their identifiers, um, using wordpress.org as a kind of centralized, uh, uh, contact [00:28:00] book, um, where can search for, for people. So maybe WordPress solve this problem in, in, in his kind of, uh, little ecosystem.

    Yeah, it

    Cory Miller: sure could. It could be a great start. Like I remember going, you know, if you, if you son did a wordpress.com, you know, go into a site and seeing the bar at the top seems similar to that. Like Yeah. Is there a way to better. All this together. Um, if you have WordPress se you can click the button or you know, whatever else, and then you become discoverable on a bigger network.

    Matthias Pfefferle: And I think wordpress.com is, is could also really be a, a game changer. Be because they are also, it’s one platform. So it’s really easy to maybe strip the whole webpress.com stuff and only use the, the subdomain part to search for other people on the, on the, on the platform to, [00:29:00] yeah. Make, make the first step.

    So with webpress.com, you kind of can build, uh, uh, uh, yeah, a master like platform completely with, uh, WordPress and Activity Pub. Um, and yeah, I think it would be one of the biggest, uh, platforms, um, with, with one. Yeah.

    Cory Miller: So overnight.

    Matthias Pfefferle: Yeah. And I think it’s, it’s also really, it should be, uh, a really interesting, um, technology for hosts and for platform providers because it’s kind of the, the only way to make, um, to, to, to have, uh, uh, an alter an alternative to, to Facebook and, and Twitter and, and [00:30:00] to bring, maybe bring PE people back to, to, um, using their own platforms and, and, um, switching to, yeah, coming, coming back to, to hosting their own platform.

    Mm-hmm. . Yeah. Maybe it’s a, it’s a joint venture between hosting providers, workforce providers. Platform providers like webpress.com to build kind of an alternative to, to the, um, wallet gardens. Yeah.

    Cory Miller: Yes. I, I see that so much. I mean, we go, if we could, I know I’m simplifying this, but turn on a setting within core to be in the network.

    We overnight could have the largest platform. Yeah. So it’s like, okay, if the end result is, for me, the question I always ask for our community is how do we continue to make a healthy, [00:31:00] vibrant, vibrant. WordPress business ecosystem. So hosting companies, product companies, cer, uh, agency climate work companies.

    And then I go, okay, I remembered the early days when WordPress was the tool. I mean, it was the best tool out there that you could do anything on the internet. Then slowly you started seeing Squarespace wigs, Weebly come in and start to take out this do-it-yourself market. And the question I’ve been asking because of my previous company and my past with WordPress is, how does WordPress stay relevant?

    Well, when it’s easy to go to, you can use a tool like Canva, then you can go to Facebook. They’ve got built-in audience, you know, and so I keep asking the question is, how do we stay relevant in the future as the best open source software on the planet? I believe , I’m very part impartial, but ibel, I, I love it.

    It’s why we’re all gravitate toward this. We’re gonna make an INCIRCLE round to make sure we stay [00:32:00] relevant. It’s like, It’s the closed garden model of things where if you, they’re gonna migrate off to these other platforms. You know, we need to stay relevant as the best tool, but we can add one, we can say content creation and then also network connection, you know, to each other.

    And that is pretty powerful for the future of WordPress. Exactly.

    Matthias Pfefferle: And it has a nice, what’s, um, name effect and, and the special words.

    Side effect. It’s a nice side effect that you also own your content. That that’s the big problem if, if you will be blocked or banned from Twitter, like many journalists were. Um, you lose everything you [00:33:00] po posted on Twitter and if you see, um, people there on Facebook since ages and from one day to the other, you will lost.

    You have lost everything. And, and that’s, um, yeah. And you go back to, I have everything on my server. Uh, and if some of the platforms, um, I’m, I’m connected with are going down, it, it doesn’t matter. I’m still on my WordPress instance. I have still all my images, my, my texts. I, I, I do not care anymore. So it’s, it’s really, I, I, I can be part of a social network and I can still be the, the owner of everything I ever created.

    Cory Miller: It’s really a rally conference open web, because we we’re, you’re trading the media WordPress, you got freedom [00:34:00] on this side, and you got control on this side. Yeah. Maybe a subset of, and it’s, to me, you know, we, I’ve slowly seen over 15 years or whatever, I’ve been in WordPress going this increasingly because they could iterate on software, come out with fresh and new ideas, not have, so WordPress is always backwards compatible and does such a good job at all that stuff.

    And so, but then you get these startups who can, fresh ideas, fresh mind, use WordPress as an inspiration, I think, and then come out new stuff. And this is, if we wanna shift power in control from closed gardens, we gotta embrace fed averse. Build tools for it. With WordPress being at the lead of the, the WordPress should be the leader of the Fed averse in my mind.

    Yeah,

    Matthias Pfefferle: true. Because it’s, at the moment, it’s nearly impossible to host your own, um, muscle instance. So to have the [00:35:00] complete freedom, it must be something as easy as WordPress. So

    Cory Miller: would WordPress need to create its own instance, ma, on instance? No,

    Matthias Pfefferle: I think Macon is, um, is also open source. So in the end, the idea is you could also host your own methadone instance and be the, the provider of your own master instance where only you are active.

    But it’s such a complicated. Platform that it’s nearly impossible, um, to run that on your own. And if you really want to be the owner of your own instance in the Fed Works, it has to be as easy as installing a WordPress. So I think to, to have a simple and easy to use, um, note in the whole verse, I think [00:36:00] it can be only WordPress.

    Yeah.

    Cory Miller: So it seems like, like part two that embrace verse part two is we need to make it more easy to create instances. Might be another piece. No, what

    Matthias Pfefferle: I wanted to say is it’s, it is easy and it is the easiest way to do that. And everything I, I’ve seen so far every other. Piece of software in the is really complicated to host.

    It’s not as easy as having a PhD p and I see my sequel. It’s, it’s way more complicated. You have to run different microservices and uh, uh, special, um, um, persistence toolings. Um, and with WordPress you are, as you said, it’s backwards, [00:37:00] comfortable. It’s comfortable with nearly every shared hosting environment, there is no easier way.

    So it’s, it’s kind of the perfect way to make such a thing. Yeah,

    Cory Miller: so, which is, see again, I just happened. I can’t. I go like, holy cow, this is a moment for WordPress. So gimme an example here for a second. Let’s take post status. Okay. I want to create, I want to have my community on our community On the Fedi verse, well, I’ll say Fedi verse, and you direct me.

    What would the steps be to do something like

    Matthias Pfefferle: that? Installing the activity, Poping plugin .

    Cory Miller: And then, and then,[00:38:00]

    Matthias Pfefferle: okay. Yeah. Um, the activity pop plugin will, um, it’s a very early stage, so, um, uh, the most requested feature is that you can follow the complete WordPress instance, the, the, the complete WordPress. So every, um, every post. Independent from the author should be shared at the moment. It’s not like that. It’s every author at the WordPress block will, um, get, uh, an identifier, it’s author login name at domain, and then you can follow the, the, the, the author on, um, a melon instance for example.

    And then you see every blog post that was written by this author on meron. That’s how it currently works.

    Cory Miller: So, so I’m post status [00:39:00] and I go act, go to post com, act activate activity

    Matthias Pfefferle: pub, then you will be cory@poststatus.com. Okay? That’s it.

    Cory Miller: And, and for our community to be on post status on the metaverse, same thing.

    So then if they’re on the Fed verse, I’m trying to understand, or they’re on MAs or they join an instance, how does the instance work in that case? Like what’s the next step for other people to connect in? Like if we said, Hey, post status, come on over. Does that make sense? How will we do that?

    I’m not

    Matthias Pfefferle: sure I understand you completely.

    Cory Miller: Um, yeah,

    like I go and, and this is why I’m probably not understanding the fed averse con concept and how [00:40:00] it all links in and I’m trying to use post as an example to help me understand it. Yeah. So I just activate, literally, I say I want post to be on the Fed averse. I just activate activity. And then what do I do?

    I’m sorry. I’m sorry. This is very basic. Yeah. Um,

    Matthias Pfefferle: then everyone on every platform, or let’s say on on methadone can follow your user on, um, post status. And everything you do on post status will be shared with the, this user in Okay. The fatty or on Macon.

    Cory Miller: That’s where it’s blowing my mind a bit is, is it’s not me creating an instance.[00:41:00]

    No. Or is it, it’s no. Me just saying I’m here.

    Matthias Pfefferle: Yeah. And that’s the difference, um, to the, the more common or mostly, um, Other Masteron plugins around there that every other plugin will only share the content using a MasterONE account. So with the other plugins, you have to, um, you have to create a MasterONE account.

    You have to install the plugin, then you have to say in the plugin, which is your Macon account, and then the WordPress will publish the, the, the, the content using this methadone user. But with the activity pop plugin, the user on this block is kind of the same as a Meone user. So you can directly follow the WordPress user on this block and everything you do in this block [00:42:00] mm-hmm.

    can be followed and commented and boosted by every master on user. So is

    Cory Miller: itar, is it like Avatar in the sense that. Isar like this system in some way where, you know, you put an email address in and then when I log in somewhere else, does that make sense? I can log in and it shows my avatar. Isn’t it like that?

    Not really.

    Matthias Pfefferle: It’s

    maybe,

    Cory Miller: and I’m sorry, I’m having to admit I don’t understand that fundamental level and it’ll click for me, but there’s a gap there. This is why I told you at time, I’m not technical. Can I? Yeah, you can share screen. Yeah. [00:43:00] In theory should be able to, here, I’ll make a cohost.

    Matthias Pfefferle: Do you see something? Um, maybe this because of.

    Cory Miller: Yeah, maybe send the,

    Matthias Pfefferle: no, I have, I have to change something. I have to give, um, system, yeah, zoom. Okay. I have to, uh, enable something. I have to restart. Is it, is it a problem if I restart, zoom? No, no, no. Cause of the Thank you. Yeah. No. Okay.[00:44:00]

    So, yes, I am back. Um, so my video, so yeah, now

    Cory Miller: it’s working.

    Thank you for doing this because No problem. I just, it’s, there’s something in my brain that’s just to get .

    Matthias Pfefferle: So,

    Cory Miller: um,

    Matthias Pfefferle: you see my screen? Yes. So, um, this is my blog and [00:45:00] that is my author page. And there you can see my followers, um, to, to follow my blog on the . I go to maam,

    and then I’m searching for my, um, username, my blog’s username. It’s my, my login at my, my Domain. I can also follow the, the URL completely. So I search for that.

    And then Masteron is finding my, my profile and I can follow the profile. And then if I click on that, I see my, my description. It’s the description from, from the block. It’s my, um, my profile [00:46:00] pi

    Antworten

  82. The WordPress ActivityPub plugin by Matthias Pfefferle has been updated. It now allows you to @mention ActivityPub users and they will be notified of the mention in your blogpost, through ActivityPub.
    This is useful. Yet, I’m holding out on using the plugin myself until three things are possible:
    Set the user name of the ActivityPub account: Now the username is the login name of the user doing the posting. I recognise using WP user names is a straightforward way of turning WP into an ActivityPub client, and prevents having to add addditional stuff to the database. As I use non-obvious user names for additional website security, having those exposed as ActivityPub users is undesirable however.
    Refuse follow requests: currently the plugin allows follows, and defaults to accepting all follows. As on my separate AP account I want to decide personally on follow requests.
    Determine flexibly which postings get shared through ActivityPub, and through which ActivityPub user account. The current set-up is that all postings get shared through ActivityPub. I’d rather be able to determine not just on a post by post basis what gets shared but also to have specific categories of postings to be shared through a specific account.
    I want to actively use the affordances ActivityPub allows on top of those WordPress as blogging tool provides. For me that is the ability to use the different activity types that AP can support, and to use dealing with followers and follows to selectively disclose content to different groups of people.
    My current usecase for this is to have a separate AP account that shares my travel plans (posted in an unlisted category on my site) with accepted followers. The first part requires selectively sharing a category of postings, the second part doing so to a group of accepted followers on an AP account that is meant for just this type of postings and not my general AP account.
    The plugin will develop in this direction, but is not there yet. I am slowly going through the code of the plugin myself to understand its architecture and choices. Perhaps it will give me an idea either on how to build on its core to create the functionality locally I want for myself, or maybe (though my coding skills are likely not adequate for it) add to the plugin itself.

    Antworten

  84. Automattic has acquired the ActivityPub plugin for WordPress from German developer Matthias Pfefferle, who will be joining the company to continue improving support for federated platforms. Pfefferle, who is also the author of the Webmention plugin, said his new role is to see how Automattic’s products can benefit from open protocols like ActivityPub.
    …
    Sarah Gooding (WPTavern)

    This is so exciting I might burst. Want to know why?
    Matt Mullenweg‘s commitment to ActivityPub makes me happy. WordPress made Pingback and Trackback take off, back in the day, and I believe that – in the same way – Automattic can help make ActivityPub more accessible and mainstream too.
    Matthias Pfefferle is both an IndieWeb and an ActivityPub star; I use (and I’ve extented upon) a lot of code he’s written every day and I sponsor him on Github! The chance that we get to work directly together is pretty slim, but it’s a chance right?
    Susan A. Kitchens expressed concern that this could increase the level of ActivityPub spam out there (which right now is very low). I worry about that too. But I’m still optimistic that we can make something awesome off the back of this acquisition and keep the interpersonal Web federated, the way it ought to be.

    Antworten

  85. On Tuesday, Matthias Pfefferle and I released Webmention for WordPress version 5. We started this project at the start of the pandemic…and it took a bit longer than we expected. It merges in the old Semantic Linkbacks plugin, rewrites large sections of code, and creates a better experience.
    However, we have already received some feedback and are working on incorporating it into version 5.1…which won’t take 3 years to release. The goal is to fix some reported bugs, address some of the feedback, and more.
    So, please, if you haven’t upgraded…do so, and give us feedback via Github.

    Antworten

  93. In der weiten Welt des Internets gibt es unzählige Möglichkeiten, Inhalte zu teilen. Von komplexen Sharing-Tools bis hin zu integrierten Funktionen in verschiedenen sozialen Netzwerken – die Auswahl ist schier endlos. Doch manchmal sehnt man sich nach etwas Einfachem, nach einer simplen Möglichkeit, Inhalte mit anderen zu teilen, ohne dabei in einem Meer von Optionen […]

    Antworten

  94. Ein Kommentar von Eddy hat mich zum Nachdenken und letztendlich dazu bewogen, diesen Beitrag zu schreiben. In einer Welt, in der Künstliche Intelligenz (KI) immer präsenter wird, sind viele Aspekte unseres Lebens von ihrer unbestreitbaren Effizienz und ihrem Potenzial fasziniert. Doch während wir uns von automatisierten Prozessen und Algorithmen umgeben lassen, stellt sich die Frage: […]

    Antworten

  103. WodPress 6 als Buch – (zu?) viele SeitenVeröffentlicht: 16. Februar 2025 von Matze – Kommentar hinterlassen Getrieben von einer etwas verrückten, aber nachvollziehbaren Idee, gibt…

    Antworten

  104. Seit einiger Zeit denke ich darüber nach, wie KrautPress sich ein wenig weiterentwickeln kann. Im Jahr 2016 habe ich ein eigenwilliges WordPress-Magazin namens KrautPress gestartet.…

    Antworten

Erwähnungen

Lesezeichen

Likes

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert