This banned Pride march is looking great 🙂!
🏳️🌈 🏳️⚧️
This banned Pride march is looking great 🙂!
🏳️🌈 🏳️⚧️
A few days ago, @florianziegler suggested that all of us running blogs with RSS feeds make a small change:
Please add your email address to your RSS feed.
Add Your Email Address to Your RSS Feed
This email address can be used by RSS feed readers to display an Email button next to each feed entry, so folks can reply to the post via email instead of visiting the post on your site to leave a comment.
That seems like a good idea. I found that there was no WordPress plugin that allowed that out of the box, so I built my own. If you’re a blogger and use WordPress, give it a try!
https://wordpress.org/plugins/rss-reply-via-email/
Next step will be for more feed readers to support that issue. I consequently opened an issue for my feed reader of choice, NetNewsWire, to support this, and another for the Android app I use, FocusReader. If you use a different feed reader, don’t hesitate to contact them about it!
You mentioning custom protocol handlers reminded me of FEP-07d7 – A Custom URL Scheme and Web-Based Protocol Handlers for Linking to ActivityPub Resources. It feels very related to your FEP-3b86 somehow.
I like your idea of not waiting for browsers though.
@manualdousuario @pfefferle If the default WordPress experience doesn’t fit your needs, and if you need the classic editor out of the box without having to make any changes, ClassicPress may be what you need, not WordPress. I think that’s another proof of the flexibility of WordPress I mention in this post, and the power of Open Source in general. If you need something, chances are someone already built it, or you can build it yourself on top of existing open source tools and solutions!
Earlier today, @davew published a blog post titled WordPress and me. He talked about WordLand, his focused and fast editor for writers and bloggers. Through developing the editor, he’s discovered WordPress again.
WordPress as the OS of the open social webI think WordPress has all that’s needed to be the OS of the open social web. We needed it and it’s always been there, and I saw something that I want to show everyone else, that the web can grow from here, we should build on everything that the WordPress community has created. It’s a lot stronger foundation that the other candidates for the basic needs of the open social web, imho.
I’ve been following Dave’s work with WordLand for the past few months, and it’s been really nice and encouraging to see him work on a product that aligns with my values. And now, Dave will get to present his tool and his ideas to others in the WordPress community! He will be talking at WordCamp Canada in October.
It should come as no surprise that someone so involved with some of the key concepts of the Open Web, like RSS, values ideals of openness and giving writers control over their content. WordLand’s approach to « what you see is what you get » is something that aligns so well with WordPress’ own ideals. It clashes with walled gardens like Twitter or Bluesky where you’re limited in length, format, content, and where you ultimately do not own your writing. It’s super motivating and empowering when someone newer to the WordPress ecosystem recognizes those shared values and the power of the platform.
Rediscovering WordPressIn his post, Dave talked about his journey of rediscovering WordPress through a new lens. The WordPress.com REST API, its endpoints and its authentication layer, gave him the tools to build the editor he needed, while still benefiting from everything the WordPress community has created in the past 22 years.
This is also what we had in mind when Automattic released Calypso 10 years ago:
Calypso is…
Calypso and its underlying API paved the way for the first REST API endpoints that made it to WordPress itself a year later. That API then became a cornerstone of the Gutenberg project:
WordPress has always been about the user experience, and that needs to continue to evolve under newer demands. Gutenberg is an attempt at fundamentally addressing those needs, based on the idea of content blocks. It’s an attempt to improve how users interact with their content in a fundamentally visual way, while at the same time giving developers the tools to create more fulfilling experiences for the people they are helping.
Matías Ventura — Gutenberg, or the Ship of Theseus
On a more technical note, the folks more familiar with WordPress will wonder why WordLand uses the WordPress.com REST API, and not the core WordPress REST API.
Dave chose to use the WordPress.com API for WordLand — and that makes perfect sense for the goals of the project. It provides built-in authentication and opinionated endpoints that would otherwise need to be built on top of the core REST API, and would need to be shipped to every site that wants to use the WordLand editor. That’s simply not what WordLand was designed to do.
Perhaps more importantly, the WordPress.com REST API is just one of the many ways to interact with WordPress. That’s the beauty of WordPress: it’s open and flexible, allowing different tools and solutions to thrive. In this case, it’s nice to see how WordLand, WordPress, and WordPress.com came together to empower writers, each bringing their own strengths to the table. It’s a great example of how open tools and platforms can work hand-in-hand to create something truly special.
It’s always exciting to see new tools emerge from old foundations — and even more so when they help bring us closer to the open web we want to build. Funny enough, the WordPress.com REST API still relies on XML-RPC — a technology built by Dave 27 years ago 🙂
Go write something!If you haven’t tried WordLand yet, go give it a try! All you need is a WordPress site, either hosted on WordPress.com or running the Jetpack plugin.
Lemmy c’est génial, mais j’ai peur que les premiers pas soient encore compliqués à expliquer au plus grand nombre. Comment vous gérez cette partie « onboarding » avec les nouvelles communautés qui se créent, pour que les gens comprennent ce qu’est un compte sur le Fediverse, où aller pour s’en créer un, comment choisir son instance, comment publier dans la communauté… Ça donne toujours l’impression de faire beaucoup de questions, et donc un vrai frein pour les gens qui veulent juste poser une question, et qui sont donc déjà dans une position d’inconfort.
@pfefferle I only have one so far. How do you ensure that people find those pages?
@tchambers@indieweb.social @voxpelli@mastodon.social Yeah, that makes sense, thanks for expanding on that!
It would be a workaround to get publication type displayed alongside the publication.
ActivityPub already comes with object types: « Note » for status updates, « Question », « Page », « Image », « Audio », « Video », « Event », and « Article » which is a good descriptor for long-form content I think.
I know some Fediverse solutions (like WordPress) allow you to set a different object type depending on the content.
Some Fediverse clients also try to display the content differently based on the object type.
I am assuming others have made that suggestion before, but maybe it would be interesting for the main Fediverse clients like the Mastodon UI / app to clearly display the object type next to the content.
This is probably even more important for object types that are close to each other. If you see an « Image » post on the Fediverse you immediately know what it is. If you see a « Note » or an « Article » however, only the length really differentiates them (if you’re lucky, since some Fediverse clients like Mastodon are built for Notes and do not even want to display full posts).
All this to say, I am all for adding an obvious sign next to long-form content to indicate that 🙂 . Until Fediverse clients do it, a hashtag can work! I’ll try to remember to do it for my next posts (but only the long ones, « Notes » don’t need to be tagged as #Fediblog!)
@pfefferle We’ve talked about adding the hashtag to federated WordPress posts ; what if the option only added it to « Article » publication types, to avoid tagging short updates or shared pictures as « Fediblog »?
@voxpelli@mastodon.social @voxpelli @tchambers I think it would quickly become quite noisy. Imagine if I added the hashtag to each one of my replies in this thread, or if one added the hashtag in a reply to a thread talking about something completely unrelated?
Similarly, should all GoToSocial users add a specific hashtag to all their posts?
I think the platform used to communicate should not matter, the content is what’s really important.
@voxpelli @tchambers Since both WordPress and Ghost sites support RSS out of the box, I don’t think you need an indicator. 🙂
Now, should we add the tag to long-form content only, or to any posts published via Ghost or WordPress (like this one)?
Quick tip if you use the ActivityPub plugin on your WordPress site, and if you write in multiple languages on your site. Use the activitypub_post_locale filter to make sure your posts on the Fediverse are set to the locale matching the post on your site.
/** * Set a post's language in its ActivityPub representation * based on post tags. * The post tags must match an array of language codes you use on your site (in my example, English, Hungarian, and French). * When no tags are found, the post's language uses the default (the blog's language). * * @param string $lang The locale of the post. * @param int $post_id The post ID. * @param WP_Post $post The post object. * * @return string The filtered locale of the post. */function jeherve_custom_ap_language( $lang, $post_id, $post ) {// Get the post's hashtags.$post_tags = get_the_tags( $post_id );if ( ! empty( $post_tags ) ) {// Is there a "en, "hu", or "fr" tag?foreach ( $post_tags as $tag ) {if ( in_array( $tag->slug, array( 'en', 'fr', 'hu' ), true ) ) {$lang = $tag->slug;break;}}}return $lang;}add_filter( 'activitypub_post_locale', 'jeherve_custom_ap_language', 10, 3 );This way, I can add the #en tag to this post, and ensure the post will be shown as an English-language post for folks on the Fediverse.
This is important for folks who filter posts per language on the Fediverse, or who use translation tools to automatically translate posts in foreign languages.
For the past couple of years, I’ve been talking more and more about ActivityPub, Fediverse, Mastodon, and lots of terms that may not always be familiar to everyone. If you were to start today, if you wanted to learn more about ActivityPub, the Fediverse, Webfinger, and how it all works, where would you start?
Following a discussion with @jackmcconnell, here are some the ressources I would recommend today:
Do you have any other recommendations? Please reply to this post to let me know 🙂
Do you know the Fediverse logo?
It’s a nice logo. It’s colorful, and it’s a good representation of the different nodes in the Fediverse. That said, its many colors and many lines also mean it doesn’t necessarily work well everywhere. Sometimes you need a small, monochrome logo. This logo’s monochrome version doesn’t work as well.
Enter, the asterism: ⁂ It’s simple, it’s a unicode symbol so available on all keyboards and scalable. It can be colored or not. I think it could make for a nice representation of the Fediverse!
Check the proposal here: fediverse symbol ⁂
Kudos to @FediverseSymbol for making this happen!
WordPress, TV Series, music, kids, and board games. I think that's probably the best way to define me in a few words. 🙂 I work at Automattic on the Jetpack plugin and its infrastructure. You'll consequently find me talking about WordPress things a lot, but also about all things open source in general. I am French and live in Brittany, so I will post in French from time to time, as well as share pictures of our beautiful Brittany. 🙂
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.