Note to self: repology.org is not authoritative.

I checked it this morning and thought, "oh good, 100% nothing needs updating."

Then I checked @grunfink's stream and saw that snac 2.34 is out!

Repology still shows 100%, but I have some work ahead of me to update the MacPort and I won't be able to get to it as quickly as I would like.

Fellow developer @Haijo7@snac.haijo.eu has created a cool, awesome CSS theme for #snac:

https://codeberg.org/Haijo7/snac-custom-css

It's #SoftwareReleaseSaturday again! I'm glad to announce the release of version 2.34 of #snac, the simple, minimalistic #ActivityPub instance server written in C. It includes the following changes:

Polls can now be created from the web interface.

New Mastodon API features: polls are shown and can be voted on.

The user@host identifier is now shown next to the user avatar (contributed by Haijo7). A small tweak to the default CSS was made to suit this change; please consider updating your style.css.

Clicking on an image attachment opens it in a new tab (contributed by Haijo7).

Bots are marked as such using an emoji (contributed by Haijo7).

https://comam.es/what-is-snac

If you find #snac useful, please consider buying grunfink a coffee: https://ko-fi.com/grunfink

I'm glad to announce the release of version 2.33 of #snac, the simple, minimalistic #ActivityPub instance server written in C. It includes the following changes:

Polls (in #ActivityPub lingo, Questions) are shown and can be voted on. Creating a poll is not yet implemented, though.

If an URL written in a post links to an image, it's converted to an attachment.

Fixed a bug in the semaphore code that caused total hangs on OpenBSD.

https://comam.es/what-is-snac

If you find #snac useful, please consider buying grunfink a coffee: https://ko-fi.com/grunfink

@grunfink, hello

#snac 2.31 and 2.32 is hang on input requests, 2.30 works fine.

By logs (dbglevel=3): job threads exit immediately.

snac[53925]: 17:26:28 using 4 threads
snac[53925]: 17:26:28 background thread started
snac[53925]: 17:26:28 job thread 1 started
snac[53925]: 17:26:28 job thread 1 wake up
snac[53925]: 17:26:28 job thread 1 stopped
snac[53925]: 17:26:28 job thread 2 started
snac[53925]: 17:26:28 job thread 2 wake up
snac[53925]: 17:26:28 job thread 2 stopped
snac[53925]: 17:26:28 job thread 3 started
snac[53925]: 17:26:28 job thread 3 wake up
snac[53925]: 17:26:28 job thread 3 stopped

Environment: running on OpenBSD. Do you know what could be wrong?

@grunfink@comam.es
Hello, i've installed last version of snac and trying to login from Mastodon client. In log everything's fine:

22:12:46 oauth x-snac-login: 'i' success, redirect to metatext://oauth.callback?code=02blah
22:13:04 oauth x-snac-login: 'i' success, redirect to com.jonny.mona://oauth?code=d81blah

But in the clients i've got "Error. The data couldn't be read because it is missing" windows (iOS)
How to solve this? Thanks in advance!

I'm glad to announce the release of version 2.32 of #snac, the simple, minimalistic #ActivityPub instance server written in C. It includes the following changes:

New user configuration switch to drop direct messages from people you don't follow, in order to mitigate spam from Mastodon open registration instances.

When updating user information (e.g. the display name or the bio), the changes are also sent to the people being followed (so they have an updated description about who the user is).

Mastodon API: account search has been implemented, so mention completion works from apps; new support for blocking users (this operation is called MUTE here).

https://comam.es/what-is-snac

If you find #snac useful, consider buying grunfink a coffee: https://ko-fi.com/grunfink

The powers that be have provided links to #snac manual pages in HTML format:

https://comam.es/snac-doc/snac.1.html - User Manual
https://comam.es/snac-doc/snac.5.html - Message Formatting and File Format Documentation
https://comam.es/snac-doc/snac.8.html - Administrator Manual

https://comam.es/what-is-snac

I'm glad to announce version 2.31 of #snac, the simple, minimalistic #ActivityPub instance server written in ANSI C. This time it's mostly bugfixes contributed by fellow developers:

Fixed webfinger and curl issues, which crashed snac while trying to follow Mitra users (contributed by Poesty).

Use named semaphores instead of anonymous ones, to make it work under MacOS (contributed by Saagar Jha).

Fixed semaphore name conflicts (contributed by Poesty).

Fix warning in ugly pointer substraction (contributed by Saagar Jha).

Added user-agent to webfinger queries (contributed by Poesty).

Mastodon API: implemented notification type filters, fixed (partially) the issue with mentions without server.

https://comam.es/what-is-snac

If you find #snac useful, consider buying grunfink a coffee: https://ko-fi.com/grunfink

I'm glad to announce the release of version 2.30 of #snac, the simple, minimalistic #ActivityPub instance server written in ANSI C. It includes the following changes:

Fixed a bug that made some notifications to be missed.

New Mastodon API features: the instance public timeline is now a real one, unfavourite / unreblog is supported (somewhat). Some regression bugs regarding image posting were also fixed.

The non-standard Ping and Pong #ActivityPub activities have been implemented as proposed by @tedu@honk.tedunangst.com in the https://humungus.tedunangst.com/r/honk/v/tip/f/docs/ping.txt document (with a minor diversion: retries are managed in the same way as the rest of #snac messages).

The build process now includes the -Wextra flag.

https://comam.es/what-is-snac

If you find #snac useful, consider buying grunfink a coffee: https://ko-fi.com/grunfink

@grunfink
have some kofi

What better way is there to bring iSH to the fediverse than by having it introduce itself? The post you're reading right now was written and served from iSH, running an instance of @grunfink@comam.es's snac :)

