<p>Dear friends of the BSD Cafe,</p><p>This idea has been in my mind since the very beginning of this adventure, almost two years ago. Over time, several people have suggested it. But until recently, I felt the timing just wasn’t right - for many reasons. Today, I believe it finally is.</p><p>So I’m happy to announce a new service: <br>The BSD Cafe Journal - <a href="https://journal.bsd.cafe" rel="nofollow"><span class="invisible">https://</span>journal.bsd.cafe</a></p><p>At first, I thought I’d use BSSG for it (I even added multi-author support with this in mind), but in the end, it didn’t feel like the right tool for the job.</p><p>The idea is to create a multi-author space, with content published on a fairly regular basis. A reference point for news, updates, tutorials, technical articles - a place to inform and connect.<br>Just like people in Italy used to stop by cafes to read the newspaper and chat about the day’s news, the BSD Cafe Journal aims to be a space for reading, sharing, and staying informed - all in the spirit of the BSD Cafe.</p><p>What it’s not:<br>It’s not here to replace personal blogs, or excellent newsletters like <span class="h-card"><a href="https://mastodon.bsd.cafe/@vermaden" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>vermaden</span></a></span> 's. And it’s not an aggregator.</p><p>What it is:<br>A place where authors can write original content, share links to posts on their own blogs or elsewhere, publish guides, offer insights, or dive into technical explanations. </p><p>The guiding principles are the same as always: positivity, constructive discussion, promoting BSDs and open source in general. No hype (sharing a cool new service is fine, posting non-stop about the latest trend is not), no drama, no politics. The goal is to bring people together, not divide them. To inform, not inflame.<br>Respect, tolerance, and inclusivity are key. Everyone should feel welcome reading the BSD Cafe Journal - never judged, offended, or excluded.</p><p>The platform I’ve chosen is WordPress, for several reasons: it’s portable (runs well on all BSDs), has great built-in role management (contributors, authors, etc.), and - last but not least - supports ActivityPub.<br>This means every author will have their own identity in the Fediverse (like: <span class="h-card"><a href="https://journal.bsd.cafe/author/stefano/" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>stefano</span></a></span> ) and can be followed directly, and it’ll also be possible to follow the whole Journal.</p><p>Original and educational content is encouraged, but it’s also perfectly fine to link to existing articles elsewhere. Personally, I’ll link my technical posts from ITNotes whenever I publish them there.</p><p>The goal is simple: a news-oriented site, rich in content, ad-free, respectful of privacy - all under the BSD Cafe umbrella.</p><p>Content coordination will happen in a dedicated Matrix room for authors. There’ll also be a public room for discussing ideas, giving feedback, and sharing suggestions.</p><p>Of course, I can’t do this alone. A journal with no content is just an empty shell.<br>So here’s my call for action:<br>Who’s ready to lend a hand? If you enjoy writing, explaining, sharing your knowledge - the Journal is waiting for you.</p><p><a href="/tags/bsdcafe/" rel="tag">#BSDCafe</a> <a href="/tags/bsdcafeservices/" rel="tag">#BSDCafeServices</a> <a href="/tags/bsdcafeupdates/" rel="tag">#BSDCafeUpdates</a> <a href="/tags/bsdcafeannouncements/" rel="tag">#BSDCafeAnnouncements</a> <a href="/tags/runbsd/" rel="tag">#RunBSD</a> <a href="/tags/freebsd/" rel="tag">#FreeBSD</a> <a href="/tags/netbsd/" rel="tag">#NetBSD</a> <a href="/tags/openbsd/" rel="tag">#OpenBSD</a> <a href="/tags/illumos/" rel="tag">#illumos</a> <a href="/tags/linux/" rel="tag">#Linux</a> <a href="/tags/oss/" rel="tag">#OSS</a> <a href="/tags/opensource/" rel="tag">#OpenSource</a> <a href="/tags/bcjournal/" rel="tag">#BCJournal</a> <a href="/tags/bsdcafejournal/" rel="tag">#BSDCafeJournal</a></p>
Edited 266d ago