linuxusers.in 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.
https://github.com/macports/macports-ports/pull/27816
3 out of 3 GitHub Continuous Integration checks passed already! (I guess whatever was slowing down that third one got resolved somehow?)
Thanks to you and inz for the continued improvements!
It's up to someone else with commit access to merge it.
#snac #MacPorts #OpenSource #ActivityPub #Mastodon #NoDatabaseNeeded
#NoJavaScript #NoCookiesEither #NotMuchBullShit #snacAnnounces
Added support for customizing and translating the web UI language via simple .po
files. For more information on how to install language files or create new ones, please see snac(8)
(the administrator manual).
New user support for blocking hashtags from the web UI.
The Content-Security-Policy
HTTP header is now always sent to disable any JavaScript, instead of just being suggested in the documentation.
Image attachments in SVG format are now disabled by default; you can enable them back by setting the enable_svg
value to true
in server.json
.
Several fixes (contributed by inz).
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
So, basically the platform you stopped to use increased the incoming traffic and even makes the half of the "Mastodon" traffic in the last days? Doesn't this show how important this source is and how much potential there still is?
Next, I'm wondering why "Mastodon" is defined as "Mastodon". #Mastodon is one of multiple solutions in the #Fediverse and I'm more than pretty sure that many people are not using Mastodon, rather than #snac / #snac2, #GoToSocial,... It's like setting "Internet Explorer" as a synonym for browsers.
Basically, all threads work in the same way. There are four states: stopped
, waiting
, input
or output
. It's almost impossible to see the first one, as it's only set while initializing or shutting down; input
is also seen rarely, unless the instance posting the data is specially slow. So they are usually waiting
except while in the «send storm», when they are mostly in output
mode. Anyway, even in this case, an incoming message has preference over everything, and the first available thread will serve it.
#snac sets up as many threads as cores are available, but being that the thread work is basically network I/O bound (there is very few CPU work to be done), you can increase the number of threads to twice or more the number of cores and performance will be slightly improved.
Interesting photo!
It gives a daily report of those asteroids with a reasonable probability of crashing into Earth, in case you are not already afraid enough of the future. Of course, using #snac, what else.
It takes its data from a very cool NASA site, so (again) in these days of uncertanty, I'm not sure how long will it work.
Everyone, take care, and have a great week.
https://github.com/macports/macports-ports/pull/27628
1 of 3 GitHub Continuous Integration checks has passed (which is a good sign the other two will pass as well).
I'm still avoiding commit access, so it's up to someone else to merge it.
Thanks to you, inz, lxo and anyone else I may have missed for the continued iterated improvements!
#snac #MacPorts #OpenSource #ActivityPub #Mastodon #NoDatabaseNeeded
#NoJavaScript #NoCookiesEither #NotMuchBullShit #snacAnnounces #FediVerse
Each post can have more than one attachment from the web UI. The maximum number can be configured in server.json
via the max_attachments
value (default: 4).
Each notification includes a link labelled Context
, that leads to a page with the full conversation tree the post is a part of.
Each followed hashtag has now a directly accesible link.
Fixed a search bug (some matches were missed).
Fixed more crashes (contributed by inz).
Fixed link detection in posts (contributed by inz).
Allow multiple editors for command-line posts (contributed by inz).
Separated maximum and default timeline entry count, allowing larger timelines to be requested without having to increase the default (contributed by lxo).
Turned message date into a link to the local post, so that it can be loaded into a separate tab for interacting with (contributed by lxo).
Special thanks to fellow developer inz for bringing my attention to code places where I should have been more careful.
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
This release has been inspired by the song Songe d'un ange by #KyrieKristmanson and #BrendanPerry.
The #Fediverse is free, free of censorship, federated and full of great content!
Also the Fediverse - instance admins randomly blocking whole instances just because a single user feels offended of a post by a single instance user. Blocking whole instances is just a finger snip away, censoring unwanted content and parenting users of instances. Defederating just because of… ok no clue :) Using content warner for any possible content just to annoy or aeemmm make it more interesting to other users. Thanks, I’m old enough :) Seeing all the spam because it’s just a thing of 5 minutes automation to create randomly new instances on different domains (or subdomains from dynamic-ip hosters) and to fill the network with automated content.
Sometimes, pros can easily switch into cons… luckily more and more single user instances are raising up for exactly this reasons and can still easily federate by using relays…
#networking #activitypub #mastodon #fediverse #gotosocial #snac #snac2 #opensource #community #socialmedia #relay #abuse #moderation
https://github.com/macports/macports-ports/pull/27571
GitHub Continuous Integration checks are running, hopefully without issues? If so, then it will be up to someone else with commit access to merge it.
Thanks for your (and inz's) continued improvements to snac!
#snac #MacPorts #OpenSource #ActivityPub #Mastodon #NoDatabaseNeeded
#NoJavaScript #NoCookiesEither #NotMuchBullShit #snacAnnounces #snacizens
Fixed memory leak (contributed by inz).
Fixed crash.
If you find #snac useful, please consider contributing via LiberaPay: https://liberapay.com/grunfink/
I submitted a Pull Request to update MacPorts' snac to 2.70 here:
https://github.com/macports/macports-ports/pull/27556
1 of 3 GitHub Continuous Integration checks has passed (which is a good sign the other two will as well, eventually).
It's up to someone else with commit access to merge it.
#snac #MacPorts #OpenSource #ActivityPub #Mastodon #NoDatabaseNeeded
#NoJavaScript #NoCookiesEither #NotMuchBullShit #snacAnnounces #snacizens
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.
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/
Improving snac Performance with Nginx Proxy Cache
https://it-notes.dragas.net/2025/01/29/improving-snac-performance-with-nginx-proxy-cache/
#Data #Fediverse #FreeBSD #Hosting #ITNotes #Networking #Nginx #NoteHUB #OwnYourData #Server #Snac #Snac2 #Social #TipsAndTricks #Tutorial #Web
@gumnos no, of course it won't. This is the beauty – and the downside – of open source and self-hosting communities: people eventually start with self-hosting, especially when it’s possible to do so with valid and lightweight tools like #snac. In a way, snac is one of the reasons for the loss of users from the BSD Cafe instance 😆
But, jokes aside, the BSD Cafe is not a server – it’s a community. Going self-hosted with solutions like snac (as @justine did too) means you’re still part of the BSD Cafe, and in fact, it's a success because the spirit of the BSD Cafe is exactly this.
In short, you can bring your own coffee ready, but the table and the welcome are always there. 🙂
CC: @grunfink
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 :)
#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/
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.
Publishing a photo of approximately 4MB from my snac instance (at home with 20 Mbit/sec uplink) meant overwhelming everything.
This happened because, for every remote instance, Nginx was requesting the multimedia file from snac. However, due to saturated connections, it took several seconds, leading to thread exhaustion in snac.
I resolved this issue by caching the multimedia files myself using Nginx, which significantly improved performance.
This matter will be covered in a subsequent (simple) blog post.