voidq.xyz 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.
Boosting your post, just in case anyone out there knows something.
plzclap
< like this >
I've been on the fence about hosting my own #fediverse account for a while now, mainly because of the insane hardware requirements.
I've considered pleroma/akkoma for a while, but i don't know the first thing about elixir and their docs are not the most clear. I've been really tempted by #GoToSocial, but #snac's easy install & general simplicity made me take the plunge.
ps -ww -p 88163 -u | awk '{for (i=1; i<=NF; i++) a[i,NR]=$i} END {for (i=1; i<=NF; i++) { val=a[i,2]; if(a[i,1]=="VSZ" || a[i,1]=="RSS") { val=sprintf("%.2f MB", val/1024) } print a[i,1] ":\t" val }}'
USER: snacIt only lacks auto-complete of handles and tags.
heck, I think I will *eventually* simply migrate to my snac. BSD cafe is best, self hosting is bestest.
@df I love this idea and the software. I'm a great supporter of #snac exactly for the same reason. You don't need beefy hardware to have your own Fediverse home.
Starling is a nice because it can be used without setting up a proper server - just a php installation and a domain.
I'll keep this testing instance on and continue to test it with MastoBlaster.
Also, I think it's important to remember that #snac also allows following hashtags by those RSS feeds provided by several Fediverse implementations (like Mastodon), avoiding the need of subscribing to a relay. E.g., you can add https://mastodon.social/tags/snac to the followed hashtags field, and it will periodically poll that RSS from the big instance and add to your timeline those posts tagged with #snac.
The usual solution is to use an ActivityPub relay. This, however, resulted in receiving looots of posts, hitting file size and inode limits on this small VM. Thus, I gave up this experiment a while ago.
Now, I just stumbled about https://relay.fedi.buzz/ from @astro@c3d2.social, which allows to only follow certain hashtags, which is kinda exactly what I wanted ❤️
After following the Subscribing to Fediverse Relays section from snac(8), I came up with the following jq(1) command to subscribe each hashtag I am already following on my #snac instance. And yes, this would be way faster to do by hand for those six hashtags in total.
$ # Create multiple snac follow commands for each hashtag the "xz"If the generated commands are looking not suspicious enough, rerun the command within
$ # user follows. The "data" directory is the $SNAC_BASEDIR.
$ jq -j \
'.followed_hashtags.[] | "snac follow data relay https://relay.fedi.buzz/tag/",.[1:],"; "' \
< data/user/xz/user.json
snac follow data relay https://relay.fedi.buzz/tag/openbsd; snac follow data relay https://relay.fedi.buzz/tag/snac; [ . . . ]
$() or execute the output manually.Finally, I am able to doomscroll #biketooter for weird and ridiculously expensive bikes from my instance; yay!
But, you can have snac running from a subdirectory of your main domain (which, as far as I know, no other fediverse implementation does). I.e. you can have your snac root in example.com/social and then you can identify as you@example.com . So you have no unnecessary subdomain just to be you.
Which is what I do for this very domain.
CC: @mms@bsd.cafe
660 for many of its data files. It makes it really easy for me to add my main user to my server's snac group, and be able to administer as my normal user without su'ing into the snac user.Addendum: I also just learned about using the setgid bit on a directory. That was used, too. Cool! https://www.gnu.org/software/coreutils/manual/html_node/Directory-Setuid-and-Setgid.html