Btw, #snac2 is extremely cool to use.

wow, that was quick - more than 30 instances already connected to my relay in just such a short time :) Let's be federated and help even smaller #instances to distribute their content & posts!

You can find more information at:
https://fedi-relay.gyptazy.com

The instance is reachable on IPv4 and IPv6.

#fediverse #mastodon #snac #snac2 #activitypub #relay #activtypubrelay #Pleroma #BSD #RUNBSD #devops #opensource #ipv6 #gotosocial #community #akkoma #pixelfed #selfhosting #homelab

@joel better use #snac/ #snac2 ;)

Thanks for providing this service and also this information. At this point, we can only say - thank you very much for your time, efforts and money you put into this service @stefano. At this point I also want to bring up the great work of @grunfink for his incredible work in the #snac / #snac2 project. Snac became the perfect solution for single user instances but also project related instances in the fediverse. Kudos, to both of you and thank you both very much! You both are doing a great job!

I can always recommend #snac2 from @grunfink
@rausgerufen @roblen

Is #snac2 a suitable fedi server for a single-person, daily-driver instance, accessed via mastodon apps, interacting with the wider fediverse?

I /think/ I've mostly seen it deployed as a more write-centric service (for info bots/etc) ... but I could be mistaken.#snac #Fediverse #hosting #selfhosting

Is there any internal method for preventing a snac2 server from federating? I don't mean blocking. I mean prohibiting all federation and contact with other activitypub instances. The goal is the local users don't see anything from the fediverse and the fediverse won't see anything from the local server.

I realize there are brute ways to hack nginx and IPtables to block ports and things like that. I'm just wondering if there is an internal method that is more sensible, or if perhaps some blocks of code could be removed before compilation.

#snac2 #fediverse #servers #activitypub

Dear friends of the BSD Cafe,

As 2024 comes to an end, it’s time to reflect on what we’ve built together during the first full year of life for BSD Cafe. Launched on 20 July 2023, this project has grown far beyond what I could have imagined. While I haven’t tracked full uptime data, I can confidently say that the downtime was less than 30 minutes overall - even though the main VM hosting our services moved multiple times (including a switch from a Proxmox hypervisor to bhyve on FreeBSD, for the sake of alignment with our mission). In a world filled with over-engineered HA systems, we’ve outperformed many “big-name” cloud providers. Not bad for a community project, right?

For me, this has been an incredible journey. The users here are not just participants - they’re collaborators, and their positivity has been inspiring. The content shared and created at BSD Cafe has been valuable not only to the BSD community but beyond. What truly sets BSD Cafe apart is the openness for dialogue and exchange. Whether it’s social media posts, Matrix discussions, repositories in our brew, or RSS feeds, people seem to genuinely appreciate what we create and the conversations we foster.

BSD Cafe is a journey - one that grows, evolves, and continues. Our goal isn’t endless growth (we’re a community, not a business) but rather to maintain a welcoming, inclusive space where everyone feels a sense of positivity and belonging. For me, opening any service with “bsd.cafe” in the domain brings joy and pride. That’s the spirit I’ve tried to convey, and I hope it resonates with all of you, whether you’re active BSD Cafe users or friends of the community.

Promoting self-hosting and #OwnYourData has, as a side effect, inspired some users to “go solo” with their own setups. But even then, they remain part of BSD Cafe - in spirit, in purpose, and in connection.

Here’s a look at what we’ve achieved together this year:

- mastodon.bsd.cafe: 370 total users
Active in the past month: 207
Active in the past six months: 286
- snac.bsd.cafe: 14 total users
Active in the past month: 7
- blendit.bsd.cafe: 61 registered users
- matrix.bsd.cafe: 23 users
- brew.bsd.cafe: 29 users - 80 repositories
- freshrss.bsd.cafe: 25 users
- miniflux.bsd.cafe: 11 users
- press.bsd.cafe: 9 users
- myip.bsd.cafe: Constantly used by various users
- wiki.bsd.cafe: Could use a bit more love and content, but it fulfills its role as a functional homepage.
- tube.bsd.cafe: Still in testing - Peertube 7.0 update is on the way.

For detailed stats from our reverse proxy and general router (excluding media services, which generate most traffic but are handled via caching reverse proxies), you can check here - updated hourly: https://netstats.bsd.cafe

The journey of BSD Cafe continues, and I look forward to seeing where 2025 will take us. Together, we’ve built something special - something driven by passion, shared purpose, and a little bit of the BSD magic that makes all of this possible.

Here’s to a new year full of joy, serenity, and connection. Thank you for being part of this adventure.

Wishing you all a fantastic 2025 - and THANK YOU!
Stefano

#BSDCafe #BSDCafeServices #BSDCafeAnnouncements #BSDCafeUpdates #Fediverse #HappyNewYear #Mastodon #Snac #snac2 #lemmy #matrix #dokuwiki #forgejo #freshrss #miniflux #wallabag #peertube

Some users gave it a try and decided to self-host. Others have kept it as a secondary account, while some use it regularly.

Happy anniversary, snac.bsd.cafe - and thanks to @grunfink@comam.es for the ongoing development and improvement, always staying true to the principles of simplicity and integrity.

#BSDCafeServices #BSDCafe #snac #snac2 #Fediverse #SocialNetworks

@brad
The fedi software I've found easiest to poke around coding in is #snac2, because of how clearly written and documented it is: @grunfink has done such a great job!
@loren

@i first, I regret it and it was a mistake. I should have kept #snac2 instead of #Mastodon (and I wrote it already several times). If you run a single user instance - don’t use Mastodon. I was one of the early adaptors of snac and also contributed to the project but back in that time, the API was very limited and several clients didn’t work or were limited in display posts (as in a kind of count). The current releases are much better and work great - especially for single user instances and @grunfink is doing an absolutely great job (thank you very much for your work!).

I’m planning to switch back to snac (it finally can do “move” actions where you’re not locked-in anymore) but switching the instance on the same domain means a three-way movement to not break the users crypto keys. There’s also a self destroy possibility, but that mostly only works on Mastodon. Snac cannot interprete this (but according to grunfink the keys are resourced in a few days, so it shouldn’t be a problem) but not quite sure about other solutions like GTS etc. So, the smoothest way is to migrate to a tmp instance on another domain and the create an instance on this domain and move back again. If I have time, I’ll do so.

There's something very satisfying about self-hosting email. Feels like I can "seize the means of communication"

Its absurd that something so simple and so ubiquitous felt so far from me before, as if it is obvious that email would need to be owned by the mega-corps (Gmail, Outlook, etc)

Mastodon (particularly via Snac) gives me the same feeling. It's a glimpse at an internet that I was too young to know. One of open communication and cooperation, rather than ad-driven bollocks

#email #snac2

I currently regret most switching from #snac2 to #Mastodon — fortunately, Snac now supports account migrations, so I’ll be able to switch back soon but it requires migrating me to migrate to another domain, where I then can switch back to this one on snac.

@al1r4d you might want to have a look at #snac2 which is a very minimalistic but awesome Fediverse server, written in C. Guess, you can see several hints

@knt any guess on how do you change themes on #snac?

#snac2

I should have posted this with public visibility.

New Blogpost: https://ddlyh.smol.pub/snac2-selfhost

#snac2 #snac

#ios client for posting from my #snac2 instance?

https://manpages.debian.org/testing/snac2/snac.5.en.html