doasu.dev 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.
snac is rather awesome software. It's lightweight, exceedingly fast and just works.
Thanks @grunfink@comam.es (and other contributors to the project).
Boosting your post, just in case anyone out there knows something.
It is my 3rd month of running #snac #snac2 instance. I wanted to share a few words about how awesome this software is.
Few points that make snac icredibly good for my usecase are:
After 3 month of posting (2 active users and 3 semi active users) my data dir is ~500MB and memory usage is ~200MB
it means i can keep running it on my infrastructure without even thinking too much about load
@grunfink@comam.es thanks for such a awesome piece of software 🩷🩷🩷
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.
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
Changed default: for newly created instances, disable_inbox_collection is set to true (see snac(8) for more information). The reason is because it seems to be used for harrasing people.
Changed default: for newly created instances, disable_history is set to true (see snac(8) for more information). The reason is because archived history files don't reflect reality after posts are deleted or modified (they always have been an ugly kludge).
Changed default: in previous versions, posts with a scope of unlisted were shown in public pages and RSS feeds. Now, they are no longer shown. If you want to get back to previous behaviour, use a new toggle in the User Settings section (see snac(1) for more information).
New admin configuration option: if the purge_static value is set to true in server.json, each user's static directory is explored and those files there that are no longer attached to any post or referenced anywhere are deleted. See snac(8) for more information about those cases where you may not want to enable this option.
Allow serving files from subdirectories of the static/ subdirectory (contributed by la_ninpre).
Minor tweak to webfinger code to handle Hubzilla's peculiarities.
Fixed a search case where URLs to GotoSocial statuses were misidentified as accounts.
Accounts that follow you are now marked with a thumb-up emoji, because followers are adorable people.
Fixed some account export errors.
Fixed an incorrect hash in post links.
Show an account's location link in the people page, if they have one.
Mastodon API: Fixed hashtags loosing the link after editing a post, minor tweak in access token processing (contributed by trondd555).
Drop usage of PATH_MAX (contributed by sergiodj).
New Polish translation (contributed by kpm).
Updated German and Czech translations (contributed by zen and pmjv).
If you find #snac useful, please consider buying grunfink a coffee or contributing via LiberaPay.
unfortunately, afaik you don't get push notifs via the masto api, so you either have to poll, or get them via ntfy.sh/telegram/email
Given #snac's low bar requirements, I think any modern web browser is fine. I use Firefox, but totally agree on the heavy side (I have an unresolved love+hate relation with Firefox). I don't recommend any Chrome-based solution, because Google (though snac works great there).
I wish a small web browser (even a text-mode one!) with support for summary / details existed. In fact, if I ever develop another web app (a case that is probably not going to happen), I would not rely on this functionality.
summary and details tags (which #snac relies very much on), I would recommend it as the best web browser for a snac experience.CC: @gumnos@bsd.cafe