I'm very glad to announce the release of version 2.27 of #snac, the simple, minimalistic #ActivityPub instance server written in ANSI C. It includes some interesting new features (that I announced some days ago):

Started Mastodon API support, so you can use Mastodon-compatible apps to access #snac accounts. What works so far: login, private and public timelines, full post information (replies and ancestors), liking and boosting posts. Things that don't work yet but eventually will: following accounts, posting and replying to messages (I still have to figure out how some things work, like posting images), notifications (needs some internal support), the instance timeline (snac does not have one, but it can be simulated with not much effort) and probably many other things. Things that will never work: bookmarks, pinning, a federated timeline, many other things that I don't remember right now. Please note that if you want to use this API in your instance, you must add some lines to your HTTP proxy configuration, see the snac(8) (administrator documentation) manual page. I'm doing my tests using the #Tusky (which sometimes crashes, surely my fault), #AndStatus, #Fedilab and #Husky Android apps. Success or failure reports will be appreciated.

Fixed some buffer overflows (contributed by Saagar Jha).

Fixed overzealous rejection of some local boosts.

https://comam.es/what-is-snac

Call me crazy, but I've started implementing the #MastodonAPI into #snac, the simple, minimalistic #ActivityPub instance server written in ANSI C that everybody loves. When it's ready, you will be able to operate your snac account from a Mastodon-compatible app like #Tusky and the like.

I hope to have it working read-only in a couple of days, but who knows.

Stay tuned!

I'm at a laundromat cleaning my clothes.

Passing time with this terrible touch screen device with a cracked screen yet repology and codeberg still shows:

@grunfink has released a new version of snac!

So after I'm done here and back at a laptop unlike this touch screen device which is wack.

Updating the MacPorts' Portfile to 2.29 I shall work, though I wouldn't call an update a hack.

Perhaps I'll add a variant for the new compile time option for no Mastodon support.

Maybe that seems odd to you but it's not a retort.

ActivityPub is not just one implementation after all.

Which is why I dig snac, it's in ANSI C and compiled? It's small!

I've just released version 2.29 of #snac, the simple, minimalistic #ActivityPub instance server written in ANSI C, including the following:

New Mastodon API features: account search, relationships (so the Follow/Unfollow buttons now appear for each account), follow and unfollow accounts, an instance-level timeline (very kludgy), custom emojis for accounts and statuses, many bug fixes (sadly, the Mastodon official app still does not work).

https://comam.es/what-is-snac

If find #snac useful, consider buying grunfink a coffee: https://ko-fi.com/grunfink

@grunfink why printf and not puts? why so many?

I submitted a PR to update MacPorts' version of @grunfink' snac to 2.28 here:

https://github.com/macports/macports-ports/pull/18390

CI/build bot checks passed!

It's up to someone else to merge it.

#snac #ActivityPub #MacPorts #Mastodon #opensource #ANSIC

'Names' are words we humans give to things and actions to distinguish from one another. But, here in the Fediverse, the act of re-sending another user's post...

In the #ActivityPub protocol, it's called 'Announce'.

In the #Mastodon web interface (and here in #snac too), it's called 'boost'.

In the Mastodon API, it's called 'reblog'.

Mastodon users say, informally, 'retoot'.

In the #Pleroma web interface (AFAIK), it's called 'repeat'.

