f6
Dries
f68c1fc5bf7f5125f992ce30ed32881fcc749777c7a9de89cc601326029df9f9
Founder and Project Lead of Drupal

Exciting news from the Mautic Community and Acquia today: Acquia is  supporting Mautic's transition into a fully autonomous Open Source project. Having been involved with Mautic from its early days, I'm thrilled to see where this takes Mautic next. Congratulations to the Mautic community and Ruth Cheesley! For more information, I invite you to read my blog post: https://dri.es/mautic-to-become-an-independent-open-source-project.  #opensource

I wrote an article for opensource.com about how Drupal helps preserve and promote the Open Web. Check it out below! https://opensource.com/article/23/4/preserving-open-web-drupal #drupal #openweb

Blog post: The evolution of Drupal's composability: from the command line to the browser https://dri.es/the-evolution-of-drupal-composability-from-the-command-line-to-the-browser <- How Automatic Updates and Project Browser will empower ambitious site builders with a no-code composable platform and modern development practices.

Replying to Avatar Bruno MASSA

Just read your latest post (https://dri.es/why-content-management-systems-can-outperform-static-site-generators)!! Even if this thread was not the catalyst, I'm happy by the discussion (which, btw, I've started as more like a curiosity thing than anything else. I totally understand the dogfood initiative).

It's late here but I later I will bring back some points:

1* the importance of clicking "publish" and getting the results. IMHO it is only useful for news sites and such

2* the benchmark table. I think it was a deliberated list of competitors that do not properly use CND/cache/Cloudflare or proper use of 3rd party libraries.

anyway, I totally can see the benefit of the workflow. 1000x better, I can attest to it!

PS: I would NEVER worry about `https://dri.es/admin` if eventually a zero-day PHP bug eventually appears since a static site is essentially stateless.

For the benchmarks, I just went with the most popular SSGs. Happy to add others to the list! I’m not sure which ones use a CDN. Even if they use a CDN, my site is likely to be faster still.

I have a Nikon and a Leica, and pick my Leica 9 out of 10 times. 📷

While static sites can offer better performance and security in theory, they don't always do in practice.

My Drupal-powered site, https://dri.es/, is fast and secure. In fact, it is 3x faster than https://gohugo.io/ and https://jekyllrb.com/ -- the official websites of two leading static site generators.

The speed and performance of a website depends more on the quality of the generated HTML, CSS, and JavaScript code than the underlying technology used (e.g. CMS vs SSG).

Drupal allows you to use various input formats, such as Markdown. So, if you prefer using Markdown, you can easily use it in Drupal.

Drupal has a module called Tome (https://youtu.be/uqmq5FBP_T0) that enables it to generate static sites. Moreover, Drupal is frequently used as the content repository/backend for Gastby (https://www.drupal.org/project/gatsby), NextJS sites (https://next-drupal.org/) and others. Check it out!

Thank you for being a long-term subscriber. 🙏🏼. This probably deserves a longer answer that could make for a good blog post, but in short: Drupal’s publishing workflow is a lot easier and faster than those of SSGs. I don’t see why they are so much better …

I’ll investigate that browser extension. I appreciate it, anty! I might report back after I learned more.

One thing that has raised a red flag for me about #Nostr is the fact that several applications require users to provide their private key. Needless to say, this is not in line with security best practices, and could put a users data at risk. Am I wrong? Thoughts on that?

It's very interesting that both habla.news and blogstack.io use the Nostr protocol as its foundation for a long-form blogging platform.

In over-simplified terms, the Nostr protocol allows habla.news and blogstack.io to share a content database. The Nostr relays essentially provide a decentralized "content hub", and the Nostr protocol defines the content type schemas.

This means habla.news, blogstack.io and others can display the same content, but with a distinct appearance and user experience.

A first use case is a blog for one person. Just show the content from one Nostr user on a website in the traditional blog format. What is interesting is that Nostr automatically provides such blog a commenting system and social media integration.

A second use case is the equivalent of an RSS feed aggregator. It gathers posts from different bloggers on specific topics/hashtags and puts them together on one page or in one new RSS feed.

At a very large scale, that would look a lot like  Medium (multi-user blog), except it wouldn't be owned or controlled by a single organizations, and with built-in micro-payments that actually benefit the content creators.

@verbiricha, @MAHcodes, @fiatjaf, did I get that right? Am I missing something? And in your mind, what are the end user benefits of this approach?

I just updated my personal website to Drupal 10.0.4 (https://www.drupal.org/project/drupal/releases/10.0.4), and it was a breeze!  Super grateful for the care and effort that so many people and organizations put into maintaining Drupal. It's impressive.  Stay amazing, #Drupal! 💙

@jack Is there any connection between Nostr and Bluesky’s AT Protocol?

I’ll check it out, @mates!

I completely agree, but Nostr is still in its early stages.

Although I believe the Nostr protocol is superior to ActivityPub (as noted in https://dri.es/nostr-love-at-first-sight), protocol superiority is not enough for Nostr to win.

In order for Nostr to become a viable alternative to Twitter and Mastodon, the overall end user experience needs to improve dramatically.

And the ultimate user experience for Nostr is this: engaging, thought-provocing, cutting-edge conversations across a diverse range of interesting topics.

Currently, these types of conversations have been infrequent on Nostr.

To improve the overall end-user experience, two things are necessary: (1) we need significant improvements to Nostr clients to make them more polished and user-friendly, and (2) we need to attract more interesting people that can bring along a more diverse user base and community.

It is impressive to witness the rapid progress that @jb55 is making with the Damus client. I'd shift more investment to Damus. Specifically, I'd love to see @jb55 surrounded with more UX testers and UX researchers. Clients like Damus are the gateway to Nostr.

Over the past few years, a significant number of leaders in web development and the Indieweb community have migrated to Mastodon. This shift was largely driven by the alignment of their values with the open and decentralized nature of Mastodon. As a result, Mastodon has become the primary hub for the most engaging web development conversations today.

In my opinion, the web development community would be an excellent early adopter for Nostr. The same reasons that prompted their adoption of Mastodon could apply to Nostr as well.

Furthermore, the web development community played a key role in Twitter's early success, as @jack may recall. I personally became a Twitter user in 2007, when the platform was less than a year old, after a conversation with Ev Williams and Larry Page.

The web development community could be a valuable target audience for Nostr. Not only are they technically savvy and able to navigate through difficult-ish user interfaces, they can also brings some more diverse and engaging conversations. Additionally, web developers have the ability to create integrations that can enhance the reach of Nostr. Since I blogged about Nostr on my site, two Nostr integrations have been created for Drupal already.

Furthermore, the web development community has a strong presence online, which can lead to increased visibility and promotion of Nostr through their blog posts, website links, and social media. Overall, targeting the web development community seems to be an opportunity for Nostr.

I just had a quick look at the code. Amazing how straightforward it is. As you are one of few people who implemented both an ActivityPub and Nostr client, it might worth writing up your thoughts.