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.
@nowster That's a #snac bug. The marker should be returned as a Datetime, documented here: https://docs.joinmastodon.org/api/datetime-format/#datetime. Based on the error message it looks like it's returning $milliseconds.$nanoseconds since the epoch.
I've reported this as https://codeberg.org/grunfink/snac2/issues/659.
@ploum @stefano I absolutely did for a while too. At some point I switched to Gotosocial because of issues with my iOS clients (likely fixed since then).
I do keep a my old #snac instance alive as an archive and update it just as easily as in the past years with that little script that just fetches the source and compiles.
I like Mastodon, I really do. But it has so, so many dependencies, and updating it on illumos or OpenBSD is getting really difficult, release after release.
Some dependencies are primarily distributed as binaries, or only build on Linux and macOS. It's not Mastodon's fault, but it depends on them.
That’s why, in my opinion, solutions like snac, GoToSocial, or littleFedi have a reason to exist: all of this is much, much easier...
#Fediverse #snac #GoToSocial #littleFedi #OwnYourData #Mastodon
On the other, whenever a post from someone you follow gets in, snac tries to retrieve (following the inReplyTo fields chain) all the conversation up to the beginning to give you some context in the conversation. It may happen that, if that account you follow deletes their post, the replied post is left in your timeline, for no apparent reason.
That might explain why I have a single instance snac
server, and still get basically spam posts.
I know I get something similar to that when there is
like a secondary relationship thru someone i am following.
But these things I see seemingly have no connecting relationships.
The best way to include links with unusual characters in #snac is to use the Markdown syntax for links, like in East of Eden.
That is, an open square bracket, then the alt text, then the open bracket, then the url, then the close bracket (see snac(5) for more info).
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/