Skip to content
  • 0 Votes
    1 Posts
    0 Views
    fabio@manganiello.euF
    I have actually found the perfect use-case for #Madblog and the new federated visibility features today. I've got an upcoming gig with a friend who also happens to have a Mastodon handle. Sharing setlists is a notorious nightmare across musicians. Sending Excel or Word documents back and forth over email or WhatsApp, and gradually lose track of the changes, is still the most common way. Until recently I used to share spreadsheets on my Nextcloud instance instead, but that also proved to be cumbersome (creating a public shared URL, asking your friends to install the CollaboraOffice app on their phones because the default rendering of spreadsheets in the Webview is suboptimal, deal with friends who would accidentally wipe rows or cells without having a proper versioning system...). Today I got a better idea: what if the setlist is just a Markdown post on my blog, set with visibility: direct, and where I tag my fellow musician(s) on the parts where I need their input? It won't clutter my blog index because it's neither public nor unlisted. My friends over Mastodon get a notification when I save the file where they're mentioned, and they can opt whether to see the setlist directly in their Mastodon client or on the Madblog URL. If they have any comments, they just drop them as direct replies on their Mastodon thread, and they're also rendered as comments under the Madblog page. The process is documented. Comments persisted. Changes versioned over git. The document can be shared as a simple URL. Songs have all the space that they want on a Markdown page (you can add chords, lyrics, notes, without cramming them into an Excel row). Everyone gets notified on their favourite app when there are some changes. And I get notified when they have comments. I don't think I'm going back to spreadsheets.
  • 0 Votes
    1 Posts
    0 Views
    liaizon@social.wake.stL
    @weekinfediverse there have been a bunch of updates to @fabio's #MadBlog this week too
  • 0 Votes
    1 Posts
    2 Views
    fabio@manganiello.euF
    Now supporting federated replies and likes from #Markdown files too #Madblog https://blog.fabiomanganiello.com/article/Federated-replies-and-reactions-in-Madblog
  • 0 Votes
    1 Posts
    2 Views
    fabio@manganiello.blogF
    Federated Replies and Reactions in Madblog Engage with the Web from plain text files Madblog is founded on a simple principle: a blog is just a collection of #markdown files in a folder. No databases, no logins, no client-side bloat — just files. The recently implemented support for both Webmentions and ActivityPub add an extra appeal to this approach: now those text files can federate, they can send mentions to Wordpress blogs or Mastodon accounts, and you can visualize mentions, comments and reactions from other corners of the Web directly under your articles. But after receiving in the past few days a bunch of reactions on my blog that I couldn't interact with, which forced me to fall back on my standard Fediverse account to send replies and likes, I've decided to take the "everything is a file" philosophy a step further. Now from #madblog you can also reply to comments and react to posts across the Fediverse - all from plain text files in your content folder. Replying to Comments When someone comments on your article from Mastodon or another ActivityPub-compatible services, their message appears on your blog. Now you can also respond directly from your blog. Or you can reply to any other post on the Fediverse or mention anyone, without those posts cluttering your blog's front page (I've learned to avoid this fatal design mistake made by e.g. Medium). How it works Create a Markdown file under replies/<article-slug>/: [//]: # (reply-to: https://mastodon.social/@alice/123456789) Thanks for the kind words, Alice! I'm glad the tutorial helped. @alice@mastodon.social Save the file, and Madblog automatically: Publishes your reply to the Fediverse as a threaded response Notifies Alice on her Mastodon instance Displays the reply on your blog, nested under her original comment Your reply lives in your content folder. Just like with your articles, you can version replies and reactions on git, synchronize them over SyncThing or Nextcloud Notes, or run some analysis scripts on them that would just operate on text files. Replying to replies Conversations can go as deep as you want. Reply to a reply by pointing reply-to at the previous message's URL: [//]: # (reply-to: https://mastodon.social/@alice/123456790) Great question! I'll write a follow-up post about that. @alice@mastodon.social The threading is preserved both on your blog and across the Fediverse. [Example of a nested thread rendered on Madblog] (I hope that @julian@fietkau.social and @liaizon@social.wake.st won't mind for using a screenshot from their conversation on my blog ) Remember to mention your mentions An important implementation note: if you're replying to someone else's ActivityPub post, it's important that you also mention them in the reply, otherwise your reply will be rendered under their comment but they may not be notified. Usually you don't have to worry about this on Mastodon because the UI will automatically pre-fill the participating accounts in a sub-thread when you hit Reply. But this is something to keep in mind when your posts are just text files. Your replies are articles in their own right Even though anything under replies/ won't appear on your blog's home page, it doesn't mean that it must be rendered just like a humble rectangle in a crowded comments section. By clicking View full reply you get redirected to a separate page where the reply is rendered as a blog article, and its comments sections consists in the sub-tree of the reactions that spawned from that specific reply. [Example of a Madblog reply rendered as a blog article, with its own sub-thread of reactions] Liking Posts Sometimes a reply is too much — you just want to show appreciation. Now you can "like" any post on the Fediverse with a simple metadata header. Standalone likes Create a file under replies/ with just a like-of header: [//]: # (like-of: https://mastodon.social/@bob/987654321) This publishes a Like activity to the Fediverse. Bob sees the notification, and your blog records the interaction. Like and comment Want to like and say something? Combine both: [//]: # (like-of: https://mastodon.social/@bob/987654321) [//]: # (reply-to: https://mastodon.social/@bob/987654321) This is such a great point! Bookmarking for later. @bob@mastodon.social Bob gets both the like and your reply as a threaded response. Unlisted Posts Not everything needs to appear on your blog's front page. Files under replies/ without reply-to and like-of headers become "unlisted" posts — they're published to the Fediverse but don't clutter your blog index. Perfect for quick thoughts, threads, or conversations that don't warrant a full article. [//]: # (title: Thoughts of the day) Quick thought: I've been experimenting with writing all my Fediverse posts as Markdown files. It's oddly satisfying to `git log` my social media history. Guestbook Replies Your blog's guestbook works the same way. Reply to guestbook entries by placing files under replies/_guestbook/: [//]: # (reply-to: https://someone.blog/mention/123) @alice@example.com welcome! Thanks for stopping by. Editing and Deleting Changed your mind? Edit the file and an Update activity is sent. Delete the file and your reply is removed from the Fediverse too. Accidentally liked something? Remove the like-of line (or delete the file) and an Undo Like is published. Your content, your rules. Getting Started Enable ActivityPub in your config.yaml: link: https://blog.example.com enable_activitypub: true activitypub_username: blog # Only specify these if you want your ActivityPub domain to be different from your blog domain # activitypub_link: https://example.com # activitypub_domain: example.com Install Madblog From pip: pip install madblog From Docker: docker pull quay.io/blacklight/madblog Run Madblog from your Markdown folder (it is recommended that your articles are stored under <data-dir>/markdown From a pip installation: madblog /path/to/data From Docker: docker run -it \ -p 8000:8000 \ -v "/path/to/config.yaml:/etc/madblog/config.yaml" \ -v "/path/to/data:/data" \ quay.io/blacklight/madblog Any text file you create under markdown/ becomes a blog article. Any text file you create under replies/ becomes an unlisted post, a reply or a like reaction. Check the README for detailed configuration options. Happy blogging!
  • 0 Votes
    7 Posts
    0 Views
    fabio@manganiello.euF
    @elettrona@poliversity.it @informapirata@mastodon.uno @fediverso@feddit.it Madblog esiste gia' da un po' di anni, ma finora l'ho usato perlopiu' a titolo personale per gestire i miei blog. Con il supporto per la federazione ho deciso di annunciare il progetto un po' piu' pubblicamente.
  • 0 Votes
    44 Posts
    3 Views
    liaizon@social.wake.stL
    @fabio this is getting annoying, every time you save your site you are sending a new version of all your likes so this thread gets bumped to the top of my feed