Scary

WRITTEN_BY David REVOY - - 116 comments
I was just thinking about how the bluebird social network was rebranded, and how it now feels legitimate to give it a place in the museum of dead social networks... [Source file and high resolution here](https://www.peppercarrot.com/en/viewer/misc__2023-07-30_Scary_by-David-Revoy.html)

Fighting for the open web.

WRITTEN_BY David REVOY - - 153 comments
A picture I had in mind about the topic of [Web Environment Integrity](https://en.wikipedia.org/wiki/Web_Environment_Integrity). [Source here](https://www.peppercarrot.com/en/viewer/misc__2023-07-27_Fighting-For-The-Open-Web_by-David-Revoy.html)

I may have found an alternative solution to my blog's comment system.

WRITTEN_BY David REVOY - - 89 comments
Artwork source: ["Mastodon mascot as postman"](https://www.peppercarrot.com/en/viewer/misc__2023-07-26_Mastodon-mascot-as-postman_by-David-Revoy.html) by David Revoy, based on the mascot of [joinmastodon.org](https://joinmastodon.org/) − CC-BY 4.0

Two days ago [I decided to give up on my blog's commenting system](https://www.davidrevoy.com/article980/ive-decided-to-give-up-on-my-blogs-commenting-system). I wrote about a solution that I had tried but abandoned along the way: synchronizing comments from my Mastodon account. I abandoned it because I thought that my instance automatically flushed all posts older than 30 days, and it was too ephemeral to be a long-term solution. But here is an update: I was wrong. The instance doesn't auto delete the message and an admin on my Mastodon instance contacted me to tell me the reason: they had an accident that resulted in the loss of comments older than that date. And he assured me that they don't plan to do it again. So, in light of this new element, I've decided to give my solution another try, even if it only affects the last five articles published on my blog after 25 June 2023. The solution works (you can see it in the footer of my recent posts) and I'm happy to have an alternative commenting system back here. As many of you understood from my previous post, removing them was really emotionally difficult for me. I'll share my code and method if you want to get something similar on your blog: ## Demo page [Demo of the Php code (public mode).](https://www.peppercarrot.com/extras/html/2023_Mastodon-Php-Comments/) ## The Php code A single file that requires pretty common php libraries (Json, Curl). https://framagit.org/Deevad/mastocomblog/-/blob/main/index.php , (MIT License). **Git repository:** https://framagit.org/Deevad/mastocomblog **Changelog:** 2023-07-29: - Move from the Snippet on Invent.kde.org to a Git repository on Framagit.org. - Privacy: Hide DM(direct) and Followers Only(private) messages. - Security: prevent harder code injections. - Support more attachement type. - Security: prevent page flooding with high character limit. - Display account address for readability of quoted discussions. - Decorate :custom_emojis: everywhere and (status) in display name. [![](data/images/blog/2023/2023-07-26_php-code-of-connecting-to-mastodon-api.png)](https://framagit.org/Deevad/mastocomblog) _a screenshot of a sample of the (v1alpha) code_ ## Setup The script needs to be in a directory with write permissions to write the cached json files. You can customize the path to this directory with `$cache_target` at the start of the CACHE section in the code. `$mastodon_post_id` The 18 numbers of your Mastodon post. You'll find this number on the URL of your post on Mastodon. `$mastodon_server` Your Mastodon instance URL. `$mastodon_account` Your account. **Token and authentification:** `$your_mastodon_access_token` (optional) This is a token you can get in your Mastodon account by going to Settings → Development and registering your site here. Without this token, the API will run in "public mode" and will limit the number of messages you can list (~60 for my instance). Instances of Mastodon might have no public mode enabled. In this case the authentication token method might be mandatory to connect to your messages. **Cache:** I wrote a caching system because with more than 13K daily visitors to my blog (which sometimes peaks at over 300K), I did not want to be a problem for the bandwidth of my Mastodon instance. The default in the code is set to 24h. You can extend it with something more complex if your blog system gives you a date. I use 1h for this week's blog post, then 4h for the month and 12h after that. Just be kind to the bandwidth of your Mastodon instance and donate to them to help cover the server costs. ## Inspiration The inspiration for this system came from Carl Schwan's blog post ["Adding comments to your static blog with Mastodon"](https://carlschwan.eu/2020/12/29/adding-comments-to-your-static-blog-with-mastodon/). If you are looking for a Javascript client-side method, check out his post. I also found a real-life example of authentication by token to be very useful, found on ["MastodonBotPHP"](https://github.com/Eleirbag89/MastodonBotPHP/tree/master) by Grimstack aka Eleirbag89 on Github. Also very useful is [the official Mastodon API documentation](https://docs.joinmastodon.org/entities/Token/), well done to the contributors who maintain this kind of detailed documentation. Bonus artwork: because I'm happy, here's a happy [Mastodon mascot as a postman](https://www.peppercarrot.com/en/viewer/misc__2023-07-26_Mastodon-mascot-as-postman_by-David-Revoy.html) that I painted this morning.

I've decided to give up on my blog's commenting system

WRITTEN_BY David REVOY - - 119 comments
I have had this blog for almost 20 years, long before social media like Youtube, Facebook and Twitter existed. For a long time, my comment system was the only way I could get feedback on what I was painting and writing. And over the years you have posted 13,007 messages on 978 posts on my blog. Thank you very much! Unfortunately, the amount of spam, attacks and hateful comments has also increased. For years I protected the humble commenting system of my [PluXML](https://github.com/pluxml/PluXml) blog system with honeypots, home-made captchas and services like Akismet. I also spent a lot of time moderating, but it started to ruin the little time I had offline during holidays, conferences and book signings. My blog comment system was open to everyone, without login, and it soon became a place loved by haters. It also became a secondary destination for all the profiles I blocked on social media. 2023 was the first year I had to make a report to the police for the many death threats I received. But I persevered: and before I gave up completely, I looked for solutions and spent more time coding them. I spent days connecting my blog to my Mastodon posts using the API and coding better protection. But then I realised that my Mastodon instance was flushing all comments older than a month [1]... Also, all my "better protections" were easy to bypass for anyone who knew a bit about VPN and the Tor browser. So I've finally come to the point where I've decided to give up on my blog's commenting system and shut it down. And it is a very hard pill to swallow. That doesn't mean I don't need your feedback anymore... I do! It is simply impossible in 2023 and with the number of visitors I now have to host and manage a comment system myself. I'm sad about that. I spent most of last week archiving all your comments, and you'll find a link to view them in the footer of my old articles. I updated my CMS, the plugins, I updated my custom code, I updated the server to a new distro and newer libraries. My blog is ready for the next few years and I'm going to keep it up. New articles, new artworks, new brushes, new tutorials, new episodes of Pepper&Carrot: I'm sure we'll find new places to discuss about it. I'm also going to accept the ephemeral nature of social media. I've seen so many platforms rise and die, with thousands of comments disappearing each time... I hate this data loss and I would like to archive all of our interactions somewhere. Unfortunately, on my little piece of the internet, I can no longer create this ideal. I'll miss all the feedback just below the installation guides, which were useful for troubleshooting other configurations. I'll miss the pages of reactions to the latest episode of Pepper&Carrot. I'll miss the little words of wisdom from the regular users of the comments section. Thanks again for all of that. Update:
[1] This is not a policy of my Mastodon instance, just a bug that happened on the server and happened to be 30 days ago. That's why I assumed the server had a 30-day flush policy. It doesn't. This made me want to take another look at this solution in the next blog-post.

🌱 My Neighbor Mastodon 3

WRITTEN_BY David REVOY - - 44 comments
A new piece of artwork to celebrate reaching 25,000 followers on [my Mastodon account](https://framapiaf.org/@davidrevoy). The scene is a parody from a still picture of the movie "My Neighbor Totoro" by Studio Ghibli. ["Source and full license here.](https://www.peppercarrot.com/en/viewer/misc__2023-07-16_My-Neighboor-Mastodon_25K_by-David-Revoy.html)

Pepper & Carrot Gamejam 2023 Recap - 10 games in less than 5 minutes.

WRITTEN_BY David REVOY - - 5 comments
Thanks again to @brettmakesgames@mastodon.gamedev.place for organising it, and (many) thanks to all the participants. 😻 [youtube]1AsvqyofhWA[/youtube] - Ptb: https://peertube.touhoppai.moe/w/fo4Udw77tSYaQQhXrpP7Y3 - Ytb: https://youtu.be/1AsvqyofhWA **The video game are here:** **https://itch.io/jam/pepper-carrot-jam/entries**