In #honk it's called 'bonk' (because, why not).

Outside there, in other crappy social networks, Facebook names the action 'share' (IIRC), Twitter users names it 'retweet'. I don't know about others, but they probably use a different verb.

I've just released version 2.28 of #snac, the simple, minimalistic #ActivityPub instance server written in ANSI C, including the following:

Added a new notification area to the web interface, accessible from a link at the top, that also shows the number of unseen events. This area lists all notifications in reverse chronological order and provides a button to clear all.

More work in the Mastodon API. The new supported features are: notifications, post of new and reply messages (including attached images). Some API v2 entry points had to be implemented, so you'll need to update your HTTPS proxy configuration again, see snac(8). #Tusky no longer crashes, or so I think. The official app and close relatives like #Megalodon still don't work, though.

If you are not interested in this Mastodon API crap, you can compile it out of your #snac by defining the NO_MASTODON_API preprocessor directive and forget about it.

Fixed an HTML cache bug (it was not refreshed after editing a post).

https://comam.es/what-is-snac

this is minimalist to the pain. it doesnt allow for polls or audio content, IDK.

this seems accessible at a first test, sending a post, the edit field is not labelled, easy fix. and there are no mention suggestions, or they are hidden for a screenreader. @grunfink

I submitted a PR to update MacPorts' version of @grunfink's snac to 2.27 here:

https://github.com/macports/macports-ports/pull/18266

Required a little bit more tweaking to the Portfile and Makefile patch, but nothing too significant thankfully!

CI/build bot checks passed OK!

It's up to someone else to merge it.

#MacPorts #snac #ActivityPub #FediVerse #opensource

Hi. Yes, you're right, images and their description should be kept from the original post when editing.

I'll add this issue to the TODO file.

I submitted a PR to update @grunfink's snac in MacPorts to 2.26:

https://github.com/macports/macports-ports/pull/18193

CI/build bot checks passed!

It's up to someone else to merge it.

#snac #MacPorts #ActivityPub #FediVerse

Hi, everyone. I've just released version 2.26 of #snac, the simple, minimalistic #ActivityPub instance server written in ANSI C. This is a low profile maintenance version that includes just the following minor changes:

The OpenSSL code has been refactored to avoid using deprecated functions.

Added more aggressive filtering on unwanted Announce (boost) messages.

https://codeberg.org/grunfink/snac2

Casually browsing fedi from #9front

I am not the internet police, but I think it would be better for people who write masto api clients to not refer to them as generic activitypub clients. Did you even read the page title of the spec you implemented?

Not sure how I missed this days ago when it was announced yet again.

My PR to update @grunfink's snac to 2.25 in MacPorts:

https://github.com/macports/macports-ports/pull/17958

It's up to someone else to merge it, but at least it passed the CI/build bot checks.

#snac #ActivityPub #MacPorts #FediVerse #OpenSource

I'm happy to announce version 2.25 of #snac, the simple, minimalistic #ActivityPub instance server written in ANSI C. These are the changes:

Federation with other instances have been improved by collecting shared inbox information from input messages more thoroughly.

Fixed an obscure bug that caused connection rejections from some instances.

Some rules regarding incoming messages have been tightened; messages that are not related to the user are not added to the timeline. This has to be implemented because some ill-behaving ActivityPub implementations were found injecting unwanted messages to user inboxes.

Messages from MUTEd users are rejected as soon as possible with a 403 Forbidden HTTP status.

Fixed a minor bug regarding the scope of the 'Update' activity (edited posts were sent to more recipients that it should).

More aggressive input sanitization (some posts were found that included strange ASCII control codes).

Added "Open Graph" HTML meta tags for better previsualization of snac links from other social media.

https://codeberg.org/grunfink/snac2

I for one don't think we're going to "win" a battle against discord/twitter and the like with software that requires a "mini cloud" installation to setup and manage it.

Sure you can install Mastodon / Matrix via docker, but it is simple to install, and complex to manage over time. Doubly so if the word "scale" ever comes up.

As soon as you mention "SQL Database" you're going to lose most people.

2020's era software missed the KISS memo.

I submitted a PR to update @grunfink' snac to version 2.24.

It's up to someone else to merge it.
#snac #MacPorts #ActivityPub #FediVerse

Hi, everyone. I've just released version 2.24 of #snac, the simple, minimalistic #ActivityPub instance server written in ANSI C, that includes the following features and bugfixes:

Sending non-public messages is now much easier: a checkbox to post a message to only those people mentioned in the message body has been added.

