Search results for tag #snac2
![[?]](https://mastodon.gyptazy.com/system/accounts/avatars/113/171/994/681/921/556/original/0e29cf7db7621054.png)
![[?]](https://microhive.social/oliver/s/1488566d18306ce3bbfdc4a9bcfd3501.jpg)
You don't know Snac? But you should: https://codeberg.org/grunfink/snac2
A simple, minimalistic and well documented #ActivityPub instance server written in C, no database needed, totally JavaScript-free, no cookies either, not much bullshit.
![[?]](https://cablespaghetti.dev/fedi/sam/s/avatar-70d122430e7f5ba4f8d1519b1f800a17.jpeg){kind=avatar}
https://cablespaghetti.dev/hosting-a-fediverse-instance-on-an-original-raspberry-pi.html
![[?]](https://snikket.de/social/menel/s/caf51b13f0d292085ff8b177266aae86.jpg)
Well I don't like cloudflare, so we're good I think.
|sort|uniq -c
337 https://furry.engineer/inbox (403 Forbidden) [<!DOCTYPE html><html lang="en-US"><head><title>Just a moment#cloudflare #Snac2 #snac #federation
91 https://gimmeloli.cc/inbox (403 Forbidden) [<!DOCTYPE html><html lang="en-US"><head><title>Just a moment
169 https://pawb.fun/inbox (403 Forbidden) [<!DOCTYPE html><html lang="en-US"><head><title>Just a moment
116 https://pixelfed.social/f/inbox (403 Forbidden) [<!DOCTYPE html><html lang="en-US"><head><title>Just a moment
I'm now wondering if I should compile it with this, and what security it adds additionally to a systemd service file with all the restrictions about the filesystem and syscalls one can do.
Do I need to configure anything with landlock to "activate" it when I compile it in? I didn't yet find the right documentation that I can understand for it it seems.
Does snac somehow "know" what to landlock and which paths to allow before landlocking itself, maybe reading my config file before that happens?
#snac #snac2 (never know which tag to use here :) ) #landlock #linux #kernel #security #selfhosting
Danke! Ich nutze #Snac2 als ActivityPub Instance, nicht Mastodon. Manchmal mit Webclient, manchmal mit Mona, es könnte auch durchaus sein dass der Link wegen irgendwas anderem nicht aufglöst wird. Ist für mich nicht so wichtig, der Link an sich reicht ja.
My relay instance for the #Fediverse evolved in a great way - more than 120 instances are already connected to boost your posts across the Fediverse.
If you're running #snac / #snac2, #Mastodon, #Pleroma or any other software on the #ActivityPub protocol that supports relay instances - feel free to join the relay! Hopefully #GoToSocial also supports relay services soon! Of course #IPv6 is supported (for IPV6 only instances).
https://fedi-relay.gyptazy.com
#opensource #relay #ipv6 #community #homelab
Alt...
Screenshot of the overview page of fedi-relay.gyptazy.com showing more than 120 connected instances for a federated network within the Fediverse.
![[?]](https://go.lema.org/santi/s/avatar-536f178e6196085844d061ba802ca1a0.jpg){kind=avatar}
Is that a #snac2 thing ? @grunfink@comam.es
#snac #snac2
Needs some tags.
And this isn't visible so nobody that doesn't get it right at activitypub can see it.
I fear even the tags won't help for that. Let's see...
![[?]](https://wirebug.ch/beni/s/fb5c81ed3a220004b71069645f112867.png)
@vinishor maybe you want to use https://fedi-relay.gyptazy.com to extend your visibility to other tech related instances :)
Already an idea about the fedi solution? Can recommend #snac2 which is simple and lightweight in our ideas of lightweight solution from BSD aspects.
The #Fediverse is growing and we're welcoming more and more new single user instances but #federation can become challenging.
With #Relay instances, single user and smaller instances can quickly become federated and grow which is supported by many Fediverse applications like #snac #snac2 #Mastodon #Pleroma etc.
More information at:
https://fedi-relay.gyptazy.com
#fedi #community #fediworld #federated #opensource #fedirelay
You might be interested in
https://it-notes.dragas.net/2025/01/29/improving-snac-performance-with-nginx-proxy-cache/
Seems this solves the 499 ngnix issue.
A bit caching if big payloads.
![[?]](https://media.bsd.cafe/bsdmmedia01/accounts/avatars/110/740/169/477/916/693/original/dfa8f1b9beefa405.png)
I've performed some tests, and it's great. #snac and #haproxy are working great together - now with caching of media and json responses, to scale up, and up, and up...and up!
#Varnish is the best tool for caching, but the setup I've tested doesn't require it and it's still good enough.
I think this will be a blog post, as soon as I'll have enough time.
Yes, panphy is maxed out at exactly 40 messages.
I've opend bug reports for that on both projects but I guess as long as no dev used these both Software, there won't be much development in that direction.
I'm using fedilab basically. It works with that...
I already wrote about caching here
Now I extended what I cache a bit.
This was because after enabling Option to proxy media I've seen access to the file paths /x/ and /y/ in addition to the path were snac stores the media that I include in my own posts ( /s/ ).
There are two locations to proxy media, depending if you requests the media via the mastodonapi or via the web. (/x/ and /y/), oh and I added the nodeinfo2 path too, because I've noticed it was queried all the time by a lot of instances and it gives me pleasure to see something cached handed out in the access logs 🙂 (I guess it is actaully irrelevant for the system resources).
This is the updated setup:
Enable the relevant modules:
a2enmod expires cache cache_disk
Be sure "htcacheclean" is running to clean up old disk cache. (under debian see /etc/default/apache-htcacheclean or else the relevant systemd service or whatever)
Then add to the snac Virtualhost config:
<LocationMatch "^/social/[^/]+/[xys]/|^/social/nodeinfo_2_0">This will use the disk cache to cache everything under the /s/, /x/ and /y/ Path, as well as for /$username/nodeinfo20, utilizing the mod_expires to generate the appropriate cache headers (for lazy ones like me), In this case caching it for 1 day.
CacheEnable disk
Header set Cache-Control "max-age=86400, public" "expr=%{REQUEST_STATUS} == 200"
ExpiresActive On
ExpiresDefault "access plus 86400 seconds"
</LocationMatch>
Further reading and all options explained under https://httpd.apache.org/docs/2.4/caching.html (and ff)
The Header that I set here, on the condition of Status code 200, is needed for the path /y/, because snac defaults to set no-cache on that location and the modexpires will honor that if we don't override it. I set it to the same Cache-Control value as modexpores woud. (mod_expires will additionally calculate the date and put that in the expiresheader. (hence the name I guess 😀 )
#Fediverse #Hosting #ITNotes #apache2 #httpd #Ownyourdata #Server #Snac #Snac2 #Tipsandtricks #Tutorial #Debian #caching
![[?]](https://files.mastodon.social/accounts/avatars/109/259/207/144/483/733/original/47ad35da5e393b00.png)
Just published a guide on setting up Snac on an Ubuntu VM using NGINX Proxy Manager. Snac is an incredibly lightweight #ActivityPub server. A true nom nom among fediverse platforms.
If you're curious about minimal fediverse instances, check it out:
#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/
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
