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

Added a new user option to disable automatic follow confirmations (follow requests must be manually approved from the people page).

The search box also searches for accounts (via webfinger).

New command-line action import_list, to import a Mastodon list in CSV format (so that Mastodon Follow Packs can be directly used).

New command-line action import_block_list, to import a Mastodon list of accounts to be blocked in CSV format.

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

If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/

#snacAnnounces

Follow

@grunfink

Did you see this PR?

codeberg.org/grunfink/snac2/pu

On top of that I'm also trying to hack a CGI+Crontab version of snac, but it's not ready yet.

@Shamar @grunfink A cgi+crontab-version would be very interesting to have in some environments. Especially with a Fossil style script configuration fossil-scm.org/home/doc/trunk/

Sorry, I overlooked it.

Please, also create a text file in the examples/ directory with your description in the first comment on how to compile snac with musl (for other people to know how to do it without resourcing to the repository), and I'll merge it.

On top of that I'm also trying to hack a CGI+Crontab version of snac, but it's not ready yet.

I think this is very hard to do, but I'll take a look at your proposal when it's ready.

Thanks.

@grunfink

Nop, I'll add an example in the following days... :-)

As for the CGI+Crontab version, actually it's not that hard to hack something together with minimal changes to existing code and few new source files, but I'm facing a couple of issues that suggests a proper fork:

1. the CGI ends up being larger than 6Mb because of curl & openssl that, as far as I can tell, are not needed because all the CGI has to do is to save the proper queue item on the filesystem
2. no command handle the global queue alone

The second issue is quite easy to solve with minimal changes and could help everybody.

The first however requires a lot of careful reorganization of the code.

On the other hand, I don't like the idea of a fork diverging too much, first because you are doing a great work here so much I think deserves much more visibility.

And yet, technically speaking, a fork would make much sense to keep both code bases clean and focused to their use case.

Well, OpenSSL isn't needed I can confirm that snac is quite happy building with LibreSSL. ;)

But, I think a TLS library of some sort may still be real dependency?

CC: @grunfink@comam.es
Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.