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.
Hi, #snac author here. As @stefano@bsd.cafe days, it's a common practice in ActivityPub implementations to use retry queues.
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.
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 😆
Hi, #snac author here. Are you following the relay on your own instance? If that is the case, you'll get boosted to your own account all posts that your relay receives.
Your setup is fine; #snac intentionally hides user metrics, because I (personally) consider them a bit toxic, a practice that convers social media into popularity contests.
Anyway, and because some users asked for it, you can share your own metrics to others. It's disabled by default; you can find a toggle in your user settings.
I've experienced that sometimes my instance does not appear in the relay's top page, but posts keep arriving demonstrating the realy is working fine, so maybe that list in not comprehensive.
FWIW, there is a work in progress to change the email notification process from spawning /usr/sbin/sendmail to a direct connection to an SMTP server, so this issue will eventually fix itself.
They/their. Author of the snac ActivityPub instance server and other pieces of singular software. Not a real Grünfink.Git repositories at https://codeberg.org/grunfink