Just added over 140 new i18n strings to Loops for the Starter Kits feature!
Translators wanted! (Please share)
Starter Kits are amazing and much needed.
But what happens when a majority of them are created on bigger Loops servers?
Does that mean smaller Loops servers miss out?
Nope! Not at all.
See, I built an Observatory service that will allow any Loops (or other software) instance to consume known/discoverable kits and import them automatically.
Shipping Soon! π₯
The Observatory has been deployed!
Preparing Loops Starter Kits for launch π
The Loops Observatory aka https://beacon.joinloops.org is getting a fresh coat of paint and a few new APIs to power Starter Kit discovery.
Shipping soon!
Before I jump back to Pixelfed dev, I have to wrap up and ship Loops Starter Kits.
The last task is the Starter Kit Observatory, a public service that powers Loops Starter Kit discovery across servers, including deletions.
This will allow Loops servers to share and consume Starter Kits across our network, so everyone can explore and use them!
Bigger servers shouldn't have all the fun π
How does Loops Starter Kits prevent abuse?
You can only add accounts that support a new actor field, and if supported, approval with public attestation is required before they can be publicly included.
Basically, you have to get permission first, publicly.
Accounts from software that doesn't support the new actor field will not appear in search results when adding accounts.
There are 80+ new and updated files that power the new #Loops Starter Kits feature!
From exploration to curation, I've built a highly polished experience that is open, accessible and federated.
Admins will love the powerful management, that also includes audit logs.
Can't wait to ship this later this week!
Starter Kit Federation is ready π
This will be compatible with Mastodon Feature Collections.
Shipping soon!
cc @dave