Fixed an over-optimization bug that caused some mentioned recipients to be skipped.

Added some new administrator tweaks: email notifications can be globally disabled.

https://codeberg.org/grunfink/snac2

This post has been inspired by the song Ghosts Again by Depeche Mode.

PR to update the MacPort for @grunfink 's snac to version 2.23:
https://github.com/macports/macports-ports/pull/17799

Previous merged PR was for 2.18. Although, someone opened this Trac ticket: https://trac.macports.org/ticket/66751 which is still open, because my attempts to refactor the Portfile with the PortGroup makefile 1.0 have been unsuccessful so far.

Thankfully, another ticket was opened: https://trac.macports.org/ticket/66989 so I can justify just pushing a version bump & solve the harder problem later?

#snac #FediVerse #ActivtyPub #MacPorts

I'm happy to announce version 2.23 of #snac, the simple, minimalistic #ActivityPub instance server written in ANSI C, including:

The user avatar can now be uploaded (instead of given as an URL).

Minor speed improvements int output messages.

Minor improvements in error logging.

https://codeberg.org/grunfink/snac2

@grunfink Help me to decide, help me make the most of freedom and of pleasure... sorry. data.c:1570 - why unlink right when an item starts to be run? Why not only unlink when we can be sure the item has either been successfully delivered, or successfully rejected?

Should I come back with a merge request implementing this?

I'm a bit embarrassed of announcing version 2.22 of #snac, the simple, minimalistic #ActivityPub instance server written in ANSI C, which fixes some bugs, one of them pretty nasty:

Fixed a bug with the Delete button in the web interface: sometimes, instead of the post (as the user intended), the follower was deleted instead 🤦

Fixed a bug in the command-line option follow (and probably others), that made it fail silently if there was no running server.

Fixed a crash under OpenBSD (a recent change needed a new permission to the pledge() call that was forgotten).

https://codeberg.org/grunfink/snac2

I'm happy to announce version 2.21 of #snac, the simple, minimalistic #ActivityPub instance server written in ANSI C. This time there are a bunch of things:

