<?xml version="1.0" encoding="UTF-8"?><feed xmlns="http://www.w3.org/2005/Atom"><id>https://vic.demuzere.be/articles/tags/meta/atom.xml</id><title>Vic Demuzere - Meta</title><link href="https://vic.demuzere.be/articles/tags/meta/atom.xml" rel="self" type="application/atom+xml" /><link href="https://vic.demuzere.be/articles/tags/meta/" rel="alternate" type="text/html" /><updated>2026-10-11T12:56:10+00:00</updated><author><name>Vic Demuzere</name></author><entry><id>https://vic.demuzere.be/articles/let-there-be-comments/</id><title>Let there be comments!</title><link href="https://vic.demuzere.be/articles/let-there-be-comments/" rel="alternate" /><updated>2026-10-11T12:56:10+00:00</updated><published>2026-10-11T12:56:10+00:00</published><content type="html"><![CDATA[<p>There has been a lot of talk about website comments on <a href="https://bubbles.town" title="Bubbles">Bubbles</a>.
I think it started with <a href="https://forkingmad.blog/i-want-to-comment-on-your-blog-post/" title="I want to comment on your blog post">a post by Forking Mad</a>, and a bunch of replies are linked at the bottom of that page.</p>
<p>My blog posts have had a &quot;Reply by e-mail&quot; button for years.
Some of them also link to other places where you can comment.
This has been a nice trade-off: giving people the chance to comment somewhere where others will find it, but not having to manage the comments myself.</p>
<p>I do enjoy reading comments below blog posts, though.
It's always enlightening to read something and then have other people's opinions right below.</p>
<p>Starting today<sup class="footnote-ref"><a href="#fn-time" id="fnref-time" data-footnote-ref>1</a></sup>, it's possible to leave comments below my blog posts.
There's a small delay, as I have to manually approve every comment.
I don't want to be advertising some shady cryptocurrency tomorrow.</p>
<p><em>(<a href="https://vic.demuzere.be/guestbook/" title="Guestbook">My guestbook</a> has also been migrated from <a href="https://guestbooks.meadow.cafe/" title="Guestbooks by Meadow">Meadow Guestbooks</a> to the same backend that now serves blog comments.)</em></p>
<h2 id="webmentions">Webmentions?<a href="#webmentions" aria-label="Link to heading 'Webmentions?'" data-heading-content="Webmentions?" class="anchor"></a></h2>
<p>When I wrote the new comment code, I also added support for <a href="https://indieweb.org/Webmention" title="Webmentions as explained by Indieweb">webmentions</a> in addition to the form at the bottom.
It was live for about an hour before I removed it.
As it happens, Kev Quirk <a href="https://kevquirk.com/privacy-and-webmentions" title="Privacy and Webmentions by Kev Quirk">wrote an article about privacy and webmentions</a> while I was testing.</p>
<p>Webmentions (and ActivityPub) cause your message to be copied to other sites, where it could remain even after you've modified or deleted the original.
That's how the system works.
In my opinion, if you publish something on a public page, it should be considered public and can be expected to stay out there for a long time.<sup class="footnote-ref"><a href="#fn-privacy" id="fnref-privacy" data-footnote-ref>2</a></sup>
But it certainly is a point of discussion.
Similar issues exist with services like <a href="https://brid.gy/" title="Bridgy">Bridgy</a> that sync messages between social media silos.</p>
<p>That's why I decided to only accept comments that were submitted through a form on the article page. Your comment is published on the exact same page where you wrote it.<sup class="footnote-ref"><a href="#fn-scraper" id="fnref-scraper" data-footnote-ref>3</a></sup> There can't be much discussion about that, right?</p>
<h2 id="upvotes">Upvotes!<a href="#upvotes" aria-label="Link to heading 'Upvotes!'" data-heading-content="Upvotes!" class="anchor"></a></h2>
<p>While researching how other people and platforms implement comments, I came across <a href="https://bearblog.dev/" title="Bear Blog">Bear Blog</a>.
They have this rather simple upvote button. I couldn't find much documentation about it; it seems to be called &quot;toast&quot; or &quot;like&quot; here and there.
You don't need an account and you don't even need to leave your contact details.
You just push it, and the number goes up.</p>
<p>So while I was adding the required interactivity for comments, I also introduced a similar thumbs up button.
If you like a post, you can click it.
The number goes up.
If you like it more, you can click it again, and the number goes up again!
It's not used for anything other than displaying a silly number at the bottom.
It does looks nice, though.</p>
<p>I was told blog posts with comments sections need some kind of actionable callout, so: please leave a comment!</p>
<section class="footnotes" data-footnotes>
<ol>
<li id="fn-time">
<p>Sorry, I lied. The comments section has been live for a few weeks now. It doesn't really matter: nobody reads these posts so nobody noticed. But now it's official! <a href="#fnref-time" class="footnote-backref" data-footnote-backref data-footnote-backref-idx="1" aria-label="Back to reference 1">↩</a></p>
</li>
<li id="fn-privacy">
<p>Comments that have been published on my own website will be removed if the author asks, as <a href="https://vic.demuzere.be/meta/privacy/#comments" title="My privacy policy: comments">explained in my privacy policy</a>. <a href="#fnref-privacy" class="footnote-backref" data-footnote-backref data-footnote-backref-idx="2" aria-label="Back to reference 2">↩</a></p>
</li>
<li id="fn-scraper">
<p>And it may be copied to hundreds of other places by random internet scrapers, like the Internet Archive. Somehow this is always ignored in discussions about webmentions and activitypub. <a href="#fnref-scraper" class="footnote-backref" data-footnote-backref data-footnote-backref-idx="3" aria-label="Back to reference 3">↩</a></p>
</li>
</ol>
</section>
<div class="footer"><hr><p>Thanks for subscribing to my feed!</p><p>Feel free to e-mail comments or corrections to <a href="mailto:vic@demuzere.be?subject=RE%3A%20Let%20there%20be%20comments%21">vic@demuzere.be</a>.</p></div>]]></content></entry><entry><id>https://vic.demuzere.be/articles/hiding-outdated-articles/</id><title>Cool URIs don't change, but don't need spotlights</title><link href="https://vic.demuzere.be/articles/hiding-outdated-articles/" rel="alternate" /><updated>2024-11-11T18:18:07+00:00</updated><published>2024-11-10T10:04:30+00:00</published><content type="html"><![CDATA[<p><a href="https://kevquirk.com" title="Kev Quirk">Kev Quirk</a> recently wrote about <a href="https://kevquirk.com/blog/on-removing-content" title="On Removing Content; Kev Quirk">removing content from public blogs</a>:</p>
<blockquote>
<p>Generally speaking, I don't delete content from this site.
Having said that, if I posted something that I later feel is particularly egregious, I think I probably would.
I personally don't think that a website should be a permanent record - how can it be?
Nothing last forever.</p>
</blockquote>
<p>This got me thinking about what to do with some of my older articles.
I believe that URLs should be stable.
The internet is a large place, there’s no way to know who might be linking to any of my webpages.
Removing a page may also <em>break other websites</em>: someone may have written about it.
Deleting the page would remove the context of their reference.</p>
<p>However, I’ve been working on this website in some form or another since 2007.
Technical articles tend to get outdated, and people change their minds about things they’ve written.
Some of the articles on this website no longer reflect what I stand for.</p>
<p>Articles older than two years already include a banner noting their age, but that’s not always enough.
Nowadays, people often form an opinion based on the title alone — especially on social media.
It’s unlikely they’d notice a note about how old the article is.</p>
<p><strong>So I decided to <em>hide</em> certain articles.</strong>
Hidden articles are no longer linked on my website and don't appear in RSS feeds.
You can’t find them by clicking around.
But if you already have the link, the content is still accessible.
Because, as they say, <a href="https://www.w3.org/Provider/Style/URI" title="Cool URIs don't change">cool URIs don't change</a>.</p>
<div class="footer"><hr><p>Thanks for subscribing to my feed!</p><p>Feel free to e-mail comments or corrections to <a href="mailto:vic@demuzere.be?subject=RE%3A%20Cool%20URIs%20don%27t%20change%2C%20but%20don%27t%20need%20spotlights">vic@demuzere.be</a>.</p></div>]]></content></entry><entry><id>https://vic.demuzere.be/articles/not-so-redesign/</id><title>The mayor CSS not-so-redesign</title><link href="https://vic.demuzere.be/articles/not-so-redesign/" rel="alternate" /><updated>2024-11-11T18:24:32+00:00</updated><published>2020-06-14T00:12:27+00:00</published><content type="html"><![CDATA[<p>Over the past few months I've been working on a <strong>new stylesheet</strong> for this website, and today I finally pushed the redesign branch to production!
The previous CSS code was largely written <em>almost 10 years ago</em> and only received small updates and enhancements.
Since then, new features like <a href="https://developer.mozilla.org/en-US/docs/Glossary/Flexbox" title="MDN Glossary: Flexbox">flexbox</a> and <a href="https://developer.mozilla.org/en-US/docs/Glossary/Grid" title="MDN Glossary: Grid">grid</a>s were added and made creating responsive websites much easier.</p>
<p>Turns out, the new design looks <strong>exactly the same as the old one</strong>!</p>
<p>A few things did change though:</p>
<ul>
<li>Wrote plain CSS instead of <a href="http://lesscss.org/" title="LESS: CSS, with just a little more">LESS</a>.</li>
<li>Stopped using <code>float</code> to position elements in favor of <a href="https://developer.mozilla.org/en-US/docs/Glossary/Flexbox" title="MDN Glossary: Flexbox">flexbox</a>.</li>
<li>Followed the <a href="https://www.w3.org/WAI/standards-guidelines/wcag/" title="Web Content Accessibility Guidelines (WCAG)">Web Content Accessibility Guidelines</a> (WCAG).</li>
<li>Made the stylesheet a lot smaller.</li>
<li>Focused on readability throughout the website.</li>
</ul>
<p>I also tried to get some insight in how people used the website:</p>
<h2 id="a-year-in-statistics">A year in statistics<a href="#a-year-in-statistics" aria-label="Link to heading 'A year in statistics'" data-heading-content="A year in statistics" class="anchor"></a></h2>
<p>Most of the traffic to this website is routed through <a href="https://www.cloudflare.com/cdn/" title="Cloudflare CDN">Cloudflare's CDN</a>.
I've configured it to cache everything, which means the access logs on my web server record only part of the actual traffic.
This creates an interesting dataset: I can see which pages are most visited, but I can't see spikes due to pages being shared somewhere.
For the same reason, my statistics about browsers, operating systems, referring websites and returning visitors are completely skewed.</p>
<h3 id="popular-pages">Popular pages<a href="#popular-pages" aria-label="Link to heading 'Popular pages'" data-heading-content="Popular pages" class="anchor"></a></h3>
<p>Articles are the most popular pages on this website.
That makes sense, as those tend to show up in searches and are shared more frequently than others.
My most popular articles are technical ones:</p>
<ol>
<li><a href="https://vic.demuzere.be/articles/using-systemd-user-units/">Managing services for non-root users with systemd</a></li>
<li><a href="https://vic.demuzere.be/articles/curriculum-vitae-cv-with-latex-moderncv/">Creating a C.V. with LaTeX and moderncv</a></li>
<li><a href="https://vic.demuzere.be/articles/golang-makefile-crosscompile/">Cross compiling Go applications with Make</a></li>
</ol>
<p>That means I need to write more articles!</p>
<h3 id="popular-404-errors">Popular 404 errors<a href="#popular-404-errors" aria-label="Link to heading 'Popular 404 errors'" data-heading-content="Popular 404 errors" class="anchor"></a></h3>
<p>The most common 404s appear to be scanners looking for vulnerabilities.
WordPress related pages like <code>wp-login.php</code>, <code>xmlrpc.php</code> and several files inside the <code>wp-includes</code> directory lead the race, followed by Joomla's <code>administrator</code> directory.</p>
<p>My work to fix broken links (using data from the access logs and Google Search Console) seems to have paid off.
I've also been trying not to delete or move pages for a few years now.
When a page is no longer relevant, I replace it with a small message pointing people to alternatives, like I did with my <a href="https://vic.demuzere.be/otr/" title="My off-the-record fingerprints">OTR fingerprint listing</a>.</p>
<p>Another interesting 404 page is <code>/irc:irc.quakenet.org/sorcix,isnick</code> which seems to be caused by a spider that doesn't understand <code>irc:</code> URLs.</p>
<h2 id="future-changes">Future changes<a href="#future-changes" aria-label="Link to heading 'Future changes'" data-heading-content="Future changes" class="anchor"></a></h2>
<p>I've been looking into <a href="https://indieweb.org" title="The IndieWeb">IndieWeb</a> after reading a few blog posts by <a href="https://jlelse.blog" title="Jan-Lukas Else's weblog">Jan-Lukas Else</a>.
People can reply to your articles by linking back from their own website, or by using one of the provided IndieWeb-compatible services.
As I'm not active on mainstream social media, this may be a great way to connect with like-minded people.</p>
<p>Features I want to roll out next:</p>
<ul>
<li>RSS feed for articles</li>
<li>Overview pages for every tag, making it easier to find related articles</li>
<li>Support for Webmentions</li>
</ul>
<div class="footer"><hr><p>Thanks for subscribing to my feed!</p><p>Feel free to e-mail comments or corrections to <a href="mailto:vic@demuzere.be?subject=RE%3A%20The%20mayor%20CSS%20not-so-redesign">vic@demuzere.be</a>.</p></div>]]></content></entry></feed>