jrollans.com is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.
This server runs the snac software and there is no automatic sign-up process.
O #OLTN ganhou uma área Conta completa: silenciados, bloqueios, domínios, privacidade, padrões de publicação, exclusão automática, segurança e importar/exportar. Também dá para silenciar alguém direto pelo menu do post.
Em busca, no menu com ícone de Lupa ao lado, agora é possível buscar por temas e idiomas, com sugestões de perfis de pessoas e feeds de notícias (servindo, inclusive como base para adicionar no Newsletter). A limpeza automática respeita o limite de 30 exclusões a cada 30 minutos e retoma de onde parou.
@jack I use them both for some months now. #snac #snac2 is the fastest way to get a working connection to the fediverse with minimal resources, the process only uses a few MB RAM and Diskspace. But if you follow a lot of people or hashtags, its web interface easily gets somewhat confusing. It mixes replies to old threads (always showing the full thread with all replies) with new posts in the interface and turns it into a mess. you may have no idea what you've read or not. And clients don't work very well with it.
#gotosocial uses more resources (app. 500 MB RAM on my Debian Linux) and, depending on your fediverse traffice, some GB for media files. It's a well thought out software that works very reliable. And IMHO it has the best implementation of relays of every Fediverse-Server I tested (it allows fine control of what you get to avoid flooding the server). It has no client web interface (only one for admin tasks), so you need a web interface like #Phanpy or a fediclient app. If you like a more traditional (like Mastodon) way to interact with the fediverse, it's the better choice.
While Codeberg is down (and I hope they'll be back soon!), I've always been (privately) mirroring the #snac repository on Brew. I've switched it to public.
So you can access it pointing to https://brew.bsd.cafe/BSDCafe/snac2
Web interface language
Since version 2.73, the web UI can be localized via simple .po files (they are directly parsed, no support for gettext is needed).
No language file is installed by default; the administrator must copy any desired .po files to the lang/ subdirectory in the base directory. Once the server is restarted, users can select the new language from the user settings. The snac source distribution may include .po files in the po/ subdirectory. You don't need to copy the English language one, as it's the default.
To create new language files, create a copy of po/en.po, rename it to a reasonable value like pl.po or pt_BR.po, change the translator in the header to yourself and fill the msgstr strings with your translation. If you have any doubt on how to modify .po files, there are many tutorials out there. If you want your language file to be included in the standard snac distribution, please send me a link to it via the Fediverse to @grunfink@comam.es or make a PR via the Git repository.
son só unhas 300 cadeas de texto, así que alá vou con gl
(mirei no repositorio e non está en #galego)
migrei a conta de servidor nicho do fediverso⁂ a servidor súper-nicho do fediverso⁂. Parece que funcionou.
(só seguín a documentación)
the issue was coming from my terminal/system who added an invisible char at the end when pasting the actor URL.Glad to know!
would you welcome a patchPatches are always welcome, if they match all requirements in the
CONTRIBUTING.md file in #snac 's distribution.Thanks!
Sometimes I forget about it, but it just keeps on doing its thing.
Loving #snac so far. I have a question regarding the relay special user: how do we #unsubscribe from a #relay? i've tried snac unfollow relay <relay_actor_url> and snac unfollow relay <relay_handle> and both returned that the relay user was not following the actor/handle. However, when exporting the following list for the relay actor, i still see the relay listed. Please advise.

Hashtag following also allow URLs to RSS feeds of ActivityPub objects (like e.g. https://mastodon.social/tags/ThankYouTuesday).
Users can now configure a webhook to receive an HTTP POST for every notification. This can be useful for implementing bots that react to activities, like autorepliers, chatbots or interactive textual games (see snac(1) for more information).
The number of pending follow confirmations is shown next to the "people" link.
Faster performance metrics (contributed by dandelions).
Improved lowercasing in hashtags (contributed by postscriptum).
A search-by-url tweak for implementations that return 200 for invalid webfinger queries (e.g. piefed).
Mastodon API: added follow confirmation endpoints, fixed collisions in attachment file names.
Fixed potential crashes in attachment uploads.
If you find #snac useful, please consider buying grunfink a coffee or contributing via LiberaPay.
Notifications are now shown in a more compact way (i.e. all reactions are shown just above your post, instead of repeating the post ad nauseam for every reaction).
New command-line option unmute to, well, no-longer-mute an actor.
The private timeline now includes an approximate mark between new posts and "already seen" ones.
Fixed a spurious 404 error in the instance root URL for some configurations.
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
This release has been inspired by the song The Answers to the Questions by #Christabell and #DavidLynch.
https://it-notes.dragas.net/2025/01/29/improving-snac-performance-with-nginx-proxy-cache/