Search results for tag #snac
![[?]](https://microhive.social/oliver/s/1488566d18306ce3bbfdc4a9bcfd3501.jpg)
![[?]](https://comam.es/snac/susie.png)
![[?]](https://snac.smithies.me.uk/justine/s/0f243b2dbc73bd550222a1433cf65dec.jpg)
Thank you @grunfink@comam.es ❤️
![[?]](https://s.dodies.lv/normis/s/3606be889ef0947b06d15b5d7abe102f.png)
Fixed memory leak (contributed by inz).
Fixed crash.
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
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.
Meine Snac-Instanz läuft administrativ bei @knt@streams.knthost.com, weil ich keine Ahnung von grundlegenden Servereinstellungen etc. habe, aber durchaus ab und zu ein Shell-Terminal bedienen kann.
Die Jungs bieten derzeit alles out-of-the-box als Betatest an:
https://www.knthost.com/snac2
Absolute Empfehlung. Also beides. K&T und Snac 🙂
https://codeberg.org/grunfink/snac2/
I'm now a huge Snac2 fan! The whole thing here on this domain was once intended as a test, but has now established itself and “taken on a life of its own”. Simply because Snac is super solid and uncomplicated and the developer is a cool guy who listens and thinks along.
My Snac instance runs administratively at @knt@streams.knthost.com, because I have no idea about basic server settings etc., but I can operate a shell terminal from time to time.
The guys are currently offering everything out-of-the-box as a beta test:
https://www.knthost.com/snac2
Absolute recommendation. So both. K&T and Snac 🙂
https://codeberg.org/grunfink/snac2/
Specifically, snac respond differently to 404 and 410 HTTP status messages by not retrying, because they somewhat explicitly say that a resource is no longer available; a 403 status may be a transient error related to RSA keys not being up to date, so it's requeued, and all 5xx (server) messages are also always retried, because they are usually temporarily fallen or overwhelmed servers that deserve another oportunity.
https://it-notes.dragas.net/2025/01/29/improving-snac-performance-with-nginx-proxy-cache/
![[?]](https://mastodon.gyptazy.com/system/accounts/avatars/113/171/994/681/921/556/original/0e29cf7db7621054.png)
#HowTo install & run #snac on #FreeBSD - run your own #ActivityPub instance in the #Fediverse!
In the last days I often got asked about #snac / #snac2 as an alternative to #Mastodon and I can highly recommend it! I few months ago, I already wrote a HowTo about setting snac up on a FreeBSD instance - might be worth to share again :) if you’re using snac, you might also want to use my relay service at https://fedi-relay.gyptazy.com to make your posts more visible in the Fediworld.
#opensource #fediverse #fediworld #alternatives #community #FreeBSD #RUNBSD #BoxyBSD #activitypub #mastodon #relay #community #federated
https://gyptazy.com/install-snac2-on-freebsd-an-activitypub-instance-for-the-fediverse/
Relays in general are already available for a longer time and there’re also many ones available. My relay instance is new - it popped up of an idea when I saw many new #snac instances and someone showed relay links. I wouldn’t have thought that my relay instance would grow that quick, so I’m happy to see this gets appreciated by the community :)
Regarding your first point (saving a thread for later replying or reacting): I use bookmarks for that.
Regarding the page reloading after actions, I'm afraid it's not possible without the use of JavaScript, which is a no/no for this project. The action requires a trip to the server, and a response back with the same (or the most similar) content you were previously shown.
And with regard the mark of "below this line, you've already seen this": it has been on my mind for long time, but due to implementation details, it's trickier than it seems. I will implement it eventually, because it's something that I deeply need 😆
Thanks for taking a chance on #snac.
Anyway, and because some users asked for it, you can share your own metrics to others. It's disabled by default; you can find a toggle in your user settings.
I hope you enjoy snac.
I'm glad you like it, thanks!
Just a few days ago, I lunched my new relay service for the #Fediverse and I'm really happy to see that there're already many ones connected to - more than 50 instances in just a few days!
But what makes me even really happy is to see, that my service [2] also gets linked in the release notes of #snac [1] / #snac2 - and I can recommend the usage of relay services (it doesn't matter which one!) to everyone. It provides more content from connected instances to you, but also brings your posts - from your local instance - up to other ones within the federated network where it can get much easier distributed around other instances.
#snac is the perfect way to host an own fediverse instance. Using the #ActivityPub protocol allows you to connect to all other instances. With the integrated #Mastodon API, you can also use most of your usual clients or web clients. Snac is light, fast, does not require any database and follows the KISS way - which the most of us BSD people are living. With relay services, it's the perfect match for singe-user instances and @grunfink is always open for ideas and to help! It does not always need to be #Mastodon, #GoToSocial etc!
And if you're using any other software, you may still benefit by using relay services. And if you're still looking for a guide, howto setup snac2 on #FreeBSD, my howto [3] might help you out.
[1]: https://codeberg.org/grunfink/snac2
[2]: https://fedi-relay.gyptazy.com
[3]: https://gyptazy.com/install-snac2-on-freebsd-an-activitypub-instance-for-the-fediverse/
#community #opensource #development #coding #c #clang #homelab #hosting #BSD #RUNBSD #Howto
I've previously used #snacizens, but #snacsters also sounds great 🙂
Added support for subscribing to LitePub (Pleroma-style) Fediverse Relays like e.g. https://fedi-relay.gyptazy.com to improve federation. See snac(8) (the Administrator Manual) for more information on how to use this feature.
Added support for following hashtags. This is only useful if your instance is subscribed to relays (see above).
Added support for a Mastodon-like /authorize_interaction webpoint entry, that allows following, liking and boosting from another account's Mastodon public web interface. To be able to use it, you must reconfigure your https proxy to redirect /authorize_interaction to snac (see snac(8)).
Some fixes to accept Event objects properly (like those coming from implementations like https://gancio.org/ or https://mobilizon.fr).
Added some caching for local Actor objects.
Hashtags that are not explicitly linked in a post's content are shown below it.
Fixed broken NetBSD build (missing dependency in Makefile.NetBSD).
The user profile can now include longitude and latitude data for your current location.
Mastodon API: implemented limit= on notification fetches (contributed by nowster), implemented faster min_id handling (contributed by nowster), obey the quiet public visibility set for posts, other timeline improvements (contributed by nowster).
Reduced RSA key size for new users from 4096 to 2048. This will be friendlier to smaller machines, and everybody else out there is using 2048.
If the SNAC_BASEDIR environment variable is defined and set to the base directory of your installation, you don't have to include the base directory in the command line.
Fixed a bug in the generation of the top page (contributed by an-im-dugud).
Added support for Markdown headers and underlining (contributed by an-im-dugud).
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
This release has been inspired by the song Nine Hundred Miles by #BarbaraDane.
On the other hand, the FediBuzz concept has the benefit that you only receive those posts you are interested in and not a firehose of data (most of it probably of no interest for you), which is a huge benefit if you have bandwidth restrictions.
I'll give it a day and see if this changes over time. 🤔
I've followed the #FreeBSD hashtag for now and will see what happens. One thing that does come to mind is that you now have a user called relay that doesn't actually seem to do much other than follow the actors ????
Do I now have to follow my relay or is this something that the snac server takes care of ???
Also is it a good idea or can the relay user follow multiple relay actors ??
greeting.html page. Started thinking I'd messed up my nginx reverse proxy config somehow but couldn't see anything wrong. So decided to bypass the reverse proxy and use curl on my snac instance to prove that it was snac that was the issue. Anyway reported and a fix has been found by another snac user which I tested and @grunfink@comam.es pushed an update.Proof that reporting issues and testing with the devs does indeed help.
The now closed issue is below.