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.
Link and resource verification is (IMHO) an important part in the #Fediverse - especially when everyone can create and use the same name on any other federated instance to fake your profile. Therefore, I really want to see this also in #snac / #snac2.
We could use the same approach like #Mastodon, fetch the resource added by the user, write the date in a file and use this for the validated_at field of the resource. @grunfink - do you have already any plans? Maybe I can provide a PR…
Btw: what about the follower/followed by counter on the mastodon API - I heard this is intentionally not provided?
This morning I installed and briefly tested an ipv6 only snac2 instance.
As expected, everything works perfectly - of course it just federates with ipv6-enabled instances.
snac2 has reached version 2.44, which is stable and undoubtedly suitable for more comprehensive use.
In the coming days, I'll likely declare this instance as stable and include it in BSD Cafe's services. Plurality and choice are fundamental in a free world.
Back to the VM.
From yesterday's commits, I noticed good performance even on Raspberry PI, but now that it's back on the VM, the performance is incredibly excellent!
Ok, I've activated a nginx cache for both posts (/p/) and static (media) files (/s/) and the (/p/) should cache in a different way, considering the type of request (web or json).
I'm testing it now, then I'll try to modify the message to see what happens.
The number of instances based on #snac2 has been on the rise in recent days.
When looking at the statistics, it appears that the (still in testing) instance of BSD Cafe is currently the most populous.
Can I proudly say we're the largest #Fediverse (snac) instance? 😉
Tonight, the snac.bsd.cafe instance will run from here. The Raspberry PI 4's internal SD is in read only, while the disk is ZFS, with #BastilleBSD managing the snac jail.
Tonight, I will leave this instance (snac.bsd.cafe) running on the Raspberry PI 4 in my office cabinet, in order to monitor its performance. When connecting with #Tusky, the performance is excellent, while using the web interface, there is occasionally some slowdown - completely tolerable, considering that there is no JavaScript, etc., and that it is running on a Raspberry PI.
It seems that snac2 is especially efficient at introducing smaller instances. This is because it sends boosts, likes, and posts to all known instances, making it easier to increase the instance's federation level. This may increase the workload, but it also boosts post visibility.