microhive.social 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.
Non "più utili alla crescita" bensì "più probabili nei sistemi in crescita".
Un altro buon esempio è costituito dai tumori, le cui cellule mutano in modo imprevedibile: il tumore cresce più rapidamente del tessuto ospitante perché svincolato dall'ordine impresso nel DNA originale.
Nota che la crescita di cui parlo non è necessariamente positiva: l'impero romano all'apice della sua estensione era talmente fragile da finire in pezzi sotto la pressione di "barbari"; i sistemi unix hanno raggiunto complessità insostenibili che causano inevitabili vulnerabilità etc...
Allo stesso modo una dimensione ridotta può essere positiva: io per esempio ti sto scrivendo tramite #snac2, un nodo #ActivityPub scritto in C, piccolo ed efficiente.
The only difference is informing other parties about the delete if it was written by me, or am I overlooking something?
Edit: I asking because I'm thinking maybe one of the buttons could go away to make room, or change its behavior. Like "hide" could be instead "mute" to only not inform anymore on the conversation, but don't delete it (like mastodon does)
#snac #snac2
It seems both options delete the post from my view. I only don't know whats the difference beside that.
I think you should ask @grunfink@comam.es but given the syscalls' documentation, my guess is that #snac2 simply reserve access to the snac-data/ dir and lock it out of anything else (unless you disable_sandbox in the server config).
|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
#snac #snac2 (never know which tag to use here :) ) #landlock #linux #kernel #security #selfhosting
To be honest, xs (and xs_json too) is infact what I liked most of #snac2 codebase: a non-conventional approach optimized for the specific use case.
Having said that, it looks trivial to modify _xs_json_load_lexer, xs_number_new, xs_number_get, xs_number_str to store/retrieve the double
as a null terminated char[sizeof(double)+1]
.
I just wonder if it's worth the performance gain, tbh.
@lizzy@social.vlhl.dev @ada@zoner.work @kimapr@ublog.kimapr.net
in fact it doesn't cause any issue: #snac2 is likely the lightest and best performing #fediverse server out there.
@rozenglass@fedi.dreamscape.link @lizzy@social.vlhl.dev @ada@zoner.work
well, strictly speaking, a FTP access to the web server could be enough: just mount the folder with sshfs and run snac over it, as I did when I installed my own instance on a cheap shared hosting.
Obviously, if you have shell access to the server it's much simpler.
I have a question though: how you delete a user from #snac2? I mean, I read how to add users in the Administration manual, but I can't find how to delete a user (and if it can be done while running the server).
Is removing the user folder all you need to do? What about the account they were following? I guess they are not going to be unsubscribed that way...
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.