@stefano It's also part of what seems broken over in the Bluesky world: sure, it's "federated", but only if you have a huge investment in infrastructure.
From Bryan Newbold's defense of atproto¹, "Our design goal is not to run the entire network on small instances…This architecture facilitates big-world indices…Such indices are not cheap at scale!"
But I want my federation to be so affordable that anybody can get a domain-name, spin up a $1/month VPS instance², and participate in the fediverse. Things like snac make the completely feasible. So thanks, @grunfink!
@grunfink For what it’s worth I believe the small buffoon & all other middle-sized clowns play a very important role in the battle.
The more I look at it, the more I feel that minimalism & most of all cost effectiveness is a central weapon against corporate control.
They’re making FB & Instagram free on your cell’s 4G while direct human information exchange has to be paid. Any effort at minimalism reduces the gap between access to the voice of billionaires and access to ours.
Added support for subscribing to LitePub (Pleroma-style) Fediverse Relays like e.g. https://fedi-relay.gyptazy.com to improve federation. See snac(8) (the Administrator Manual) for more information on how to use this feature.
Added support for following hashtags. This is only useful if your instance is subscribed to relays (see above).
Added support for a Mastodon-like /authorize_interaction webpoint entry, that allows following, liking and boosting from another account's Mastodon public web interface. To be able to use it, you must reconfigure your https proxy to redirect /authorize_interaction to snac (see snac(8)).
Hashtags that are not explicitly linked in a post's content are shown below it.
Fixed broken NetBSD build (missing dependency in Makefile.NetBSD).
The user profile can now include longitude and latitude data for your current location.
Mastodon API: implemented limit= on notification fetches (contributed by nowster), implemented faster min_id handling (contributed by nowster), obey the quiet public visibility set for posts, other timeline improvements (contributed by nowster).
Reduced RSA key size for new users from 4096 to 2048. This will be friendlier to smaller machines, and everybody else out there is using 2048.
If the SNAC_BASEDIR environment variable is defined and set to the base directory of your installation, you don't have to include the base directory in the command line.
Fixed a bug in the generation of the top page (contributed by an-im-dugud).
Added support for Markdown headers and underlining (contributed by an-im-dugud).
Yes; subscribing your #snac to a relay has two benefits: 1) you reach a big stream of posts where you can "fish" those with the hashtags you like, and 2) your posts are also sent to that stream, so that other relay subscribers can receive them. FediBuzz doesn't provide 2.
On the other hand, the FediBuzz concept has the benefit that you only receive those posts you are interested in and not a firehose of data (most of it probably of no interest for you), which is a huge benefit if you have bandwidth restrictions.
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