Well, that was fun - thought I'd do a little filesystem cleansing and ended up accidentally (I did not check my work, tut tut tut) removed fedi VM ( I thought it was on a different disk, whoops!) - joy!
#Backups are available of course and restoring now. #Snac2 being the easiest to restore so that's back online first! I've lost today, but that's OK I've been pretty quiet!
tapi memang benar, kalo hanya sekedar host app seperti #snac2 atau #GotoSocial saja maka pakai VPS spek tinggi dan host di luar negeri itu terlalu berlebihan.
Aye pastikan pakai Vultr dalam 3 bulan ini dengan 1C 1Gb RAM dan 25 Gb SSD ternyata lebih daripada cukup. Pemakaian CPU lebih sering idle daripada kerjanya (baru kerja max kalo dipakai compress data untuk dibackup) dan Mem hanya kepakai 300 - 400 Mb saja dengan 1 load balancer, 3 http server, 2 app fediverse.
Instance juga tak terlalu ramai dengan pemakaian bandwidth sebesar 8Gb saja perbulannya, bahkan SSD tak kunjung penuh meski storage media sudah dilokalkan.
dengan segala keterbatasannya lebih suka pakai #snac2 versi web, entah kenapa pakai aplikasi pihak ketiga itu sering banget error dan atau banyak fitur tak bisa bekerja sebagai mana mestinya.
Enafore/Semaphore yang paling lumayan. Feditext tak bisa render boost properly, sedangkan Phanpy selalu menyatakan ada notifikasi setiap beberapa detik.
Here at Emacs.ch we run an experimental side instance [1] based on Snac2 [2], which is a Mastodon-compatible Fediverse server written in C, runs completly file-based and features a zero-JS UI.
It doesn't have many of the fancy features of Mastodon, but is a bright example of how a super-minimal system can do the job very well. It'll also work with your mobile Mastodon apps and small browsers like Dillo[3].
It runs on OpenBSD and we accept a few more testers. There is no automatic sign-up, so if you are interested, DM me with the desired account name and I'll send you the credentials.
So, I've setup a Snac2 instance, which is a very minimalistic Mastodon-compatible fediverse server written in C, running on OpenBSD. It runs completely filesystem-based, Web UI is free of JavaScript and can be used with mobile Mastodon clients. If anyone is interested in a test account, lmk.
Which may be a feature as far as most GTS and Snac users are concerned!
But I do want Threads to technically be able to federate with most/all other software that uses #ActivityPub, so it can be user/admin choice whether to accept connections from the giant instance...and more importantly, to cut down on the risks of vendor lock-in and EEE.
And I hope more compatible systems will cut down on the "OK, my software federates with itself and Mastodon, I'm done" problem. In some cases there may be bugs on the smaller project's side, and fixing them might also fix issues talking to other small projects.
If Facebook had an issue tracker for threads, someone could open an issue there. If threads was an open source project, we could look at the code and immediately know what's up, but... 🤷
Dear friends of #BSDCafe and the #Fediverse,
since December 2023, snac.bsd.cafe has been operational, initially in an experimental phase but has proven to be stable and reliable.
Thus, Snac2 is now available as a service of BSD Cafe. It is considered one of the best and most comprehensive "lightweight" implementations of #ActivityPub, offering one of the best ways to interact with the Fediverse without the need for the extensive dependencies and components of Mastodon.
It is now possible to request an account on the snac2 instance of BSD Cafe. There isn't an automatic sign-up process (snac2 does not provide one, as it wasn't designed to create large communities).
Dear friends of #BSDCafe and the #Fediverse,
since December 2023, snac.bsd.cafe has been operational, initially in an experimental phase but has proven to be stable and reliable.
Thus, Snac2 is now available as a service of BSD Cafe. It is considered one of the best and most comprehensive "lightweight" implementations of #ActivityPub, offering one of the best ways to interact with the Fediverse without the need for the extensive dependencies and components of Mastodon.
It is now possible to request an account on the snac2 instance of BSD Cafe. There isn't an automatic sign-up process (snac2 does not provide one, as it wasn't designed to create large communities).
https://fedidb.org/software/snac
Wait a second, #SNAC2 only has a total user count of 128?
I feel like, given the quality of the software, that number should be way higher
I want to publicly thank @grunfink for creating the amazing snac2, which powers my instance.
They've read everything I noted, suggested changes, and adapted the code to make it work optimally even on my slow VM. If all open source developers were as kind and helpful as they have been with me, the world would be an idyllic place.
A shoutout to @stefano too - using snac2 was his idea, and he's responsible for the technical implementation of the instance.
And thanks to everyone who makes my timeline interesting and complete - without you, all of this would be utterly pointless.
@stefano I think #Snac2 has dns issue or some issue regarding notifications , because every single time I open my Tusky app I get the same notifications over and over again. So weird.
For those, like me, who want their own space here and prefer self-hosting, I suggest considering snac2. I'm having a great experience with it, and it's easy to install and configure.
I've just released version 2.45 of #snac, the simple, minimalistic #ActivityPub instance server written in C. This one includes fixes to some nasty bugs and some interesting contributions:
Fixed a collision in webfinger caching. This may affect federation with some software, so I recommend an upgrade.
Fixed crashes in some command-line options.
New command-line option state, that dumps some information about the running server and the state of each thread (note: this feature uses shared memory blocks and you may need an argument to the make call in older Linux distributions; please see the README file for details).
Fixed a bug that may leave an inconsistent state for a followed actor in a special case of repeated messages.
Mastodon API: added some fixes for integration with the Mona iOS app (contributed by jamesoff).
Added support for ntfy notifications, both using a self-hosted server or the official ntfy.sh (contributed by Stefano Marinelli).
Ok, I’ve setup my own #snac2 instance. But I can't follow users from other instances with msg „cannot resolve user dziq@mammuthus.xyz to follow”. @stesnac do you have any suggestions?
@smallcircles@tobyjaffey@ben Although I will switch to something like #snac2 in the near future, since the nomenclature Honk invented is just ... bizarre.
Yesterday, while adding support for #ntfy, I introduced a small bug that causes duplicate notifications on #snac2. My fault 🙂 I've already sent the PR with the fix to the developer.
Evening thoughts: Since I started talking about #snac2, some BSD Cafe users have set up their own instances and begun using them.
Maybe I shouldn't have mentioned it.
@stefano Pretty raw BUT this is the first time a microblogging platform makes it simple to see the thread.
Sure it is just a css/html thing but back before the twitter debacle, you had to click on the date/time element which was one of the wrongest UX choice that mastodon did at the time.
Today, yes, you just click on the card to access the thread.
anyway, i could envision #snac2 for my one man instance.