Users can now specify an expire time for the entries in their timelines (both their own and others').

Added support for sending notifications (replies, follows, likes, etc.) via Telegram.

Followers can now be deleted (from the people page in the web interface). Yes, to stop sending in vain your valuable and acute posts to those accounts that disappeared long ago and flood the log with connection errors.

The internal way of processing connections have been rewritten to be more efficient or, as technical people say, "scalable". This way, snac is much faster in processing outgoing connections and less prone to choke on an avalanche of incoming messages. This is a big step towards the secret and real purpose of the creation of this software: being able to host the account of #StephenKing when he finally leaves that other site.

The note action from the command-line tool can also accept the post content from the standard input.

Usage tips: never reply to toxic people (apply the MUTE button to them). Enjoy a coffee. Smell the sea. Listen to Mahler. Spend a bit less time in social media and a bit more with your loved ones.

https://codeberg.org/grunfink/snac2

The #ActivityPub protocol is specially hostile when you're starting over, because you must implement almost everything of it before you can even test the most basic things.

Given that you plan to work in Go, you may also be interested in taking a look at honk, which is an ActivityPub implementation in that language:

https://humungus.tedunangst.com/r/honk

$ curl -I https://go-fed.org
curl: (60) SSL certificate problem: certificate has expired

Yes, I agree honk is a bit peculiar in the naming of things, and opinionated in the interface. Its author, @tedu@honk.tedunangst.com , is an awesome hacker, so the code is surely of immense quality.

My programming approach is very different to tedu's. Also, the codebase of #snac is probably smaller, so it may be easier to explore.

I am just hoping your code is a little more readable.

I also hope so 🙂

You're right; I just implemented what I understood as the minimum code for a having a basic "presence" in the Fediverse: basic 'Person' management (i.e. retrieving Person objects to get the keys for signing the messages, and serving your own 'Person' objects to others for them to validate your signatures), 'Follow' messages (in both directions) and then 'Note' messages (in both directions). Likes and boosts (in the protocol named 'Announces') came after that.

These things are the bare minimum. Of course, as all #ActivityPub traffic is HTTP signed, you need to get that code very finely tuned. The problem is that there is no "implementation reference" to test against, you have to communicate with real servers, and everyone of them behaves a little different. Some instances are hostile to testing code (which I understand) and may block you. If your signing code does not work well, you won't get any useful response from any implementation.

Also, I consider the ActivityPub to be a bit ambiguous in some places.

What I suggest is that you install #snac or any other simple implementation and bang your messages against.

Hi. Sorry, I know next to nothing about the Pleroma code. Do you consider it a bug, or a good thing?

I'm glad to announce version 2.20 of #snac, the simple, minimalistic #ActivityPub instance server written in ANSI C, including just one new feature:

Image attachments in posts can now have a description (a.k.a. "alt text").

There has been several internal changes, but nothing visible.

https://codeberg.org/grunfink/snac2

Very cool how adding an editable text label with the logo gets the biggest centralized code hosting site — an abusive one at that, feeding all your code to train a Microsoft-owned AI — loads of free publicity around here. 🤔

Instead, I'm gonna send some love to @Codeberg and @forgejo, since they might actually *implement federation* for code hosting systems.

As in: joining fedi, instead of just paying lip service like that other code hosting site.

#FLOSS #FOSS

I'm glad to announce version 2.19 of #snac, the simple, minimalistic #ActivityPub instance server written in ANSI C, including the following changes:

You can edit your own posts from now on.

Fixed the breakage of Emojis I introduced when implementing HashTags because I am a moron.

Added adaptative timeouts when sending messages to other instances.

https://codeberg.org/grunfink/snac2

Is it just me or does technology just continue to get increasingly creepier and grosser?

I'm thinking about adding some new features to snac, the minimalist ActivityPub server written in C. As these features are opinionated and probably even controversial, they will be off by default. These are the ideas:

First, add an option to automatically drop all announces (boosts). Unless your affinity with the people you follow is deep, boosts are just (usually) tangentially interesting, probably flooding your timeline and just forcing you to spend more and more time inside the social media space. A variant of this would be to make this option not global, but by actor, so that you can 'boost-mute' only those adorable but annoying fellows that are particularly trigger-happy to the boost button (implementing the option this way is more work for me, but not that much).

Second, add an option to drop all messages that are not public nor mentioning you. That is, filter out those infamous 'follower-only' messages. People use to engage in these follower-only conversations, so you only receive these chat fragments without context (unless you also follow all the people involved) and they are purely noise. In my opinion, follower-only messages are a very bad idea that just pollute the space (and this is why snac doesn't implement them and never will).

Third, add an option to drop all replies to your messages from people that you are not following. This would prove useful for very popular, mostly announce-only accounts. I agree that it's a bit elitist and probably toxic, but also helps in spending less time inside the social networks and more time painting or writing or taking the dog for a walk.

What do you think?

https://codeberg.org/grunfink/snac2

awk -F, 'NR > 1 { print $1 }' /path/to/following_accounts.csv | \
           xargs -n 1 snac follow $SNAC_BASEDIR $SNAC_USER

I'm happy to announce version 2.18 of snac, the simple, minimalistic ActivityPub instance server, including the following changes:

Added support for #HashTags (they are not internally indexed yet, only propagated to other instances).

Added support for OpenBSD enhanced security functions unveil() and pledge() (contributed by alderwick).

The purge ttl for stray global objects has been shortened.

In the HTML interface, don't show the collapse widget for non-existent children.

Added support for HTTP signature pseudo-headers (created) and (expires), that are used by some ActivityPub implementations (e.g. Lemmy).

When replying, the mentioned people inherited from the original post will be clearly labelled with a CC: prefix string instead of just being dropped out there like noise like Mastodon and others do. (I hope) this will help you realise that you are involving other people in the conversation.

https://codeberg.org/grunfink/snac2

@grunfink This seems awfully minor, too minor for bug report formalities, but I couldn't help but notice:

"snac 2.18 - A simple, minimalistic ActivityPub instance
Copyright (c) 2022 grunfink - MIT license"

Yet, we are now in 2023 C.E.

@grunfink Hello from the fediverse this time! 👋

Great idea about including a relayd config file for snac in the examples/ folder: I just wanted to let you know I haven't forgotten about it, just that the next few days will be very busy 😊

I also have snac working with both unveil and pledge, with a WIP commit at https://codeberg.org/alderwick/snac2/commit/a33686992747f6cbd35420d23ff22717938b6228 . I'm not happy with the extra complexity to send an email, but after asking around at https://merveilles.town/@alderwick/109548339343453576 it's unavoidable without “unveil("/bin/sh","x");”.

I'm happy to announce version 2.17 of snac, the simple, minimalistic ActivityPub instance server. This time is mostly bugfixes:

Fixed a header bug (contributed by alderwick).

Fixed a bug in the Boost by URL option when the URL of the boosted message is not the canonical id for the message (e.g. Mastodon's host/@user/NNN vs. host/users/user/statuses/NNN).

Fixed crash on a corner case regarding failed webfinger requests.

Usage tips: Don't reply to morons, MUTE them. Try to spend less time on social networks. Go for a walk. Read a book. Watch a movie.

https://codeberg.org/grunfink/snac2

Mastodon + Motif = mastif! 😎​
Experimenting with Xm, Xt, X11, libcurl, libjson-c on IRIX.

Projects that need taggable accounts on the fediverse that align with their name:
#Friendica, #GoToSocial, #snac, #Seppo, #Fedilab and #Metatext

When someone asks about options for servers or clients I have a habit of tagging recommendations, and when there is not an account for the thing, I have to stop and search for a dev or find a website address to link to etc.

I'm proud to announce version 2.16 of snac, the simple, minimalistic ActivityPub instance server, featuring:

Some outgoing connection tweaks: the protocol is no longer forced to be HTTP/1.1 and timeouts are less restrictive. This has proven useful for some unreachable instances.

Conversations can be collapsed.

Added support for edited posts on input. These updated messages will be marked by two dates (creation and last update).

Some tweaks to the docker configuration to generate a smaller image (contributed by ogarcia).

https://codeberg.org/grunfink/snac2

Just noticed that @grunfink's #SNAC (https://codeberg.org/grunfink/snac2, Social Networks Are Crap, a simple, #minimalistic #ActivityPub instance written in #C → #Fediverse) is now available in #Debian Experimental: https://tracker.debian.org/pkg/snac2

Never heard of it before, but having a Mastodon-compatible instance packaged in Debian is great. So maybe time for my own instance? 😁 Will at least toy around with it. The question is on which host. But I suspect my Raspberry Pi running Debian Unstable will do. 😎

@grunfink@comam.es
Thank you for the snac

I've just released version 2.15 of snac, the simple, minimalistic ActivityPub instance server. This time is mostly bugfixes:

Fixed bug in message posting that may result in 400 Bad Request errors (contributed by tobyjaffey).

Fixed crash and a deletion error in the unfollow code.

Added configuration files and examples for running snac with docker (contributed by tobyjaffey).

Serve /robots.txt (contributed by kensanata).

Use the Fediverse sparingly and wisely.

https://codeberg.org/grunfink/snac2

Here's an interesting part of the img help at MDN:

lazy
Defers loading the image until it reaches a calculated distance from the viewport, as defined by the browser. The intent is to avoid the network and storage bandwidth needed to handle the image until it's reasonably certain that it will be needed. This generally improves the performance of the content in most typical use cases.
Note: Loading is only deferred when JavaScript is enabled. This is an anti-tracking measure, because if a user agent supported lazy loading when scripting is disabled, it would still be possible for a site to track a user's approximate scroll position throughout a session, by strategically placing images in a page's markup such that a server can track how many images are requested and when.

So, as strange as it might sound, even if the site doesn't use JavaScript, it makes a different if you have it available? Wow. And how does the browser know if JavaScript is disabled by NoScript and uBlock Origin and the like? Does the browser test itself?

The web browser is a battleground.

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img

Test post from SNAC2 https://codeberg.org/grunfink/snac2
Tiny ActivityPub instance in C, by @grunfink@comam.es

@alex

hello I am just curious about your server. Never heard about #snac

I'm proud to announce version 2.14 of snac, the simple, minimalistic ActivityPub instance server, that include the following new features and fixes:

Previous posts in the public and private timelines can be reached by a "More..." post at the end (contributed by kensanata).

Clicking the 'Like' and 'Boost' buttons don't move the full conversation up; after that, the page is reloaded to a more precise position. Still not perfect, but on the way.

New command-line operation, resetpwd, to reset a user's password to a new, random one.

Added a user setup option to toggle if sensitive content is shown or not by default (contributed by kensanata).

All images are loaded in lazy mode for a snappier feel (contributed by kensanata).

Fixed crash in the data storage upgrade process when debug level >= 2 (contributed by kensanata).

Log message improvements for excelence (contributed by kensanata).

The logging of "new 'Delete'..." messages has been moved to debug level 1, because I'm fed up of seeing my logs swamped with needless cruft.

Don't show the 'Boost' button for private messages.

Added (partial) support for /.well-known/nodeinfo site information. This is not mandatory at all, but if you want to serve it, remember that you need to proxy this address from your web server to the snac server.

Some internal structure improvements.

https://codeberg.org/grunfink/snac2